OUR PROCESS
A clear path from idea to launch.
Good work starts with shared understanding. We connect your business goals with clear design decisions, a considered build, and practical launch preparation. You bring the context; we work through the decisions together, with a review checkpoint before each next step.
Discover & plan
Understand your business, audience, and goals. Define the scope and website structure.
Give the project a useful starting point: a shared understanding of what the website needs to do and what belongs in this engagement.
What we do
- Discuss your business goals, audience, and the problems your current website needs to solve.
- Review available content and branding, then outline the pages and functionality needed.
- Clarify responsibilities, priorities, and dependencies before design or development begins.
What we need from you
Your goals, existing website, brand assets, available content, and the people who will review and approve the work. For ecommerce, share product information and the intended catalog structure too.
Typical outputs
An agreed scope, website structure, and a clear view of the content and decisions needed. The proposal defines which design, development, or ongoing activities are included.
Before we move forward
Confirm the priorities, scope, responsibilities, and website structure together before moving into detailed work.
Design the experience
Shape the visual direction, key pages, and user journeys through collaborative feedback.
Turn the agreed structure into an experience that makes your business recognizable and helps visitors find their next step.
What we do
- Shape the visual direction using your existing branding, or develop identity assets when brand design is included.
- Design the agreed key pages and user journeys, with layouts for desktop and mobile.
- Review the direction together and refine the designs using consolidated feedback.
What we need from you
Brand guidelines, logo files, page copy, and suitable images or product assets. Feedback should explain what needs to change and how that change relates to the agreed goals.
Typical outputs
Website layouts in Figma and responsive desktop and mobile designs. Logo and visual identity assets are included only where the brand design scope calls for them.
Before we move forward
Review the visual direction, key layouts, and content together. Agree the designs to carry into the build, or the final handover for a design-only engagement.
Build & refine
Develop a responsive website and check accessibility, performance, and essential SEO foundations.
Bring the agreed designs into a working website, then check how the experience behaves across screens and everyday use.
What we do
- Develop the agreed pages and editable content structure using the platform defined for the project.
- For ecommerce work, build the scoped product and collection layouts, cart, and checkout setup.
- Refine responsive layouts and check accessibility, performance, and essential SEO foundations within scope.
What we need from you
Reviewed designs, final content, and the access needed for the agreed build. Your team reviews the website journeys and confirms that business and product information is accurate.
Typical outputs
A responsive website with editable content, or the agreed storefront. Functionality and any connections to existing systems need to be defined in the scope rather than assumed.
Before we move forward
Review the working website against the agreed pages and functionality. Identify corrections and confirm readiness for the final launch review.
Launch & support
Prepare for launch, hand over the website, and agree on any ongoing support.
Make the transition from a reviewed website to a live one deliberate, with a clear understanding of who looks after it next.
What we do
- Review content and key journeys, and complete the launch preparation included in the engagement.
- Hand over the website and clarify the access and responsibilities needed to manage it.
- Agree any ongoing website updates, maintenance, or marketing work separately.
What we need from you
Final content confirmation, approval to proceed, and the access required for the agreed launch tasks. Identify who will manage the website and which ongoing needs should be discussed.
Typical outputs
The agreed launch and website handover, with responsibilities made clear. Ongoing support activities are defined for the engagement; they are not automatically included in every build.
Before we move forward
Confirm the final website review and launch responsibilities before going live. At handover, agree what remains with your team and what belongs in any ongoing support scope.
Good collaboration makes the work clearer.
Feedback with context
Bring comments together before a review. Explain the problem or business need behind a request so we can find an appropriate response.
Clear decision-makers
Agree who gathers feedback and who approves the work. Make differing opinions visible so a decision can be made before the next stage.
Shared responsibilities
Identify who provides content, assets, access, and approvals. Flag missing inputs early and discuss how they affect the work.
Review before moving on
Use the agreed checkpoints to assess work against the scope and goals. Review stages and communication arrangements are defined for your engagement.
The same clarity. A different scope.
These stages describe a full website project. The emphasis changes with the work you need, and the proposal defines which activities apply.
Design-only
Focus on the visual identity and responsive website layouts included in scope. The final checkpoint is the design handover; a website build and launch are separate activities.
Website development
Start with the available designs and content, resolve what the build needs, then focus on responsive development, review, and the agreed launch and handover.
Ecommerce
Give product information and catalog structure attention from the start. Design and review the browsing-to-buying journey, including the scoped product pages, cart, and checkout setup.
Ongoing maintenance
Begin with the current website and agreed update priorities. Review changes against those needs; social media or paid advertising activities are discussed where relevant to the engagement.
Questions about working together.
How involved does our team need to be?
Your team provides business context, content and assets, and feedback at the agreed review checkpoints. A clear decision-maker helps turn that feedback into approvals. The review stages and communication arrangements depend on the proposal rather than a fixed schedule for every project.
Does all our content need to be ready before we start?
Bring what you already have so we can assess readiness during planning. We identify missing copy, images, brand assets, or product information and agree who will provide them. Final content is needed to review layouts and website journeys accurately; unresolved inputs may affect the project schedule.
What happens if the scope changes?
Raise new requirements when they become clear. We review how they affect the agreed pages, functionality, deliverables, and dependencies before proceeding. Any changes to scope, pricing, or schedule need to be agreed in the proposal or its update; extra work is not automatically included.
What is included in the handover?
The deliverables depend on the engagement: design work can include identity assets and responsive layouts, while development can include a responsive website with editable content. We clarify access and website management responsibilities at handover. Any ongoing maintenance or marketing support is agreed separately, and specific handover requirements should be included in the scope.