Shape the experience
Turn your brief, audience and content into a page structure and clear visitor journeys. Bring missing content and competing priorities into the review.
Hand-over: sitemap, page outlines and content questions.
02 / Web designer & integrator
Good ideas.
Made for the web.
Your brand has a point of view. Give it a colleague who can carry that intention from the first layout to the last responsive detail.
Discuss this roleA place in your team / Role 02
An eye for the design.
A hand in the build.
For studios, agencies and companies with a website to launch or a growing list of pages to improve. A defined role that connects visual thinking with the work of implementation.
The responsibilities
Give the work
a clear owner.
Choose a first responsibility, agree the expected output and define the way it will be reviewed.
Develop the visual direction
Explore typography, colour, composition and image treatment within your brand. Prepare a coherent direction for your creative lead to approve.
Hand-over: key-page concepts and a focused visual rationale.
Design the interface
Develop the approved direction across page types, navigation, forms and important states. Work through mobile layouts as part of the design.
Hand-over: page layouts, component specifications and responsive behaviour.
Integrate the approved design
Build the pages in the agreed stack. Translate spacing, type, interactions and content into a working website with reusable components.
Hand-over: a working preview and editable source or CMS pages.
Prepare the website for review
Check the agreed breakpoints, navigation, forms and content. Prepare accessibility, performance and browser checks within the project brief, and document outstanding items.
Hand-over: a review list, check results and a clear release checklist.
Keep the website coherent
Create new campaign pages, update content and extend existing components while following the approved visual language.
Hand-over: reviewed updates with a record of what changed.
Example briefs / A starting point
What would you
hand over first?
These are proposed assignments to shape an introduction. Your pilot is defined around your own project, files and review process.
Example 01 / A first website
A first website
“Take our brand and offer, propose the key pages, then build the approved direction into a responsive website.”
Start with
Your brand assets, audience, offer, draft content and preferred publishing environment.
Receive
- Page structure and one direction for approval
- Designed and integrated core pages
- Preview and hand-over documentation
Your team approves the direction, content and public release.
Example 02 / Design to integration
Design to integration
“Bring these approved layouts into our website. Keep the details consistent, including mobile and the form states.”
Start with
Approved layouts, design tokens, content and access to a scoped development environment.
Receive
- Reusable components in the agreed stack
- Responsive implementation and interaction states
- A comparison against the approved layouts
Your designer reviews fidelity; your site owner approves the release.
Example 03 / The ongoing website
The ongoing website
“Prepare our next campaign page and bring the older pages back into line with the current brand.”
Start with
The existing website, campaign brief, current brand rules and a prioritised page list.
Receive
- Page updates and campaign layouts
- Consistent components and content structure
- A reviewable change list
Your marketing or creative lead approves the message and publication.
The working rhythm
A hand-over your team can follow.
01
Align the direction
Agree the audience, content, brand references and the website’s next useful action.
02
Design, then integrate
Review the key layouts before carrying the approved direction into the working pages.
03
Review the experience
Inspect the preview, close the agreed checks and prepare the hand-over for publication.
Your environment
The tools you use.
The standards you keep.
Bring your existing design files and publishing setup. Figma hand-offs, Webflow, WordPress and code-based websites are considered during scoping. Access, versions and the exact editing workflow are tested in the pilot.
Design files & brand assetsHTML / CSSReact-based websitesCMS workflowsResponsive previews
How the role is configured A clear working relationship
Prepared with care.
Released with your approval.
ResponsibilityAI colleagueYour team
Visual directionPropose and developApprove the brand expression
Page contentStructure and prepare draftsApprove the message and claims
Website integrationImplement in the agreed environmentReview the preview and changes
Public launchPrepare release stepsAuthorise publication
Other roles / The same considered approach
A different responsibility?
Role 01
The architecture colleague.
A colleague for the drawings, quantities and coordination questions that keep your projects moving.
- Drawing intelligence
- Working quantities
- Project coordination
Role 03
The developer in your team.
A colleague for the features, fixes and integrations on your backlog, working within the conventions of your codebase.
- Feature development
- Bug investigation
- APIs & integrations
Role 04
The marketing colleague.
A colleague who learns your audience, voice and priorities, then prepares the content, campaigns and reporting that keep your marketing moving.
- Brand & content
- Campaign preparation
- Performance reporting
Private access / Web designer & integrator
Your next website.
A colleague to carry it through.
Tell us about the work, your current environment and the person who would review the result. The first assignment starts there.
Request an introduction