Working software, fixed price, a number back within a week.
Two to four senior people, weekly working releases, your product IP transferring to you at go-live. No day rates. No retainers against a calendar.
You get an answer, code, or a capability.
Same practice underneath: senior people on the work that needs judgement, agents on the work that doesn't, fixed price, weekly visible output. The deliverable shape changes with the question.
- Advise
A decision, written down.
A clear answer to a specific question. Assessments, Discovery, or a fractional CTO retainer. If the question would be better answered by a small piece of working software, we will tell you and quote it as Build instead.
- Build
Working software in your environment.
Greenfield, rescue, or hardening a prototype into a production system. A paid Discovery or audit comes first; the fee credits against the build if you proceed. Two to four senior people, weekly releases into staging, IP transfers at go-live.
- Teach
A live capability your team owns.
Two to six months alongside your people, building their own agentic capability on your tools, tuned to your work. You end up with your own version of the idea, not a copy of ours.
Pick a rough shape. We will come back with a number.
Every line is fixed price. The shapes below are starting points; the spec and the price are agreed in the first conversation. Discovery, audit, and triage fees credit against the full engagement if you proceed.
New here? Most engagements start with a focused assessment or a light Discovery, the smallest ways in.
Advise
Assess
3 options A single-system or platform-wide read on where you are and what to do next. Written down, short, actionable.
A single system or a single question. Written report with findings and a recommended path.
Platform review or AI opportunity scan. Interviews, architecture review, prioritised action plan.
Enterprise estate review or full AI roadmap across multiple teams. Board-ready recommendation.
Discover
3 options Paid Discovery that produces a buildable spec. The spec is yours either way; the fee credits against the build if you proceed.
Internal tool, single-feature MVP, narrow scope.
Full MVP or a product strategy for a specific line of business.
SaaS platform, complex integrations, regulated environments.
Retain
3 options Fractional CTO on a defined cadence. Three-month minimum. The same senior in the room every week.
Right call on a small number of decisions for boards and founders.
Active in architecture, hiring, vendor selection, and delivery oversight.
Senior technical co-pilot for the CEO.
Build
Greenfield
4 options From nothing to working software in your environment. Paid Discovery comes first; fee credits against the build.
Single workflow, internal tool, dashboard, narrow-scope MVP.
Full MVP, multi-workflow internal tool, lightweight SaaS.
Multi-user SaaS, AI-powered platforms, production integrations.
Multi-tenant platforms, complex compliance, deep integrations.
Rescue
3 options For builds gone off track, codebases nobody wants to touch, and projects the original team cannot finish. Always starts with triage; triage fee credits if you proceed.
Honest assessment of the codebase and a recommended path forward.
Fix to a working state. Retain the existing codebase where it is salvageable.
Scrap and rebuild. We recommend it only when starting over gets you to a working product sooner than untangling the existing code.
Harden
3 options For prototypes that found product-market signal but were not built to take production load. Tests, auth, observability, infra, scaling, and the product decisions made permanent. Audit first; audit fee credits if you proceed.
Honest read on the prototype: what survives to production, what does not. Gap list against tests, auth, data, observability, infra, scaling, and compliance.
Keep the prototype's product decisions. Rebuild the parts that cannot survive production, layer in the parts that are not there, leave you with a system your team can run.
When the product is right but the code cannot carry forward. The audit becomes the spec; the rebuild runs as a normal Build.
Teach
Capability programmes
3 options Your team becomes AI-native on their own tools and their own work. When we leave, they keep a live capability they can extend without us.
One team adopting agentic workflows. Engineering is the common starting point.
One function across multiple teams. Product, design, or engineering end to end.
Cross-functional rollout across product, design, and engineering with exec sponsorship.
The ones your board and your legal team usually raise first.
-
Will the seniors named in the proposal actually do the work?
Yes. The person who pitches the work is the person doing the work. Every name in the proposal has at least ten years of shipping experience. We will not substitute without telling you, in writing, before it happens.
-
Who owns the code your agents produce?
You do. All product code, infrastructure, IP, and credentials transfer to you at go-live. We use standard, open stacks. There are no proprietary frameworks for you to keep licensing once we're done.
-
Where do our source code, prompts, and data go?
Into your repositories, your cloud, your environments. We work inside your perimeter wherever your security policy requires it. Our toolchain runs on enterprise tiers with training opt-out. We sign your DPA and walk your infosec team through the data flow before we start.
-
Who is liable when an agent ships a defect?
We are. We carry professional indemnity, every commit is reviewed by a senior human before it ships, and the warranty terms are written into the contract with no AI carve-outs. If a defect lands in production within the warranty window, we fix it on us.
-
What if your AI tooling changes mid-build?
Tooling and token costs are ours, not yours. If a vendor deprecates, hikes prices, or changes terms mid-engagement, we absorb the cost and switch underneath. Your fixed price does not move.
-
Can our team maintain what you build after you leave?
Yes, that's the design goal. Standard stacks, documented architecture, no proprietary frameworks, every decision in the repo. Thirty days of post-engagement support for questions, then it is fully yours.
-
What if scope changes mid-build?
We price the change explicitly before we do the work. You see the cost, you decide. We do not change the budget unilaterally and we do not hide scope drift in a timesheet.
-
Do you do day rates?
No. The billable hour rewards delay, and a day rate is the billable hour in bulk. We only do fixed-price engagements or monthly retainers with a defined deliverable.
-
How small can we start?
A focused assessment or a light Discovery are the smallest engagements we run. Both are useful in their own right, and both can become bigger things.
Start a conversation.
or email us directly at [email protected]