Consulting
Straight answers before you spend the budget
Sometimes the most valuable thing an engineering partner can do is tell you not to build something. Our consulting work is deliberately short, independent of any build contract, and it ends in a written document you can hand to your board.
Scope
What this covers
Architecture review
An independent read on whether your current design holds at three times the load, where the failure points sit and what the three highest value changes would be.
Technical due diligence
For investors and acquirers: code quality, key person risk, security posture, licence exposure, infrastructure cost and a realistic estimate of what the roadmap will actually take.
Build versus buy
Costed comparison across three to five years including integration, maintenance and the switching cost of getting it wrong. We have talked clients out of builds more than once.
Security assessment
Threat model, dependency and secret scanning, access review and a prioritised remediation plan with effort estimates against each item.
Modernization roadmap
A staged plan to get from the current system to the target, sequenced so business value lands early and no stage requires a freeze on feature work.
Stack
What we build it with
Tools are chosen per project and justified in an architecture decision record. This is what we reach for most often in this practice.
Deliverables
What you actually receive
- Written report, typically twenty to forty pages
- Prioritised findings with effort and impact against each
- Costed options, including the option of doing nothing
- Working session with your engineering and executive teams
- No obligation to engage us for the build
Related case studies
Where we have done this
Rebuilding a payments ledger that was losing money it could not find
The original system tracked balances rather than transactions, so a discrepancy could be observed but never explained. We migrated to an immutable double-entry ledger with zero downtime and no change to the customer-facing product.
Replacing 1,100 hours a month of manual approvals inside an enterprise change process
The engineering was not difficult. Delivering it inside a change advisory board, an SAP integration and 14 sets of local approval rules was the project.
Questions
What clients ask first
How long does a review take?
Will you recommend yourselves for the build?
Can you review a system you did not build?
Services
Practices that pair with this one
Product engineering
SaaS platforms and web products built to carry real load
Mobile engineering
iOS and Android apps that hold up outside the demo
Agentic and generative AI
AI features that pass review, not just demo well
Cloud and platform engineering
Infrastructure your team can operate at three in the morning
Data engineering and analytics
Numbers your leadership team actually trusts
Need technology consulting?
Send a short brief and a senior engineer will read it. You get a written response with our honest read on scope, risk and cost within one business day. No discovery call required to get a real answer.
- A senior engineer reads every brief
- NDA signed before you share anything sensitive
- No sales sequence, no automated follow ups