Turn “optimise the website” into work you can assess
Two proposals can offer “website optimisation” while describing different work. One proposal might reduce image sizes; another might investigate why search is slow. Even if both offer “optimisation”, you need to check which problem each addresses. Compare them through the need addressed and the way delivery will be checked.
Start with the observed issue and affected pages or tasks. “The catalogue waits when filters are used on a phone” gives a clearer scope discussion than “we want a fast website”.
If the right intervention is unknown, investigation may be needed first. Distinguish its delivery—evidence and recommendations—from subsequent implementation. Both have value, but they are different commissions.
A worksheet for reviewing scope
| Item | What to document | Illustrative example |
|---|---|---|
| Need | The problem to address. | Investigate waiting when filtering a catalogue. |
| Starting reference | Pages, tasks and available evidence. | Identified listing and filters; recorded test conditions. |
| Included work | Investigation, changes and dependencies. | Review the journey and apply agreed corrections. |
| Exclusions | What needs a different scope. | Redesign or replacement of a whole integration. |
| Verification | How you will check that the work has been completed correctly. | Repeat the agreed journey and compare with the reference. |
| Handover | What the team receives and included support. | Documented changes, checks and follow-up conditions. |
Review the financial terms too: price and taxes, payment arrangements, the split between investigation and implementation, and how extra work will be approved. Identify third-party costs such as licences or services, and whether they are one-off or recurring.
The schedule should state which information or access is needed to start, what each phase delivers and what the final date depends on. You can then compare the cost and timing of the complete work alongside its technical description.
These examples are neither Nodo91 commercial terms nor requirements for every project. Adapt them to the actual work during the discussion.
Two proposals addressing the same reported issue
Fictional comparison without prices or improvement promises. Both proposals begin with a delay when filtering the same catalogue.
Proposal A: adjustments to page images and files
It includes reviewing and adjusting loading resources on agreed pages, with documented changes and checks. It may be relevant if investigation connects the delay to those resources, but its description does not yet explain how it addresses the filter request.
Proposal B: investigating and fixing the delay when using a filter
It includes reproducing the interaction, reviewing participating components and agreeing a correction after identifying the cause. Changes outside initial scope are defined before execution.
If investigation is commissioned first, agree what you will receive even if the cause remains unresolved: checks performed, findings, limitations and proposed next steps. The quote should distinguish that commitment from a defined correction.
This does not establish that either proposal is better or cheaper. It reveals whether they address the same need and what remains open. Their financial terms can then be compared in context.
Agree how you will recognise a successful delivery
Define an observable outcome and a checking procedure. For numerical targets, identify the metric, tool, configuration, pages and conditions. An initial mobile test and a later desktop test are not equivalent comparisons.
Check related functions too. A change improving a measurement should preserve the agreed behaviour of search, enquiry or checkout. Functional checks belong within acceptance criteria.
A score can contribute evidence. Our article on a favourable PageSpeed result alongside ongoing delays explains its scope. It should not become a standalone promise of sales or rankings.
What the team will need and the support available afterwards
Establish required information and access, who authorises changes and how work will be coordinated with other providers. Make conditions that can change scope or timing explicit.
Before modifying the live website, agree testing and recovery with the team. Afterwards, retain the change record, verification and open tasks. Specify follow-up availability and its duration.
If the proposal replaces substantial parts of the website, revisit the case for improving, partially renewing or rebuilding it. Optimisation and renewal proposals need clearly described scope to be assessed meaningfully.
A clear proposal makes collaboration easier
The worksheet cannot remove every technical uncertainty. It helps agree what will be investigated, how findings will be communicated and what requires further agreement. That clarity supports both parties’ work.
Nodo91 agrees scope before starting and distinguishes assessment, recommendation and implementation. Use our priority matrix when several improvements compete, or tell us about the decision you are considering.