Fractional Statement of Work
When To Use
The fee is agreed and you can already hear "can you also". This skill answers: what exactly did the company buy, how will both sides know a deliverable is done, what is out, and what happens when the asks exceed the days? It is the signed baseline every later change is measured against.
When Not To Use
If you need the working page (who decides what, when your days fall, response times), run Engagement Charter; none of that belongs here. If the fee or the shape is not agreed yet, run Good-Better-Best Engagement Options; a statement of work fixes a deal, it does not sell one.
Inputs
- The agreed option: outcome, days, fee, start date, and any message where scope or dates were agreed
- How you use AI on this work, in a line, and what client data you will receive
- The client's own contract or master agreement, if this sits under one
If you have none of this, I start from the agreed fee, the days and a list of deliverables, and mark the output as a first draft.
Approach
The US Federal Acquisition Regulation 37.602 asks that work be described by required results and measurable standards, not by hours or method; a public playbook for fractional executives adds what a part-time senior seat needs in writing: a change rule, review points and exit triggers. The failure this prevents is a deliverable called "leadership" or "ongoing support", which grows every week because nothing said when it was done or what was out.
Workflow
- Ask at most three questions: who signs for the client; does this sit under a master agreement; what did you agree should happen when asks exceed the days?
- Write the outcome in one sentence, in the client's terms, then the days per month and their shape (fixed days, or a number to place each month).
- Write each deliverable as a noun you hand over or a result someone can check, with acceptance criteria a third person could verify: what it contains, who reviews it, how long they have. "The CEO is happy" is not a criterion.
- List the assumptions the fee rests on (access, a named owner for execution, review turnaround, the CEO's time), each with what happens if it fails. Then the exclusions, in plain words.
- Write the overflow rule: when asks exceed the days, they roll to next month, swap with a named item, or go through a priced change before work starts. Then the review date and the exit triggers both sides accept (outcome reached, the workload now needs a full-time hire, priorities changed).
- Write the AI use line and the client data line so they match what you do: which tools the data may enter, and that no other client's material is used in this work and none of this client's in theirs.
- Put fee, invoicing and payment terms in plain words. Everything else (status as a contractor, liability, IP, confidentiality, notice) goes on the adviser list: check with a qualified adviser.
Output Format
# Fractional Statement of Work
Client: [name] · Under agreement: [name and date, or none] · Version: [n], [date]
## Outcome and days
[One sentence in the client's terms] · [days per month] · [fixed days / placed monthly]
## Deliverables and acceptance
| # | Deliverable or result | Acceptance criteria | Reviewer | Response time |
|---|---|---|---|---|
| D1 | [noun] | [checkable criteria] | [role] | [days] |
## Assumptions and exclusions
| Assumption the fee rests on | If it does not hold |
|---|---|
| [access, owner, turnaround] | [scope change request before work continues] |
Not included: [exclusions in plain words]
## Overflow, review and exit
Overflow rule: [roll / swap / priced change] · Review date: [date] · Exit triggers: [list] · Notice: [as agreed]
## AI use and client data
[How AI is used on this work] · [Where client data may go; no other client's material is used here, and none of yours elsewhere]
## Fee and terms
[Agreed fee] · [invoice date] · [payment terms] · Marked for an adviser: [contractor status, liability, IP, confidentiality, notice]. Check with a qualified adviser.
## Decision
[Your name] and [client signatory] sign by [date]; from then on every change goes through a scope change request.
Done When
- Every deliverable has acceptance criteria a third person could check
- Exclusions and the overflow rule are in plain words, and the AI and data lines match what you actually do
- The fee, days and dates match what was agreed exactly
Quality Bar
- Fees, days and dates come from what you agreed; Claude adds no number of its own
- No open-ended deliverable such as "support" or "ongoing advice"
- No decision-rights list, response-time rule or meeting rhythm here; those live in the Engagement Charter
- Legal terms are listed for the adviser, never drafted; whether the engagement could look like employment is a question to check with a qualified adviser
- Nothing is invented, and no clause, fee or wording is copied from another client's contract
Next
Run frac-engagement-charter (Engagement Charter) to agree the working page that sits beside this baseline.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: frac-statement-of-work3description: Writes the signed commercial baseline of a fractional engagement, with the outcome, days per month and their shape, deliverables with checkable acceptance, the assumptions the fee rests on, exclusions, the overflow rule, the review date and exit triggers, the AI use and client data lines, plain fee terms and a list of points for an adviser. Use for "run frac-statement-of-work", "write a statement of work for a fractional role", "fractional SOW", "turn what we agreed into a statement of work", "stop scope creep on my retainer", "what goes in a fractional contract", "exit triggers and overflow rule", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-statement-of-work6---78# Fractional Statement of Work910## When To Use11The fee is agreed and you can already hear "can you also". This skill answers: what exactly did the company buy, how will both sides know a deliverable is done, what is out, and what happens when the asks exceed the days? It is the signed baseline every later change is measured against.1213## When Not To Use14If you need the working page (who decides what, when your days fall, response times), run Engagement Charter; none of that belongs here. If the fee or the shape is not agreed yet, run Good-Better-Best Engagement Options; a statement of work fixes a deal, it does not sell one.1516## Inputs17- The agreed option: outcome, days, fee, start date, and any message where scope or dates were agreed18- How you use AI on this work, in a line, and what client data you will receive19- The client's own contract or master agreement, if this sits under one20If you have none of this, I start from the agreed fee, the days and a list of deliverables, and mark the output as a first draft.2122## Approach23The US Federal Acquisition Regulation 37.602 asks that work be described by required results and measurable standards, not by hours or method; a public playbook for fractional executives adds what a part-time senior seat needs in writing: a change rule, review points and exit triggers. The failure this prevents is a deliverable called "leadership" or "ongoing support", which grows every week because nothing said when it was done or what was out.2425## Workflow261. Ask at most three questions: who signs for the client; does this sit under a master agreement; what did you agree should happen when asks exceed the days?272. Write the outcome in one sentence, in the client's terms, then the days per month and their shape (fixed days, or a number to place each month).283. Write each deliverable as a noun you hand over or a result someone can check, with acceptance criteria a third person could verify: what it contains, who reviews it, how long they have. "The CEO is happy" is not a criterion.294. List the assumptions the fee rests on (access, a named owner for execution, review turnaround, the CEO's time), each with what happens if it fails. Then the exclusions, in plain words.305. Write the overflow rule: when asks exceed the days, they roll to next month, swap with a named item, or go through a priced change before work starts. Then the review date and the exit triggers both sides accept (outcome reached, the workload now needs a full-time hire, priorities changed).316. Write the AI use line and the client data line so they match what you do: which tools the data may enter, and that no other client's material is used in this work and none of this client's in theirs.327. Put fee, invoicing and payment terms in plain words. Everything else (status as a contractor, liability, IP, confidentiality, notice) goes on the adviser list: check with a qualified adviser.3334## Output Format35```markdown36# Fractional Statement of Work37Client: [name] · Under agreement: [name and date, or none] · Version: [n], [date]38## Outcome and days39[One sentence in the client's terms] · [days per month] · [fixed days / placed monthly]40## Deliverables and acceptance41| # | Deliverable or result | Acceptance criteria | Reviewer | Response time |42|---|---|---|---|---|43| D1 | [noun] | [checkable criteria] | [role] | [days] |44## Assumptions and exclusions45| Assumption the fee rests on | If it does not hold |46|---|---|47| [access, owner, turnaround] | [scope change request before work continues] |48Not included: [exclusions in plain words]49## Overflow, review and exit50Overflow rule: [roll / swap / priced change] · Review date: [date] · Exit triggers: [list] · Notice: [as agreed]51## AI use and client data52[How AI is used on this work] · [Where client data may go; no other client's material is used here, and none of yours elsewhere]53## Fee and terms54[Agreed fee] · [invoice date] · [payment terms] · Marked for an adviser: [contractor status, liability, IP, confidentiality, notice]. Check with a qualified adviser.55## Decision56[Your name] and [client signatory] sign by [date]; from then on every change goes through a scope change request.57```5859## Done When60- Every deliverable has acceptance criteria a third person could check61- Exclusions and the overflow rule are in plain words, and the AI and data lines match what you actually do62- The fee, days and dates match what was agreed exactly6364## Quality Bar65- Fees, days and dates come from what you agreed; Claude adds no number of its own66- No open-ended deliverable such as "support" or "ongoing advice"67- No decision-rights list, response-time rule or meeting rhythm here; those live in the Engagement Charter68- Legal terms are listed for the adviser, never drafted; whether the engagement could look like employment is a question to check with a qualified adviser69- Nothing is invented, and no clause, fee or wording is copied from another client's contract7071## Next72Run frac-engagement-charter (Engagement Charter) to agree the working page that sits beside this baseline.7374## About the makers7576This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).