The scope of work that protects both parties

Most fractional engagements start with scope defined as a job title — "provide product leadership," "own our go-to-market," "be our fractional CMO." This produces a predictable outcome: scope creep from the client, under-delivery from the operator, and a relationship that deteriorates over three to six months because both parties had different mental models of what was agreed. The scope of work is the only document in a fractional engagement that matters, and most of them are written badly.

Why vague scope is not a starting point — it is a liability

There is a reason fractional engagements start with vague scope: the early conversations between a client and a prospective operator are relational, not contractual. Both parties are trying to establish whether there is a fit, whether they can work together, and whether the operator's experience is relevant to the problem. Specificity feels premature. The client does not want to constrain the engagement before it starts. The operator does not want to look inflexible before the relationship is established.

This dynamic produces SOWs that read like job descriptions: "Provide strategic marketing leadership across brand, demand generation, and product marketing. Collaborate with the leadership team on go-to-market strategy. Manage the existing marketing team." This tells you nothing about what the operator is actually delivering, how much time it requires, what success looks like, or what is explicitly not included. It is a basis for misunderstanding, not a contract.

The consequences of vague scope are asymmetric. The client interprets vague scope as broad mandate — everything that touches the operator's domain is fair game. The operator interprets vague scope as a defined time commitment that covers a reasonable subset of that domain. Neither interpretation is wrong, given the document both parties signed. But they are incompatible, and the incompatibility surfaces at the worst possible moment: when the client asks for something the operator considers out of scope, and the operator's refusal reads to the client as unwillingness to do the job they were hired for.

What a well-written SOW must contain

A well-written fractional SOW has six elements. Most fractional SOWs contain two or three of them. All six are required for the document to actually protect both parties.

A problem statement, not a title. "Fractional CMO" is not a problem statement. "Build the demand generation function from zero to 50 qualified pipeline opportunities per month within six months, with a team of two" is a problem statement. It is specific about the outcome, the timeline, and the resources available. It makes it possible to evaluate at any point whether the engagement is on track. A title-based SOW makes this evaluation impossible.

Defined outputs, not activities. "Attending weekly leadership team meetings" is an activity. "A revised ICP definition with supporting data, delivered by end of month two" is an output. "Developing a content strategy" is an activity. "A 12-month content strategy document, reviewed and approved by the CEO by week six" is an output. SOWs that list activities rather than outputs make it impossible to determine whether the operator is delivering — because attending meetings and writing strategies can happen without producing anything usable.

A time commitment with hard edges. "Approximately two days per week" is not a time commitment. "Eight hours per week, on Tuesdays and Thursdays, with availability for one additional hour on urgent matters with 24-hour notice" is a time commitment. Hard edges protect the operator from being treated as a full-time employee. They protect the client from discovering at month two that the operator has four other engagements and is only available at unpredictable intervals.

An explicit out-of-scope section. This is the element that most SOWs are missing, and it is the one that prevents scope creep. The out-of-scope section names the activities that are specifically not covered by this engagement: managing the sales team, handling customer escalations, attending investor meetings, producing creative assets. Not because these are unreasonable requests in the abstract, but because they are the requests that will arrive if they are not excluded explicitly. The presence of an out-of-scope section makes the response to an out-of-scope request obvious and non-adversarial: "That falls outside the current SOW — would you like to discuss a scope amendment?"

A review cadence with decision points. The SOW should specify when both parties will formally review the engagement — typically at the end of month one and at the midpoint — and what decisions are available at each review: continue as scoped, amend the scope, change the time commitment, or conclude the engagement. Building these decision points into the SOW removes the awkwardness of raising performance or fit issues mid-engagement, because the conversation is expected rather than exceptional.

A definition of done for the engagement. Not all fractional engagements have a natural end date, but all of them should have a defined condition that signals the operator has delivered what they were hired to deliver. "When the demand generation function is producing 50 qualified pipeline opportunities per month consistently for 60 days" is a definition of done. "Ongoing" is not. A definition of done protects both parties from an engagement that continues indefinitely because neither party wants to be the one to end it.

How to negotiate SOW without starting adversarially

The objection to a rigorous SOW negotiation is that it sets the wrong tone for an engagement that is supposed to be collaborative and trust-based. This is a real concern, and it is why the negotiation approach matters as much as the document itself.

The framing that works is: "I want to make sure we both have the same picture of what success looks like. Let me draft a scope document that captures what I understood from our conversations — review it, correct anything that does not match your expectations, and add anything you expected that I have not included." This positions the SOW as a shared communication tool rather than a lawyer's document. The first draft reveals assumptions. The negotiation over the draft surfaces misalignments before they become conflicts.

Two things that experienced fractional operators do in SOW negotiations that less experienced ones do not: they write the first draft themselves, and they propose the out-of-scope section explicitly. Writing the first draft gives the operator control over the framing and forces the client to react to a concrete document rather than starting from a blank page. Proposing the out-of-scope section normalises the concept of explicit exclusions. Clients who resist out-of-scope sections at the SOW stage are telling you something important about how they will behave in month three.

• 01
  Replace the title with a problem statement. Write the SOW's opening section as: "The problem this engagement is solving is [X]. Success is defined as [specific, measurable outcome] by [date]." A problem statement makes the engagement evaluable at every point. A title does not.
• 02
  Define outputs, not activities. Every deliverable in the SOW should be a document, a decision, a metric target, or a system — something that can be checked against a standard. Activities fill time. Outputs produce value. If you cannot define the output, you do not yet understand the problem well enough to start the engagement.
• 03
  Write the out-of-scope section before the in-scope section. Start by listing everything that is not included. This forces both parties to be explicit about expectations and makes the out-of-scope conversation a normal part of scoping rather than a difficult conversation after an unwanted request arrives.
• 04
  Build monthly review gates into the SOW. Specify when both parties will formally review the engagement, what data will be reviewed, and what decisions are on the table. This transforms performance and fit conversations from exceptional events into expected ones.
• 05
  Write the first draft yourself, as the operator. Control the framing. Propose the out-of-scope section. Let the client react to a concrete document. The negotiation over a specific draft reveals misalignments that a verbal conversation never surfaces.
• 06
  Treat resistance to an out-of-scope section as a signal, not an obstacle. A client who will not agree to explicit exclusions at the SOW stage is telling you how they will behave when the engagement is live. Decide whether to proceed with that information, not without it.

Frequently asked questions.