Count journeys, not just pages
A ten-page brochure and a ten-page customer portal are different projects. List what a visitor needs to do: understand a service, filter a catalogue, request a quote or manage an account. Identify who supplies the writing, images and translations. Include mobile layouts and accessibility requirements in the brief, rather than assuming they are separate polish at the end.
Ask what the quotation actually includes
Use one scope sheet when comparing suppliers. Record included work and exclusions in the same format. This is a buying checklist, not a TCT price list or a claim about Malaysian market averages.
| Area | Confirm in writing |
|---|---|
| Content | Who writes, translates, uploads and approves it? |
| Design | Which templates, responsive views and revision rounds? |
| Functionality | What happens to a real enquiry, payment or booking? |
| Ownership | Who controls the domain, source, hosting and administrator accounts? |
| Operations | Hosting, licences, maintenance and usage fees. |
| Acceptance | Which checks define a completed delivery? |
Define editing and integration needs
If staff need regular updates, agree exactly what they can edit and how drafts are reviewed. Confirm whether an integration uses a supported API, what access is required and how failed updates are handled. A link to a third-party page is not the same deliverable as a synchronised customer portal. Ask for an example of the finished workflow.
Make launch and handover part of the scope
Include redirect mapping when replacing a site, metadata checks, form testing, backup responsibility and administrator training. Agree what counts as a defect versus a new feature and how each is handled. A useful proposal makes these decisions explicit. Bring your current content and a short list of real customer tasks to make the estimate more dependable.