Note for the owner: Draft — review before use (not legal advice).

Sprint terms

These terms apply to every sprint. You accept them together with your scope, in your client portal, by ticking a box and typing your full name.

1. The scope is fixed

Your scope is the numbered list of items in the scope you accept, with its price, sprint length and start date. Once you accept it, it is locked. Neither of us can edit it. I build exactly that list.

2. New ideas go on the after-launch list

New ideas are welcome, and none of them enter a running sprint. When you ask for a change during the sprint, it goes on your after-launch list. After launch I quote the list separately, as another sprint or as smaller paid work. Changing the scope needs a new scope version that you accept again, and I only open one after delivery.

3. When the clock starts

The 7-day clock (or 14-day, if your scope says so) starts once you have provided everything the scope needs from you: access to the accounts the product will run on (for example GitHub, hosting, domain, Supabase, Stripe) and the content the product needs (copy, logos, data). If something arrives late, the delivery date moves by the same number of days.

4. What you own

The code is yours. It lives in your GitHub repository, and the product runs on accounts in your name. I never need to keep your passwords or keys: you invite me to your accounts and remove me after handoff.

5. Warranty and bugs

For 14 days after delivery I fix bugs in the items in your scope at no cost. A bug is something in the scope that doesn't work as described. The warranty doesn't cover new features, changes of mind, or problems caused by changes made by someone else.

Report bugs in your portal under Requests, against the scope item they're in, with how bad it is:

When I mark a bug fixed, check it and close it, or tell me it's still broken. If you don't reply within 3 days, it closes; you can always report it again. A bug reported during the warranty is covered even if the fix lands after it ends. If something works as scoped but you want it different, it becomes a change on your after-launch list.

6. Payment

A deposit of 50% of the scope price is due when you accept the scope, and it books your start date. The rest is due at delivery. Work agreed after acceptance, such as a quoted change, is billed as a separate payment.

You can pay by bank transfer or by card (through Stripe). The bank details are shown only in your client portal. I will never email you new or changed bank details; if anyone does, don't pay and contact me first.

If something isn't right, tell me before you contact your bank or card issuer. Bugs in scoped items are fixed under the warranty, and a scoped item that isn't live by the last day gets finished at no extra cost.

7. How we talk

Your client portal is where the project lives: scope, progress, messages, bugs, changes and payments. Keeping it there means nothing gets lost and we both have the same record. Please don't send scope or feature requests over chat apps or text; I answer them in the portal.

8. Your acceptance

When you accept, the portal records the time, your IP address, your browser and a fingerprint (hash) of the exact scope version you accepted, so we both have a clear record of what was agreed.