Look first. Then build.
Most people arrive knowing something is wrong rather than knowing what to buy. So we look properly first, at a fixed price, and tell you what is worth doing and what is not worth doing yet. Then we build what that calls for, against a definition of done you sign, delivered in full or your money back.
Engagements start small on purpose. The first piece is sized so you can find out what we are like without a large commitment, and it carries the same signed done-test and the same money back as a full build. We ask for bigger commitments after we have earned them.
01
Assess
Find out what you are actually dealing with.
- Technical due diligence, security, AI-readiness, architecture, codebase rescue.
- A fixed price and a board-ready report: what is worth doing, what is not worth doing yet, and what each costs.
- The report stands on its own and is yours whatever you decide next.
02
Build
Then we build what it calls for.
- Priced against a signed done-test; delivered in full or your money back.
- New product, rescue, migration, or the one capability holding up a deal.
- Full ownership: source, docs and IP assign to you stage by stage as each is paid.
03
Advise
For the decisions that are expensive to get wrong.
- Reserved senior capacity, monthly, at three commitment levels.
- Two clients at Standard, or one at Embedded, so you get the partner rather than a junior with an escalation path.
- Sometimes called a fractional CTO. Runs alongside a build or on its own.
04
Run
We build it and run it; you own your cloud account; we never mark up your infrastructure.
- Your account, your bills: cloud and licences bill you first-party.
- The management fee is the product; we take nothing from the size of your spend.
- Cover agreed up front, priced to fund it.
Not sure which you need?
That is the normal starting position, and working it out is our job rather than yours. Tell us what is going on and we will come back with the right way in, including telling you if the answer is nothing yet.