# Founder Sales Sprint Pack: "No Decision" Rescue

**Scenario:** Prospects agree there's pain but keep stalling, asking for "more time" or "send info."

---

## 1) Context Snapshot

**Product (1 sentence):**
[Assumed] A B2B SaaS tool that solves an operational pain point for mid-market companies (specific product details not provided -- see Assumptions below).

**ICP wedge (who + where):**
[Assumed] Ops/department leaders at mid-market companies (100-1,000 employees) who have acknowledged a workflow pain point in discovery calls but are not converting to next steps.

**Goal + time box:**
Convert 3-5 stalled prospects into active pilots within 4 weeks. Reduce "no decision" rate from the current pipeline.

**Stage:** Early revenue -- discovery calls are happening, pain is validated, but deals stall before commitment.

**Offer:**
[Assumed] Bounded pilot: 30 days, limited scope, defined success criteria, with option to expand or walk away.

**30-day customer success definition:**
Customer has completed pilot setup, processed real data/workflows through the product, and achieved a measurable first-value milestone (e.g., time saved, errors reduced, visibility gained).

**Constraints:**
[Assumed] Founder-led; ~10-15 hours/week available for sales; primary channels are email, LinkedIn, and existing warm relationships. No large sales team.

**Assumptions & unknowns:**
- **Assumption:** The product is real and functional enough for a bounded pilot (not vaporware).
- **Assumption:** Prospects are mid-market ops leaders who have decision-making authority or strong influence.
- **Assumption:** Pricing is in the $500-$2,000/month range for a pilot.
- **Unknown:** Exact product, industry, and ICP details.
- **Unknown:** Number of stalled prospects currently in pipeline.
- **Unknown:** What "send info" materials have been sent previously (and whether they helped or hurt).
- **Unknown:** Whether stalls are coming from the economic buyer, the end user, or both.

**Validation plan (next 2 weeks):**
- Identify exactly which prospects are stalling and at what stage (post-discovery, post-demo, post-proposal).
- For each stalled prospect, determine: who else is involved in the decision? What is the actual blocker?
- Test the Decision Enablement Kit (below) on 2-3 stalled prospects and track response rates.

---

## 2) ICP Wedge + Founder POV

### ICP wedge (for the "no decision" rescue)

**Ideal buyer titles:**
VP/Director/Head of Operations, or the department leader who owns the broken workflow.

**Company type:**
Mid-market (100-1,000 employees); growing enough that manual workarounds are breaking but not so large that procurement cycles add 6 months.

**Trigger event ("why now"):**
The prospect already told you: they have the pain. The trigger is that the pain is getting worse (growing team, increasing volume, recent incident, new compliance requirement, or leadership pressure to fix it this quarter).

**Pain (in their words):**
"We know this is a problem. We just need more time to evaluate." (Translation: "I believe you, but I'm afraid of making a visible mistake, spending political capital, or committing resources to something that might not work.")

**Impact:**
[To be quantified per prospect] Time lost per week on manual workarounds, error rates, missed SLAs, team frustration, or revenue leakage.

**Exclusion criteria (not for):**
- Prospects who have NOT acknowledged the pain (go back to discovery).
- Prospects where the real answer is "no" but they are being polite (test with a direct question -- see below).
- Organizations in a genuine freeze (hiring freeze, budget freeze, reorg) where no decision CAN be made.

### Founder POV (problem-first narrative)

**What's changing / why now:**
The workflow your team relies on was designed for a smaller scale. As you grow, the manual steps, workarounds, and tribal knowledge that held it together are becoming the bottleneck -- not the solution.

**What breaks in the old way:**
Every week your team spends [X hours] on [manual process]. When it breaks -- and it does -- the cost is [missed SLAs / rework / customer complaints / delayed decisions]. The longer you wait, the more institutional muscle memory builds around the workaround, making the eventual switch harder and more expensive.

**The cost of doing nothing:**
"More time" is not free. Every month of delay costs [quantify: hours lost, errors accumulated, opportunities missed]. In 6 months, the problem will be bigger, the switching cost higher, and the urgency greater -- but your team will have 6 fewer months of results to show.

**Your insight (why you see it):**
"I've spent [X years] in [domain]. I've seen this pattern at [N] companies: the pain is real, everyone agrees it needs fixing, but the fear of a bad decision keeps teams stuck on manual workarounds for months or years. The fix is not a massive transformation -- it's a bounded, low-risk pilot that proves value in 2 weeks."

