Published numbers, so nobody wastes a meeting.
We publish where our work starts because it saves both sides time. If the floor is above your budget, you have found that out in ten seconds instead of after three calls.
Three ways to work with us.
Almost everyone starts with the sprint. It is the cheapest way to find out whether the rest is worth doing.
Architecture Sprint
Buy the plan before you buy the build.
Best for: Teams who need a defensible technical direction and a real number to budget against.
- Two working sessions with your team
- System and data model design
- Architecture decision record with trade-offs
- Risk register with mitigation options
- Phased delivery plan and cost model
- Credited in full against a build within 60 days
Project Build
A defined system, delivered and handed over.
Best for: A specific outcome with a clear boundary: an MVP, an AI system, a platform migration, a security programme. Most land between $8,000 and $40,000.
- Fixed scope with a fixed price band
- Weekly staging builds you can click
- CI/CD, tests, and monitoring included
- Architecture decision records throughout
- Full source and infrastructure ownership
- 30 days of post-launch support
Embedded Team
An engineering function, not a staffing line.
Best for: Companies who need continuous senior capacity across product, AI, and infrastructure.
- Dedicated senior engineer plus architect oversight
- Your tools, your repository, your standards
- Roadmap planning and technical leadership
- Priority response during your working hours
- Monthly architecture and cost review
- Pause or cancel with 30 days notice
Where each practice starts.
These are floors, not quotes. The estimator will get you considerably closer in about a minute.
Four rules we do not bend.
You see a number before you commit
Every engagement starts with a written scope and a price band. If we cannot estimate something confidently, we say so and time-box a spike instead of padding the number.
Fixed bands, not hourly meters
You are buying an outcome. We carry the estimation risk within the agreed band, which means we have the same incentive you do to keep scope honest.
You own everything, always
Code, infrastructure, prompts, workflows, and documentation live in your accounts from day one. There is no proprietary layer holding your system hostage.
Scope changes are priced, not absorbed
When you want something new mid-build we give you the cost and the timeline impact in writing, and you decide. No silent overruns, no end-of-project surprises.
Pricing questions
Because the work below it is not the work we do well. Small isolated tasks need a freelancer, and we would be an expensive way to buy them. Our minimum reflects the point where architecture, testing, and handover actually pay for themselves.
Third-party costs are yours and billed to your accounts directly — cloud hosting, model inference, SaaS licences, domains. We will forecast them during the architecture sprint so there are no surprises, and we design to keep them low.
Occasionally, as a partial offset against cash for companies we would have invested in anyway. It is never the whole arrangement, and we will tell you honestly and quickly whether it is a fit.
Within the agreed scope, the band holds and the overrun is ours. If the scope changed, we priced that change in writing when it was requested. The failure mode we design against is discovering the problem at the end.
Typically 40% to start, 30% at an agreed midpoint milestone, and 30% on handover. Retainers are billed monthly in advance. We invoice in USD and can accommodate wire, card, or stablecoin settlement.
That is usually the right move. The Architecture Sprint exists exactly for this: five days, a fixed fee, and a plan you own whether or not you continue. It credits in full against a build.
Let us look at your architecture.
Two ways to start, both of them short. Bring the problem, not a specification — the first useful thing we do is tell you what we would build and roughly what it costs.
Book an architecture call
Fifteen minutes, no deck. We map your problem to an approach and tell you what a realistic scope and budget look like.
- A specific technical recommendation
- A budget band you can plan against
- An honest answer if we are the wrong fit
Send a written brief
Prefer to write it down? Email us the shape of the problem and we will reply with a first take, usually under 12 hours.
- Goes straight to an engineer, not a sales inbox
- We reply with an approach, not a brochure
- Attach anything: repos, docs, screenshots