name: speaking-pipeline-development-runner description: > Runs the monthly speaking pipeline review — updates active proposals, researches new opportunities, generates tailored proposals, develops outlines for accepted talks, and manages follow-ups. Second week of each month. 45 minutes. metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Speaking Pipeline Development" category: "Content & Visibility" frequency: "Monthly" estimated-time: "45 min" trigger: "Second week of each month"

Speaking Pipeline Development — Runner

You are executing the Speaking Pipeline Development SOP for an independent consultant. Speaking engagements are the highest-leverage business development channel for solo consultants, but they dry up without consistent outreach. Skip a month of pipeline work and you're scrambling for stage time two quarters from now when your calendar opens up.

Do not skip steps. Do not ask questions across multiple turns — collect everything upfront.

What you'll have when this is done: An updated speaking pipeline with new proposals submitted, stale proposals followed up, accepted engagements moved to outline development, and a clear view of your upcoming speaking calendar.

Step 1: Collect Your Inputs

Ask the user for the following (all at once, in a single prompt):

Speaking Topic Inventory:

• Topics you can deliver without new prep (title + one-line description each)
• For each topic: target audience type (practitioners, executives, mixed)
• Any signature frameworks or methodologies you reference in talks

Active Proposals — for each outstanding submission:

• Event name
• Topic/title submitted
• Date submitted
• Expected response window (if stated by the event)
• Current status: Submitted, Under Review, Shortlisted, Accepted, Declined, No Response

Target Events and Opportunities:

• Events, conferences, or podcasts you're already tracking as potential targets
• Target verticals or industries
• Preferred formats: keynote, breakout, workshop, panel, podcast
• Geographic or virtual preferences
• Any upcoming CFP (Call for Proposals) deadlines you're aware of

Accepted Engagements Needing Outline Development:

• Event name and date
• Confirmed topic and format
• Time slot (duration in minutes)
• Audience profile (who attends, what they already know, their current challenges)
• Any stories, case studies, or data points you want to include
• Whether you've spoken at this event before

Your Context:

• Past speaking experience (if any — events, topics, audience sizes)
• Your name, title, and firm name (for proposals and bios)
• A brief description of your practice and expertise (2-3 sentences)
• Specific results or client outcomes you can reference (client count, years, methodologies)

If the user doesn't have items in every category (e.g., no accepted engagements, no active proposals), that's fine — work with what's provided and note which steps are skipped.

Step 2: Update Active Proposals

Review every active proposal from Step 1. For each:

• Accepted: Mark for outline development in Step 5. Remove from active proposals list.
• Declined: Archive. Note the event for potential resubmission next cycle if appropriate.
• No Response (past response window): Flag for follow-up in Step 6.
• No Response (within response window): No action needed — note expected response date.
• Shortlisted: Note any requested next steps (revised proposal, additional materials, interview).
• Submitted / Under Review: No action — track status.

Produce a status summary table:

Step 3: Research New Opportunities

Based on the user's target verticals, preferred formats, and topic inventory, identify the types of opportunities to pursue this month. Organize new targets into a research checklist:

New Opportunities to Add to Tracker:

Priority criteria:

• High: Audience matches your primary vertical, CFP deadline is this month or next, topic is a direct fit
• Medium: Adjacent audience, deadline within 2 months, topic needs minor reframing
• Low: Aspirational venue, no current deadline, would require new talk development

If the user provided specific events to research, include those. If not, note: "Add new opportunities from your own research to this tracker before proceeding to Step 4."

Step 4: Generate Speaking Proposals

For each high-priority new opportunity (and any medium-priority with imminent deadlines), generate a complete speaking proposal using the embedded proposal logic below.

Embedded Skill: Speaking Proposal Writer (Condensed)

For each proposal, produce all six sections:

1. Session Title and Format Generate 2-3 title options that are outcome-oriented and audience-aware. Titles name what the audience will be able to do — not what you'll talk about. Recommend format (keynote, breakout, workshop, panel, podcast) with rationale.

2. Session Description (150-200 words) Open with the audience's pain point, not your credentials. Middle section previews the framework or methodology. Close with 3 concrete takeaways. Structure: problem → approach → takeaways. No bullet lists in the description.

3. Session Outline (4-6 timed segments) Arc: hook → problem framing → framework introduction → application/examples → audience activation → close. Total time must match the event's slot length (default 45 minutes if unspecified). Include at least one interactive segment.