**What you do differently:**
We don't ask you to rip and replace. We start with a 14-day pilot on ONE workflow, with clear success criteria, and you decide based on evidence -- not a sales pitch.

**Proof points:**
- [Insert: specific results from early customers or pilots, e.g., "Company X reduced [metric] by [%] in [timeframe]"]
- [Insert: founder credibility -- background, domain expertise, why you understand this problem]
- [Insert: or state "Generating first proof points is part of this sprint"]

---

## 3) Targeting Plan + Target List

### Targeting criteria (for stalled prospects)

Since the problem is stalled deals (not new pipeline), the "target list" here is your existing pipeline, re-segmented by likelihood of rescue.

**Tier 1 -- High rescue probability:**
- Prospect explicitly named the pain and quantified impact during discovery.
- There is an identifiable trigger (deadline, incident, leadership mandate).
- The person you spoke with has authority or direct access to the decision-maker.
- They asked specific questions about implementation (signal: they were thinking about "how," not just "whether").

**Tier 2 -- Medium rescue probability:**
- Prospect acknowledged pain but did not quantify impact.
- No clear trigger or urgency beyond general agreement.
- Contact may be a champion but not the decision-maker.

**Tier 3 -- Low rescue probability (qualify out or nurture):**
- Prospect was polite but vague ("sounds interesting, send info").
- No pain quantification, no trigger, no access to decision-maker.
- Possible "polite no" -- test with a direct question before investing more time.

### Target list table (stalled pipeline)

| Prospect | Tier (1/2/3) | Pain acknowledged? | Impact quantified? | Trigger / why now | Decision-maker access | Last contact | Next action | Status |
|---|---|---|---|---|---|---|---|---|
| [Prospect A] | 1 | Yes | Yes -- [X hrs/wk] | Q2 deadline | Direct | [date] | Send decision guide + pilot proposal | Stalled |
| [Prospect B] | 1 | Yes | Partially | Team growing 2x | Champion (not buyer) | [date] | Request intro to decision-maker + send MAP | Stalled |
| [Prospect C] | 2 | Yes | No | None clear | Direct | [date] | Re-engage with impact quantification question | Stalled |
| [Prospect D] | 3 | Vague | No | None | Unknown | [date] | Send "is this still a priority?" email (qualify in/out) | Stalled |

### Next actions (this week)

1. Populate the table above with every stalled prospect.
2. For Tier 1: Send the Decision Guide + Pilot Proposal (Section 6 below) within 48 hours.
3. For Tier 2: Re-engage with an impact-quantification question to move them to Tier 1 or qualify them out.
4. For Tier 3: Send a direct "is this still a priority?" message. If no response in 7 days, move to nurture.

---

## 4) Outreach Kit (Stall-Breaking Sequences)

### A) Re-engagement email: "The cost of waiting" (for Tier 1 stalled prospects)

**Subject:** The cost of waiting on [problem] -- quick question

Hi [Name],

I've been thinking about our conversation on [date] where you mentioned [specific pain they described, in their words].

One thing I keep seeing with teams like yours: the longer the workaround stays in place, the harder it becomes to change -- not because the problem gets smaller, but because the team builds more muscle memory around it. At [peer company], that meant [X hours/week] of manual work that compounded every quarter.

I put together a 1-page decision guide that lays out your three options (keep current approach, build internally, or run a bounded pilot with us) with the real tradeoffs of each. No pitch -- just a clear framework for deciding.

Would it be useful if I sent that over?

-- [Founder name]

### B) Re-engagement email: "Pilot, not commitment" (for prospects who asked to "send info")

**Subject:** 14-day pilot -- no commitment required

Hi [Name],

You asked me to send some info after our last call. Rather than a generic deck, here's what I think would be more useful:

A **14-day bounded pilot** on [one specific workflow]. Here's what that looks like:
- **Scope:** [One workflow or use case] only
- **Your time commitment:** [X hours] total over 2 weeks
- **Success criteria:** [Specific metric] improves by [target], or we part ways
- **Risk:** Zero. If it doesn't work, you've lost [X hours] and gained clarity

I've attached a 1-page pilot plan with dates and owners. Want me to walk through it in 15 minutes this week?

-- [Founder name]

### C) Follow-up sequence (after sending decision guide or pilot plan)

**Follow-up #1 (3 days later):**

Subject: Re: [original subject]

Hi [Name] -- wanted to make sure the decision guide landed. Any questions, or does it match how you're thinking about this?

