THE WEBSITE PROCESS
A website gets easier to approve when each stage has a client input, a Gman deliverable and a visible decision point.
What happens next
The exact working pace depends on scope, content readiness and approvals. Before committed build work begins, we confirm qualification, dependencies, the written scope and any required payment; commercial terms and dates come from that agreement, not this template.
We clarify the offer, audience, proof and the decision the site needs to support.
Client inputs
Business context, audience notes, existing links, constraints
Gman output
A focused project brief and questions worth resolving
Ready when
The primary audience and outcome are clear enough to scope.
We turn the brief into a deliberate page plan, content model and feature boundary.
Client inputs
Priority pages, required tools, must-keep routes
Gman output
Approved sitemap, page responsibilities and build assumptions
Ready when
You approve the page plan before copy and visual production.
Every page gets a job before words are polished. We identify what is ready, missing or needs support.
Client inputs
Draft copy, offers, proof, FAQs and calls to action
Gman output
Content requirements, page outlines and copy direction
Ready when
Required content owners and review points are named.
The visual system follows the business, with clear provenance for every image.
Client inputs
Brand references, original photography, licensed stock and AI concepts
Gman output
Art direction, image shot list and a consistent design language
Ready when
Assets are supplied or clearly marked as still needed.
We make the structure visible early so feedback improves the work instead of reopening scope.
Client inputs
Consolidated feedback from the agreed approver
Gman output
Responsive page designs and a documented design direction
Ready when
The approver signs off the page direction and content hierarchy.
The approved design becomes a working site with the agreed routes and tools.
Client inputs
A client-side invitation or collaborator access for approved services, supplied content and decisions
Gman output
Implemented pages, responsive states and connected integrations
Ready when
The build is ready for a structured QA pass.
We test the experience where people actually use it, then resolve consolidated feedback before launch.
Client inputs
A final fact check, business-critical scenarios and one consolidated review list
Gman output
QA findings, agreed changes and a launch checklist
Ready when
Critical issues and agreed changes are closed, with written launch approval recorded.
We prepare the handoff, make launch responsibilities visible and review early learnings together.
Client inputs
Launch contact, access owner and post-launch observations
Gman output
Handover notes, launch support and an agreed post-launch review
Ready when
Ownership, next actions and the post-launch review are agreed.
Useful resources
Download these working files, fill in what you know and bring the brief to your consultation. Your draft stays local until you explicitly choose Send brief to Gman Design for follow-up.
Download the resources, or open the project brief and explicitly choose Send brief to Gman Design when you are ready for follow-up.