Pricing
What drives the cost
We price every project individually, because the same feature list can differ several times over depending on what's underneath it. Here's exactly what moves the number — and how to get a real figure for your project.
Every project is quoted individually
A published price would either be padded to cover the worst case, or wrong for most people. We'd rather understand what you're building first and give you a number we can stand behind — scope, timeline and range, in writing, at no cost.
Free 30-minute call · Written scope and range · No commitment
What moves the number
Six things that decide cost
Number of user types
Each distinct role — admin, end user, or each side of a marketplace — is closer to its own product than an extra permission flag. Two-sided platforms are the most consistently underestimated.
Integrations
One payment gateway is routine. Payments plus a CRM plus a legacy ERP with no documentation is a different project, because each is someone else's API, rate limits and downtime.
Compliance requirements
GDPR, ISO 27001 or industry rules shape the data model, logging and infrastructure. Building with them in mind is a modest overhead; retrofitting them is not.
Design starting point
An existing design system is meaningfully cheaper than starting from research and wireframes. Not always the right call, but it is a real lever on cost.
Scale and performance needs
Ordinary traffic is straightforward. Event-day spikes, real-time updates, or heavy data processing change the architecture and therefore the cost.
Existing code
Extending a clean codebase is fast. Taking over an undocumented one starts with an audit, because the plan has to account for the code as it is.
How we work together
Engagement models
Fixed scope
A defined deliverable, a fixed price, and a timeline. Works when requirements are clear and stable — a marketing site, a defined MVP, an audit. You know the number before we start.
Sprint retainer
A monthly rate for a committed capacity, working through a prioritised backlog. Works when the product is evolving and the roadmap will change based on what you learn.
Discovery first
A short paid engagement that produces the scope, architecture and a real estimate. Sensible when the problem is complex enough that a fixed quote up front would be guesswork.
Pricing FAQ
Questions about cost
Why don't you list prices?
Because the same feature list can differ several times over in cost depending on user types, integrations and compliance. A published price would either be inflated to cover the worst case or misleading for anything non-trivial — and you would find out which only after committing. We would rather scope your project properly and give you a number we can stand behind.
How do I find out what my project will cost?
Get in touch and tell us what you're building. The first 30-minute call is free, and we follow it with a written scope, timeline and range at no cost. Most people get a useful figure from that one conversation.
Do you charge for the initial call?
No. The first 30-minute call is free, and we follow it with a written scope, timeline and range at no cost. Paid Discovery only applies where the problem needs real investigation before anyone can estimate honestly.
How do payments work?
Fixed-scope projects are milestone-based, typically an advance followed by payments tied to agreed deliverables. Retainers are billed monthly. We will put the schedule in writing before work starts.
What if the scope changes mid-project?
It usually does, and that is normal. Changes within the original intent we absorb. Genuinely new scope gets estimated and agreed before we build it, rather than appearing as a surprise on an invoice.
Do you work with international clients?
Yes. Our portfolio includes international governing bodies and organisations across multiple countries. We quote in INR by default and can bill in other currencies where needed.
What ongoing costs should we budget for after launch?
Infrastructure for an early-stage product is usually modest, plus any third-party services and payment processing. The larger ongoing cost is engineering time for iteration — available as a retainer, or handed to your own team, which is a perfectly good outcome.
Let's collaborate
Want a real number for your project?
Share the primary user journey, how many user types you need, and any integrations you already know about. That's usually enough for a range you can plan around.
No commitment needed · Free 30-min strategy session