Saltwork
Delivery playbook

What happens after they say yes

Selling it is the easy half. This is the order things get done, who does each bit, and how long it should take before the job stops being profitable.

Contents

  1. Who does what
  2. They replied to the audit
  3. Before any money moves
  4. The £750 sprint, step by step
  5. The website build
  6. The monthly plans, and the hours rule
  7. Custom software
  8. When it goes wrong

1 · Who does what

Macka is the face and has a phone. Andrés is the build and has the machines. Almost every problem comes from blurring that line.

MackaAndrés
Sends the outreach, runs the audits, takes the calls, answers the client, chases access, chases payment, signs things Everything technical: the sprint work, the builds, hosting, deployments, the monthly SEO and reporting
Owns the relationship. The client should only ever hear from one person Never contacts the client directly unless Macka asks. Two voices is how confusion starts

The one rule that keeps this working

Macka never promises a date without asking Andrés first. There's an eight-hour time difference, so "I'll check and come back to you within the hour" is always a better answer than a guess. Nobody minds waiting an hour. Everybody minds a missed deadline.

2 · They replied to the audit

The moment that matters most, and the one most likely to be fumbled.

SAME DAY

Reply within a few hours, even if it's shortMacka

Speed beats polish here. A three-line reply the same afternoon lands better than a considered one two days later, because they're deciding right now whether you're the sort of outfit that gets back to people.

If they asked a question you can't answer, say you'll check and give a time you'll come back by. Then meet it.

STEP 02

Don't jump to a priceMacka

The instinct is to send a quote. Resist it. First get them to say out loud what bothers them, because the thing they care about is rarely the thing highest on the audit.

One question does most of the work: "Out of everything in there, what would you most want fixed first?" Whatever they answer is what you quote.

STEP 03

Offer the sprint, not the rebuildMacka

£750 is small enough to approve without a meeting. £3,450 needs a decision, a think, and usually a conversation with a business partner.

Get the first one done, prove it with before-and-after numbers, and the second is a much easier conversation. Nobody buys the big thing from a stranger.

3 · Before any money moves

Four things, always, in this order. Skipping any of them is how jobs go bad.

Contract signed. Scope, what's not included, payment terms, IP transfers on final payment. It's already written — fill in the yellow bits and send it.
Deposit received. 50% up front on the sprint and the build. Not "on completion", not "on invoice". Work starts when the money lands.
Access confirmed and tested. Not promised — tested. Andrés logs in and confirms it works before anything is scheduled.
Dates agreed in writing. After access works, not before. The clock starts from access, and the contract says so.

Access is where sprints die. Not the work — the work is straightforward. What kills the timeline is waiting nine days for a WordPress login that the client's nephew set up in 2019 and nobody remembers.

Ask for all of it in one message, on day one, and be specific. A vague "can you send me access" gets a vague answer. The checklist below gets you logins.

The access list to send them

WordPress admin login (or whatever the site is built on)
Hosting control panel — where the site actually lives
Domain registrar — where the web address is registered. Often a different company, often forgotten
Google account for Analytics and Google Business, or an invite to it
Anything the site depends on — booking system, payment provider, stock feed

Never let them email you a password

Ask them to add hello@saltwork.co.uk as a user instead, which is safer for everyone and means access can be revoked cleanly at the end. If they insist on sending credentials, get them to use a one-time link rather than a plain email. And whatever arrives goes straight into the password manager, never into a chat thread.

4 · The £750 sprint, step by step

The core product. Everything else grows out of getting this one right.

#What gets doneTimeWho
1Measure and screenshot everything first. Full audit saved before touching a thing — this is the "before" half of the proof, and once it's changed you can't get it back20 minAndrés
2Full backup. Files and database. Non-negotiable, even on a small job20 minAndrés
3Images. Resize to what's actually displayed, re-compress, add lazy loading. Usually the single biggest win1.5 hAndrés
4Analytics. GA4 installed and firing, old dead tag removed, Meta Pixel if they want ads later. Confirm real data arrives before calling it done45 minAndrés
5The SEO basics. Meta descriptions, one H1 per page, structured data, Open Graph so shared links show a picture1 hAndrés
6Conversion leaks. Tap-to-call links, a working contact form, WhatsApp if it suits them45 minAndrés
7Whatever they said mattered most in step 2 of the reply, if it wasn't already covered1 hAndrés
8Re-measure and write the after report. Same tool, same page, side by side with the before30 minAndrés
9Send it and get paid. Report, remaining 50% invoice, and the upsell conversation30 minMacka

The numbers

About 6 hours of work for £750, which is roughly £125 an hour. That comfortably clears the 60% margin floor the house runs on.