If it's easier, I can walk through it in 10 minutes. [Calendar link]

**Follow-up #2 (5 days later -- value nugget):**

Subject: What [peer company] decided (and why)

Hi [Name] -- quick data point. [Peer company / similar team] was in a similar spot -- pain was clear but timing felt uncertain. They ran a 14-day pilot and [specific result]. The thing that surprised them was [insight].

Happy to share details if helpful. If not, no worries at all.

**Follow-up #3 (10 days later -- direct close or qualify out):**

Subject: Should I close this out?

Hi [Name] -- I want to respect your time. It sounds like [problem] is real but the timing may not be right.

Two options:
1. **If the timing is wrong:** No problem. I'll check back in [timeframe]. Any specific trigger I should watch for?
2. **If it's still relevant:** Let's do a 15-minute call to map out a pilot plan with dates. [Calendar link]

Either way, I appreciate the conversations we've had.

-- [Founder name]

### D) "Is this a polite no?" qualification message (for Tier 3)

Subject: Quick honest question

Hi [Name] -- I've sent a few follow-ups and I want to be direct:

Is [problem] still something you're actively trying to solve this quarter, or has it moved off the priority list?

Either answer is completely fine -- I'd just rather know so I can be respectful of your time.

-- [Founder name]

---

## 5) Diagnostic Discovery Kit (Re-Discovery for Stalled Deals)

For stalled prospects, the issue is usually NOT that discovery didn't happen -- it's that discovery didn't go deep enough on **impact** and **decision process**. The re-discovery call focuses on what was missed.

### Re-Discovery Call Agenda (20 minutes)

1. **Re-anchor on the pain (2 min):** "Last time we spoke, you mentioned [pain]. Is that still true? Has anything changed?"
2. **Quantify impact -- this is what was probably missed (8-10 min):** See question bank below.
3. **Surface the real blocker (5-7 min):** See "stall diagnosis" questions below.
4. **Propose a bounded next step (3 min):** Decision guide review OR pilot kickoff.

### Impact Quantification Questions (the missing piece)

- "You mentioned [pain]. Can you help me put a number on it -- how many hours per week does your team spend on this?"
- "When this breaks, what's the downstream impact? Who feels it?"
- "If this stays as-is for the next 6 months, what happens? What gets worse?"
- "Is there a deadline, mandate, or event that makes this more urgent soon?"
- "What would your team be able to do with the time/resources you'd get back?"

### Stall Diagnosis Questions (surface the real blocker)

- "What would need to be true for you to move forward on this?"
- "Is there someone else who needs to weigh in before a decision happens?"
- "What's the biggest risk you see in trying something new here?"
- "Have you been burned by a vendor/tool change before? What happened?"
- "If I could remove one barrier, what would it be?"
- "Is the issue that this isn't a priority, or that the path forward isn't clear enough?"

### Call Notes Template (Stall-Specific)

**Call date:**
**Company / contact:**
**Role:**
**Original pain (confirmed? changed?):**
**Impact quantified (hours/$/risk):**
**Real blocker surfaced:**
- [ ] Timing / competing priorities
- [ ] Fear of making a bad decision
- [ ] Need another stakeholder's buy-in
- [ ] Unclear ROI / can't justify internally
- [ ] Switching cost / implementation fear
- [ ] Budget
- [ ] "Polite no" (not actually a priority)
**Verbatim quotes (capture exact language):**
-
**Next step agreed:**
**Follow-up owner + date:**

---

## 6) Decision Enablement Kit (Beat "No Decision")

This is the core deliverable for the stalling problem. "No decision" is not the same as "no." It means the buyer sees the pain but the path forward feels risky, unclear, or politically dangerous.

### A) Decision Guide (1 page -- send to prospect)

**Title:** Deciding on [problem area]: Your Options

**The decision:**
How to address [specific pain] that is currently costing your team [quantified impact].

**Option 1: Do nothing (status quo)**
- **What happens:** [Pain] continues. Your team spends [X hours/week] on manual workarounds. [Downstream impact] compounds.
- **Cost over 6 months:** [Quantify: hours lost, errors, missed SLAs, team frustration, opportunity cost]
- **Risk:** The problem grows. Switching cost increases. Team builds more habits around the workaround.
- **Best for:** Teams where this genuinely is not a priority this quarter.

