Pricing

How we price projects.

No published price list - the right model depends on how well-defined your scope is. Here's exactly how we think about it.

Step Zero

Every engagement starts with a paid discovery sprint.

We don't quote a fixed price off a single call. A short, paid discovery sprint - typically 1–2 weeks - lets us review your existing codebase or requirements, scope the real work, and give you a number we'll actually commit to.

This protects both sides: you get an accurate estimate instead of a guess, and we don't under-price work we haven't actually looked at.

Discovery sprint1–2 weeks, paid
Typical MVP timeline8–14 weeks
Typical enterprise timeline3–6 months
Minimum engagement~6 weeks

Illustrative Timeline

What a Fixed-Price MVP schedule tends to look like.

Example schedule shape, not a specific project. Your actual timeline is set during the discovery sprint above.

Week 1–2

Discovery Sprint

Requirements and architecture review, fixed-price quote delivered.

Week 3–4

Architecture & Design Sign-off

System design finalized, UI/UX wireframes approved.

Week 5–10

Build Sprints

Two-week sprints, working software at every checkpoint.

Week 11–12

QA & Hardening

Automated and manual testing, performance benchmarking.

Week 13–14

Deploy & Handoff

Production deployment, documentation, knowledge transfer.

Engagement Models

Three ways to work with us.

Best for defined scope

Fixed Price

Suited for well-specified projects where the requirements are stable. We scope in a paid discovery sprint, agree on deliverables, and price accordingly. You know the cost upfront.

8–14 weeks for an MVP, agreed and locked during the discovery sprint.

  • -MVP builds
  • -Feature additions
  • -Design system creation
  • -Migration projects

Best for evolving scope

Time & Materials

Suited for exploratory or fast-changing products where requirements evolve with each sprint. You pay for actual time spent, with full visibility into progress and effort.

Billed in two-week sprints; runs as long as the roadmap does.

  • -Ongoing product development
  • -Research-heavy builds
  • -Startup iteration cycles
  • -Proof-of-concept work

Best for long-term scale

Dedicated Team

A dedicated engineer embedded in your team, operating as an extension of your engineering organisation - on your tools, your processes, and your roadmap. Minimum 3-month commitment.

Minimum 3-month commitment, monthly billing thereafter.

  • -Scale-ups with growing product needs
  • -Enterprises augmenting internal teams
  • -Ongoing platform maintenance

FAQ

Pricing questions.

See all FAQs

Next Step

Ready to scope your project?

Book a 30-minute call and we'll tell you exactly how we'd approach your problem - and roughly what it would cost.