Start with the commercial job
Choose a primary outcome: qualified enquiries, appointments, direct sales or customer self-service. Identify the buyer, the service being sold and the decision the site must support. A brochure site and a transactional system need different work, even if their page counts look similar.
Build a scope inventory
List page types rather than counting URLs alone. Record the owner, readiness and approval path for each content item.
- Content: copywriting, translations, photography, proof and legal text
- Experience: templates, navigation, search, forms and accessibility
- Technology: CMS, accounts, payments, integrations and data migration
- Release: redirects, metadata, testing, training and handover
- Ongoing operation: hosting, licenses, updates, backups and support
Resolve uncertainty before a fixed proposal
If a critical integration, content requirement or migration is unknown, isolate it in a diagnostic or technical proof. The diagnostic should produce an agreed requirement, an evidence-based option and an explicit decision to continue, reduce scope or stop. It should not silently become an open-ended build.
What actually drives the quote
Phaos Lab should estimate work by discipline and phase, then account for external costs, delivery management, quality assurance and identified risk. The customer-facing proposal should separate one-time work from recurring commitments, identify taxes where applicable and state the commercial validity period. Actual rates, supplier quotations and tax treatment must come from the responsible service and finance owners.
Agree the commercial boundaries
Define included deliverables, review rounds, client dependencies, acceptance criteria, payment milestones and change approval. Tie acceptance to observable behaviour, such as a form reaching its intended channel or a language link opening the equivalent page. Avoid promising revenue, traffic or a launch date before dependencies are understood.
Compare proposals on the same basis
Ask each provider to explain who supplies content, what integration means, how failures are handled, who controls the domain and what ongoing support includes. A useful comparison covers total ownership costs and delivery responsibilities. There is no invented market price range in this guide.
Sources and editorial approach
Sources support the referenced concepts. The proposed process is Phaos Lab’s planning synthesis, not a certification or affiliation with the source organisations.
