A complete model of a working warehouse. Watch it take on three real jobs as you scroll.
Isolate, drain and remove TK‑07, then set and connect the replacement unit in the same bund position.
In through D2, down the main aisle, east at the junction, and into Zone B from the north side.
Racking aisle closed for 40 minutes. No work under the pipe bridge while the unit passes. Move runs outside picking hours.
Book TK‑04’s inspection now. Schedule surface treatment for TK‑02 before winter. Keep TK‑05 on the watch list.
Ask in plain language. Review what comes back. The same understanding of your site backs every job.
I asked our production facility a question yesterday. It answered.
Bike Club plans its 25,000 sq ft Rainham site from Berlin: layouts explored through conversation, capacity modelled against the building as it is, and reports prepared in minutes, with a person reviewing every output.
If your team produces it from a site, Plenex can prepare it.
Time to produce a risk assessment and method statement went from a working week to eight minutes in a single deployment with one of the world’s largest privately held manufacturers. Every draft is reviewed by people before use.
Every report starts from the current state of your environment, not a blank template. What is there, what condition it is in, and what has changed.
Each finding links to the exact place it came from. Reviewers open that location in 3D and see it for themselves before signing off.
Upload your internal policies once and drafts reference them directly, so the output reflects how your organisation actually works.
Anything practical about a site: what is there, what condition it is in, what has changed, whether something fits, what risks to consider before work. You can tag a specific asset in the conversation to ask about exactly that.
Teams use Plenex to prepare RAMS (risk assessments and method statements), condition reports, health and safety assessments, contractor and insurance surveys, and maintenance and inspection reports. The same understanding of the site backs each one.
Yes. Upload your policies to the policy library and reports reference them, so the output reflects your controls and requirements.
Yes. Multiple people work in the same scenes and reports, with comments, teammate mentions and sharing. You can select any report text and use Ask Plenex to dig further.
Every finding links to the physical context it came from, so a reviewer can open the exact location in 3D and see the evidence for themselves. Reports are drafts for your team to review and sign off; they do not go out on their own.
Very little from your side. We set your site up in Plenex with you, and you add the documents your reporting relies on, such as internal policies. Book a demo and we will walk you through it.
Yes. That is how most teams start: one site, the reports you already produce, and your own questions. Expanding later reuses everything you have set up.
Tell us about your sites and the reporting your team produces today.
Thanks, that is with us.
We will be in touch to arrange your demo.Multi-step tasks, guided measurement, space planning in 2D and 3D, and reporting your whole team can work in.
Read 30 Sep 2026Customer storyWarehouse planning through conversation, capacity modelling against the actual building, and reports reviewed by people.
Read 30 Sep 2026Practical insightsWhy site reporting consumes so much time, and what changes when the site itself can answer questions.
Read 30 Sep 2026Product updateHow the policy library turns internal requirements into part of every generated report.
ReadPlenex makes the physical world queryable. Understanding what exists within complex physical environments, where assets are, their condition and what has changed still requires repeated site visits, manual inspections and fragmented information. This makes maintenance, H&S, compliance and insurance slow, expensive and difficult to scale.
Commercial background across finance, fintech, growth and strategy, previously Head of Growth at a physical AI startup. Leads strategy, commercial and customer development.
AI researcher and engineer with over a decade of experience in computer vision. PhD in generative AI and published author on image generation. Leads architecture and product engineering.
This month’s release is about doing whole jobs, not just answering single questions.
Give Plenex a job with several stages and it works through the site itself, showing you what it is examining at each step. You watch the task progress rather than waiting on a black box.
Measure within a scene with the assistant guiding the points, and explore storage and layout options against the actual building, represented in both 2D and 3D.
Tag a specific asset in chat so Plenex knows exactly what you mean, and attach files to a conversation when the job needs them.
Bird’s-eye views with the roof cut away, and the ability to open the relevant area in 3D directly from a report finding, so reviewers can see the physical context behind every conclusion.
Multiple people can now work in the same scenes and reports. Comment, mention a teammate, share the report, and select any report text and use Ask Plenex to continue the conversation from that exact point.
Reports can also reference the policies your organisation has uploaded to its policy library, so the output reflects your internal controls.
These improvements are rolling out to current customers now.
“I asked our production facility a question yesterday. It answered.”
Stefan Marcus Neuber, Bike Club
Bike Club’s operations site in Rainham, east London, covers roughly 25,000 square feet. The manager responsible for planning it is based in Berlin. That distance used to work the way it does everywhere: questions about the site waited, either for someone on the floor to stop what they were doing, or for the next visit.
With Plenex, Stefan queries the Rainham site directly. In his own account of using it, three things changed.
Warehouse planning happens through conversation. Instead of waiting on successive CAD iterations to evaluate a layout idea, he explores options against the building as it actually is.
Capacity is modelled against the real building. When dimensions or constraints change, the capacity question is asked again rather than re-surveyed.
Reports come together in minutes. The output is prepared from the site itself, and a person reviews it before it is submitted anywhere.
The part we care most about is the friction that disappears. Questions about a remote site normally consume someone else’s time, which is exactly why managers postpone them and decisions wait for the next visit. Plenex makes it easy to ask the question at the moment it arises.
Bike Club’s Operations and Facilities Management teams are using Plenex at the Rainham site today, with remote capacity planning and site assessment as the primary use case.
Ask an operations or facilities team where their time goes and reporting is always near the top. Not because writing is hard, but because of everything that comes before the writing.
Information about a site is fragmented across old reports, drawings, spreadsheets, asset registers, maintenance records and people’s heads. Answering a practical question usually means finding the right person, arranging a visit, inspecting the environment and manually turning observations into documentation. Then the next job starts the process again, on the same site, for a different document.
Plenex changes the shape of that work. The workflow is: physical environment, question, grounded answer, report, review.
Take one concrete example. A team needs a RAMS, a risk assessment and method statement, for replacing a damaged racking run. Plenex identifies the risks from the site itself, draws controls from the company’s own uploaded policies, drafts the method, and hands the document to a person to review, adjust and sign off.
The important part is what happens next. The understanding that produced the RAMS does not disappear into the PDF. The same site knowledge backs the next job, a condition report, a contractor survey, a capacity assessment, without anyone rebuilding their understanding from scratch.
Two honest boundaries. Plenex reduces unnecessary visits where the required information already exists; it does not pretend every inspection can disappear. And outputs that need specialist judgement or professional sign-off still get it. The aim is that your experts spend their time judging, not gathering.
A report is only useful if it reflects how your organisation actually works. Generic safety boilerplate helps nobody, least of all the person on site who has to follow it.
That is what the policy library is for. Your organisation uploads its internal policies to Plenex once: safety rules, working procedures, site-specific requirements. From then on, when Plenex prepares a report, findings can reference the relevant policy directly, and the controls that appear in the output come from your own requirements.
In practice it looks like this. Plenex flags damaged racking near a walkway. Your internal policy on racking inspections and exclusion distances is in the library, so the finding cites it, and the drafted report carries your control, not a generic one.
The result is consistency. Two sites, two teams, two contractors, one set of rules, applied the same way in every report, with the source visible to whoever reviews it.
As always, the report is a draft for your team. People review, adjust and sign off before anything is issued.