agentleFS
agiea-brainagiea-brain/agency-skills/skills/gary-magnone/delivery-audit-discovery-call/SKILL.md

delivery-audit-discovery-call

Skill1 starsChanged 17 days agoMITView on GitHub

Use this skill when you have 30 minutes with the owner of a professional service firm or agency (an existing customer, a closed-lost contact, or a net new prospect) to find the one client-delivery problem worth building a custom solution or pilot for. Produces a quantified pain (annual dollar figure plus opportunity cost in the owner's own words), a price framing delivered on the call, and a booked next step. Also use for "delivery audit", "AI audit call", "discovery call for a custom build", "scope a pilot", "find the gnarliest workflow", "price on the call".

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    MUST get a named pain before the drill.

    line 42
  2. Distinctive:

    MUST anchor the activity's value before digging into the pain.

    line 43
  3. Distinctive:

    MUST stay on one pain. Park every second pain for the follow-up.

    line 44
  4. Distinctive:

    MUST leave the magic-wand block with an annual dollar figure, an opportunity-cost number, and the owner's own words on why it matters.

    line 45
  5. Distinctive:

    MUST discuss pricing on the call.

    line 46
  6. Distinctive:

    MUST book the next step before hanging up.

    line 47
  7. Distinctive:

    MUST ask for the referral on every call, as a separate last thing.

    line 48
  8. Distinctive:

    NEVER lead with a category list, a dashboard or an audit report before the owner has named their own pain.

    line 49
  9. Distinctive:

    NEVER do the math out loud during the drill.

    line 50
  10. Distinctive:

    NEVER quote the price before restating their figures.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Applies the moment a 30-minute "delivery audit" or discovery call starts with a firm owner. Produces one quantified pain, a price the owner has already justified to themselves, and a next meeting on the calendar before they leave.

The play

Timings are for a 30-minute call. Open references/call-script.md for the exact lines in each block and the net-new variant.

  1. Open empty (0-2 min). Ask what was on their mind when they accepted the invite. Then stop talking for three full seconds. If they deflect, ask what comes up when you say "client delivery". Do not show a list of categories first; a list boxes them in and you miss the biggest pain.
    • Net new or closed-lost: add a 3-minute scene-set (what the firm does, delivery team size, active engagements). You need a named pain by minute 10.
    • Existing customer with usage data: bring the data in after they name a pain, as ammunition. It either backs up what they said or surfaces something they forgot. Leading with it boxes them in.
  2. Anchor the activity's value (2-5 min). Before digging in, get a yes to "this is a critical part of what clients pay you for" and "this is a competitive advantage piece". Without the yes, the later number is just time saved and the price looks expensive.
  3. Vertical drill, one pain only (5-15 min). Walk the process start to finish, as nitpicky as they can. Then: which step eats the most time, what share of the work, how often, who does it, their loaded cost, what they already tried and why it failed. Collect the numbers; no math out loud yet. A second pain gets parked. Deep on one, not shallow on five.
  4. Magic wand (15-22 min). "If the [biggest step] were just done for you, what does your day look like?" Then convert: what a new client is worth per month, what a hire would unlock. If they answer small, agree it is huge and ask whether it means more work or headspace for something else. Leave the block with an annual dollar figure for the pain, an opportunity-cost number, and their words on why it matters. Open references/pain-math.md for the capture sheet and the conversion.
  5. Price on the call (22-27 min). Wait for them to ask. If they have not by minute 24, offer to share what the investment usually looks like. Restate their figures, anchor at the standard range, offer the early-partner rate for this scope, ask whether that feels like the right ballpark. Describe the build in one breath. Open references/pricing-frame.md for the lines and the objection handling.
  6. Lock and ask for the referral (27-30 min). Yes-ish: one-page scope by a named time, 30 minutes booked this week to walk it through. Maybe: send the summary with the rough numbers and let them sit with it. Always close with the referral ask: another firm owner they respect wrestling with similar stuff.

What good looks like

  • First thing I check that most people skip: whether the owner said the value of the activity out loud before I started counting hours. Without that anchor, every number after it is "time saved" and the price conversation becomes a cost conversation.
  • Second tell: whether the dollar figure came from their mouth or mine. If I said it first, the proposal has no teeth.
  • The mediocre version: a horizontal tour of the whole delivery process, a little digging on five things, no number on any of them, "let me send you some pricing" by email, and "let me know" at the end. It feels like a good conversation and nothing happens.
  • I know the output is right when, by minute 22, I can fill in one sentence without guessing: "[Owner] is losing about [annual figure] a year on [one step], which is stopping them from [opportunity], and they said it matters because [their words]."
  • I know the call landed when the next meeting is booked before the call ends and the owner treated the price as a ballpark question, not a shock.
  • Red flag: the owner is excited about three problems and you leave with none quantified. Go back and pick one.

Rules

  • MUST get a named pain before the drill. On a net-new call, by minute 10.
  • MUST anchor the activity's value before digging into the pain.
  • MUST stay on one pain. Park every second pain for the follow-up.
  • MUST leave the magic-wand block with an annual dollar figure, an opportunity-cost number, and the owner's own words on why it matters.
  • MUST discuss pricing on the call. Pricing by email doubles the stall rate.
  • MUST book the next step before hanging up. "Let me know" is not a next step.
  • MUST ask for the referral on every call, as a separate last thing.
  • NEVER lead with a category list, a dashboard or an audit report before the owner has named their own pain.
  • NEVER do the math out loud during the drill.
  • NEVER quote the price before restating their figures.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.