Count the different kinds of work, not just pages.

Content and page types

List the layouts and information structures the site needs. Reusable service pages, staff profiles, resource libraries and location details each bring editing and display decisions. The amount of existing content to review or move also matters.

Store and account rules

Describe product choices, shipping or fulfillment arrangements, account access, subscriptions and bookings where relevant. Include the exceptions staff deal with, not only the simplest purchase.

Custom behavior and connected systems

A CRM handoff, fulfillment integration or custom product rule needs an expected result and a plan for failure. Identify the systems, providers and account owners involved. An unavailable provider feature can affect the scope before development begins.

What the current site contributes

Useful content and working features may be retained. Old links, product data, account records and current orders need consideration before a move. A plan should say which information transfers, how it will be checked and when the live site changes.

Review and handoff

Allow for responsive and keyboard checks, editor tasks, forms and relevant store tests. Documentation and training should match the actual work the team will take over.

• Describe the audience and the site’s main purpose.
• List important page types, products and business rules.
• Name connected providers and who controls them.
• Identify content or data that must be retained.
• State deadlines and what the first release needs to include.

Use those notes to begin a project conversation. You do not need to send account access or private exports with the first inquiry.