**Option 2: Build/fix internally (DIY)**
- **What happens:** Your team allocates [X] engineering/ops hours to build a solution or improve the current process.
- **Cost:** [Estimate: internal team time, opportunity cost of those resources]
- **Timeline:** [Estimate: weeks/months to build, test, and adopt]
- **Risk:** Competes with roadmap priorities. May take longer than expected. No external expertise or benchmarks.
- **Best for:** Teams with spare engineering capacity and a well-understood problem.

**Option 3: Run a bounded pilot with us (14 days)**
- **What happens:** We implement [product] on [one specific workflow] in 14 days. You evaluate based on agreed success criteria.
- **Cost:** [Pilot pricing, e.g., $0 / reduced rate / standard rate with exit clause]
- **Timeline:** 14 days to first value. Decision point at day 14.
- **Risk:** [X hours] of your team's time. If it doesn't work, you walk away with clarity on what you need.
- **Best for:** Teams that want evidence before committing, without a multi-month evaluation.

**Our recommendation:**
If [problem] is costing your team [X] per month and you don't have spare engineering capacity for a DIY fix, Option 3 gives you the fastest path to an evidence-based decision with the lowest risk.

### B) Risk Reversal / Pilot Framing

**Pilot scope:**
[One specific workflow or use case] -- not the whole organization.

**Timeline:**
14 days from kickoff to decision point.

**Success criteria (measurable):**
- [Metric 1]: e.g., "Reduce time spent on [task] from [X hours] to [Y hours] per week"
- [Metric 2]: e.g., "Process [N] transactions/records without manual intervention"
- [Metric 3]: e.g., "Generate first [report/insight/output] within 7 days"

**What we do (white glove):**
- Dedicated founder/engineer onboarding support
- Setup and configuration handled by us
- Weekly check-in calls (2x in 14 days)
- Direct Slack/email access to founder

**What you do:**
- Designate one point person (2-3 hours/week for 2 weeks)
- Provide access to [system/data/workflow] needed for the pilot
- Attend kickoff and review calls

**Price/terms:**
[Insert: free pilot / discounted pilot / standard pricing with 14-day exit clause]

**Exit criteria:**
If success criteria are not met by day 14, the pilot ends with no obligation. We'll share a summary of what we learned and recommend next steps regardless.

### C) Mutual Action Plan (MAP)

This is the artifact that converts "let me think about it" into a concrete, dated path forward.

| Date | Milestone | Buyer Owner | Seller Owner | Evidence/Output |
|---|---|---|---|---|
| Day 0 | Decision to pilot (verbal yes) | [Buyer name] | [Founder] | Email confirmation |
| Day 1 | Kickoff call (30 min) | [Buyer point person] | [Founder] | Kickoff agenda + success criteria doc |
| Day 1-2 | Access + setup | [Buyer IT/ops] | [Founder/engineer] | System access confirmed, config complete |
| Day 3-5 | First workflow processed | [Buyer point person] | [Founder] | First [output] generated |
| Day 7 | Mid-pilot check-in | [Buyer point person] | [Founder] | Progress vs. success criteria reviewed |
| Day 10 | Expand to [additional workflow/users] (if Day 7 is positive) | [Buyer point person] | [Founder] | Expanded scope confirmed |
| Day 14 | Pilot review + decision | [Buyer decision-maker] | [Founder] | Results summary. Go/no-go decision. |
| Day 14+ | If go: transition to paid agreement | [Buyer] | [Founder] | Contract or PO |

**Key principle:** Every row has a date, an owner on each side, and a concrete output. If a prospect cannot commit to Row 1 (kickoff date), they are not ready to pilot -- and that's useful information.

---

## 7) White-Glove Activation Plan

### Activation definition

**Activated when:**
(1) Product is set up and configured on the pilot workflow, (2) at least one real workflow/transaction has been processed, and (3) the buyer point person confirms they can see the value.

**Time-to-first-value target:** 5-7 days from kickoff.

### Implementation checklist

- [ ] Kickoff call scheduled BEFORE the prospect says "yes" (during the close, not after)
- [ ] Calendar invite sent with agenda, attendees, and pre-work
- [ ] Access/setup requirements listed and assigned (who provides what, by when)
- [ ] First value milestone defined: "[Specific output] by Day [X]"
- [ ] Buyer point person identified with dedicated time (2-3 hrs/week)
- [ ] Training plan: [live walkthrough / async video / documentation] by Day [X]
- [ ] Weekly check-in cadence agreed (Day 7, Day 14 at minimum)
- [ ] Escalation path defined: if blocked, [buyer point person] emails [founder] and we resolve within 24 hours
- [ ] Success criteria documented and shared with both sides

