If website design only includes a homepage mockup, which other deliverables should the buyer confirm?

A homepage mockup shows only how one page looks with particular content at a particular size. Buyers should also confirm interior pages, component states, responsive rules, and the boundary between design and development deliverables. If a corporate website includes products, services, or content management, list these as inspectable deliverables so that you can judge whether the design is sufficient to proceed with implementation.

Ask which pages will differ from the single image

List actual page types rather than simply counting URLs. Company profiles, service details, and article pages may have different information structures, while several product pages may share a template. Ask which design covers each page type and where exceptional content belongs. Providing only a homepage does not automatically mean every interior page is included.

Use real materials when checking each page type. Product specifications, long article titles, and a company timeline all affect components and layout. A provisional structure is possible before materials are available, but clearly identify unconfirmed content so that placeholder images are not mistaken for final deliverables. See Corporate Website Deliverables: Designs, Assets, and Code for related checks.

The checklist should cover states that are not immediately visible

Beyond ordinary pages, check interactive states: how to return after opening a menu, whether clicking a button produces processing feedback, what appears when search finds nothing, and which inputs remain after a form error. These may be absent from the homepage image but matter in actual use. Select them according to the project; do not treat nonexistent functions as default requirements. See What Should Corporate Website UI Designs Include? Pages, Breakpoints, and Interaction States for related checks.

Record a component under four headings: object, state, design file, and implementation notes. For an inquiry entry, for example, the object is a form; states include normal completion, missing required fields, submission in progress, and the result. The design file should show visible feedback, while implementation notes explain where the result comes from. Buyers can compare each item without first learning development terminology.

Also ask where fonts, images, icons, and animation assets come from and how they may be used. A photograph in a mockup may not have been licensed for actual use, and a display font may not suit web loading. Confirm separately whether the company supplies an asset, the design team handles it, or it must be purchased. Its appearance in a mockup is not proof of permission.

Responsive deliverables should explain the rules for changes

Desktop and mobile mockups help explain the direction but cannot cover every window width. Ask which areas change from side-by-side to stacked layouts, when navigation changes, whether images are cropped, and what happens when text is longer than expected. Procurement documents need not specify every technical parameter, but buyers should understand the expected behavior when content changes.

Suppose a service name is twice as long as the example: may the homepage card grow taller, and can users still find the button? Asking the design team to show this scenario tests whether the rules are specific. Success means accommodating reasonable content differences while preserving important explanations, rather than merely keeping screenshots tidy.

When confirming a corporate website project with JVDS Design Studio, list design files, development work, and content entry separately and check each scope. Explain the connections between website planning, design, and development as well, so that one party does not expect to deliver images while the other expects a launch-ready site.

Acceptance should support the next stage of work

At acceptance, ask the receiving team to open the files, locate specified interior pages, components, and assets, and check whether the instructions are sufficient to continue production. If rules must repeatedly be filled in through verbal questions, the checklist still has gaps. Record unfinished items as specific outstanding deliverables instead of signing a general statement that ‘all design has passed.’

Agree on revision rounds, file versions, and subsequent walkthroughs too. A content correction and an additional page are different work items and may have different approval processes. Complete delivery does not require endless revisions; it requires clear outcomes for the agreed objects, states, and materials, which the receiving team can understand and use.

Frequently asked questions

Does every interior page need its own mockup?

Not necessarily. Pages with the same structure can share a template, but real content variations and exceptional states should be demonstrated. A page with a unique process or substantially different information structure needs additional design or clear instructions for combining components.

Can interior page visuals still change after the homepage is approved?

They can change within the approved brand principles. If interior content needs clearer hierarchy, explain the reason and impact. If the change affects site-wide fonts, colors, or navigation, reconfirm the related scope and version.