Prepare the product information before asking for a larger build

A useful preparation pack is small enough to inspect and varied enough to expose the difficult decisions. For an industrial website, several hundred product rows can conceal the same uncertainty repeated hundreds of times. Begin with one family whose examples include a straightforward item, a meaningful variant and a record that needs explanation.

Gather a representative set

Choose a current public page, an approved specification and a blank version of the enquiry the office receives. Identify the person who maintains each. If the public page and specification disagree, record the disagreement; do not quietly choose the more convenient value before the project begins.

Include one historical reference if customers still ask about it. A retired product may need an explanation, a replacement link or continued access to a drawing. Those outcomes require a product decision, not simply a new page template.

Describe what happens after the enquiry

Trace a made-up request through the office. Who checks it first? What information must be present? Which system becomes the working record? If a technical question goes to another person, how does sales know that a response is still outstanding?

The first scope might improve that handoff without introducing a customer login or automatic quotation. Record what staff must be able to see and the evidence that would show the change works. A single complete task is more useful for planning than a list of disconnected screens.

Separate available material from promised material

A drawing that will be supplied later is a dependency. A Polish translation awaiting review is not an approved source. Mark the owner and expected decision for each missing item, especially where it changes the structure of the proposed work.

Name the existing platform and any required business systems. Describe available export or integration facilities without sharing passwords or assuming that a menu option establishes API access. Technical inspection can be scoped where the supported connection is uncertain.

Define who reviews the first result

Identify the product owner, language reviewer, office user and person authorised to accept scope changes. One person may hold several roles, but the decisions remain distinct. Their availability affects when a preview can be assessed.

Write an ordinary acceptance example and an exception. For instance, a buyer finds the selected variant and submits its reference; a buyer following an older drawing receives a clear explanation without being silently moved to a different item.

Bring this preparation to a planning discussion. The scope guide explains the cost questions that follow, and the quotation worksheet helps condense the first task into a short starting point.