The Working Website
Your customers use the website to understand your offer and make an enquiry. Your team uses the connected records and workflows to manage what happens next. Working Website covers that agreed scope, with handover included.
It takes about one hour a week with the project lead, with additional time around kick-off, final approval and launch. Across the wider team, allow roughly 12 to 20 hours over the whole build, mainly for content, review and handover.
We use fixed working sessions and agreed review windows, so the project can be planned around the business rather than interrupting it.
What is in scope
The pages, and the machinery behind them.
Positioning and information architecture
What the business says, and the order it says it in.
Website design and build
The visible customer experience, built rather than themed.
Enquiry capture and qualification
Enquiries arrive structured, not as unread inbox mail.
CRM and email integration
The enquiry becomes a record, and the record drives the follow-up.
Product or service structure
Information held once, in a shape the site can use.
Analytics
Enough measurement to tell whether any of it worked.
Reusable content workflows
A route from idea to published that does not depend on one person.
AI on defined workflows
Repetitive work with a known shape. Never a layer over everything.
Team handover
The system is operated by the client, not rented back from us.
A separate app or internal product is scoped separately after the review.
Where it starts
Every build begins with the review that scopes it.
Office Review produces the diagnosis and the scope. The implementation is quoted from what it finds, as a separate fixed project.
The largest variable is content readiness. Missing, inaccurate or fragmented source material may require additional client time, extend the schedule or be scoped as separate content work.