Process
The workflow keeps scope, decisions and responsibilities visible. Use the timeline controls or scroll through all seven stages.
Seven-stage workflow
Smaller projects may combine stages, but the underlying questions remain the same: what are we solving, what are we delivering and how will we know it is ready?
You share the offer, audience, goals, existing material, deadline and constraints. A first conversation separates essential requirements from assumptions and identifies unanswered questions.
The discovery findings become a recommended solution with page scope, functionality, responsibilities, indicative milestones, price and explicit exclusions.
The final scope, payment schedule, feedback rounds, content responsibilities, third-party costs and target timing are agreed. A deposit may be required for the work to be scheduled.
Content hierarchy, visual language and responsive implementation are developed together. Review points focus feedback on the decisions that are ready to be made, avoiding a single surprise reveal at the end.
The website is reviewed across relevant desktop, tablet and mobile widths. Navigation, forms, links, focus states, content, accessibility, performance and agreed browser support are tested. Contracted revisions are incorporated.
After final approval, the website is deployed to the agreed hosting account. Domain routing, HTTPS, redirects and key forms are verified. Source files and the agreed management notes are handed over.
Support is optional. It may include monitoring, a defined allowance for minor changes and prioritised technical help. Larger improvements remain separate pieces of work with their own estimate.
Working together
“Make it bigger” is a change. “Visitors miss the primary service” is a problem we can solve together.
One organised round from the decision-makers reduces contradictions and protects the schedule.
The proposal states who writes, supplies, translates and approves content—and by when.
Requests outside the agreed scope are estimated before they become additional work.
Process FAQ
Timing depends on scope and content readiness. A focused landing page may take a few weeks; a larger multi-page site takes longer. The proposal states a realistic schedule and the dependencies that can affect it.
Some structural work can begin, but final design and testing require representative content. The proposal identifies which content must be available at each milestone.
The number and purpose of feedback rounds are defined in the written proposal. Additional rounds or a change in direction can be added after their impact is agreed.
Normally yes. The new version is prepared separately and replaces the current site during an agreed launch window. The exact method depends on the hosting environment.
Ready for step one?
Share what the website should help the business and its visitors accomplish.