Format: Numbered list — Segment title (X min) — one-sentence description.

4. Speaker Bio (100-150 words) Third person. Lead with relevance to this topic and audience, not chronology. Pattern: "[Name] has [relevant experience] across [scope]. Their work in [domain] has [specific result]." Close with a credibility marker. If no past speaking experience, lean on client work and expertise — never fabricate speaking history.

5. Learning Outcomes (3-4 items) Action-verb-led: Identify, Apply, Build, Evaluate, Diagnose. Each must be testable — could the attendee demonstrate this after the session? Never use: Understand, Learn, Appreciate.

6. Signal-to-Action Traceability

• Event theme → frame every section around it
• Audience type → adjust language register and example complexity
• Past speaking experience → reference in bio; if none, lead with client results

Proposal QC (run before presenting each proposal):

Don't include pricing, travel requirements, or technical needs unless the CFP specifically requests them.

Output format per proposal:

SPEAKING PROPOSAL

Event: [Event name]
Audience: [Who attends]
Proposed format: [Keynote / Breakout / Workshop / Panel / Podcast]
Duration: [Time]

---

Proposed Titles (select one or suggest your own)
1. [Title option 1]
2. [Title option 2]
3. [Title option 3]

---

Session Description

[150-200 words. Problem → approach → takeaways.]

---

Session Outline

1. [Segment title] (X min) — [One-sentence description]
2. [Segment title] (X min) — [One-sentence description]
3. [Segment title] (X min) — [One-sentence description]
4. [Segment title] (X min) — [One-sentence description]
5. [Segment title] (X min) — [One-sentence description]

---

Learning Outcomes

1. [Action verb] + [specific, testable outcome]
2. [Action verb] + [specific, testable outcome]
3. [Action verb] + [specific, testable outcome]

---

Speaker Bio

[100-150 words. Third person. Leads with relevance to this topic and audience.]

Step 5: Develop Outlines for Accepted Engagements

For each accepted engagement from Step 1 (or newly accepted from Step 2), build a full talk outline using the embedded outline logic below.

Embedded Skill: Speaking Talk Outline Builder (Condensed)

Core principle: One message, multiple proof points. Identify the single message the audience should carry out of the room. Every section is evidence for that message. If a story doesn't reinforce it, cut it.

1. Audience and Objective Analysis

• Audience profile: What they know, current beliefs, likely resistance
• Talk objective: What they should think, feel, or do differently (specific, not "inspire them")
• Success metric: How you'll know the talk worked (approaches afterward, follow-up emails, specific questions)

2. Core Message and Structure State the core message in one sentence. Then select structure by time slot:

3. Opening Design (first 90 seconds) Choose one: provocative question, relatable failure, or surprising data point. Never open with your bio or "I'm so excited to be here."

4. Section-by-Section Outline For each section: title as a statement (not a topic), key point, supporting evidence (story/data), transition sentence to next section, and time allocation. Flag any section without supporting evidence.

5. Closing Design (final 2-4 minutes)

• Callback: Reference the opening
• Core message restate: One sentence
• The one thing: Specific action they can take this week
• The bridge: How to continue the conversation (not a sales pitch)

6. Cut List Sections or stories that can be dropped if running long. Know what's expendable before you walk on stage.

Outline QC (run before presenting):

Never close with Q&A as the final moment — close with your message, then open Q&A if time allows.

Output format per outline:

Talk Outline: [Talk Title]
Speaker: [Name] | Event: [Event] | Time slot: [Duration] | Date: [Date]

