Project Terms

Plain English, no legalese. This is what you're agreeing to when you pay a deposit, and what I'm agreeing to when I take it. Read it — it protects both of us.

1. Scope of Work

What gets built is what's listed in your bundle, plus what we agree to in writing before the build starts. The bundle features are the scope. Anything outside them is a change request.

Before I start, we'll confirm the details over Discord or email. That written confirmation becomes the definition of "done." If it isn't in the bundle and it isn't in that confirmation, it isn't in the project.

2. Changes and Additions

Projects evolve — that's normal, and small tweaks are part of the deal. But if you ask for something that meaningfully expands the work (a new feature, a redesign, a different platform), that's a change request.

I'll quote it before doing it. You can approve it, decline it, or defer it. I won't quietly do extra work and surprise you with a bill, and I won't quietly drop things either.

3. Revisions

Each bundle includes a set number of revision rounds (listed in the bundle details). A revision round means: you review the work, send me a consolidated list of changes, I make them.

4. Payment

The deposit is non-refundable once work has begun. It covers the time I've set aside for you and turned down other work to protect. If you cancel before I've started, I'll refund it.

5. If You Go Quiet

This one matters, so I'm being direct about it.

I can't finish a project without you — I'll need feedback, assets, and answers along the way. If I ask for something and don't hear back:

I'll email you before either of those deadlines hits. You won't get blindsided.

6. If I Go Quiet

Fair is fair. If I stop responding for 14 days without warning you, you get your deposit back in full — no argument, no hassle.

If something comes up on my end (illness, emergency), I'll tell you and we'll agree on a new timeline or I'll refund you. I don't disappear.

7. Cancellation

8. Ownership & Intellectual Property

This section matters, so I'm being precise rather than vague. There are two different things inside every project, and they're owned differently.

What you own, outright and forever

When your final payment clears, you own the Deliverable — the finished, working thing I built for you. Specifically:

You get the full source. You can modify it, extend it, resell it, hand it to another developer, or throw it away. No subscriptions, no license fees, no lock-in, no permission needed from me. Ever. I will never resell your project, your business logic, or your branding to anyone else.

What I keep — and why you should want me to

I retain ownership of my Background IP: the generic, reusable engineering that exists independently of your project and that I bring to the work rather than invent for it. This includes:

Plain English: if I write a function that checks whether an email address is valid, you own the copy of it sitting in your codebase. I do not lose the right to ever write an email validator again. If I build you a login system, you own your login system — I keep the right to build login systems.

Every developer on earth works this way. A carpenter who builds you a cabinet doesn't surrender the right to use a chisel afterward. Background IP is the chisel.

The line between them

The test is simple: would this code make sense in someone else's project, with the names changed?

You receive a perpetual, irrevocable, royalty-free license to use, modify, and distribute any Background IP embedded in your Deliverable, as part of that Deliverable, forever. You never have to think about this again, and nothing I keep can ever be used to hold your project hostage.

I will never reuse your branding, your content, your business logic, your data, your credentials, or anything you've marked confidential. Not in another project, not in a template, not anywhere.

Before final payment

Until the balance clears, the work remains mine and is licensed to you only for review. Once you've paid in full, ownership transfers automatically — no extra paperwork, no signature required.

9. What You Provide

I build. I don't design logos or produce branding assets. You'll need to bring:

You confirm you have the right to use everything you send me. If you hand me copyrighted material you don't own, that's on you, not me.

10. Hosting and Third-Party Costs

The build price covers my labor. It does not cover ongoing third-party costs — hosting, domains, API fees, database services. Those are yours, in your own accounts, under your own name.

I'll set them up and show you how they work. You own them, which means nobody can hold your project hostage — including me.

11. Support After Delivery

Bundles that include post-launch support cover bug fixes — things that don't work as we agreed they would. That's free, within the window listed.

New features, new requests, and changes after delivery are billed as new work. I don't disappear after delivery, but "still around" isn't the same as "free forever."

12. Limitation of Liability

I build carefully and test my work. But software is software.

My total liability for any claim is limited to the amount you paid me for the project. I'm not liable for indirect or consequential damages — lost profits, lost data, business interruption, or downtime.

You're responsible for backing up your own data and for testing the work in your environment before relying on it in production.

13. Reviews & Showing the Work

Two small asks at the end of a project. Both are optional, and saying no to either costs you nothing — not a discount, not priority, not goodwill.

A review. If the work was good, a few honest sentences help more than you'd think. I'm building a reputation from nothing, and a real client saying real words is worth more than anything I could write about myself. If the work wasn't good, I'd rather hear that directly so I can fix it.

Showing the work. I'd like to display what I built for you in my portfolio — screenshots, a description, maybe a link. This is how future clients decide whether to trust me.

You control exactly how much of that happens. Any of these is fine, just tell me which:

Default: I'll ask before posting anything. If you don't answer, I assume no.

Regardless of what you choose, I will never publish your data, your credentials, your customers' information, your internal business details, or anything you've marked confidential. That's not a preference — it's a hard line, and it holds even if you say "show everything."

14. Governing Law

These terms are governed by the laws of the State of Florida, USA.

Last updated: July 2026

Back to Start a Project