The commitment

The 6-Week Guarantee

Last updated: 28 September 2026

A guarantee with no terms behind it is marketing. This page is the terms. It says exactly what we are promising, when the clock runs, when it stops, and what you do if we miss.

What “in production” means

The first agreed version of your system is deployed to a live environment you control, reachable by your real users, running against real data.

It does not mean code complete, a demo, or something sitting on a staging server waiting for you to look at it. If your team cannot use it to do real work, it is not in production and we have not met the guarantee.

What counts as the first version

The scope written into the specification you sign off before we start. That document is the whole definition — not the conversations around it, not the ideas we both had in the call, not anything either of us assumed.

If the spec is vague, that is our problem to fix before you sign it, not a gap we get to argue about in week five.

When the six weeks start

Not when you sign. The clock starts on the first working day after all three of these are true:

• You have signed off the written specification.
• The first invoice is paid.
• We have every access we need — accounts, credentials, data, and any third-party services the build depends on.

We start the clock in writing, on the day it starts, and we tell you the target date in the same message. You should never have to work out whether the guarantee is running.

When the clock pauses

The clock pauses, day for day, whenever we are blocked waiting on you for:

• A decision or approval we have asked for in writing.
• Access to a system, account, or environment.
• Content, data, or assets the build needs.
• Payment of an invoice that has fallen due.

It also pauses for third-party blockers genuinely outside our control — an app-store review, a bank or payment provider’s approval process, a vendor outage.

Every pause appears in that week’s update, with the reason and the revised target date. No pause gets counted retroactively. If we did not tell you the clock stopped at the time, it did not stop.

Changes you ask for

Anything added after spec sign-off is a change request. We will tell you what it does to the date before you decide, and we agree a new target date in writing. The guarantee then runs to that new date on the same terms.

A change request does not void the guarantee. It moves it.

If we miss

If the target date passes and your first version is not in production, and none of the pauses above account for it, then 50% of the setup fees you have paid us to that date comes back to you.

• You claim it by emailing us within 30 days of the missed date. One line is enough.
• We pay it within 14 days of the claim, to the account the invoice was paid from.
• You keep everything we built. Code, infrastructure, documentation, accounts. It is yours, and it is yours whether or not you carry on working with us.
• There is no condition attached. You do not have to stay, re-sign, or accept credit instead of money.

What this is not

It is a guarantee about a date. It is not a guarantee that the software will make your business money, that your users will adopt it, or that it will never have a bug. Those are real risks and we are not pretending to carry them.

It also only covers setup engagements. Retainers are monthly and you can stop them at any time, which is a different kind of protection and does not need a guarantee on top.

Why we offer it

Because you cannot check our references yet, and “trust us” is not an argument. Putting our own fee behind the date is the only version of that argument that costs us something.

It also keeps us honest about scope. A promise like this makes us refuse work we cannot land in six weeks, which is better for both of us than taking it and hoping.

Questions

Ask before you sign, not after. Anything in here that reads ambiguously to you is something we should fix in writing first — get in touch.

These terms sit alongside our Terms of Service. Where the engagement contract you sign says something different, the contract wins.

Last updated: 28 September 2026