The homepage is often the first page shown in a review meeting. Buyers may approve its look and assume the service, product, contact, and policy pages will follow. Yet each page has a different job. A consistent visual system is useful; copying the same generic section onto every page can leave important questions unanswered.
Build a page matrix from the proposal
List every page promised in the signed scope. For each, record its intended visitor, primary question, main action, content owner, and reviewer. Then add columns for desktop, mobile, links, accessibility basics, and approval. This creates a short acceptance record, not a second design brief.
For a service business, the matrix might say: homepage explains the offer and routes visitors; service page shows deliverables and fit; about page establishes who performs the work; contact page makes a working inquiry path; policy page carries required terms. Your actual pages may differ. The point is to test each page against its own purpose.
Review real content, not visual placeholders
Ask to see staging pages with representative final copy and images. Placeholder paragraphs can hide whether a layout handles a long service name, a detailed qualification statement, or an important disclosure. Check that headings distinguish pages and that staff names, contact details, and pricing claims match the approved source.
Open every template at a narrow mobile width. Look for clipped text, tiny controls, menus that cover content, and a call to action that disappears. Follow the principal link from each page and submit any form on that path with test data. Note the exact URL and device when reporting a defect; “mobile feels off” is hard to fix.
Separate shared components from unique pages
If the quote promises five pages, ask whether it means five distinct designs or one reusable layout populated five times. Either can be suitable, but the review criteria change. Shared navigation, footer, and button styles should be consistent. The offer, proof, FAQs, and action on a service page should answer that service’s specific buyer questions. If unique content or layout work was excluded, ask for a priced option before expecting it.
Use a simple pass/fail review: correct approved content, legible mobile layout, functioning links and forms, and the agreed purpose served. Collect comments in one place and decide which are defects, in-scope revisions, or new scope. Final approval should cover the actual page set, not a homepage image.
ARCHV scope and evidence
ARCHV says its website proposals define pages and layouts and that agreed pages, links, forms, and mobile layouts are checked. The precise number of unique layouts depends on the signed scope. Its quote comparison tool helps you ask whether two page-count promises mean the same work.
One contested public review described secondary pages as weaker than the homepage; the company disputed aspects of the account and cited limited design scope and delayed client feedback. That single account supports a buyer checklist, not a claim that a named provider systematically neglects interior pages.