Align scope before comparing prices
Two proposals may describe a ten-page website while covering very different projects. One might include ten distinct layouts; the other, a repeated template. Ask which pages will be designed, which interactions are included and what counts as a revision. Comparison becomes useful when deliverables are described at the same level of detail.
Make content work visible
Who writes the copy, selects images and prepares translations? Who uploads product pages or case studies? This work may be yours, the studio’s or shared. Record that allocation explicitly. A lower price that assumes weeks of internal preparation is not directly comparable to a proposal that includes that preparation.
Examine operating costs
Separate the build project from recurring costs: hosting, domain, third-party services, licences and support. Ask who owns the accounts and which features would stop working if a subscription changed. The objective is not a cost-free website; it is understanding the expenses to plan for and the decisions you will remain responsible for.
Compare the handover
Delivery might include training, documentation and a correction period, or simply access to the website. Clarify the support scope and how future changes are requested. Add a “needs clarification” column to your comparison table. A written answer to an important question is more useful than an optimistic interpretation of a proposal.
Your checklist
- The same page list for each proposal.
- Writing, translation and integration explicitly assigned.
- Recurring costs separated from build costs.
- Access, ownership transfer and support documented.
