A price band cannot tell you what a website proposal contains. Two quotes may include different content, integrations, design work and support even when they use the same package name. Compare the deliverables before treating the totals as equivalent.
Describe the Scope in Layers
Core information: services, company details, contact and navigation.
Publishing: content types, editing roles, preview and approval.
Interaction: forms, booking, commerce, accounts or other visitor tasks.
Integration: CRM, payments, inventory or internal systems.
Operation: monitoring, updates, backups, support and handover.
A project can need any combination of these. A small page count with a complex integration may require more work than a larger content site built from shared templates.
A Comparison Table for Proposals
| Proposal item | Record the supplier’s answer |
|---|---|
| Page types and languages | Which unique layouts and translated content are included? |
| Content work | Who writes, supplies images, migrates and enters material? |
| Functions | What exactly happens when a visitor submits, books or buys? |
| Integrations | Which interfaces and permissions have been assessed? |
| Testing | Which tasks, devices, access needs and performance conditions are checked? |
| Approval | How are corrections recorded and changes authorised? |
| Handover | Which rights, accounts, documents and training are provided, and when? |
| Maintenance | What is included, for how long, and what happens afterwards? |
Ask for assumptions and exclusions as well as included items. A useful proposal makes uncertainty visible instead of disguising it as a fixed promise.
Check the Price Basis
Confirm currency, applicable tax treatment, payment milestones and third-party subscriptions. A net amount does not translate into the same final cost for every transaction. Compare renewal and operating costs over the same period.
Do not assume hosting is free for commercial use or that domain renewal is included forever. Check provider limits and the party responsible for each account.
Spend on the Actual Bottleneck
Additional work can be justified by clearer content, accessible interaction, a maintainable editing process or a necessary integration. More animation, more pages or a custom framework do not automatically create more value.
If the aim is more enquiries, inspect discovery, the offer and the contact journey together. If the aim is less administrative work, define the handoff to the team and test it. A website alone does not guarantee demand.
Agree What Happens When Scope Changes
Distinguish correcting work against the agreed requirement from adding a new requirement. Record the effect on price and schedule before proceeding. Keep decisions and approvals in a shared record so the team can identify which version is accepted.
For a wider budget model, see website total cost and the contract checklist.
Working with Q-Dev
Q-Dev is QA10’s software house offering. Scope, price and schedule are agreed for each project. Four gates cover design, MVP, deployment, and training with the start of maintenance. Each gate has a review meeting and an agreed corrections document; after approval, two further rounds of changes to completed work are available at that gate. Changes may affect timing; price changes only outside the contract scope. The first six months of maintenance are included. Code rights transfer after full project payment.
Describe your website project.
Frequently Asked Questions
Can a price band define the complete website scope?
No. Page types, content, functions, integrations, testing and operation determine the work. Compare explicit deliverables and assumptions.
When does Q-Dev change the price?
Price changes only when work goes outside the contract scope. Changes can also affect the schedule, and their impact should be agreed before proceeding.
When do code rights transfer?
For Q-Dev and Q-Journey, rights to the code transfer after payment for the entire project. Third-party components remain subject to their own licences.