Fractional engagement disputes almost never come from bad intent; they come from things nobody wrote down. Whose laptop does the dashboard live on, what happens to the half-finished positioning project at termination, can the operator take a competitor next quarter. Below is the checklist I’d want covered in any fractional CMO contract, from either side of the table. It is a checklist, not legal advice; have a lawyer turn it into your actual agreement.
I’m Andrii Byzov, an AI-native fractional CMO for B2B tech; this completes the hiring kit alongside the job description template, interview scorecard and 90-day plan.
Key takeaways
- Scope as outcomes plus a time budget prevents the most disputes I see; activity lists invite them.
- IP splits two ways: client owns work product, operator keeps pre-existing methods with a license to the client. Write both halves.
- 30-day notice both sides is the common market standard; tie termination to a handover obligation, not just a date.
- Contractor status protects both parties; daily-standup expectations and equipment provisioning erode it.
- Renewal is a decision point, not an autopilot: align the initial term with the 90-day plan gates.
The checklist
1. Scope and deliverables
- Outcomes for the initial term, copied from the agreed 90-day plan: diagnosis, signed strategy, live dashboard, experiments running.
- The scope shape, named: strategy-only / strategy plus system-building / strategy plus defined execution areas.
- A change mechanism: how scope gets added or swapped (written agreement, effect on fees), so “could you also quickly…” has a process.
- What is explicitly out of scope. One honest paragraph here saves a quarter of friction.
2. Time and availability
- Days per week or hours per month, with a band rather than a false precision (“8-10 days/month”).
- Sync cadence and response expectations (“weekly leadership sync, async response within one business day”), replacing any always-on assumption.
- Treatment of overflow: pre-agreed day rate for work beyond the band, triggered only by written request.
3. Term, renewal and termination
- Initial term aligned to the evaluation gates: 3 months is the honest minimum for the 90-day arc.
- Renewal as an explicit decision with a date, informed by the renewal memo, not silent auto-extension.
- Termination: 30 days written notice both sides (14 inside a trial period if you want one).
- Handover obligation on exit: access transfer, documentation of running systems, final report. This clause is why termination clauses exist.
4. Fees and payment
- Retainer amount, invoicing cadence, payment terms (net 15 or net 30 are common), late-payment consequence.
- What the retainer includes and excludes: tools and ad spend are the client’s costs; travel handled by policy.
- Rate context for calibration: typical market retainers run $5,000-$15,000/month (rates report); a fintech or deep-vertical premium of 20-30% is reported in published guides.
5. IP and work product
- Client owns deliverables created for the engagement: strategies, copy, dashboards, playbooks written for the client.
- Operator retains pre-existing IP (frameworks, templates, methods) and grants the client a perpetual license to keep using whatever was installed.
- AI-tooling clarity, increasingly worth a line: who owns prompts, agents and automation built during the engagement, and whether they run on the client’s accounts or the operator’s. My own practice: systems built for the client run on the client’s accounts, so nothing breaks at exit (why that matters).
6. Confidentiality and data
- Mutual NDA covering numbers, roadmap, customer data on one side; methods and playbooks on the other.
- Data access hygiene: named systems the operator gets access to, accounts created in the client’s workspace (not personal accounts), revocation at exit.
- Reference rights: can the operator name the client and results publicly? Agree now, not after the case study is drafted.
7. Exclusivity and non-solicitation
- Reasonable: no simultaneous engagement with a named list of direct competitors; non-solicitation of staff both ways for 12 months.
- Where good operators typically walk away: broad category non-competes (“no other B2B SaaS clients”). Portfolio work is the fractional model; a named-competitor list protects you without pretending otherwise.
8. Status and liability
- Independent contractor status stated plainly: operator controls how the work gets done, invoices as a business, no employment benefits.
- Liability capped at fees paid (a common standard for advisory work); operator carries their own professional insurance if your procurement requires it.
- No authority to bind the company without written approval, useful when the operator negotiates with agencies and vendors on your behalf.
Two habits that make the paper matter less
First, the renewal memo ritual: at each term end, results against commitments in writing, then a deliberate renew/adjust/exit decision. Engagements that drift past their usefulness do so because nobody scheduled the conversation. Second, build on client accounts from day one: every dashboard, automation and content system on infrastructure the client controls. It makes the IP clauses mostly theoretical, which is exactly what you want from contract clauses.
If you want a sanity check on an engagement structure before you sign it, either side of the table, message me on LinkedIn.
FAQ
What should a fractional CMO contract include?
Scope and deliverables, time commitment, term and renewal, fees and payment terms, IP ownership of work product, confidentiality, a non-solicitation clause, termination notice on both sides, and contractor status. The scope section prevents the most disputes; write it as outcomes plus a time budget.
Should a fractional CMO sign an NDA?
Yes, and serious operators expect to. They will see your numbers, roadmap and customer data. A mutual NDA is reasonable since the operator also shares their methods and playbooks. What a sensible operator will push back on is a non-compete that blocks working in your broad category.
Who owns the work a fractional CMO produces?
Standard practice: the client owns work product created for the engagement (strategies, content, dashboards), while the operator keeps their pre-existing methods, frameworks and templates, granting the client a license to keep using them. Put both halves in writing to avoid the ugly version of this conversation at exit.
What termination terms are normal for a fractional CMO?
30 days written notice on both sides is the common standard, sometimes 14 days inside an initial trial period. Tie termination to a handover obligation: access transfer, documentation of running systems, and final reporting. Avoid long lock-ins before the first renewal decision.