agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/proposal-follow-up/SKILL.md

proposal-follow-up

Skill13 starsChanged 22 days agoMITView on GitHub

Use this skill when a proposal or quote has been sent and the buyer has gone quiet or is stalling: \"follow up on my proposal\", \"they have the quote but no decision\", \"proposal stuck in review\". Diagnoses where the deal is really stuck (economic buyer, budget, competitor, priority, procurement, champion), writes a follow-up sequence that addresses that cause with value instead of nagging, and sets the point to escalate or close the opportunity.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Use this when a proposal sits unanswered.

    line 16
  2. Distinctive:

    If three touches over three weeks get nothing, mark the deal lost to "no decision" and move to nurture.

    line 45
  3. Distinctive:

    Every follow-up contains something the buyer can use internally.

    line 53
  4. Distinctive:

    MUST diagnose the stall before writing.

    line 59
  5. Distinctive:

    MUST keep the champion informed before contacting other stakeholders.

    line 60
  6. Distinctive:

    NEVER offer an unrequested discount as a follow-up tactic.

    line 61
  7. Distinctive:

    NEVER invent an expiring offer.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Use this when a proposal sits unanswered. Silence after a proposal almost always has a specific cause; following up on the cause works better than asking "any updates?".

Inputs

  • The proposal: what, how much, when sent, any deadline in it.
  • Deal notes: who saw it, who decides, competitors, what was promised.
  • Stakeholders and the champion's last message.

The play

1. Diagnose the stall

ClueLikely causeFollow-up angle
Champion silent, was engaged beforeLost internal fight or priority shiftAsk directly, offer help with the internal case
"Reviewing with the team" for 2+ weeksEconomic buyer not convinced or not involvedOffer a short call with the economic buyer
Questions about price onlyBudget gap or competitor quoteOptions: phasing, packaging, terms
Procurement or legal mentionedPaper processOffer documents and pre-approved terms
Nothing since the demo went poorlyFit concernAddress the concern or offer a focused trial

2. Sequence (over 2-3 weeks)

  1. Day 3-5: value plus a question about the cause: a one-page business case built from their numbers, and "What questions came up when you shared it?"
  2. Day 8-10: address the likely blocker: options for price, security documents, or an offer to join the internal meeting.
  3. Day 14-16: multi-thread: a short note to another stakeholder you have met, adding value, not going around the champion.
  4. Day 21: honest check-in with a multiple-choice question, or close the opportunity.

3. Escalate with care

Executive-to-executive outreach works when there was real engagement and the deal is meaningful. Frame it as a check on how the evaluation is going, never as pressure.

4. Decide when to close

If three touches over three weeks get nothing, mark the deal lost to "no decision" and move to nurture. An honest pipeline beats a hopeful one.

Example

Hi Priya, I put your numbers into a one-page case for the CFO: 5 days saved a month, about $480k a year at your volumes, against a $60k cost. Feel free to edit it before sharing. What questions came up when you discussed the proposal with the team?

What good looks like

  • Every follow-up contains something the buyer can use internally.
  • The diagnosis drives the angle; price follow-ups do not go to a champion whose problem is the economic buyer.
  • The common mistake is "Just checking in on the proposal" five times, then an unrequested discount.

Rules

  • MUST diagnose the stall before writing.
  • MUST keep the champion informed before contacting other stakeholders.
  • NEVER offer an unrequested discount as a follow-up tactic.
  • NEVER invent an expiring offer.

Example prompts

  • "Sent the proposal 12 days ago, no reply from our champion. Diagnose and write the follow-ups."
  • "They said 'reviewing internally' three weeks ago. What now?"
  • "Build a business case one-pager from our discovery numbers to send as a follow-up."

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.

Check your setup, free