Most construction software is built to manage a problem the industry created for itself. A building passes through an architect, an engineer, a consultant, a main contractor and a row of subcontractors before anyone pours concrete. Every handover is a translation. Every translation loses something. BIM, 3D models and planning tools exist largely to keep those translations from going wrong.
I run a company that builds timber modular houses in factories in Estonia and Latvia. We design, produce and deliver. There is no consultant layer between the drawing and the production line. That structure changes what software is for. It stops being a referee between parties and becomes the thing that carries one decision all the way to a finished module.
This article is about what that looks like in practice, and what I think the industry gets wrong about digital planning.
The Model Is the Problem, Not the Tools
I have visited more than 120 factories across Europe over the past seven years. The best ones are not the ones with the most advanced software. They are the ones with the fewest handovers. A factory that receives a complete, production-ready model from a team that will also deliver the house works differently from a factory that receives a tender drawing and has to guess the rest.
In the traditional chain, a 3D model is a document of intent. Someone else will interpret it. Someone else will price it. Someone else will build it. Each party protects itself with margins, exclusions and assumptions. The software records the disagreement very precisely. It does not remove it.
When the same organisation designs and produces, the model stops being a document of intent and becomes an instruction. The wall in the model is the wall that gets cut. The window opening is the opening the machine mills. There is no step where a third party reinterprets the geometry.
What Digital Planning Does When the Chain Is Short
Three things change.
First, decisions move earlier. In a conventional project the real decisions are made late, often on site, because that is when the real constraints become visible. In a factory chain the constraints are known before the drawing starts. Panel dimensions, transport widths, crane limits, the sequence of the line. A planning tool that encodes those constraints at the design stage removes the late decisions entirely. The architect does not draw a module that cannot be transported. The tool will not allow it.
Second, price becomes a function of the model rather than a negotiation. When you own production, you know what a square metre of CLT costs you, what a window costs you, what an hour on the line costs you. A configurator that sits on top of that data can give a customer a price the moment the geometry is set. There is no tender round. There is no consultant adding a percentage to another consultant’s percentage.
Third, coordination collapses into one system. Most project coordination software exists to synchronise parties that do not share a database. When the designer, the production planner and the delivery team work from the same model, there is much less to coordinate. The planning tool is not a communication channel. It is the single record.
Why We Built Our Own Tools
We did not set out to build software. We set out to remove the steps where projects lose money. Every time we looked at a step, the available software assumed the step would stay. Estimating tools assumed a tender. Planning tools assumed a main contractor. Coordination tools assumed five parties.
So we built what the chain needed. A floor plan engine that only produces layouts the factory can build. A price and CO2 calculator that reads from our own production data. A configurator that partners can embed so their customers see real options and real prices without a sales meeting.
None of this is complicated technology. The difficult part is not the code. The difficult part is being allowed to make the assumptions the code relies on. You can only build a tool that prices a house instantly if you control what the house costs. You can only build a planner that guarantees buildability if you control the factory.
What the Industry Does Not Say Out Loud
Digital planning tools are often sold as a fix for fragmentation. They are not. They are a way of living with it. A beautifully coordinated BIM model across six companies is still six companies, six contracts and six places for the risk to land.
The plain version is this. Software improves a chain in proportion to how short that chain already is. Add a 3D model to a process with eight handovers and you get a well-documented process with eight handovers. Add the same model to a process with one owner and you get a production instruction.
That is uncomfortable for a lot of the industry, because the consultant layer is where many businesses sit. I am not saying those people lack skill. I am saying the structure makes their skill expensive, and the software compensates for the structure rather than fixing it.
What I Would Tell a Developer or a Client
Ask who owns the model after the drawing is done. If the answer is a chain of parties, the software is managing risk. If the answer is one party that will also build it, the software is removing risk. Those are different products, even when they look the same on screen.
Ask what the planning tool refuses to let you draw. A tool with no constraints is a drawing tool. A tool that stops you from designing something the factory cannot produce is a planning tool.
Ask where the price comes from. If it comes from a tender, it is an opinion. If it comes from production data, it is a number.
Where This Is Going
I think the next few years in construction software will not be about richer models. They will be about shorter chains. The companies that can connect a drawing directly to a production line, and stand behind the result, will have less use for coordination software and more use for tools that encode their own constraints.
The technology for that already exists. What is missing in most of the industry is the structure that lets the technology do its job. That is a business decision, not a software decision. I have stood on the factory floor enough times to be certain of that.