How Freelancers Can Use Claude Skills to Turn a Discovery Call Into a Statement of Work

Warning: If the call includes confidential pricing, security details, regulated data, or NDA-bound material, only use Claude in a setup that matches your contract terms.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

Problem and who this is for

A discovery call goes well, then the real work starts. You need a statement of work that reflects what the client actually asked for, what you actually agreed to, and what still needs definition. If you rush, you either overscope the job or send something vague that creates revision pain later.

This workflow is for freelancers, agencies, consultants, and solo operators who run discovery calls and need a usable statement of work fast.

Prerequisites

• A Claude setup with Skills available.
• A call transcript or a solid call summary.
• Your preferred SOW sections. Example: scope, deliverables, timeline, assumptions, exclusions, revision policy, investment, approvals.
• A decision on what you will not promise without follow-up.

How to gather the source material

1. Get the call into text. Use a transcript if possible. If not, write a same-day summary while the details are fresh.
2. Pull any pre-call questionnaire, proposal notes, or email clarification into the same working set.
3. Convert odd formats into plain text, DOCX, or PDF.
4. Make one short file called engagement-rules.txt with your standard revision limit, payment terms, and what counts as out of scope.
5. Make another short file called client-context.txt with the client name, industry, and primary success outcome.

Numbered workflow steps

1) Use a doc-coauthoring Skills pattern, not a one-shot draft

The public doc-coauthoring skill is useful here because a statement of work is not just a summary. It is a structured document that benefits from context gathering, section-by-section refinement, and reader testing.

2) Make Claude extract scope facts before it writes the SOW

{
  "task": "Extract scoped project facts from a discovery call for a statement of work",
  "input": {
    "call_transcript_or_summary": "ATTACH OR PASTE",
    "client_context": "PASTE client-context.txt",
    "engagement_rules": "PASTE engagement-rules.txt"
  },
  "rules": [
    "Use only what is explicit in the call or support files.",
    "Separate confirmed deliverables from requested ideas.",
    "Mark anything not yet agreed as [OPEN ITEM].",
    "List assumptions and exclusions separately.",
    "Do not write contract language yet."
  ],
  "output": {
    "confirmed_scope": "What was clearly agreed",
    "possible_deliverables": "Requested items not yet confirmed",
    "timeline_inputs": "Dates, dependencies, approvals, review windows",
    "assumptions": "Items the work depends on",
    "exclusions": "What is explicitly or logically outside the scope and should be stated"
  }
}

3) Sanity-check the scope list yourself

Before Claude drafts anything, remove wish-list items that were only brainstormed. Add anything important that was agreed verbally but did not make it cleanly into the transcript.

4) Draft the SOW

{
  "task": "Draft a statement of work from verified discovery-call facts",
  "input": {
    "verified_scope_input": "PASTE THE REVIEWED OUTPUT FROM STEP 2",
    "document_sections": [
      "Project summary",
      "Deliverables",
      "Timeline",
      "Client responsibilities",
      "Assumptions",
      "Out of scope",
      "Revision policy",
      "Approval and next step"
    ],
    "tone": "professional, plain, specific"
  },
  "rules": [
    "Keep promises narrow and explicit.",
    "Do not turn brainstormed ideas into committed deliverables.",
    "Keep [OPEN ITEM] markers where details are missing.",
    "Use clean business language instead of sales language."
  ],
  "output_format": {
    "type": "structured_document"
  }
}

5) Reader-test the document before you send it

Use the doc-coauthoring pattern's reader-testing idea. Ask Claude to pretend it has never seen the project and list the places where a client could misunderstand scope, timing, or acceptance criteria.

Tool-specific instructions

Claude Skills

• Read the Claude Skills explainer page in the site's Tools menu if the feature is unfamiliar.
• Use the doc-coauthoring pattern for structured documents like proposals, specs, and statements of work.
• If you need a private version with your own section order and contract language, Claude's help documents how to upload a custom ZIP skill.

Quality checks

1. Every deliverable in the SOW can be pointed back to the transcript or a manual confirmation note.
2. Assumptions and exclusions are visible and not buried at the end.
3. Timeline language includes dependencies, reviews, or approval steps where those matter.
4. The document is specific enough that a new reader could tell what is included and what is not.

Common failure modes and fixes

The SOW commits to too much

Fix: separate confirmed scope from optional ideas in Step 2 and keep [OPEN ITEM] markers instead of smoothing them away.

The tone sounds too salesy

Fix: ask Claude to remove persuasive language and keep only operational wording.

The client can still misread what is included

Fix: add a deliverable acceptance line under each major deliverable. Example: what the client receives, in what format, and what counts as one revision.

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: How to create custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-how-to-create-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: doc-coauthoring skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/doc-coauthoring

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Cowork availability, mobile dispatch requirements, project behavior, and supported setup paths.