Services / Service line 06
Solution Architecture & Consulting
Decide what to build before you pay to build it.
02problem
The problem
The expensive mistakes in AEC technology are made before the first line of code: automating a process that should have been redesigned, buying a platform to solve what was actually a standards problem, or committing to a build that the API was never going to allow.
We are a development company, which makes this an unusual page to write — the most valuable thing we can tell some clients is that the project should be smaller, different, or not happen. We would rather say it in week one than bill for it in month six.
03entry_points
Our two entry points
Feasibility Review
A 30-minute technical session with the engineers who would build the thing, followed by a written verdict.
You get
- Whether it is possible within the API
- The specific technical risks
- Where the version and scale constraints sit
- What production would realistically involve
- An honest recommendation, including “don’t build this”
Suited toA new idea, a vendor proposal you want checked, or a build-versus-buy decision.
Book a Feasibility ReviewProduction Readiness Audit
Bring the prototype — yours, your vendor’s, or the one an AI tool generated — and we tell you exactly what it takes to ship it.
You get
- An assessment of the existing codebase and architecture
- The gap between demonstration and production conditions
- Deployment, version and support implications
- A phase plan with fixed scope
- A stabilise-versus-rebuild recommendation with the reasoning behind it
Suited toA working prototype that has stalled, an inherited codebase, or a tool that works for three people and needs to work for three hundred.
Request a Production Readiness Audit04ongoing_consulting
Ongoing consulting
- BIM implementation strategy
- Standards, templates, execution plans, adoption sequencing.
- ACC and Autodesk Platform adoption
- Migration, permissions architecture, workflow design.
- VDC process setup
- Coordination cadence, roles, model health governance.
- Automation roadmap
- Which processes to automate, in what order, with what expected return.
- Software architecture review
- For teams building their own AEC tools.
- CTO-as-a-service
- Fractional technical leadership for AEC firms without an in-house software function.
05where_it_breaks
Where it breaks
Five decisions that cost more than any line of code.
Automating a broken process
Automation makes an existing process faster, including a bad one. Workflow comes before tooling, always.
Buying software to fix a standards problem
A platform will not enforce conventions your team has not agreed on. The order matters.
Roadmaps without an owner
A twelve-month automation roadmap with no named internal owner and no protected time is a document, not a plan.
Pilots that never leave the pilot team
Adoption fails at rollout far more often than at proof of concept. Deployment, training and support belong in the plan from the beginning.
Estimates built on the demo
Scoping a project from what the prototype does, rather than from what production requires, is the single most common cause of a stalled build.
06proof
What you get
Written deliverables you own outright
Documents you can act on with any vendor — not a sales document. If our recommendation is that you should not build, or should build with someone else, that is what the document will say.
Case — pending
Format: the client had X. It broke at Y. We built Z. The measurable outcome was W. Two to three per page, anonymised where required.
07engagement
Who we are
Founded in 2021. A senior engineering team of more than twenty, with no layers of management and no account managers between you and the people writing the code. More than 200 tools shipped, and our own commercial products maintained in production — which means the advice comes from a team that carries the long-term consequences of its own architecture decisions.
Senior by design. You work directly with the engineers.
08faq
Frequently asked
Is the Feasibility Review free?
The session is a genuine technical conversation, not a sales call, and it ends in a written verdict. We no longer offer free development or free proofs of concept — that work is scoped and paid.
Do we have to use you to build it?
No. The output is yours and is written to be actionable with any competent development team.
Can you review a proposal from another vendor?
Yes, and this is a common request. We assess technical feasibility, architectural soundness and risk without commenting on commercial terms.
Do you sign an NDA first?
Yes. A countersigned mutual NDA precedes any access to code, models or proprietary information, without exception.
From prototype to production
AI made prototypes cheap. We make them ship.
A Feasibility Review is a 30-minute technical session with the engineers who would build it, followed by a written verdict: what the API actually allows, where it will break at scale, and what production costs. No obligation to proceed.
- Straight answers
- Written verdict
- Senior engineers, not account managers