// Pricing
Starting prices, scoped to your project.
Every engagement is scoped by hours before we quote a number, so the price below is a realistic starting point, not a teaser. Final pricing depends on your actual scope and complexity, not a recurring team retainer.
Scoped Sprint
Starting atA focused engagement on one well-defined problem. Scoped by hours upfront, so the number is known before work starts.
- One senior engineer
- Scoped by hours before kickoff
- Weekly working demos
- CI/CD and testing included
Full Build
Starting atA complete MVP build or modernization project, priced to your actual scope, not a recurring retainer.
- Everything in Scoped Sprint, plus:
- 2-3 senior engineers
- Dedicated PM
- Fixed-scope milestones
Ongoing Partnership
For companies that need an embedded team long-term, with scope reviewed and re-agreed every month.
- Everything in Full Build, plus:
- Team sized to your roadmap
- Dedicated engineering lead
- Monthly scope review
// Questions
Pricing FAQ
Is this an hourly rate, or a fixed price?
It's a fixed project price, built from an hourly estimate we agree on before work starts, not an open-ended hourly clock with no ceiling. We scope the work in hours first, based on your actual requirements, then quote a flat number for the engagement so you know the total before you commit.
What does the price actually depend on?
Mainly the number of engineering hours the work realistically takes, which comes from the complexity of what you're building, how many integrations or data sources are involved, and how much of the system already exists versus needs to be built from scratch. The tiers below are starting points; every real quote is scoped to your specific project first.
What happens if the scope changes mid-engagement?
Scope changes are normal in real software work. We re-scope explicitly, in writing, with an updated hours estimate and price, rather than quietly absorbing extra work into the original number or padding the timeline without saying so.
Do you work with early-stage, pre-funding startups?
Sometimes, if the problem is well-defined and the team can commit to weekly review of working software. We're a poor fit for exploratory, ill-defined 'build us an app' engagements with no technical stakeholder on your side.