How we price work.
We don't publish a flat rate card, because the honest cost of a project depends entirely on its scope — and a number with no context is more misleading than useful. Here's how engagements are actually structured, and how to get a real number for your project.
Project-based
A fixed-scope build with a clear start and end — most internal tools, SaaS MVPs, and marketing sites work this way.
Best for
A defined product or feature set with a known launch date.
- ✓Scoped after a short discovery phase, so the quote matches the real work
- ✓Fixed price once scope is agreed, broken into phases with clear deliverables
- ✓Source code and documentation handed over at the end
Monthly retainer
Ongoing development capacity for products that keep evolving — new features, integrations, and iteration.
Best for
A live product that needs continuous work, not a one-off build.
- ✓A fixed block of monthly development time, reviewed and adjusted as priorities shift
- ✓Direct access to the same team that built (or knows) your product
- ✓Month-to-month — no long lock-in contract
Support & maintenance
For products already built — by us or someone else — that need monitoring, fixes, and small improvements.
Best for
A stable product that mostly needs to keep running well.
- ✓Bug fixes, security patches, and dependency updates
- ✓Monitoring and uptime checks
- ✓A clear monthly report of what was done
Want an actual number?
Tell us what you're building on a short call. We'll ask enough questions to give you a real range, broken down by phase — not a guess pulled from a price list.