A practical website quote comparison worksheet for small businesses
By DOT IT Services
Two website quotations can list the same number of pages and still describe very different projects. One may include copywriting, content entry and launch support. Another may expect the customer to supply finished material, configure the receiving inbox and arrange maintenance separately.
Before comparing prices, turn each proposal into a list of responsibilities and observable outcomes. The worksheet below helps a business owner identify missing information without needing to understand every technical term.
1. Describe the job the website must do
Write down the main action a visitor should be able to complete: make an enquiry, request a quotation, book an appointment or purchase a product. Choose the primary journey first. A brochure website and a booking system should not be compared as if they have identical requirements.
Then name the intended customer and the questions that person needs answered before making contact. For example, a local service buyer may need the service area, typical process, examples of relevant work and a clear way to explain the job.
Avoid treating every possible future feature as a launch requirement. Separate the essentials from optional improvements so suppliers can quote against the same brief.
2. Compare responsibilities, not just features
Copy the following table into your project notes. Fill one column for each supplier using the proposal itself. Mark a missing answer as “not stated” instead of assuming it is included.
| Item | Question to resolve |
|---|---|
| Written content | Who supplies, checks and enters the copy? |
| Images | Who provides images and confirms usage rights? |
| Page layouts | Are unique layouts included, or are pages based on one template? |
| Enquiry form | Who configures the destination and checks that submissions arrive? |
| Existing URLs | Will useful addresses be preserved, and who handles necessary redirects? |
| Editing access | Which parts can the business update after handover? |
| Hosting and domain | Who controls the accounts and pays renewal charges? |
| Paid tools | Which licences are needed, who owns them and what do they cost to renew? |
| Support | What is included after launch and for how long? |
| Acceptance | What evidence is required before the work is approved? |
This is particularly useful when reviewing a small-business website proposal. A starting price is only one piece of information; the agreed scope determines what the business will actually receive.
3. Ask for the enquiry journey to be demonstrated
“Contact form included” does not explain whether it works from the visitor's phone through to the receiving team. Ask for a test using fictional details and confirm that the resulting record can be found in the intended inbox or system.
Check the success message, the error shown when a required field is missing and the behaviour on mobile. A failed submission should not look like a completed enquiry.
If measurement is included, ask what the conversion event represents. A button click is different from a successfully received message. The proposal should identify which outcome the reporting is intended to measure.
4. Record recurring costs separately
A build fee, hosting charge and maintenance arrangement cover different responsibilities. List them separately and ask which costs are required for the website to keep working.
Do not assume that a paid theme or plugin licence transfers to you because it is installed on the website. Ask who owns the licence and what happens if the development or maintenance relationship ends.
Likewise, clarify domain and hosting access. The business should understand how its accounts are controlled and how another authorized supplier could take over if needed.
5. Agree a simple change process
A project can change for good reasons. The important question is how a request becomes an agreed commitment.
For each change, record the requested behaviour, its effect on price and timing, and who approved it. Distinguish a defect against an agreed requirement from a new feature that was never part of the brief.
The same principle applies to a website build with DOT IT: the responsibilities, assumptions and acceptance checks should be agreed in writing rather than inferred from a package name.
6. Make the final comparison
For each proposal, note the complete launch scope, customer responsibilities, recurring costs, acceptance criteria and unresolved questions. Compare those answers alongside the fee and timeline.
A useful decision record is short: why the proposal fits the business, what remains outside the scope and who owns the next step. It helps prevent a low initial price or a long feature list from hiding work that someone still needs to do.
This worksheet is a planning resource. It does not replace the supplier's written proposal or the terms agreed for a particular project.