Find Answers to Your Questions
We build engineering automation products – not outsourced development teams. Most of the questions below are the ones that come up on the first technical call: whether this fits your setup, how a project runs, what it costs, and what you actually get at the end. If yours isn't here, a 30-minute call with an engineer is faster than a form.
Contact UsFit & Scope
We already use the software that came with our formwork system. Why would we need you?
Because that software was built for its own catalogue and its own standard cases – not for your edge cases. The pattern is the same in every formwork design team we talk to: the supplied tool covers most of the work, and what’s left is done by hand in AutoCAD, floor by floor, on every project. We don’t replace that software and we don’t ask you to migrate. We automate the part it can’t reach. On POSforAFS that meant panel layout and material take-off built around the process the team already had – and a 70% reduction in formwork costs.
Do you replace our AutoCAD or Revit?
No. Our tools run inside them. What your engineers open in the morning stays the same – the difference is that the work that used to take a day of manual drafting happens in the background. Nothing about your file formats, your drawing standards or your existing library changes.
Isn’t this something AI can generate now?
Some of it, yes. Ask a language model for a script that renames layers and you’ll get a working script. Ask it for a panel-layout engine that respects your manufacturer’s catalogue constraints, tie spacing and pour sequencing, and you’ll get code that compiles and produces geometry that fails on site. We work in the places where generation breaks: geometric kernels, legacy system integrations, and engineering logic with real consequences. On a CAD/BIM-to-SAP integration we took the error rate on bills of materials from 15% down to under 2% – that’s a domain-modelling problem, not a code-generation one.
Our case is unusual. How do you know it can be automated before we take the risk?
We don’t take your word for it and we don’t ask you to take ours. Before any proposal we look at your actual drawings and your actual process on a technical call. That call is where the honest answer comes out – including “this part isn’t worth automating,” which we say more often than you’d expect. What gets into the proposal is the part we can name, scope and price.
We’re a team of four engineers, not an enterprise. Are we too small?
No – that’s most of who we work with. The teams that get the most out of this are small enough that one person’s manual work is a visible bottleneck and senior enough to know exactly which step they want gone. Company size isn’t the filter; having a repetitive, rule-based engineering task with real volume behind it is.
How a Project Works
What happens on the first call?
Thirty minutes with an engineer, not a salesperson. You show us the workflow you want automated – ideally on a real drawing. We tell you whether it’s automatable, roughly what it involves, and what the first module would cover. No slides, and no proposal until we’ve seen the work.
How long does a project take?
The first module usually ships in weeks rather than months, because it’s scoped to do one defined job. Full systems take longer and are built in stages, so you’re using something working while the rest is in development. For context: one client had spent two years trying to get a system built before coming to us, and we delivered it in six months.
What do you need from us while you build it?
Less than you’d think, but it isn’t zero. We need sample drawings that reflect real cases rather than clean examples, your catalogue or standards data, and one engineer who can answer questions about why your process works the way it does. That last one matters most – the domain logic lives in someone’s head, and getting it out is the actual work.
Who writes the code?
Our own engineers. We don’t subcontract, we don’t hand projects to a partner network, and the people on your technical call are the people building your tool. It’s also why our answer on the security questions below is what it is.
Didn't find your question?
The fastest route is a 30-minute technical call. Bring a drawing and the step you want gone – you'll get a straight answer on whether it's automatable, including if the answer is no.