Skip to content
WebAsk

How we work — four stages, no surprises.

Every engagement runs Discover, Design, Build, Grow. Different services, same rhythm — you always know what we're delivering, when, and why.

The fastest way to lose months on a project is to skip the boring parts. We don't. Every WebAsk engagement runs the same four stages so you see the trade-offs early, the work as it happens, and the results in numbers — not just at the end.

The four stages

Discover, Design, Build, Grow.

  1. Discover

    Decide what we're actually solving.

    1–2 weeks

    Discovery is one to two working sessions plus a short async loop. We map your current stack, the user journeys that matter, and the metrics that decide success. We pressure-test the brief — sometimes the right project is smaller than the original ask; sometimes it's bigger. By the end you have a written scope, a phased delivery plan, a fixed-fee proposal (or a capped day rate), and a target launch date. If we don't think we're the right partner, we say so on this call.

    What you receive
    • Discovery write-up — problems, users, success metrics
    • Scope document with in/out of scope, assumptions, and dependencies
    • Fixed-fee proposal (or a capped day rate) with milestones and payment schedule
    • Target dates for Design, Build, and Grow phases
    What we need from you
    • Decision-maker in the room for the kickoff session
    • Access to current analytics, CRM exports, and brand assets
    • Three to five examples of work you admire (and why)
  2. Design

    Make the right thing — before we build the wrong one.

    2–4 weeks

    Design starts with sitemap and wireframes — the parts that matter for SEO, conversion, and information hierarchy. Then we layer on visual design in real working sessions where you see options and trade-offs side by side. Engineering pairs in throughout so the design lands as components, not as Figma frames that need re-interpretation. Two rounds of revisions are built in. By the end of Design you've signed off on every screen and flow, the component system is half-built, and engineering already has the green light to ship.

    What you receive
    • Sitemap and IA
    • Wireframes for every key screen and flow
    • Visual design in Figma — every screen, mobile and desktop
    • Tokenised component system handed off to engineering
    What we need from you
    • Working-session attendance (no email-only reviews)
    • Clear feedback within 3 working days of each delivery
    • Final copy approvals — voice and substance
  3. Build

    Ship the thing, performance-budgeted from line one.

    3–8 weeks

    Build runs in weekly sprints with a preview URL you can open from your phone the moment commits land. Every page is performance-budgeted in CI — Lighthouse runs on every pull request, accessibility is audited end-to-end, and SEO foundations (schema, sitemap, robots, OG) are wired before the design layer. You see the work as it's built; we don't surprise you with a Big Reveal at the end. Pre-launch, we run a complete QA pass on mobile and desktop, validate JSON-LD in Rich Results Test, and submit the sitemap to Google Search Console.

    What you receive
    • Preview URL updated on every commit
    • Accessibility, SEO and page-weight budgets enforced in CI
    • Pre-launch QA report and a launch checklist
    • Production launch with smoke-test verification
    What we need from you
    • Weekly sprint review attendance
    • Final copy, photography, and legal-page sign-off
    • DNS and domain access when you're ready to go live
  4. Grow

    Measure, tune, and keep the asset earning.

    Ongoing

    Launch is a milestone, not a finish line. For 30 days post-launch we're on hand for tweaks, training, and the small things that surface only in real traffic. Beyond that, optional retainers — Maintenance for the asset, SEO for the rankings, CRM for the funnel — keep the work compounding. A care plan includes a quarterly health review: Core Web Vitals, search rankings, lead-flow metrics, conversion rate. We bring the numbers, you bring the questions. The point is to keep the thing we built earning — not to bill you for re-doing it in a year.

    What you receive
    • 30-day post-launch support — bug fixes, copy edits, training
    • Quarterly health review — CWV, rankings, leads, conversion
    • Maintenance, SEO, or CRM retainer if it earns its place
    • Year-one growth plan with named experiments
    What we need from you
    • Access to analytics, Search Console, and CRM data
    • A point of contact who can act on findings
    • Honest feedback when something isn't working
How we work

Seven principles we don't compromise on.

Written scope before any code.

If it isn't in the scope document, it isn't in the build. We re-scope rather than scope-creep — change requests get an honest delta, not a quiet expansion.

Performance is a budget, not a goal.

A pull request that pushes layout shift, main-thread blocking or script weight past budget doesn't merge until it's fixed. LCP is tracked alongside them as a warning — a localhost run under mobile throttling isn't the number that decides anything, so the field data governs it.

Designs reviewed in real time.

Email feedback loses 80% of the nuance. Every design review is a working session — screen-shared, decisions made on the call, captured in writing afterwards.

Honest trade-offs over silent assumptions.

Every meaningful choice (Shopify vs custom, GHL vs HubSpot, native vs React Native) gets named, weighed, and recorded — so future-you knows why this thing is the way it is.

Your data, your accounts.

Domains, hosting, analytics, CRM, repositories — all live in accounts you own from day one. We are a collaborator, not a hostage-taker. If you ever leave, you take everything with you because it was never ours to hold.

The person who scopes it, builds it.

There is no account-manager layer and no offshore handoff, because there is nobody to hand off to. Whoever you speak to in Discover is who commits the code, configures your CRM and answers when something breaks at eight on a Friday.

Regulated sectors get a compliance pass.

If you work in aesthetics, dentistry or anything else where what you may say is governed, the rules shape the build rather than getting bolted on at the end. That means the site structure, the navigation and the copy are checked against the relevant code before launch — and where something sits genuinely close to the line, it goes to the regulator's own free advice service rather than to a guess.

Read the process? Now see if we're the fit.

Book a 30-minute discovery call. We'll either be the right partner or we'll tell you who is.

Book a discovery call