### 30-Day Success Plan

**Week 1: Setup + First Value**
- Day 1: Kickoff call. Align on success criteria. Begin setup.
- Day 2-3: Complete configuration. Process first real workflow.
- Day 5-7: Buyer point person confirms first value milestone achieved.
- Founder check-in: Day 3 (async) + Day 7 (live call).

**Week 2: Validate + Expand**
- Process additional workflows or add users.
- Measure against success criteria.
- Capture first proof point (metric improvement, time saved, quote from user).
- Founder check-in: Day 14 (live review call with decision-maker).

**Week 3: Measure Impact + Build Internal Case**
- Compile results vs. success criteria.
- Create a 1-page "results so far" summary the champion can share internally.
- Identify expansion opportunities (additional workflows, teams, use cases).
- Founder check-in: Day 21 (async or live).

**Week 4: Decision + Next Steps**
- Formal review: present results, discuss expansion plan, agree on terms.
- If positive: transition to paid agreement. Schedule expanded rollout kickoff.
- If mixed: identify what needs to change. Extend pilot with revised criteria, or part ways with a clear summary.
- Capture testimonial/case study (even a 2-sentence quote) if customer is willing.
- Founder check-in: Day 28 (live -- decision meeting).

### Follow-Up Cadence

| Day | Action | Owner | Channel |
|---|---|---|---|
| Day 1 | Kickoff call | Founder | Video call |
| Day 3 | "How's setup going?" check-in | Founder | Email/Slack |
| Day 7 | Week 1 review (first value?) | Founder | Video call |
| Day 10 | "Anything blocking expansion?" | Founder | Email/Slack |
| Day 14 | Pilot review with decision-maker | Founder | Video call |
| Day 21 | Impact check + internal case prep | Founder | Email/Slack |
| Day 28 | Decision meeting | Founder | Video call |

---

## 8) Learning Loop (Tracking + Iteration)

### Pipeline Tracker (Stalled Deals)

| Prospect | Tier | Stall Type | Action Taken | Date | Response | Next Step | Status |
|---|---|---|---|---|---|---|---|
| [A] | 1 | "Need more time" | Sent decision guide | [date] | [pending] | Follow up in 3 days | Active |
| [B] | 1 | "Send info" | Sent pilot proposal | [date] | [pending] | Follow up in 3 days | Active |
| [C] | 2 | "Need more time" | Sent re-discovery questions | [date] | [pending] | Await response | Active |
| [D] | 3 | "Send info" (vague) | Sent "is this a priority?" | [date] | [pending] | Qualify in/out in 7 days | Qualifying |

### Weekly Review (30 minutes, every Friday)

**Calls/emails this week:** #
**Responses received:** #
**Stall patterns observed:**
- What specific language are prospects using when they stall?
- Are stalls happening at the same stage (post-discovery? post-proposal? post-demo?)?
- Is there a common missing stakeholder or blocker?

**What worked:**
- Which re-engagement message got the best response?
- Which decision-enablement asset was most useful?
- Did any prospect move from stalled to active?

**What to change next week:**
- [ ] Update outreach language based on responses
- [ ] Adjust pilot framing based on objections heard
- [ ] Add/remove prospects from active pipeline
- [ ] Revise decision guide based on new "do nothing" cost data

**Message iteration plan:**
- Test 2 subject line variants per week on stall-breaking emails.
- Track: which variant gets opens? Which gets replies? Which gets meetings?
- After 2 weeks, consolidate to the best-performing message and test a new variant.

---

## 9) Risks / Open Questions / Next Steps

### Risks

1. **"More time" may actually mean "no."** Some stalled prospects are being polite. The qualification email (Section 4D) will surface these -- be prepared to let them go and focus energy on genuine interest.
2. **The real blocker is a missing stakeholder.** If the person you're talking to cannot make or strongly influence the decision, no amount of decision-enablement material will work. The re-discovery call (Section 5) must surface who else is involved.
3. **Decision guide backfires if pain is not quantified.** The "cost of doing nothing" argument only works if you have real numbers. If impact was not quantified in discovery, re-engage with impact questions before sending the decision guide.
4. **Pilot capacity constraints.** White-glove pilots require significant founder/engineer time. If you have 8+ stalled prospects, you cannot pilot all of them simultaneously. Prioritize Tier 1 and stagger kickoffs.
5. **"Send info" becomes a dead loop.** If you keep sending materials without a specific next step attached, you train the prospect to treat you as a content source, not a partner. Every piece of material sent must have a clear, low-commitment ask attached (e.g., "15-minute walkthrough of the pilot plan").

