SOW generator from brief + transcript

What it works from

• The client brief
• The scoping-call transcript or notes
• Your SOW conventions and commercial terms

What you get back

• A structured Statement of Work ready to edit and send
• Explicit assumptions and exclusions
• A human review gate on the commercial facts

Why this is expensive by hand

Most SOW disputes trace back to something said on the scoping call that never made it into the document. In practice it shows up as turning a scoping call into a SOW: capture what was actually agreed on the call alongside the written brief, in one document. It is the kind of work that decides whether a recommendation survives scrutiny — and the kind that quietly eats 1 day of senior time whenever it comes round.

How this Skill produces it

Here the same job runs as a Skill. Your material goes in; a structured Statement of Work ready to edit and send comes out, alongside explicit assumptions and exclusions. What sits between input and output is the codified method: thresholds, sequencing and the points where a human confirms a call — all of it visible and editable in the Skill. Net effect: 1 day down to ~15 minutes, no drift between runs, and every conclusion traceable back to the evidence behind it.