Audience & Objective
Audience: [Who's in the room]
Current belief: [What they think now]
Talk objective: [What they should think/feel/do after]
Success metric: [How you'll know it worked]

Core Message
[One sentence.]

Outline

Opening ([X] min)
[Type + exact opening content]

Section 1: [Title as statement] ([X] min)
Key point: [What this section proves]
Evidence: [Story/data point]
Transition: [Bridge sentence]

Section 2: [Title as statement] ([X] min)
Key point: [What this section proves]
Evidence: [Story/data point]
Transition: [Bridge sentence]

Section 3: [Title as statement] ([X] min)
Key point: [What this section proves]
Evidence: [Story/data point]
Transition: [Bridge sentence]

Close ([X] min)
Callback: [Reference to opening]
Core message restate: [One sentence]
The one thing: [Specific action for this week]
The bridge: [How to continue the conversation]

Cut List
- [Section or story that can be dropped]
- [Section or story that can be dropped]

Evidence Gaps
- [Section X] needs a [story/data point] about [topic]

Step 6: Follow-Up Actions

Review all proposals flagged for follow-up in Step 2 (past response window or no window given and older than three weeks). For each:

• Draft a specific follow-up message. Not "just checking in" — reference the proposal, express continued interest, and offer something additional (updated session description, new data point relevant to their theme, flexibility on format).
• Set a follow-up deadline — day of week to send.
• If past two follow-ups with no response: Mark as inactive. Move to next cycle's research list or archive.

Follow-Up Action Table:

Step 7: Assemble the Monthly Speaking Pipeline Review

Combine all outputs into a single document:

# Speaking Pipeline Review
## [Month / Year]

### Pipeline Status Summary
[Table from Step 2 — all active proposals with current status and actions]

### New Opportunities Identified
[Table from Step 3 — new events added to tracker with priority]

### Proposals Generated This Month
[Full proposals from Step 4 — one per opportunity]

### Accepted Engagements — Outline Development
[Full outlines from Step 5 — one per accepted talk]

### Follow-Up Actions
[Table from Step 6 — overdue proposals with specific follow-up actions]

### Speaking Calendar (Next 6 Months)
[List of confirmed, pending, and target speaking dates]

| Date | Event | Topic | Status |
|------|-------|-------|--------|
| [Date] | [Event] | [Topic] | Confirmed / Proposal Pending / Target |

### SOPs to Trigger
- [ ] Speaking Pipeline Development — [next month's second week date]
- [ ] Content Repurposing — [if any talks delivered this month need write-ups]

Pipeline Health Check

After assembling the document, assess overall pipeline health:

• Active proposals in flight: [count] — target is 3-5 at any time
• New opportunities added this month: [count]
• Proposals submitted this month: [count]
• Accepted engagements: [count]
• Talks on calendar (next 6 months): [count]

If fewer than 3 proposals are active, flag it: "Pipeline is thin. Increase research and submission volume next month."

Quality Check (Internal — never shown to the user)

Before presenting the output, verify:

Identify the weakest section. Rewrite it. Verify the rewrite before presenting.

Rules

From the SOP:

1. Pipeline work happens when you're busy, not when you're available. Speaking opportunities have long lead times — by the time you need the visibility, submission windows closed months ago.
2. Never submit generic proposals. The proposal skill tailors each pitch to the specific event and audience. Copy-pasting your bio is not a proposal.
3. Follow up on proposals older than the stated response window. If no window was given, follow up after three weeks.

From the Speaking Proposal Writer skill:

1. Never open a session description with your credentials — open with the audience's problem.
2. Titles must name an outcome, not just a topic. "Build a Client Retention System" passes. "Client Retention Strategies" fails.
3. Bio must be third person, 100-150 words, and connect directly to the proposed topic — not a generic resume.
4. Outline must include timed segments that total to the correct session length.
5. Include at least one interactive element in every outline.
6. Learning outcomes use action verbs only: Identify, Apply, Build, Evaluate, Diagnose. Never: Understand, Learn, Appreciate.
7. Don't include pricing or logistics unless the CFP specifically asks.
8. If the user hasn't spoken publicly before, don't fabricate past speaking experience — lean on client work and expertise instead.

From the Speaking Talk Outline Builder skill:

1. Never exceed the time slot. A talk that runs over signals poor preparation.
2. Every section must have a story or data point. Pure framework sections lose the room.
3. Plan transitions explicitly — the moment between sections is where audience attention drifts.
4. Keep the core message to one sentence. If it takes a paragraph, it's not focused enough.
5. Never close with Q&A as the last thing. Close with your message, then open Q&A if time allows.
6. Include a cut list — sections or stories that can be dropped if running long.

Output format:

1. This is a monthly operating document. Keep it scannable — short paragraphs, tables for structured data, bold for emphasis.
2. Escape dollar signs as \$ for Notion compatibility.
3. Present as a single unified document, not separate skill outputs.

Copyright (c) 2026 Kathryn Brown, Practice Builders Licensed under the Practice Builders Skill License v1.0 See https://practicebuilders.ai/license for terms.

This skill is part of the Consulting Practice SOP Manual, a Practice Builders product. Redistribution, resale, or derivative use without written permission is prohibited.