Studying a business properly is the difference between a website that looks nice and one that earns its keep. This is the exact route we run for every brand - no shortcuts, no mystery phases.
06Phases, every time
4-12Typical weeks
100%Code you own
Scroll ↓
THE ROUTE
We don’t guess. We navigate.
Six stations, in the same order, on every engagement - keep scrolling to walk them left to right.
The six phases
01 → 06
Walk the route.
Keep scrolling ↓
013 - 5 days · ≈8% of the trip
Discover
Who are you, and who are you actually for?
We learn your business before we design a pixel.
Most agencies open Figma on day one. We open a notebook. Before anything gets designed we sit with you, map how the business actually makes money, and find out what your customers are really trying to do.
What we do
Stakeholder interviews with the people who run the business
Competitor teardown - what the market already trained your customers to expect
Audience research and a real definition of who we are building for
Audit of what you have today, and what is quietly costing you customers
What you get
Discovery report
Competitor matrix
Audience profiles
Opportunity list
022 - 4 days · ≈7% of the trip
Define
What are we building, and how will we know it worked?
We turn what we found into a plan you can sign off.
Findings are useless until they become decisions. We agree the goals, write down the numbers that define success, and fix the scope - so nobody discovers a surprise in week six.
What we do
Goals and success metrics, written in numbers not adjectives
Scope and feature list, with what is explicitly out
Sitemap and information architecture
Tech stack chosen for your budget and your team, not our habits
What you get
Project brief
Sitemap
Signed scope
Timeline and milestones
031 - 3 weeks · ≈22% of the trip
Design
What should it feel like to be your customer?
We make it look like you - not like a template.
Design starts in grayscale so structure wins before colour does. Then we build the identity out into a system - type, colour, spacing, components - so every future page already knows how to look.
What we do
Direction and moodboard, agreed before detail work starts
Wireframes for every key screen, mobile first
Full UI design and a reusable design system
Clickable prototype plus two rounds of structured review
What you get
Figma source file
Design system
Clickable prototype
Asset pack
042 - 6 weeks · ≈38% of the trip
Build
Will it still be fast and maintainable in two years?
We engineer it to be fast, scalable and yours.
We build on modern, boring-in-a-good-way foundations. Performance, SEO and accessibility are written in from the first commit, because retrofitting them later costs three times as much.
What we do
Frontend built from the design system, component by component
Backend, database and third-party integrations
CMS wired up so your team can edit without calling us
Performance, SEO and accessibility budgets enforced as we go
What you get
Staging environment
Full source code
CMS access
Integration docs
053 - 5 days · ≈10% of the trip
Launch
Is it genuinely ready for real customers?
We ship it properly - not just upload it.
Launch day is a checklist, not a leap of faith. Everything is tested on real devices, measured against the budgets we set, and handed over with the training your team needs to own it.
What we do
QA across real devices and browsers, not just one laptop
Accessibility and performance pass against the agreed budgets
Analytics, search console and conversion tracking wired up
Deploy, DNS, monitoring and a live handover session
What you get
Live site
Handover documentation
Training session
Launch report
06Ongoing · ≈15% of the trip
Grow
What did real users do, and what do we change next?
Launch is the start line, not the finish.
The first version is our best guess made with the best information available. Real traffic replaces guessing with evidence, and we iterate against what people actually did.
What we do
Monthly analytics review against the metrics we agreed in Define
Iteration sprints on whatever the data says is weakest
Maintenance, security patches and uptime monitoring
A rolling roadmap for what comes next
What you get
Monthly report
Rolling roadmap
Support agreement
Iteration sprints
Then we ship it.
And keep walking ↓
WORKED EXAMPLE · NARPADHAM FOODS
The route, run for real.
Here is the same six phases applied end to end to Narpadham Foods - a traditional foods brand that needed to sell online for the first time.
01
Discover
Found that most buyers were older, on mobile, and abandoning at checkout because delivery cost appeared too late.
02
Define
Set one metric that mattered: completed checkouts. Scoped a catalogue, cart and order tracking, and cut everything else.
03
Design
Built a warm, high-contrast product-led interface with pricing and delivery cost visible on every single screen.
04
Build
Shipped a mobile-first storefront with payments, inventory and order tracking, and a CMS the owner updates himself.
05
Launch
Tested on the low-end Android phones the real customers use, wired up analytics, and trained the team in one session.
06
Grow
Monthly reviews now drive the roadmap - the checkout flow has been through two evidence-led iterations since launch.
