Pricing
A published price for "a website" is either meaningless or misleading, because the same brief can be a two-week job or a four-month one. What we can do is be completely open about how we price, what drives cost, and how you pay.
Engagement models
Which one fits depends on how well defined the requirement is. If you are not sure, describe the project and we will tell you which we would suggest.
The requirement is clear enough to write down.
You know what you want built and the scope is unlikely to change much. We agree the scope, price and dates up front.
Best for: brochure sites, ecommerce builds, redesigns
The requirement will change as you learn.
You get a developer working to your priorities, full time or part time. You re-prioritise whenever you need to, without a change request each time.
Best for: products, internal tools, ongoing build
You are live and need steady maintenance.
A fixed number of hours each month for updates, fixes and small changes, with priority response when something breaks.
Best for: anything already launched
Cost drivers
Twenty pages using four templates costs far less than eight pages that are all different. Templates are the unit of work, not pages.
Every external system — payment, CRM, ERP, shipping, accounting — adds build and testing time. A well-documented API is cheap; an undocumented one is not.
If copy and images exist, the build runs to plan. If they do not, the project waits. This is the most common cause of a project costing more than estimated.
A booking rule, a pricing calculation, a multi-step approval — anything where the behaviour is specific to your business rather than standard.
Moving an existing site means auditing what is there, mapping URLs and preserving what already ranks. It is real work and we price it separately rather than hiding it.
GDPR, accessibility conformance and data residency each carry specific work. Say early if any apply — retrofitting is more expensive.
Commercial terms
We invoice in USD, GBP, EUR, AED, AUD, CAD or INR. Pick whichever suits your accounts — we do not convert silently or add a spread.
Fixed-scope projects are paid across milestones, typically an advance to start and the balance across agreed stages. Retainers and dedicated developers are billed monthly in advance.
The code is yours. The repository sits in your account from the first commit, and IP transfers on final payment. We do not build on a proprietary platform you cannot leave.
We will sign your NDA and your contract. If you would rather use ours, we have one. Governing law is negotiable — tell us what your legal team needs.
Third-party costs — hosting, domains, licences, stock images, paid APIs — are yours and billed at cost if we buy them on your behalf. We list these before you commit.
Warranty covers anything that does not work as agreed, at no charge. If we get an estimate badly wrong through our own error, that is our problem to absorb, not yours.
Questions
Because it would be wrong often enough to be useless. Two clients asking for "an ecommerce site" can differ by a factor of ten depending on catalogue size, tax rules and integrations. A published number would either be a low figure we have to walk back, or a high one that puts off projects we could have done well.
Usually, by adjusting scope rather than quality. Tell us the budget and we will tell you honestly what fits inside it, what would have to wait for a second phase, and whether the whole thing is realistic. If it is not, we will say so rather than take the work and disappoint you.
For most clients in the US, UK, EU and Gulf, yes — that is straightforwardly the cost of engineering in India rather than a claim about efficiency. What matters more is whether the work is good and the communication holds up, which is what the process page and the case studies are for.
That is fine. Small, well-defined jobs are often how a working relationship starts, and we would rather do one well than turn it down for being under some minimum.
No. We are a services business, and an arrangement like that would leave both sides with the wrong incentives.
Next step
"Not sure" is a valid answer on the form — we will suggest a range based on what you describe.
Scripted, not an AI. Anything you send here reaches the team.