agentleFS
agiea-brainagiea-brain/agency-skills/skills/jay-dingwall/upsell-opportunity-brief/SKILL.md

upsell-opportunity-brief

Skill1 starsChanged 17 days agoMITView on GitHub

Use this skill before a review or check-in with an existing client, or when a project is weeks from ending and nothing has been lined up after it. Produces a one-page brief: the one opportunity worth raising, the evidence from delivery that supports it, the price, who signs, and the sentence to open with. Also use for "what else can we sell [client]", "prep the renewal conversation", "this project ends next month", "expansion opportunities in the book".

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add what the team worked around.

    line 22
  2. Distinctive:

    Add what the client asked for and did not get quoted.

    line 23
  3. Very specific:

    Write the brief to the format in references/brief-format.md, including the one sentence that opens the conversation.

    line 32
  4. Distinctive:

    MUST run the health gate first and stop there when it fails.

    line 44
  5. Distinctive:

    MUST base the opportunity on evidence from delivery, quoted where possible.

    line 45
  6. Distinctive:

    MUST name one opportunity, not a menu.

    line 46
  7. Distinctive:

    MUST name the signer and when they were last engaged.

    line 47
  8. Distinctive:

    MUST raise an end-of-project continuation at least six weeks out.

    line 48
  9. Distinctive:

    NEVER upsell an account with unresolved delivery problems.

    line 49
  10. Distinctive:

    NEVER lead with a service the client has not given a reason to need.

    line 50

≈ “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 to a client already paying, before a review or at the end of a project. Produces one page naming a single opportunity and the proof from the work itself.

The play

  1. Start in the delivery record, not the service list. What the team actually did, worked around and absorbed is where real expansion lives. Reading the service list first produces a pitch for whatever the firm most wants to sell, which the client can hear coming. The sources, in order of how well they convert, are in references/signal-sources.md.
  2. Pull the free work first. Everything delivered this quarter that was not in scope and was not billed. On most accounts this is the entire brief: the client already values it, already receives it, and is already not paying for it. Converting it is a pricing conversation, not a pitch.
  3. Add what the team worked around. A thing the delivery team keeps patching is a problem the client has, whether or not they have named it.
  4. Add what the client asked for and did not get quoted. Asked once is a note, asked twice is an opportunity, asked three times and not quoted is a failure of account management.
  5. Run the gates before writing anything. Account health, a named problem in the client's own words, a budget holder, and timing. All four, in that order, with the failure conditions in references/qualifying-gates.md. The first gate is the one that matters: an unhealthy account is never upsold, it is fixed.
  6. Pick one opportunity. Not three with a recommendation, one. A brief listing options moves the decision back onto the client, and an unhappy or busy client declines all of them.
  7. Branch by the situation:
    • Project ending, delivery went well: lead with continuation, priced as a retainer, raised at least six weeks out. Four weeks is already late.
    • Project ending, delivery was rocky: no expansion. Close well, fix the relationship, revisit next quarter.
    • Retainer running steady: convert the free work. Nothing new, just scope and price catching up with reality.
    • Champion has changed: the new person did not buy the original work and owes it nothing. Re-establish value before proposing anything.
    • Client raised budget pressure in the last quarter: the only sellable opportunity is one that removes a cost they have already named.
  8. Write the brief to the format in references/brief-format.md, including the one sentence that opens the conversation. Draft that sentence before the price, because an opportunity that cannot be opened in one sentence is not clear enough to sell.

What good looks like

  • First thing I check that most people skip: how much unbilled work went out the door last quarter. The biggest expansion on most accounts is already being delivered free, and nobody has counted it.
  • The mediocre version: a list of every other service the firm offers, mapped to the client with no evidence, raised at the renewal meeting because that is when somebody remembered. The client hears a vendor trying to grow an account.
  • I know the brief is right when the opening sentence quotes something the client said and the opportunity sounds like their idea.
  • Second test: it names who signs, and that person has been in a room with the firm this quarter. If they have not, the real work is getting access, not writing a proposal.
  • Red flag: the evidence section cites the firm's capability rather than the client's situation. That is a brochure.

Rules

  • MUST run the health gate first and stop there when it fails.
  • MUST base the opportunity on evidence from delivery, quoted where possible.
  • MUST name one opportunity, not a menu.
  • MUST name the signer and when they were last engaged.
  • MUST raise an end-of-project continuation at least six weeks out.
  • NEVER upsell an account with unresolved delivery problems.
  • NEVER lead with a service the client has not given a reason to need.

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.