Quoted on scope, agreed in writing
Studio work is priced per project, not from a single rate card. This page explains the four engagement models, what is always included, what is itemised separately, and what happens before any money is committed.
- Quoted after
- A discovery conversation and written scope
- Not published
- Rates and packages still being confirmed
- Separate from
- Library Pricing for developer products
Commercial detail is being finalised
Published rates, package inclusions and support terms are not yet confirmed. Rather than invent numbers, this page shows the structure of a quote and what each part depends on. Ask for current terms in writing.
Engagement models
Four ways a project can be priced
The model follows the work, not the other way round. A defined website and a workflow that needs testing should not be quoted the same way.
Fixed-scope project
01The default for websites and defined application scopes.
After discovery you receive a written scope covering pages, screens, integrations and deliverables. The quote covers that agreed work, with review checkpoints named in the schedule.
Best for ·A clear outcome, a defined deadline, one decision-maker.
Staged application build
02For tools where the workflow needs testing before the full build.
Discovery and scoping are quoted first. Delivery then runs in stages, so you can use and review part of the system before the next stage is committed.
Best for ·Internal tools, portals and processes with exceptions.
Design-only engagement
03For teams with their own developer.
Interface and brand work is scoped by the number of page types and screens. Handover includes component notes and states so build decisions stay consistent.
Best for ·In-house or partner development teams.
Ongoing support
04A small, agreed block of help after launch.
Used for fixes, content changes and small improvements. Terms, response times and inclusions are confirmed in writing before any support begins.
Best for ·Teams who want continuity without a retainer they cannot use.
What a quote contains
Always included, itemised, or explicitly out of scope
This is the part most quotes leave vague. Every proposal separates these three lists so you can compare what you are actually buying.
In every project
- Discovery notes and an agreed scope
- Named review checkpoints
- Staging preview before launch
- Launch checks and handover
- A single point of contact
Itemised separately
- Copywriting and content migration
- Photography or illustration
- CRM / ERP / AI integrations
- Extra page types beyond the agreed set
- Additional editor training sessions
Not included by default
- Hosting and domain fees
- Ongoing maintenance after support ends
- Third-party subscription costs
- Brand new features after launch
- Advertising or SEO campaign management
Process
From conversation to a written scope
Nothing is charged before scope is agreed. If the project is not a fit, we will say so at this stage rather than after a proposal.
- 1
Discovery conversation
What the business needs, who maintains it, and any systems that must connect.
- 2
Scope document
Page types, screens, deliverables, exclusions and review checkpoints.
- 3
Written quote
Cost per stage, payment stages and the assumptions the quote depends on.
- 4
Approval and kickoff
Work starts after you approve the scope in writing.
Quoted on scope, agreed in writing
There is no single headline rate that would hold across a brochure site, an application and an integration. Scope is agreed before work starts.

Content and integrations itemised
Writing, migration and third-party connections are listed separately so you can see what each part adds — and remove it if you do not need it.

Changes handled openly
If scope changes mid-project, we explain the effect on cost and timing before any extra work begins. No silent additions.

Commercial detail being confirmed
Published rates, package inclusions and support terms are being finalised. Anything not yet confirmed is requested in writing rather than estimated here.

Two separate price lists
covers done-for-you studio work.
covers reusable code and membership for developers. Buying a library product does not include studio services, and a studio project does not include code licensing.
FAQs
The awkward questions, answered directly
Start with the scope you can describe
A short description of the problem is enough for a first conversation. We will confirm whether an estimate is possible at that point or whether scoping is needed first.
Developer? Explore the UI Library
Built for creative developers. Every component we design, build, and experiment with contributes to a growing library of reusable Payload CMS blocks and React components, shared with the developer community.