Define the pages and buying journey
We map how visitors arrive, what they need to understand and which action each page supports. The page plan distinguishes general marketing content from product information, help and transaction screens. For e-commerce, we review catalogue structure, variants, stock, shipping regions and the information needed before purchase. Those requirements influence platform choice and integrations. We also identify who supplies copy, imagery and policies, and when they must be available. A design built on placeholder content can hide real problems, so representative material belongs in early reviews rather than appearing only just before launch.
Choose the publishing and commerce approach
The technical plan considers how your team updates content, how products are managed and where transactions happen. We compare the required capabilities with the complexity of maintaining them, rather than choosing a custom system automatically. A content-managed site and a shop with operational integrations have different needs. Checkout, notifications and payment-provider connections are scoped around the chosen platform and account responsibilities. We plan responsive layouts, accessible interactions and loading behaviour alongside the visual direction. Where custom code is appropriate, its role and ongoing dependencies are documented so the site can be understood after handover.
Review the paths that matter before release
Working pages are reviewed through regular demos on a live URL. We check navigation, forms, content editing and the agreed commerce paths, including failed or interrupted transactions where relevant. Release preparation covers deployment, domain configuration responsibilities, redirects and the operation of external services. Transactional emails or payment processing must be checked in their intended environment; a local preview does not establish that they work. Your team receives the agreed source files, account ownership and operating documentation. Maintenance or further optimisation is a separate scope with clear responsibilities rather than an undefined obligation attached to the build.
We also agree what happens to existing URLs and content during a replacement. A migration may need redirects, retained downloads or updated product links. Those items are inventoried before release, helping avoid a new interface that looks complete while leaving returning visitors or existing search links pointing to missing information.