Normalise the scope
Create a table of pages, templates, languages, integrations, data volumes and review rounds. Ask for a specific answer on each row. “Complete website” and “automation included” do not support a meaningful comparison. Record assumptions: a price difference may simply reflect a different understanding of the scope.
Separate build and operation
Separate the initial build from hosting, licences, support, content and API usage. Calculate the first year against an explicit usage scenario, not a guaranteed spending prediction. Identify which charges go to the supplier and which go to third parties, and check whether packages contain overlapping work.
Connect payments to deliverables
A payment schedule should correspond to milestones both parties can recognise. Define the evidence for each milestone: a reviewed prototype, a working flow or accepted handover. Clarify what happens when client materials are delayed. Record terms before work begins; they cannot be inferred from a promotional price.
Ask about handover and exit
Confirm which files, accounts, documentation and exports you will receive. Ask who controls the domain and how maintenance continues if the team changes. Check the terms of the licences used. A useful proposal explains both launch and business continuity after the handover.
Key takeaways
- Compare the same work over the same cost horizon.