### Open Questions

- What is the exact product and ICP? (This pack uses assumptions -- customize all outreach, decision guide, and pilot framing with real details.)
- How many stalled prospects are in the pipeline? (This determines whether to focus on rescue or also build new pipeline.)
- What materials have already been sent to stalled prospects? (Avoid re-sending the same type of content.)
- Is the stall pattern consistent across prospects, or are there different blockers for different segments?
- Is there a specific quarter or budget cycle driving timing?

### Next Steps (This Week)

1. **Populate the pipeline tracker** (Section 8) with every stalled prospect. Assign each a tier (1/2/3).
2. **Customize the Decision Guide** (Section 6A) with your real product, pricing, and quantified "cost of doing nothing."
3. **Send the Tier 1 re-engagement** (Section 4A or 4B) to your top 2-3 stalled prospects within 48 hours.
4. **Send the "is this a priority?" email** (Section 4D) to Tier 3 prospects to qualify them in or out.
5. **Schedule the first weekly review** (Section 8) for Friday of this week.
6. **Book re-discovery calls** with any Tier 1 or 2 prospect who responds, using the stall-specific discovery agenda (Section 5).

### Next Steps (Weeks 2-4)

- Iterate outreach and decision-enablement materials based on Week 1 responses.
- For prospects who agree to pilot: execute the MAP (Section 6C) and activation plan (Section 7).
- For prospects who qualify out: move to a nurture cadence (quarterly check-in) and redirect energy to new pipeline.
- Capture proof points from any active pilot to strengthen the decision guide for remaining stalled prospects.

---

## Quality Gate: Checklist Verification

### A) Scope + decision framing
- [x] Goal is measurable and time-boxed: "Convert 3-5 stalled prospects into active pilots in 4 weeks"
- [x] Stage is appropriate for founder-led sales (learning > scale)
- [x] Constraints captured (founder time, channels)
- [x] 30-day customer success defined

### B) Founder POV
- [x] Founder POV leads with insight (cost of waiting, not features)
- [x] Credibility is explicit (template provided for founder to fill in)
- [x] Exclusion criteria exist
- [x] Proof points section included with plan to generate them

### C) Diagnostic discovery
- [x] Re-discovery call is diagnostic (no demo)
- [x] Question bank covers impact, blocker diagnosis, decision process
- [x] Call notes template captures verbatim language and stall type
- [x] Every call ends with a concrete next step

### D) Decision enablement
- [x] "Do nothing" is explicitly addressed with quantified cost
- [x] Decision guide includes 3 options + criteria + recommendation
- [x] Risk reversal/pilot is bounded (14 days, clear success criteria, exit clause)
- [x] MAP exists with dates, owners, and outputs

### E) Close-to-activation
- [x] Activation defined (implemented + first value)
- [x] Kickoff scheduled as part of the close
- [x] Owners assigned on both sides
- [x] Follow-up cadence defined (4 weeks)
- [x] "Closed" requires activation criteria met

### F) Learning loop + iteration
- [x] Pipeline tracker with statuses and next actions
- [x] Weekly review loop defined
- [x] Assumptions and unknowns listed with validation plan
- [x] Pack ends with Risks / Open questions / Next steps

### G) Safety + ethics
- [x] No deceptive claims or spam guidance
- [x] No requests for secrets
- [x] All outreach is ethical, targeted, and includes opt-out language

---

## Rubric Self-Score

| Category | Score | Notes |
|---|---|---|
| 1) ICP wedge clarity | 1 | Assumed ICP -- needs real product/industry details to reach 2 |
| 2) Founder POV strength | 1 | Template is insight-led but needs real founder credibility + proof points |
| 3) Outreach kit quality | 2 | Targeted stall-specific sequences with clear CTAs and personalization hooks |
| 4) Discovery quality | 2 | Diagnostic re-discovery focused on impact quantification and blocker diagnosis |
| 5) Decision enablement | 2 | Complete decision guide + bounded pilot + MAP with dates/owners |
| 6) Activation plan | 2 | Full 30-day plan with milestones, owners, and follow-up cadence |
| 7) Learning loop + completeness | 2 | Weekly review, pipeline tracker, message iteration plan, risks/questions/next steps |
| **Total** | **12/14** | **Passes (>= 10/14).** Score improves to 14/14 once real product/ICP details are applied. |