The prospect said yes on the call. Then you sent a two-line email — "$1,500/mo, let's go!" — and three weeks later you're in a fight about whether "the agent" included the Spanish line, the CRM write, and unlimited revisions. The deal didn't go bad because of the price. It went bad because nobody wrote down what "done" means. That's what a scope of work and a contract are for. You don't need a lawyer to get the basics right — you need to stop skipping them.
SOW vs. contract: they do different jobs
- The SOW (scope of work) defines what you're building and delivering — the agent, the integrations, the number of revisions, the timeline. It's the anti-scope-creep document.
- The contract (MSA / service agreement) defines the terms of the relationship — payment, term length, liability, what happens when someone wants out. It's the anti-lawsuit document.
For a $1,500/mo local client you can run both in a single 2–4 page agreement. For anything enterprise, keep the MSA standing and attach a new SOW per project. Don't let a big prospect's legal team hand you their MSA without reading it — that's where unlimited liability and net-90 payment terms hide.
What the SOW must nail down
Vagueness always gets billed to you. Be specific about:
- Deliverables. "One inbound voice agent for [use-case]" — not "voice AI." Name the intents it handles and, just as importantly, the ones it doesn't.
- Integrations, by name. "Books to Google Calendar; logs calls to GoHighLevel." If an EHR or a custom API write is in scope, say so — and if it isn't, say that too.
- Revisions. "Two rounds of prompt/flow revisions included; further changes billed at $X or under the monthly." Unlimited revisions is how a profitable build becomes a loss.
- What the client provides. Access to their CRM/calendar, a phone number or porting, knowledge-base content, and a point of contact who can actually answer questions. Note that your timeline starts when they deliver these — client delays are the #1 reason "two-week" builds take six.
- Timeline and go-live. A target date with the dependency ("assuming access provided by [date]").
What the contract must nail down
- Payment terms. Setup fee due upfront (or 50/50), monthly billed in advance, autopay via card/ACH. Late-payment clause. Never start the build on a promise.
- Term and renewal. Month-to-month is easiest to sell but easiest to churn; a 3–6 month initial term protects the setup investment you're partly eating. State auto-renewal and the notice period to cancel (30 days is standard).
- The price escalator. Build a 10–15% annual increase into the contract from day one. Nobody churns over it at signing; everybody negotiates it away if you ask later.
- Usage boundaries. If you price flat, name the fair-use ceiling — "up to 5,000 minutes/month, $0.10/min after" — so a volume spike doesn't quietly eat your margin.
- Liability cap. Cap your liability at fees paid (commonly the last 1–3 months). This one clause is why you read the client's MSA before signing it.
- Ownership and offboarding. State that you own the build/prompts and the client licenses the service; specify what they get if they leave (usually: their data, not your IP). Vague ownership terms turn a cancellation into a hostage negotiation.
The clauses that save you money
Two disclaimers, in plain language, that pre-empt the ugliest disputes:
- AI performance disclaimer. The agent is an AI system; it will occasionally mishandle a call, and the client is responsible for the human escalation path for anything critical. This is not you dodging accountability — it's setting the expectation that "100% perfect" was never the deal.
- Compliance responsibility. For regulated clients (medical, legal, outbound), the client is responsible for their own regulatory obligations (HIPAA BAAs, TCPA consent for the numbers they hand you). You build to spec; you don't indemnify their compliance program.
Keep it human
A contract the client is scared to sign kills momentum. Write it in the same plain voice you sold in, keep it short, and walk them through it on a call rather than emailing a wall of legalese. The goal isn't to win a courtroom — it's that six months from now, when memories differ, there's one document you both agreed to. Get a real lawyer to review your template once; then reuse it on every deal.