Goated Designs logo
How we work

No black box. You see it being built.

Most agency horror stories are the same story: a scope nobody wrote down, then weeks of silence, then a reveal that misses. Our process exists to make both of those impossible - the scope is fixed in writing before we start, and there is a live URL from the first week.

48h

From first call to a written scope and a price

Day 1

You get a staging URL and watch it come together

2x

Short check-ins a week - no status theatre

0

Account managers between you and the builders

The ground rules

Three things we don't bend on.

Everything else about the process is negotiable. These three are what stop a project going quietly wrong.

The scope is written before we start

Every engagement opens with a document listing what is being built, what isn't, when it lands and what it costs. You sign that, not a vague retainer. Nothing on it is a surprise later, and nothing off it appears in an invoice.

There is always something to look at

A staging URL exists from the first week and updates continuously. You never wait for a reveal, which means a wrong turn gets caught on day four instead of week six, when fixing it is still cheap.

You talk to whoever is building it

No account manager relaying your feedback to someone who wasn't on the call. The person answering your message is the person writing the code, which is why answers arrive the same day.

Stage by stage

What actually happens, in order.

The same five stages whichever service you buy. Only the length of the middle three really changes - a landing page and a SaaS platform run the same shape at different scales.

Ask about your project
  1. 01

    Scope

    2 to 5 days

    A call, then a written scope. We work out what you're actually trying to change about the business, and what the smallest build is that does it.

    • A 45 to 60 minute call about the business, not the feature list
    • We write down the outcome, the audience and the one thing that has to work
    • Scope split into what's in, what's explicitly out, and what's a maybe
    • A fixed price and a fixed timeline against that scope
    You leave with
    A scope document and a quote you can say yes or no to.
    We need from you
    One person who can make the call, and an honest budget range.
  2. 02

    Design

    1 to 3 weeks

    Structure and message first, then the interface. We design the flows that carry the weight to production fidelity, and build the rest from the same system.

    • Sitemap or user flows agreed in writing before any pixels exist
    • Key screens designed in your brand, not a template with your logo on it
    • A design system - type, spacing, colour, component states - so page five looks like page one
    • Reviewed live on a call, with changes made while you watch
    You leave with
    A clickable prototype of the real flows, and a design system behind it.
    We need from you
    Brand assets, and feedback within a couple of working days.
  3. 03

    Build

    2 to 12 weeks

    Engineering against the agreed design, on a staging URL that updates continuously. The longest stage, and the one where most agencies go quiet. We don't.

    • Staging environment live in week one and updated as work lands
    • Two short check-ins a week - what shipped, what's next, what's blocked
    • Code reviewed before it merges, tests where a break would be expensive
    • Scope changes priced openly rather than absorbed and quietly cut elsewhere
    You leave with
    A working product on staging that you've watched take shape.
    We need from you
    Content, accounts and API access lined up before this stage starts.
  4. 04

    Launch

    3 to 5 days

    The unglamorous checklist. Performance, accessibility, analytics, backups and the cutover itself - done deliberately rather than at 11pm on a Friday.

    • Performance and accessibility pass on real devices, not just a fast laptop
    • Analytics, error tracking and search console connected and verified
    • Backups and rollback rehearsed before we need them
    • DNS cutover with us watching the logs for the first few days
    You leave with
    A live product, monitored, with the keys in your accounts.
    We need from you
    Domain access, and a date that isn't the day before you go on holiday.
  5. 05

    After

    Ongoing, if you want it

    Two weeks of close support is included regardless. What happens beyond that is entirely your call - there's no support contract you get rolled into.

    • Two weeks of close support after launch, included
    • Anything broken that we built is fixed indefinitely, at no cost
    • Full handover - repo, documentation and a walkthrough with your team
    • A retainer or per-project work afterwards, only if it's useful to you
    You leave with
    Everything needed to run it without us, whether or not you do.
    We need from you
    Nothing. This part is on us.
Working together

What it feels like week to week.

Roughly three hours of your time a week, concentrated at the start. The rest of the time you can get on with your job.

One channel, real people

WhatsApp or Slack, whichever you already live in. Messages go to the people building it, and most get answered the same working day.

A URL, not a screenshot

Staging is live from week one. Look at it whenever you like - you don't have to wait to be shown something.

The repo is yours from commit one

Code sits in your GitHub organisation from the start. You can read every change as it happens, and remove us the day you'd like to.

Written summary at each stage

What shipped, what changed, what it means for the timeline - in writing, so nothing important only exists in someone's memory of a call.

Your part

Four things we need, and that's the list.

Every timeline we quote assumes these. When a project slips, it's almost always one of them rather than the engineering - so it's worth being honest up front about whether you can commit to them.

1

One decision-maker who can say yes without convening a committee

2

Feedback inside two working days - the schedule assumes it

3

Content, brand assets and system access ready before the build stage

4

Tell us early when something is wrong; late is expensive for both of us

Questions

About the process itself.

Anything about scope, price or a specific service lives on the FAQ and the service pages.

The same process, per service

Stage one is a conversation.It costs you nothing.

Tell us what you're trying to change about the business. You'll get a written scope and a real number back, normally inside 48 hours.