The 95/7 Ironclad Guarantee

95 or above on every metric, in seven days — or your site is free.

Most guarantees are vague where they should be generous and generous where they should be vague. This one is the other way round. The payout is total and automatic. The only things that don’t count are the ones genuinely outside our hands — and every one of them is stated here, in full, before you ever sign.

The promise

Two triggers. Either one alone makes it free.

Within seven calendar days of your brand assets and content arriving complete — verified by timestamp — your site is live on your own domain, scoring 95 or above on every Google Lighthouse category. The guarantee covers the contracted pages: three on Launch, five on Growth.

Miss the score, or miss the window, and the entire fee is refunded. There is no third trigger and no small print that quietly adds one. Below is exactly what you get when we miss, exactly how the score is measured, and exactly what does and does not count as a miss.

If we miss

The remedy, with nothing to claim.

If we miss, the entire fee for the engagement is refunded to you — and you keep the finished site and the full source code.

The full fee, back
The entire engagement fee is refunded. Not a partial credit, not a discount on the next one — the whole fee.
You keep the site
The finished site and its complete source code are yours. The hosting already included continues unchanged, so the site stays live exactly as delivered.
Nothing to argue
We run the audit ourselves and publish it. If it shows a miss, the refund is issued within five working days — without you asking.
Stated up front
All of this is written into your engagement agreement before you sign, so a miss is settled by a rule you already read, not a negotiation after the fact.

Continued hosting covers keeping the delivered site up and running. It is not an extension of the engagement and does not include further changes, updates, or support beyond what was already contracted — that boundary is there so “your site is free” can never quietly become “you owe us free work forever.” Generous where it costs us nothing; firm only where it would otherwise become open-ended.

How the score is measured

One protocol, published with every build.

A single Lighthouse run on a mid-range phone can swing several points on identical code. So “95 or above” is not one lucky run — it is a fixed, published method, and every run is shown to you, including any that fall below the line.

The number
The median of five Lighthouse runs per page, on your launch date, run against your production URL. All five runs are published in your audit report — including any below the median.
The conditions
Mobile emulation with simulated throttling — the harder of the two profiles, the one a real visitor on a phone actually experiences.
The version
The guarantee is bound to the Lighthouse version current on your launch date. Google changes its scoring between versions; binding to yours means a future release can never retroactively “fail” a site we already delivered.
What’s excluded
Google’s real-world field data (CrUX) is excluded from the guarantee — it needs 28 days of visitor traffic that neither of us controls on launch day. We report it once it exists; we don’t stake the guarantee on it.
We measure our own site this exact way, in public — see The Ledger

How the clock runs

Seven days — and it pauses whenever we’re waiting on you.

The clock does not start until your asset submission is confirmed complete: a vector logo, images at full resolution, your page copy, and domain access. The moment it does, an immutable timestamp is recorded and you receive the exact start time and the exact deadline in writing.

0
Assets confirmed complete
The intake gate checks everything is present, records clock_started_at, and emails you the timestamp and deadline. The clock starts here — not a day earlier.
1
Staging link
A private preview of the real site, live, for your first look.
3
Revision round
Your feedback is due within 24 hours. Every hour beyond that adds an hour to the deadline — the clock pauses while it waits on you, and the pause is logged.
7
Launch + audit report
The site goes live on your domain, and a signed audit report lands at a permanent URL: all five Lighthouse runs, zero-violation accessibility output, page weight, and the full clock ledger — every start, pause, resume and delivery, with reasons.

What counts — and what doesn’t

The exclusions, in plain language.

A guarantee is only honest if the fine print is in the shop window. Every exclusion below is something a fair client would agree with before signing — which is exactly why we state them before you sign, not after a miss.

1

Third-party code you add later

Scores are measured on the site as we deliver it, before any third-party code is added. If a tag manager, chat widget, tracking pixel, embedded video, or marketing script is added afterward — by you, your agency, or any tool — the score guarantee no longer applies to the affected pages. We can’t guarantee the behaviour of code we didn’t write; we’ll gladly advise on which options stay fast.

2

The measurement is the published protocol

“95 or above” means the median of five Lighthouse runs at the version current on your launch date, mobile with simulated throttling, against your production URL. All five runs are published — including any below the median. Field data (CrUX) is excluded; it needs traffic neither of us controls.

3

The clock pauses when it waits on you

Seven calendar days run from the confirmed-complete timestamp and pause whenever we are waiting on you. The full ledger — every start, pause, resume and delivery, with reasons — is visible to you throughout and included in your audit report.

4

Scope is what was contracted

The guarantee covers the contracted pages — three on Launch, five on Growth. Pages, features, or integrations added after intake are a change order with their own agreed timeline, and do not extend or void this guarantee.

5

One remedy per engagement

If both triggers occur, or several pages are affected, the remedy is the same single refund of the engagement fee. It does not compound.

6

Pass-through costs are excluded

Third-party costs paid on your behalf — domain registration, stock imagery licences, commercial font licences — are not part of the refund, because they were not paid to us and cannot be recovered. They are itemised at intake, and they are small.

7

Force majeure, narrowly

A total outage of the hosting platform or the domain registrar lasting more than four hours within the final 24 hours of the window pauses the clock for the duration of the outage. Nothing else does.

8

No claim window is needed

We run the audit and publish it. If it shows a miss, the refund is issued within five working days — you do not have to ask, argue, or file anything.

9

A refund closes the engagement, not the relationship

A refund stands on its own. If you come back for further work — a rebuild, a redesign, additional pages — that is a new engagement with its own scope, price and timeline, and this guarantee applies to it fresh rather than carrying over.

Why it’s shaped this way

Generous payout. Precise trigger.

A guarantee has two independent dials: how generous the payout is, and how precisely the trigger is drawn. Most agencies get it exactly backwards — they promise vaguely and pay reluctantly, the worst combination for both sides.

We turned both dials the other way. The payout is unambiguous and you never fight for it. The trigger excludes only what is genuinely outside our control: your own third-party scripts, your own response time, your own scope changes. Because the build runs on a pre-certified chassis measured far above the line before your project even starts, the realistic chance of a miss is low — and on the rare occasion it happens, paying it fast and in public is worth more to us than the fee. That is the whole point. Nothing can match the human touch — and nothing builds trust like a promise you can read in full before you sign it.

Ready when you are.

Pick a track, send your assets, and the clock starts the moment they’re complete — not a moment before.

The formal version

This page explains the guarantee in plain language. The exact, binding terms — and any project-specific details — live in your engagement agreement, which you read and sign before any work begins. Where this summary and that agreement ever differ, the agreement governs. Read the full Terms before signing.