Discovery Call to Scope of Work

The gap between a good call and a sent proposal is where deals go cold. Most of that gap is transcription, not thinking.

That is the gap this drop closes. It is a sales & leads skill built for Claude, and it takes about ten minutes to set up the first time. After that it runs in under a minute.

Who should use it

Consultants and agencies who lose two days writing every proposal.

How it works

The skill file does five things, in this order.

1. Drop in the transcript. Otter, Fireflies, or a raw voice-note transcription all work.

2. Separate stated from implied. The client said X. The client probably needs Y. Keep the two apart.

3. Build deliverables from verbs. Every commitment in the call becomes a line item with an owner.

4. Flag the scope risks. Anything vague gets an assumption line so it cannot become free work.

5. Price in bands. Three tiers with what drops out of each, not one take-it-or-leave-it figure.

What comes back

A deliverables table, an assumptions list, a phased timeline, and three price bands.

The mistake to avoid

Ask it to write the assumptions section first. Assumptions are where margin is protected, and writing them before the deliverables changes what you agree to deliver.

Running it

Save this as SKILL.md inside a folder named after the skill, then drop the folder into your Claude Code skills directory or upload it to a Claude Project. Claude reads the frontmatter to decide when the skill applies, so keep the description line intact. For a one-off run, paste the prompt block directly.

Where this fits

On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.

In the file

Convert this discovery call transcript into a scope of work.

Produce, in order:
1. ASSUMPTIONS, every vague requirement restated as a bounded assumption.
   Format: "We assume X. If X is false, this becomes a change request."
2. DELIVERABLES, table of item, description, owner, acceptance criteria.
3. EXPLICITLY OUT OF SCOPE, five things a client in this industry will
   assume are included but are not.
4. TIMELINE, phases with dependencies, in weeks not dates.
5. PRICE BANDS. Essential / Standard / Complete, and exactly which
   deliverables drop out of the lower tiers.

Quote the transcript when a deliverable came from something the client said.
Mark anything you inferred with [INFERRED].

<transcript>{paste}</transcript>