A blueprint, not a deck of recommendations.
In 30 days an engineer connects the systems you already run, learns how your business actually works, and hands you a written plan for where AI pays off first. You keep the plan and the foundation underneath it whether or not you build anything with us.
Ask for a blueprint- 30
- Days to the blueprint
- 60
- More to production
- Flat
- Cost, no billing meter
- Yours
- The plan and the data map
Four things, all specific to you.
A blueprint is a document about your operation, not about us. Every number in it carries the assumptions it came from, so you can argue with the arithmetic.
- Your systems as they actually areWhere the work lives today, named system by system. The ERP that few people can drive, the travelers still on paper, the MES installed and underused, the tracking that ended up in spreadsheets and forms.
- A day-30 scoreboardThe measures we expect to move, written down before we start. Floor trips to procurement for an answer. Hours in spreadsheets and manual entry. Data errors in the ERP.
- The applications worth building, rankedFive candidates in order, each with what it takes to build, what it costs, and what it returns. Quoting and margin, demand and reorder signals, capacity and scheduling, paper and legacy digitisation.
- The arithmetic behind every claimStaff count, how often the work happens, how long it takes, loaded rate. Shown as a calculation rather than a number, so you can replace our assumptions with yours.
Two halves, and an engineer on your floor for part of it.
Laying the foundation
We connect the ERP, PDM, QMS, spreadsheets and shared drives, and build a data-level and business-level understanding of how the operation runs. This part is real work, not discovery calls, and what it produces stays yours.
Delivering the blueprint
We write it down. Where AI pays off, ranked, with the cost and the return of each, and the scoreboard we expect to move. Then you decide whether anything gets built.
If you say yes
The first application goes into production on the foundation the blueprint already built, as client-owned code with every change reviewed and logged. Each one after that starts from what the last one left behind.
Flat cost, and no obligation at the end of it.
- Flat cost, no billing meter
- You know the number before it starts. Nothing about the engagement rewards us for taking longer.
- No new software to learn
- Applications get configured to your spec and land in the tools your people already work in. We build, you give feedback.
- We never train on your data
- Your instance understands your business through context engineering, and your data does not leave your environment.
- You can stop at day 30
- The blueprint and the data map are yours either way. That is the point of paying for a foundation rather than a pilot.
