Skip to content
unfilteredmargin - home

Our process

No mystery middle. No surprise ending.

A website is easier to judge when you know how it was made. This is the seven-stage process behind every project, including what we deliver, what we need from you, and where approval happens.

Typical project rhythm

Discovery and scope first. Design before build. Production checks before launch. Optional support only after a separate agreement.

  1. 01Stage 1 of 7

    Discovery

    Understand the business, the people it serves, and the job the website has to do.

    We start with a focused conversation and a short written questionnaire. The aim is not to collect every possible requirement; it is to identify the commercial goal, the audience, the constraints, and what a successful first release actually needs to achieve.

    Deliverables

    • Discovery notes and open questions
    • Audience and decision-path summary
    • Competitor and reference review
    • Prioritised requirements
    • Technical constraints and integration checklist

    Your part

    • Share existing brand, content, analytics, and access details
    • Describe the business goal behind the project
    • Nominate one decision-maker for approvals

    Approval point

    You review the discovery summary before any scope or design direction is proposed.

  2. 02Stage 2 of 7

    Scope & proposal

    Agree on exactly what is being built, what it costs, and what each side is responsible for.

    A clear project is easier to build and easier to judge. The proposal defines the pages, functionality, content responsibilities, timeline, revision rounds, payment milestones, and exclusions. If a requirement is uncertain, it is marked as an assumption rather than hidden.

    Deliverables

    • Written scope and page list
    • Fixed project fee and payment schedule
    • Estimated timeline with decision points
    • Revision and change-request terms
    • Content and asset checklist

    Your part

    • Review the proposal and raise questions
    • Approve the scope and pay the deposit
    • Provide required content and accounts by agreed dates

    Approval point

    Work begins only after written acceptance of the proposal and receipt of the deposit.

  3. 03Stage 3 of 7

    Design

    Turn the agreed structure and content into a clear, responsive visual experience.

    Design moves from structure to surface. We establish the information architecture, then the visual direction, then key page designs across desktop and mobile. Content is treated as part of the design, not something poured in afterwards.

    Deliverables

    • Sitemap and navigation structure
    • Visual direction and design tokens
    • Key page layouts for desktop and mobile
    • Reusable component patterns
    • A concise review presentation

    Your part

    • Supply approved copy and assets
    • Review the design at the agreed checkpoints
    • Consolidate feedback into one response

    Approval point

    Development starts after written design approval. Changes after approval follow the revision or change-request process.

  4. 04Stage 4 of 7

    Development

    Build the approved design into a fast, accessible, maintainable website.

    The site is built with semantic structure, responsive layouts, server-rendered pages where appropriate, and a small amount of client-side JavaScript only where it earns its place. Metadata, images, forms, and integrations are implemented alongside the interface rather than left as a last-minute layer.

    Deliverables

    • Responsive page build
    • Reusable components and content structures
    • Working forms and integrations
    • Metadata and social-sharing setup
    • Performance and accessibility passes

    Your part

    • Provide timely feedback on staged work
    • Supply any integration credentials through a secure channel
    • Keep the chosen decision-maker available for clarifications

    Approval point

    You receive a preview link for structured review. Scope changes are quoted before implementation.

  5. 05Stage 5 of 7

    Testing

    Check the parts that are easy to miss: links, forms, keyboards, small screens, and real failure states.

    A visual review is not a test. We verify navigation, routes, responsive layouts, form validation, server responses, keyboard access, metadata, and production-like builds. External services are only confirmed as operational when their credentials have been configured and the real operation has been tested.

    Deliverables

    • Functional and responsive test pass
    • Keyboard and accessibility checks
    • Form success, failure, and validation tests
    • Production build verification
    • Known-limitations list

    Your part

    • Test the preview on devices you actually use
    • Confirm content accuracy and business details
    • Complete any owner-side account or domain verification

    Approval point

    Launch requires your written sign-off on the tested preview and any agreed final fixes.

  6. 06Stage 6 of 7

    Launch

    Move to production carefully, then check the real environment.

    Launch covers deployment, domain and DNS coordination, production environment variables, redirects where relevant, and post-deploy verification. We test the live URL rather than assuming that a successful preview means a successful launch.

    Deliverables

    • Production deployment
    • Domain and DNS coordination
    • Production security and metadata checks
    • Live form and integration verification
    • Owner handover and access record

    Your part

    • Provide domain and DNS access where required
    • Confirm the production content and contact details
    • Complete final payment before handover

    Approval point

    The project is considered launched after the production checks are complete and access has been handed over.

  7. 07Stage 7 of 7

    Support

    Keep the website useful after launch. Support is optional, explicit, and scoped.

    Websites are not finished objects. Dependencies, content, browsers, and business needs change. We offer optional fixed support blocks for agreed updates and checks. There is no subscription, and every block states what is covered.

    Deliverables

    • Fixed update blocks with no recurring subscription
    • Agreed update and support windows
    • Backup and monitoring review where supported
    • A written summary with each support block
    • A clear route for new development requests

    Your part

    • Report issues with enough detail to reproduce them
    • Keep third-party accounts and services active
    • Use agreed channels for support requests

    Approval point

    Each support block starts only with a separate written agreement.

Approvals, revisions & time

A realistic rhythm.

Timelines are estimates, not calendar guarantees. They begin after the deposit and required materials are received, and assume consolidated feedback at each stage.

Delays in content, approvals, access, or third-party verification can move the schedule. We tell you when the critical path changes.

Design feedback

Two consolidated rounds

Typically included, subject to the proposal.

Development fixes

One practical round

For issues within the approved scope.

New requirements

Quoted first

Change requests are priced and approved in writing.

Launch

After sign-off

Production checks and final payment before handover.

What does not count as a revision: a new page, a different navigation model, a new integration, a new feature, or work changed after approval. These are scoped as new work so the original budget stays honest.

Process questions

Before we begin.

All FAQs
How many approval rounds are included?
Most projects include two design feedback rounds and one development revision round. Your proposal may differ. Feedback should be consolidated and sent by the nominated decision-maker.
What counts as a revision?
A revision refines work already in the approved direction, such as adjusting copy, spacing, or an image. A new page, changed navigation model, or new feature is a scope change and is quoted separately.
How involved do we need to be?
One decision-maker should be available for discovery, design review, content approval, and launch sign-off. Projects move fastest when feedback is consolidated and content is supplied on time.

Ready when you are

The first step is a useful conversation.

You do not need a finished brief. Tell us what the business does, what is not working, and what you hope the site will change.

Next step

Have a project in mind?

Tell us what you are building. We will help you find the right approach, scope, and next step — even if you are not ready for a quote yet.