When this scope is useful
The current page cannot explain the offer, support a key action or pass information reliably to the next system.
If the page already works and only one hypothesis needs testing, a conversion experiment may be smaller than a rebuild.
Questions that distinguish the team
- Is a landing page or multi-page site needed?
- Who supplies and approves content?
- What source files, accounts and documentation will be handed over?
Inputs before work starts
Offer, user tasks, content inventory, brand assets, integration requirements and publishing owner.
Three ways to scope the work
These are buyer-side scope models, not an agency price list. Use the inputs, client responsibilities and exclusions below for each model.
01 / Site audit
- Work
- Audit the decision journey, content and accessibility.
- Handover
- Prioritized site brief.
02 / Landing page or website
- Work
- Build a defined landing page or multi-page site with working forms and integrations.
- Handover
- Source files, content, test evidence and account handover.
03 / Maintenance and development
- Work
- Maintain content, dependencies and agreed improvements after handoff.
- Handover
- Maintenance log and documented changes.
Acceptance and shared responsibility
Critical journeys work on mobile and keyboard; forms are tested; the client can update and deploy the handed-over source.
Client responsibilities
Approve content and ownership, provide integration access and nominate a maintenance owner.
What needs separate agreement
Copy production, paid tools, hosting and CRM redesign need explicit inclusion.
Ask for a cost estimate based on the actual access, production volume, integrations and review cadence. A comparable price requires the same scope.
Take this into the brief
Service: Website development Inputs: Offer, user tasks, content inventory, brand assets, integration requirements and publishing owner. Acceptance: Critical journeys work on mobile and keyboard; forms are tested; the client can update and deploy the handed-over source. Questions: Is a landing page or multi-page site needed? Who supplies and approves content? What source files, accounts and documentation will be handed over?
Common buying questions
Is a screenshot a finished website?
No. Inspect navigation, source handoff and actual user actions.
Must a landing page become a full site?
No. Scope follows the information and actions needed by the buyer.
Evidence to examine
Evidence review
One Click Contractor: traffic and MQLs move differently
Different growth rates can be useful for diagnosing the journey, but they do not by themselves prove that a redesign caused the change. Inspect audience mix and qualification rules.
Evidence review
United Elite Group: inspect the advertising-to-CRM handoff
Two buying paths should not share an unexplained lead-quality rule. A homeowner enquiry and a professional partnership require separate definitions and routing.
Sources and review date
Sources read on: 2026-09-11. A source review is not an audit of the agency’s systems.