Pricing & project scope
A price that starts with a clear scope.
Digital projects vary with the work, the systems involved and the responsibility you want us to take. We prepare a proposal after understanding those choices.
Scope comes before a dependable estimate.
Two projects with a similar headline can require very different work. The number of user journeys, existing code quality, integrations, data migration, content volume, security requirements and testing needs all affect effort. We begin by understanding the outcome and the system you have, then identify what can be defined now and what needs investigation. A single public number would hide those differences rather than help you make a decision.
A proposal should show what is included.
We describe deliverables, assumptions, responsibilities, exclusions and review points in a written scope. It should be clear who supplies content and provider access, who approves business rules, and how a requested change is assessed. The commercial model, payment schedule and any continuing service are then agreed for that scope. If important requirements are still unknown, a focused discovery stage can establish the facts before a wider implementation commitment.
See the full cost picture.
Hosting, platform subscriptions, paid extensions, advertising spend and usage-based providers may be separate from the work of design or development. We identify relevant dependencies in the proposal so an implementation figure is not mistaken for the total operating cost. Taxes, currency, invoicing terms and renewal choices need an approved agreement; this page does not invent them. Where you already own a suitable provider account, that may change the recommended scope.
Prepare a brief that supports a useful response.
Share the outcome you need, important users, current systems, integrations and any timing or budget constraints you can disclose. It helps to know who will approve decisions and who will operate the result. We can discuss a narrow first phase when the entire project is not yet ready to define. A proposal is a chance to make tradeoffs visible, not a promise of a fixed result without seeing the actual work.
Questions before we start.
Can I get a fixed price before discovery?
Only when the scope, dependencies and acceptance criteria are sufficiently clear. If they are not, we can first define a bounded discovery stage. We will not fill gaps with assumed business rules or promise a fixed total that ignores known uncertainty.
Are provider subscriptions included in project fees?
They may be separate. The proposal identifies relevant licenses, hosting, media spend or usage charges and who owns each account. The exact terms are agreed before work begins.
EXPLORE
Continue exploring
Bring us the problem. We’ll work through the next step.
Share what exists today and what you want to change. We can discuss the scope, dependencies and a practical way forward.