What belongs in a fractional CMO scope of work
A fractional CMO scope of work should name the deliverables, set the reporting cadence and its audience, put decision rights in writing, list the systems access required and the date it is granted, and define notice and exit. A vague scope is the most common reason these engagements quietly fail.
What deliverables should a scope name
Strategic guidance is not a deliverable. It is a category. A scope that promises strategic guidance and leadership gives neither side anything to check against later. Name the artifacts instead: a quarterly growth plan with budget allocated by channel, a measurement definition document stating which number the business reports on and how it is calculated, a creative testing queue with a stated monthly volume, a monthly performance review with written decisions, and documented account structure notes. Each either exists on a date or does not. Add who produces each one, because a fractional CMO who directs execution is not the same as one who builds every asset.
Reporting is a deliverable too, and it has two parts: cadence and audience. A weekly operating review with the marketing team and a monthly review with ownership are different documents, and a scope that says monthly reporting usually produces only one of them. Say what each report contains, because the choice of metric is a governance decision rather than a formatting one. A report built on platform-attributed revenue and one built on blended revenue and margin support different decisions from the same month of data. The reporting clause and the decision clause interact, which is why what a fractional CMO scope should cover is worth settling in one sitting rather than clause by clause.
Can this person reallocate budget, or only recommend it
This is the clause most engagements get wrong. Both arrangements are legitimate, and only one is usually written down. Recommend only means every shift waits for an approval cycle, which works if the approver is fast and stalls the engagement if not. Reallocation authority means the fractional CMO can move spend between channels inside an agreed band without separate approval, and reports the move afterward. Define the band, the approval path above it, and what requires ownership regardless: new channels, new vendors, contract commitments. Then name who can stop something, because the authority to pause spend that is not working matters more in practice than the authority to add it. Without that clause, an engagement defaults to recommend only, whatever both sides assumed at signing.
With a womens fashion brand, we worked to a scope defined this way. Sales rose 99% while efficiency improved at the same time: ROAS up 7.3%, new customer CPA down 21%, marketing efficiency ratio down 6.7%, new-customer ROAS up 58%, net profit up 136% and net margin up 119%. Net margin is still around 3%, which we state openly.
What access is needed, and what happens at exit
Access is a scope item with a date attached: ad accounts at admin level, analytics, the store backend, the email platform, and whatever reporting tool the business already pays for. A first month spent waiting on permissions is a first month spent guessing, so put the list in the contract with a date beside it and grant it before the start date rather than during the first week. Notice deserves the same specificity, meaning the period itself and what happens inside it. Name who keeps the documentation: measurement definitions, account structure notes, testing history, vendor contacts. That work should stay with the business by default, in a location the business controls. A scope that leaves this unstated tends to leave the knowledge with the person who is leaving.
Before signing, read the scope and ask whether an outsider could tell whether it was met. If not, the clause needs a name, a date, or an owner attached. Plaid Testing runs a free thirty minute audit before any scope is written: tracking, account structure, and three fixes on paper. Scope should follow diagnosis, not precede it.
