Our pricing approach
We work on a project-based pricing model. Once we understand what you need, you receive a written proposal that states the price, what is included, what is excluded, the delivery timeline and the payment schedule. You can review it, ask questions and compare it before committing to anything.
We deliberately do not advertise headline prices such as "websites from $X". Published starting prices tend to describe a project nobody actually orders, and they set an expectation that changes as soon as the real requirements are known. We prefer to give you one figure that reflects the work your project genuinely requires.
Requesting a quote does not commit you to anything, and no charge is made for reviewing a request or issuing a proposal.
What determines the price
The price of an engagement is assessed against the following factors:
- Project scope — the number of features, screens, user roles and processes covered by the engagement.
- Complexity — how intricate the business rules, data structures and technical requirements are.
- Development time — the effort required to design, build, test and deliver the solution.
- Integrations — the number and nature of external systems, services and APIs that must be connected.
- Technical requirements — performance, security, availability, compliance and infrastructure expectations.
- Maintenance requirements — whether ongoing maintenance, updates or technical support are included after delivery.
Where a project depends on paid third-party services — hosting, domains, licences, app store fees, external APIs — those costs are identified separately in the proposal. They are not absorbed into our fee, and we do not add undisclosed charges on top of an accepted quotation.
Engagement models
The commercial model is agreed with you at proposal stage, according to how precisely the requirement can be defined in advance.