Our working system

How do we work?

Four steps, something concrete at the end of each, and measurable criteria that must be met before launch. Know what to expect before we start.

Four principles.

However well a process is written, it's these four habits that carry the work. We apply them the same way on every project.

  • One team

    The people who design the interface sit with the people who write the code. Nothing gets lost in the handoff.

  • Metrics first

    Before we start, we agree on what we'll measure. We talk about success in numbers, not taste.

  • Step-by-step approval

    Each step ends with something concrete. We don't move on from a step you haven't approved.

  • Straight talk

    If we're not the right fit, we say so up front. If we see a risk to the timeline, you hear it first.

What happens
at each step?

You know in advance what we do at each step and what you get at the end. Most projects take 6–9 weeks in total.

  1. Step 1

    Discover

    1 week

    Business goals, users and constraints become clear. This is where we decide what we'll measure.

    In this step

    • Agreeing on goals and success metrics
    • User, competitor and current site review
    • Content inventory and technical constraints

    What you get

    • Scope and timeline document
    • List of metrics to track
    • Sitemap
  2. Step 2

    Design

    2–3 weeks

    Flows, interface and design system take shape. Approved through a clickable prototype.

    In this step

    • User flows and page structure
    • Interface design, colour and typography decisions
    • Token and component library

    What you get

    • Clickable prototype
    • Design system library
    • Approved page designs
  3. Step 3

    Build

    3–5 weeks

    We work in weekly deliveries. Every release can be followed live on staging.

    In this step

    • Development with Next.js and TypeScript
    • Headless CMS setup and content models
    • A new release on staging every week

    What you get

    • Reviewable site on staging
    • Content management panel
    • Weekly progress note
  4. Step 4

    Launch and beyond

    ongoing

    We launch after speed, accessibility and analytics checks. Monthly improvements start right after.

    In this step

    • Pre-launch quality checklist
    • Analytics and measurement setup
    • Monthly review with real usage data

    What you get

    • Live website
    • Usage guide for your content team
    • Monthly improvement list

Our launch
criteria.

These aren't targets, they're minimums. A page that doesn't meet them doesn't launch; an effect that strains this budget gets adapted.

  • LCP< 2.0 sLargest content visible on mobile over 4G
  • INP< 200 msResponse time to interaction
  • CLS< 0.05Layout shift while the page loads
  • Lighthouse95+Performance, accessibility and SEO score

Accessibility: WCAG 2.1 AA

  • Every interactive element works with a keyboard and has a visible focus ring.
  • Touch targets are at least 44 × 44 pixels.
  • Headings follow a logical order; every image has descriptive alt text.
  • Form fields have visible labels, and errors are linked to their fields.
  • Colour never carries meaning alone; it's backed by an icon or text.
  • No autoplaying video or animation.

Working together.

Throughout the project you know what happens when. No surprise meetings, no vague waiting.

Weekly rhythm

  1. Start of weekA short planning session. What will be delivered that week is agreed in writing.
  2. During the weekProgress is live on staging. Questions go through a shared channel and are answered the same day.
  3. End of weekA short demo and feedback. Decisions go into the next week's plan.

What we need from you

  • One point of contact who can make decisions
  • Brand assets and existing content — if they're not ready, we plan them together
  • Timely feedback at the end of each step

Technology we use

A setup that loads fast, can be managed by your content team, and doesn't break as it grows.

  • Next.js
  • TypeScript
  • Headless CMS
  • Static generation
  • Edge delivery
  • Analytics

What we don't do

Off-the-shelf theme installs, per-page pricing and promises of unlimited revisions. We don't do these, and if we're not the right fit we'll tell you.

FAQ

How long does a project take?

For most company websites and web applications, the four steps add up to 6–9 weeks. We give you a firm timeline at the end of the Discover step, once the scope is clear.

Can we update the content ourselves?

Yes. With a headless CMS your content team can add pages and content without a developer. Design system rules keep new content from breaking the layout.

How many revisions do we get?

We don't promise unlimited revisions. Changes happen within each step and the step closes with your approval, so the next step is built on solid ground.

What happens after launch?

Speed, conversion and accessibility are tracked with real usage data. Each month produces a concrete improvement list, and we set priorities together.

Do you install ready-made themes?

No. We don't do theme installs or per-page pricing. If that's what you need, we'll tell you up front.

How does the proposal process work?

Tell us what you want to build and we'll reply within two business days with a scope and timeline. If we're not the right fit, we'll say so.

Have a project in mind?

Tell us what you want to build and we'll reply within two business days with a scope and timeline. If we're not the right fit, we'll say so.

Start a project[email protected]