Two to four weeks to know exactly how to build your AI product.
A fixed-scope sprint for founders who want the big technical decisions made properly before they commit to building an AI product. You get the decisions a good CTO would make in the first month, and a working prototype of the riskiest part, delivered by our team.
At a glance
- Length
- Two to four weeks
- Scope
- Fixed, agreed before we start
- Fee
- Fixed fee, agreed upfront in the proposal.
- Led by
- Our founder, with our team
- You leave with
- A written plan and a working prototype
Settle the decisions that are hard to change, before you build
The early choices in an AI product shape everything after them: which AI approach you take, what you build and what you buy, where your data lives, and what each customer will cost you to serve. Once a team has built on top of them, they are slow and costly to reverse.
The sprint gives those decisions senior attention and enough time, and tests the riskiest assumption with working code rather than a slide. At the end you know what to build, how to build it, who should build it and roughly what it will cost to run.
The first month of technical decisions, written down
Seven deliverables, each one something you can act on whether you build with us, with your own developers or with another team.
Architecture and stack recommendation
How the product should be put together and which technologies to build it on, with the reasoning written down so it can be questioned later.
Build vs buy for each major component
Models, vector search, data pipelines and vendors: what to build, what to buy or integrate, and what each choice commits you to.
AI approach and evaluation plan
The AI approach that fits the problem, and how we will know it works: the test cases, the quality checks and what "good enough" means before customers see it.
Cost-to-run estimate
What inference and hosting are likely to cost as usage grows, with the cheap option and the safe option side by side.
A team plan
Who to hire, what to outsource and what to leave to AI coding agents, so the build is staffed for what it actually needs.
A working prototype of the riskiest technical assumption
Our engineers build the technical assumption the product depends on most, so it is tested with working code before you commit to the full build.
A written plan you could hand to any team
Decisions, reasoning, costs and next steps in one document. Use it with us, with your own developers or with another team.
From first conversation to a plan you can act on
The length depends on how much there is to decide and how hard the riskiest part is to prove. Scope and length are fixed before we start.
Discovery and mapping
Week 1We talk to the people who know the customer and the data, and map the data, systems and constraints the product has to work with.
Options and decisions
Week 2We set out the options for architecture, AI approach and build vs buy, with their trade-offs, and make the calls with you.
Prototype the riskiest part
Weeks 2–4Our engineers build a working prototype of the assumption the product depends on most, using your data wherever we can.
Plan and walk-through
Final weekYou get the written plan, the cost-to-run estimate and the team plan, and we walk you and your team through the prototype and the decisions behind it.
Founders about to commit to an AI product
The sprint suits founders and CEOs who are about to build an AI product or AI feature. It fits three situations in particular.
No technical co-founder
You have the idea, the customers and the budget, and want the technical decisions made properly before you spend on a build.
Developers, but no one in charge
You have an in-house team or an agency, and want someone senior to settle the architecture, the AI approach and the vendors before they build.
Between CTOs
Your CTO has left, or you are about to hire your first, and you want the plan settled so the product keeps moving and your new CTO starts from a clear position.
Carry out the plan with us, or with anyone.
Many founders continue with Technology Leadership to carry out the plan. You're under no obligation to; the plan is yours.
Questions we often hear
Is the prototype production-ready?
No. It is built to prove the riskiest assumption quickly and honestly, not to carry real customers. Production follows once the plan is agreed, whether that is with our team, your own developers or another team.
Do we need a technical team already?
No. The sprint works with no developers in place, and the team plan sets out who to hire, what to outsource and what to leave to AI coding agents. If you already have developers or an agency, we involve them from the first week.
Can you work with our agency?
Yes. We work alongside your agency through the sprint, and the written plan gives them a clear brief to build from. Our role is to make the technical decisions with you, not to replace people who are already doing good work.
What do you need from us?
Access to the people who know the customer and the data, and a few hours a week. Our team does the technical work, the research and the prototype, and brings the decisions to you to make together.
Related reading and tools
Tell us what you want to build.
A short note is enough. Our founder, Irwan, reads every message. You'll get a reply within 24 hours with an honest view on whether we're the right fit, or who might be.
Based in Singapore · Working with founders globally · Reply within 24 hours