→ cat pricing.model
billing_model: fixed_fee
billing_basis: written_scope
hourly_billing: not_offered
published_numbers: indicative_ranges
✓ ranges are starting points, quotes come from scope
// pricing
Fixed fee. Written scope. Never hourly.
We publish indicative ranges so you can tell early whether this studio is in your budget. A binding price only ever comes from a written scope, after we both know what is being built.
Why we quote fixed fees
Hourly billing punishes efficiency. Because tooling makes this studio faster, a clock works against both sides. A fixed price keeps speed as our problem and budget control as yours.
The clock rewards being slow
Hourly billing pays for time, not outcomes. A studio that gets faster earns less and a client who finds a faster route is charged the same. That incentive runs the wrong way.
One number, one scope
A fixed fee means one price for one defined outcome. You approve a scope, we commit to a price. What that scope contains is written down in plain language before anyone starts.
Our speed, your budget
If AI tooling and good engineering let us finish early, the saving is ours to keep and your spend stays exactly where you set it. Efficiency stops being a cost you pay for.
Honest limits
Fixed fee only works when scope is defined. That is why discovery is a separate, paid, fixed-fee phase rather than something we quietly absorb and hope for the best.
What fixed fee does NOT mean
It does not mean we guess. It does not mean unlimited revisions. It does not mean we absorb an undefined product for free. It means: this scope, this price, and anything outside the scope is discussed and priced in writing before it is built.
Indicative budget ranges
Starting points, gathered from 2026 agency market research. Use them to sanity-check whether we are in range, not to budget from.
Read this before the numbers
These ranges are indicative and deliberately non-binding. They are not a quote, not an offer, and not a ceiling or a floor for your project. They describe the 2026 market band for each engagement type. Your price is whatever your written scope says it is, and nothing else.
| Engagement | Indicative range (USD) | Typical duration | What moves you inside the range |
|---|---|---|---|
| Brand and design system | $8,000 - $30,000 | 4 - 8 weeks | Number of screens or components in the system, brand maturity, illustration and motion work |
| Marketing site build | $12,000 - $40,000 | 4 - 10 weeks | Page count, CMS choice, copywriting and imagery supplied or not, animation and 3D |
| E-commerce build | $20,000 - $75,000 | 6 - 16 weeks | Catalogue size, payment and tax complexity, ERP or PIM integrations, checkout customisation |
| SaaS MVP | $40,000 - $120,000 | 10 - 24 weeks | Multi-tenancy, billing and subscription logic, role model, integrations, compliance surface |
| Mobile app | $45,000 - $150,000 | 12 - 26 weeks | Native versus cross-platform, number of screens, offline and sync behaviour, store and backend work |
| Growth retainer (SEO, paid, CRO) | $3,000 - $12,000 per month | 6 months minimum | Site size and current technical debt, market competition, content volume included or separate |
| Dedicated delivery pod | $18,000 - $45,000 per month | 6 months minimum | Pod size and seniority mix, number of parallel workstreams, on-call expectations |
| Discovery and scoping phase | Quoted separately, credited to the build | 1 - 3 weeks | Legacy code review, stakeholder interviews, technical due diligence |
Indicative starting points only, compiled from 2026 agency market research. They are not a quote, not an offer, and not binding. Your price comes from a written scope.
Why the bands are wide
A band is wide because the same engagement name covers very different products. A six-screen marketing site and a forty-screen marketing site are both "a marketing site". The spread is not we hedging. It is the honest width of the category.
What changes the price
Six things move a number, in roughly this order of impact. If you want a tighter estimate, sorting out these six is the fastest route.
| Driver | Why it moves the number |
|---|---|
| Scope | Features, screens, user roles and edge cases. This is the single biggest lever in any estimate. |
| Integrations | Each third-party system means API mapping, failure handling, reconciliation and testing. |
| Compliance and data-protection burden | Personal data handling, retention rules, consent, audit trails and access control add design and engineering work. It does not make your organisation compliant, and we do not certify compliance. |
| Content volume | Written copy, photography, video and product data you supply save money. Anything we must produce or ingest adds cost. |
| Timeline pressure | A compressed schedule means parallel work and overtime. It is possible, and it is priced. |
| Non-functional requirements | Availability targets, performance budgets, data volumes, accessibility level and load testing all shape the architecture. |
Fixed fee vs hourly vs retainer vs pod
Each model is right for a different situation. Here is when to use which, including the cases where ours is the wrong choice.
| Model | How billing works | Budget certainty | Right choice when | Main risk |
|---|---|---|---|---|
| Fixed-fee project | One price for a written scope, invoiced against milestones | High, once scope is signed | You have a defined deliverable with an end date and want the budget locked before we start | Scope drift. Handled through written change requests, priced before work begins |
| Hourly | Billed for time as worked | Low. Open-ended | Genuinely undefined work: incident response, exploratory spikes, internal tooling | Rewards going slowly and leaves you unable to forecast. We do not offer it |
| Retainer | Fixed monthly fee for a defined capacity of ongoing work | Medium. Recurring, cancelable | Continuous work after launch: SEO, growth, iteration, maintenance | Needs real priorities from your side every month, or the retainer buys idle capacity |
| Dedicated pod | Fixed monthly fee for a named team working in parallel | Medium. Capacity sized up front | Multiple workstreams and roadmap ownership rather than a single deliverable | A long commitment. Needs an internal counterpart on your side |
Where fixed fee is the wrong choice
If the work is genuinely undefined, if you want our judgement continuously rather than an outcome, or if you need several workstreams running at once, an hourly or retainer arrangement may serve you better. We would rather say so before you sign than defend a bad fit afterwards. Most of the market works this way: 78% of agencies now use retainers, up from 64% in 2023 (SPI Research, 2026).
Payment terms
How money actually moves. Specifics are set per contract, not published as a universal policy.
Discovery is its own fixed-fee phase
Scoping, technical review and planning are quoted separately and delivered as a written output you own. It is not hidden inside the build price, because hiding it means neither of us knows what the build really costs.
The discovery deposit is credited to the build
What you pay for discovery comes off the build invoice in full. If you decide not to proceed with the build afterwards, you still keep the scope, the technical assessment and the plan.
Builds are invoiced in milestones
Payments fall against agreed delivery milestones defined in the contract, not against hours logged. You can see what has shipped for each payment before it is due.
Retainers and pods bill monthly, in advance
Recurring work is a fixed monthly fee for a defined capacity, invoiced at the start of each month. Either side can end the arrangement at the end of a month, with notice.
Change requests are priced before they are built
If something falls outside the signed scope, you get a written change with a price and a schedule effect. We do not start the work and invoice you for the surprise afterwards.
Payment schedule details
The exact deposit percentage, milestone split, payment terms and notice periods are set in each contract and confirmed in your proposal. We do not publish a single universal schedule, because the honest numbers differ between a small design system and a multi-quarter platform build. Ask for them in writing with your quote.
Market context
Third-party figures that explain the environment this studio operates in. These are market data points, not WebNuvexa results, and no claim is made about our own performance.
We publish these because they help you calibrate us against the market rather than against a competitor’s marketing. They say nothing about how fast we work or how good the result is. For that, the only honest evidence is a written scope, a demo, and references we can actually produce on request.
How to get a real number
Three steps, no sales process attached to them.
Send the brief
What you are building, who it is for, what already exists, and your real deadline. Use the request-a-quote form or the form below.
We scope it, fixed fee
A short technical and product scoping phase produces a written scope: what is included, what is explicitly out, and what it costs. You own that document either way.
You decide with the number in front of you
If the fixed price does not work, the scoped range will usually show you how to cut scope instead of guessing. Shrinking the work is cheaper than gambling on it.
What we will not promise
No guaranteed rankings, no guaranteed conversion lifts, no guaranteed revenue outcomes, and no compliance certification. Those depend on factors we do not control.
Get a written scope
Tell us what you are building. We reply within 24 hours and a senior engineer reads every enquiry.