It stops being profitable past about nine hours. If a job is heading that way — a broken site, a hosting company that won't cooperate, a client who keeps adding things — stop and re-quote. Don't absorb it quietly, because that's how a good product turns into a bad habit.

The before-and-after report is the actual product

They can't see faster loading; a page that takes four seconds instead of eleven just feels normal. What they can see is two numbers side by side, and that's what they'll remember, repeat to other people, and buy again.

Run the audit tool before and after and put both in one message. It takes ten minutes and it's the difference between "he did some work" and "he cut my page weight by 94%".

The upsell, at the right moment

Right after sending the after-report is the best moment you'll get. They're happy, the proof is in front of them, and you've just been easy to work with.

Don't pitch the £3,450 rebuild. Pitch the monthly plan, because it follows naturally: "Now analytics is running, you'll actually have numbers next month. Want me to keep an eye on it and send you a summary?"

5 · The website build

£3,450. Usually sold after a sprint, rarely before.

STEP 01

Content before designMacka

Get every page's text and images agreed and in hand before anything is designed. Building around placeholder text and then swapping it later is how a one-week job becomes a two-month one.

STEP 02

Check what the site depends onAndrés

Booking systems, payment providers, stock feeds. Find out early whether they'll work on a new site. One prospect's booking system only allows embedding on their existing domain — that's a support ticket with a third party, on their timetable, and it can hold a whole project. The contract covers it, but you still want to know on day one.

STEP 03

One round of changes, then it's liveMacka

Say this at the start, not when it's becoming a problem. "One round of changes included, anything after that is quoted separately." Written into the contract, so it's a reminder rather than a new rule.

STEP 04

Hand over properlyAndrés

Logins in their name, a short recorded walkthrough of how to change things, and the invoice for the remaining balance. IP transfers on final payment, so the handover and the payment happen together.

6 · The monthly plans, and the hours rule

Where the real money is, and also where margin quietly dies.

Every plan has an hours cap. Say it out loud at the start.

Without a cap, "unlimited small changes" turns into a client who emails four times a week, and a £450 plan that eats twelve hours. This is a house rule from the Peru side, learned the expensive way.

PlanPer monthHours capEffective rate
Care£1502 hours£75/h
Growth£4506 hours£75/h
Machine£85010 hours£85/h

Over the cap, it's quoted separately. Unused hours don't roll over — otherwise you end up owing someone thirty hours in month six.

What actually gets done each month

WeekCareGrowth and Machine
Week 1Updates, backups checked, uptime reviewedSame, plus the month's content or page work
Week 2Google Business post, review requests sent out
Week 3Client's change requestsClient's change requests, ad adjustments if on Machine
Week 4The report. Non-negotiable

The monthly report is what stops them cancelling

Retainers don't get cancelled because the work was bad. They get cancelled because nobody could remember what they were paying for.

Keep it to one page in plain English: what changed, what the numbers did, what's next month. Same date every month. If a month is quiet, say that honestly — silence is what gets you cancelled, not a slow month.

7 · Custom software

The £8k–25k work. Different rules, because the risk is different.

Discovery first. Always. No exceptions.

£1,000–£2,000, two or three sessions mapping how the job actually flows today, ending in a written spec they own and keep.

Three reasons it's non-negotiable: you can't price a build you haven't scoped, it filters out people who were never going to buy, and if they won't pay £1,500 to find out what they need, they were never paying £15,000 to have it built.

8 · When it goes wrong

THE CLIENT GOES QUIET

Pause the clock, in writing

The contract says dates move by the length of any wait. Send a short, friendly note recording that you're waiting and the dates have shifted. Not a telling-off — a record. Then you're not the one who missed a deadline.

THEY KEEP ADDING THINGS

Quote it, cheerfully, every time

"Happy to do that — it's outside what we agreed so it'd be an extra £X, want me to add it?" No irritation, no lecture. Most people stop asking after the first quote, and the ones who don't are paying for it.

SOMETHING BREAKS AFTER LAUNCH

Fix it first, work out whose fault it is later

If it's something you did, fix it free and fast — that's how you keep a client for three years. If it's a third party or something they changed, fix it anyway on a small job and mention what it was. Arguing about blame over two hours of work is how you lose a retainer.

THE INVOICE ISN'T PAID

Follow the sequence, don't improvise

Friendly reminder, then statement of account, then letter before action, then Money Claim Online. It's in the paperwork page. Don't skip steps and don't chase over WhatsApp.

The one that actually costs money: agreeing to something over the phone and not writing it down. Every change, every new date, every extra — confirm it in an email afterwards. One line is enough. "Just to confirm what we said: X, by Y, for £Z."

Six months later that email is the only thing that settles a disagreement, and it takes twenty seconds to write.

The short version

Money before work. Access tested before dates. Measure before and after. Cap the hours. Write down what was agreed. Report every month whether or not there's news.