Method

Six stages, each ending in something you can read and approve

Projects go wrong when the plan lives in someone's head. Ours lives in documents you hold: objectives, scope, content outline, design system, test results and a launch record.

Six sheets of paper showing a layout progressing from rough wireframe to refined design
Rough structure first, refinement second — so agreement comes before effort.
01

Understand

3 to 7 days

Discovery and objectives

We start by finding out what the project actually has to achieve, and whether the brief we have been given is the right one. This stage is deliberately plain: a conversation, a look at your numbers, and a written summary you can check we have understood correctly.

What happens in this stage

  • Written objectives with a measure attached to each
  • Review of current site, analytics, enquiries and search visibility
  • Audience and buyer-question mapping
  • Competitor review, including who currently wins and why
  • Named constraints: budget, timeline, systems, approvals

Your part

One or two conversations with the people who know the business and the customers.

02

Plan

3 to 5 days

Scope and proposal

Everything we intend to do is written down before work begins, including what is excluded. You see the sitemap, the deliverables, the assumptions, the schedule and the price, so there is no ambiguity later about whether something was included.

What happens in this stage

  • Sitemap, page inventory and URL structure
  • Technical specification and platform choice, with reasoning
  • Deliverables list, assumptions and exclusions
  • Fixed price and staged payment schedule
  • Project schedule with client review points

Your part

Review the scope, raise anything missing, and approve in writing.

03

Arrange

1 to 3 weeks

Content and structure

Most delays come from content, so we settle it early. Existing pages are inventoried, gaps identified, and every page is given a defined purpose and a draft outline before design begins.

What happens in this stage

  • Page-by-page content outline and word budget
  • Copywriting or editing support where needed
  • Image, video and document asset list
  • Redirect and content-retirement plan for existing pages
  • Keyword and intent mapping per page

Your part

Supply the raw material or approve our drafts, and confirm facts we cannot verify ourselves.

04

Design

1 to 3 weeks

Design

Structure first, then visual language. We design the argument of each page before styling it, review it as a system rather than a set of screens, and design mobile and desktop together so neither is an afterthought.

What happens in this stage

  • Wireframes for each template
  • Visual design across desktop, tablet and mobile
  • Component and type system
  • Two rounds of consolidated revisions per template
  • Accessibility and contrast checks at design stage

Your part

Consolidated feedback at agreed review points, ideally from one decision-maker.

05

Build

2 to 5 weeks

Build and quality assurance

Development happens on staging with real content. Before launch we test the things that actually break in production: forms, integrations, redirects, slow connections, small screens and every page that matters commercially.

What happens in this stage

  • Build to the approved design across browsers and devices
  • Form delivery, spam handling and confirmation flows tested
  • Speed, image weight and Core Web Vitals work
  • Metadata, schema, sitemap and index controls
  • Cross-browser, mobile and accessibility checks
  • Content proofread on the built pages with your team

Your part

Test the staging site on your own devices and report anything that reads incorrectly.

06

Launch and improve

1 to 2 days, then ongoing

Launch and ongoing care

Launch is a controlled operation, not a hopeful one: DNS changes in a low-traffic window, verification immediately afterwards, and a documented rollback route. Afterwards we review what the site is doing and improve it against evidence.

What happens in this stage

  • Go-live checklist, DNS cutover and SSL verification
  • Redirects, sitemaps and analytics confirmed live
  • Post-launch monitoring and fix window
  • Training and written handover documentation
  • Optional care plan and a quarterly performance review

Your part

Be available on launch day so approvals are not delayed, then review the first month's data with us.

01

Working together

What we need from you, and what you can expect from us

Projects run fastest when both sides know their part. These are the only two lists that matter operationally.

Two people in a first consultation across an oak table in a bright minimal studio
A short scoping conversation prevents most project problems.

What we need from you

  • One decision-maker who can approve design and content without a committee round-trip.
  • Access to analytics, hosting and existing accounts, so we can audit rather than guess.
  • Final content or agreement on our drafts, before design review points.
  • Factual checks on claims, specifications, pricing and certifications.
  • Availability on the launch day so approvals do not stall the cutover.

How we communicate

  • Written update at the end of every stage, against the agreed plan.
  • A single project document holding decisions, scope and open questions.
  • Email to your named contact; no buried chat threads and no verbal-only agreements.
  • Changes quoted in writing before they are carried out, with schedule impact stated.
  • A short post-launch report once real traffic has run through the site.

Direct enquiries: support@growthandcraft.com · Inquiries answered within one business day

Next step

Ready to start at stage one?

Send your objectives and constraints. We will confirm whether we have understood the brief before proposing anything.

Direct contact

support@growthandcraft.com

Inquiries answered within one business day

You keep full ownership of your code, content and data.

Our Process — Six Stages From Brief to Launch | Growth & Craft