How it goes
1 · We talk
A call or a coffee. You describe what you're trying to build, I ask questions and tell you honestly whether I'm the right fit. No charge, no commitment
2 · NDA, if you want one
If your idea is sensitive and you'd rather have it signed before we get into detail, say so and I'll sign one. Some clients want it before step one — that's fine too. On request
3 · Master Services Agreement
The one-time contract that governs our whole relationship: payment terms, confidentiality, IP ownership, liability limits, and how either of us can end things. Signed once, and every project after this skips straight to step four. Signed once per client
4 · Statement of Work
The project-specific document: what I'm building, what you're getting, the milestones, the timeline, and the price. This is where scope gets pinned down so neither of us is guessing. One per project
5 · Deposit, then build
A deposit starts the work. From there you get regular check-ins and something you can actually click on — not a three-month silence followed by a reveal. Milestone billing
6 · Handoff
Code, accounts, documentation, and access all transferred to you. You leave owning the thing, not renting it. Everything transfers
7 · After
Defects in what I delivered get fixed on my time for a set window after launch. Past that, bring me back as needed or set up a retainer. Warranty window
The Rules
Posted so there are no surprises later.
- We start with an MSA One master agreement per client, signed once. It covers payment terms, IP ownership, confidentiality, liability limits, and termination. Sign it once and every project after that moves faster.
- Every project gets its own SOW Scope, deliverables, milestones, timeline, price. The MSA stays put; the SOW is what changes project to project. If we can't describe it in a SOW, we don't understand it well enough to start.
- An NDA can be signed on request Confidentiality is already covered in the MSA, but if you want a standalone NDA before we talk specifics, just ask. No friction, no charge.
- You own what you paid for The finished deliverable is yours outright — code, accounts, and access all transfer at handoff. I keep rights to the general-purpose libraries and tooling I bring with me, which is what keeps your build from starting at zero.
- Scope changes get written down New ideas are welcome. They become a change order or a new SOW rather than quietly stretching the original timeline — which protects your budget as much as my schedule.
- Deposit up front, then milestones A deposit starts the work, with the balance tied to milestones in the SOW. Invoice terms are set in the MSA so they're the same on every project.
- Bugs are on me after launch Defects in delivered work get fixed free during the warranty window named in your SOW. New features are billable — repairs aren't.
Want to read the paperwork before we talk? Ask and I'll send the MSA and a sample SOW.
Plain english
MSA — Master Services Agreement
The rules of the relationship. Signed once. Nothing in it is project-specific, which is exactly why it only has to be negotiated a single time.
SOW — Statement of Work
The rules of one project. Signed each time. It hangs off the MSA, so it can stay short and focus on what's actually being built.
NDA — Non-Disclosure Agreement
A promise to keep your idea to myself. Available standalone on request, and also folded into the MSA once that's signed.
Change order
A short written amendment when scope grows mid-project. It says what's being added, what it costs, and what it does to the timeline.
This page describes how I like to work — it's a plain-english summary, not the contract itself and not legal advice. The signed MSA and SOW are the documents that actually govern the engagement, and you're welcome to have your own attorney review them before signing anything.