Engagement Models: Pick the Shape That Fits Your Stage
A founder with an idea and an enterprise with a legacy system need different things. We offer three engagement shapes, and you can move between them as the work evolves.
Which model fits you
| Scoping sprint | Dedicated build team | Advisory and audit | |
|---|---|---|---|
| Best for | An idea or project that is not yet defined | A defined product ready to be built or extended | An existing codebase, architecture or roadmap |
| You get | Specification, architecture, estimate | Working software in weekly increments | An independent written assessment |
| Scope | Short and fixed | Ongoing, reviewed every week | Fixed, agreed upfront |
| Commitment | None beyond the sprint | Agreed with you, adjustable | None beyond the review |
Model 1: Scoping sprint
A short, fixed engagement to interrogate the idea, write the specification and hand you an architecture and estimate you own, whether or not you build with us. It is the cheapest way to find out what a project really involves.
- Problem, users and constraints written down and agreed.
- A specification that separates what is needed now from what can wait.
- Architecture and data model sketches, with the main risks listed.
- An estimate based on the specification, not on a guess.
- Everything handed over to you, with no obligation to continue.
Choose this when the idea is still forming, when you need something concrete to take to investors or stakeholders, or when previous estimates varied wildly. The AI Idea Validation Assistant is a good free first step.
Model 2: Dedicated build team
A senior pod covering engineering, architecture and review that owns delivery end to end, in reviewable increments from first commit to launch. You get a single accountable team rather than a loose collection of contractors.
- Weekly releases to a staging site you can use and comment on.
- A shared backlog you can read and re-order.
- Automated tests, code review and scripted deployments on every change.
- Code, documentation and infrastructure in your accounts from day one.
- Support and maintenance after launch if you want it.
Choose this when the product is defined, when you want one team accountable for the result, or when your own team needs senior capacity. See how it works in practice on our process page.
Model 3: Advisory and audit
An independent review of an existing codebase, architecture or roadmap: an honest read on technical debt, risk and what to build next. We tell you what we find, including when the answer is that you are in better shape than you feared.
- Code, architecture and infrastructure reviewed against your goals.
- Security, scalability and maintainability risks ranked by impact.
- A prioritised plan with effort estimates.
- A written report you can share with your team and board.
Choose this before taking over a codebase, before a big investment in a rewrite, or when delivery has slowed and you do not know why.
Questions people ask
Can we start with a sprint and then build with you?
Yes, and that is the most common path for early-stage founders. The specification and architecture are yours either way.
Can you work alongside our in-house developers?
Yes. A build team can join your delivery, lead it, or review it, depending on what you need.
What do we own at the end?
Everything we write: repository, documentation and infrastructure live in your accounts from the first commit.
How do we get started?
Send a short description through the contact page. We reply within one business day with questions, not a sales pitch.