Engagement models
Pick by how much certainty you need on scope and how long the work will last. Pricing is agreed per engagement, in writing, before anything starts. We do not publish a rate card because a number without context misleads.
Best for
Clearly defined projects with a known outcome and deadline.
We agree scope, timeline and price up front, deliver in milestones you can see, and handle change through a simple, written process. Best when you know what you need and want certainty on cost.
What is included
Best for
Long-term product development with an evolving roadmap.
A cross-functional team with a tech lead works as part of your organisation, month to month, on your tools and rituals. Best when the product will keep changing and you want a team that knows it deeply.
What is included
Best for
Adding senior engineers to a team you already run.
Individual engineers join your existing team, your processes and your codebase, with our technical leadership behind them for support and quality. Best when you have the product direction and need capacity.
What is included
Best for
Architecture decisions, assessments and technical strategy.
Fixed-scope engagements that produce decisions: an architecture review, a build-versus-buy analysis, a modernisation roadmap or a technical due diligence. Written down, with the trade-offs, so your team can execute.
What is included
Choosing
| You have… | Choose | Why |
|---|---|---|
| A defined project and a deadline | Fixed scope | Certainty on cost and delivery |
| A product that will keep changing | Dedicated team | Deep product knowledge, flexible roadmap |
| A team that needs more hands | Team extension | Your process, our senior engineers |
| A decision to make before building | Technology consulting | Written options and a roadmap |
FAQ
Describe the situation. We will recommend one and explain why, even if the answer is a smaller engagement than you expected.