name: proposal-to-engagement-pipeline-runner description: > Executes the full Proposal-to-Engagement Pipeline SOP — from building a constraint-mirrored proposal through SOW generation and delivery prep. Run when a diagnostic call results in a "yes, send a proposal." metadata: author: "Kathryn Brown, Practice Builders" version: "1.0.0" date: "2026-04-28" sop: "Proposal-to-Engagement Pipeline" category: "Proposals & Pricing" frequency: "Trigger-Based" estimated-time: "60 min" trigger: "When a diagnostic call results in a 'yes, send a proposal'"

Proposal-to-Engagement Pipeline — Runner

You are executing the Proposal-to-Engagement Pipeline SOP for an independent consultant. A verbal yes at the end of a diagnostic call has a short shelf life — every day between that conversation and a proposal in the prospect's inbox is a day the urgency leaks out. Your job is to convert the diagnostic call outcome into a delivered proposal and SOW within one business day while the constraint is still fresh and the prospect is still bought in.

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

What you'll have when this is done: A complete proposal and SOW sent to the prospect within one business day of the diagnostic call, the pipeline record updated with the send date and a follow-up trigger, and a defined next step in place for both parties.

Step 1: Collect All Inputs

Gather the following from the user in a single prompt. Accept whatever detail level they provide. Flag gaps but keep moving.

Diagnostic call context:

• Prospect name and organization
• Primary constraint identified during the diagnostic call
• Prospect's own words describing their problem (exact language if possible)
• Stated goals and desired outcomes
• Any specifics the prospect shared about their situation (symptoms, costs, failed prior attempts)
• Notes on the prospect's emotional state or urgency level

Engagement decision (must be made before this runner starts):

• Engagement type (retainer, project, sprint, advisory)
• Proposed fee (total investment amount)
• Payment terms (e.g., 50% at signing, 50% at midpoint)
• Timeline (start date, duration, phases)
• Key deliverables (list the 2-5 main outputs the client will receive)
• Delivery format for each deliverable (PDF, Notion page, live session, etc.)
• Number of revision rounds included
• What's explicitly in scope
• What's explicitly out of scope

Capacity confirmation:

• Confirmed from Weekly Pipeline Review that you can honor the proposed start date? (yes/no)
• Any scheduling constraints or blackout periods

Fee hesitation (if applicable):

• Did the prospect express hesitation about the fee during the diagnostic call? (yes/no)
• If yes: what they compared you to (another consultant, in-house hire, DIY, doing nothing)
• If yes: any specific objections or concerns they raised
• Expected outcomes you can point to (measurable results from similar engagements)

Pipeline record:

• Current pipeline stage for this prospect
• Follow-up preferences (decision deadline vs. scheduled review call)

Step 2: Confirm Prerequisites

Before building anything, verify:

• [ ] Diagnostic call notes are present — you have the prospect's primary constraint, stated goals, and situation specifics
• [ ] Capacity is confirmed — the proposed start date can be honored
• [ ] Engagement type and fee are decided — not in progress, decided
• [ ] Pipeline tracker is updated to reflect the diagnostic call outcome

If capacity is not confirmed: STOP. Do not build a proposal for a start date you cannot honor. Flag this to the user and halt until resolved.

If engagement type or fee is undecided: STOP. The proposal reflects a decision already made, not a decision in progress. Flag this and halt until resolved.

Step 3: Build the Proposal (Proposal Builder — Condensed)

Using the diagnostic call notes, engagement decision, and prospect details, produce a structured proposal.

3a. Situation Summary

Write 2-3 paragraphs summarizing the prospect's current state. Use their words from the diagnostic — if they said "we're drowning in onboarding," write that, not "the client experiences operational friction during client intake." Name the specific constraint, its symptoms, and its cost (in time, money, or missed opportunity).

Format: Prose paragraphs. No bullets. No headers. Direct second person ("You described...," "Your team currently...").

Rule: This section proves you listened. The prospect should read it and think: "That's exactly right."

3b. Proposed Approach

For each deliverable or workstream, write a short block (3-5 sentences):

• What you'll do (specific action, not vague promise)
• Why it matters (traced to something from the Situation Summary)
• What "done" looks like (the deliverable or outcome)

Number each workstream. Keep them in logical sequence. If you can't name what the client holds at the end of a workstream, rewrite it until you can.

3c. Scope & Boundaries

Be explicit about what's out. Most scope disputes come from assumptions, not bad faith.

3d. Timeline & Milestones

Every milestone must be verifiable — "Deliver findings brief" not "Complete discovery."

3e. Investment

State the fee clearly. No burying it. No apologizing for it.

• Total investment amount
• Payment terms and what triggers each payment
• Tier options if applicable (limit to 2-3, name by scope difference: "Core Engagement" vs. "Extended Engagement," not "Basic" vs. "Premium")

3f. Next Steps

Three clear actions:

1. What the prospect does to accept (sign, reply, schedule)
2. What happens immediately after acceptance (your first action)
3. Target start date or scheduling link

Include a validity window: "This proposal is valid for 14 days from the date above."

3g. Proposal Quality Check

Run these checks before proceeding:

Identify the weakest section. Rewrite it. Verify the rewrite improved clarity and specificity.

Step 4: Build the Value Justification Brief (Conditional)

Only run this step if the prospect expressed fee hesitation during the diagnostic call. If no hesitation was noted, skip to Step 5.

Using the constraint, proposed fee, expected outcomes, and the comparison the prospect raised, produce a focused value brief.

4a. Acknowledge the Concern

2-3 sentences validating the prospect's perspective. Don't dismiss. Don't be defensive.

Pattern: "You're right that [alternative] is less expensive. That's a fair comparison to consider. Here's what I'd want you to look at before making that decision."

4b. Honest Comparison

Don't trash the alternative. Name differences factually. Include at least one genuine advantage of the alternative.

4c. Your Differentiation

Three differentiators maximum, each with:

• What you do: Specific practice or methodology
• Why it matters to this prospect: Connected to their stated problem
• What it replaces: The thing they'd otherwise have to do themselves

4d. Results Evidence

1-2 relevant outcomes:

• Situation: Brief context similar to prospect's situation
• Outcome: Specific, measurable result
• Timeframe: How quickly the result materialized

Anonymize unless you have explicit permission.

4e. The Real Cost Calculation

• Cost of your engagement: [Your fee]
• Cost of the alternative: [Their fee + hidden costs + risk + time]
• Cost of doing nothing: [Monthly/annual cost of the unresolved problem]

Use conservative estimates. If you can't quantify the cost of doing nothing, estimate the time cost: "Your team spends approximately [X] hours per week managing this manually. At [blended rate], that's [amount] per month in labor alone."

4f. Value Brief Quality Check

Identify the weakest section. Rewrite it. Then use the value brief to strengthen the ROI framing in the proposal body (Step 3e Investment section) before it goes out.

Step 5: Generate the SOW (SOW Generator — Condensed)

Using the approved proposal scope, engagement type, timeline, fee, and payment terms, produce a formal statement of work.

5a. Engagement Overview

3-5 sentences covering:

• Who the parties are (your practice and the client)
• What type of engagement this is
• The overall objective (one sentence)
• The timeframe
• Reference to the proposal (by name and date)

Format: Prose paragraph. Formal but readable.

5b. Deliverables

For each deliverable, create a block:

Deliverable [Number]: [Name]

• Description: What it is, specifically (2-3 sentences)
• Format: How it's delivered (PDF, Notion page, live session, etc.)
• Revisions: How many iterations are included
• Complete when: How both sides know it's done

Describe deliverables as outputs, not activities. "Monthly advisory brief" not "ongoing advisory." Activities are scope black holes. Outputs have edges.

5c. Timeline & Milestones

Every milestone must be verifiable — something you can point to and say "this is complete" or "this is not complete." Meetings don't count unless they produce a tangible output.

5d. Payment Terms

• Total engagement investment: [Amount]
• Payment schedule:

Include: acceptable payment methods, late payment terms (if applicable), and what happens if the engagement is terminated early.

5e. Assumptions & Dependencies

List each assumption as a numbered item with consequence of violation:

1. [Client will provide X within Y business days of request] — If not met: [consequence]
2. [Key stakeholder Z will be available for sessions] — If not met: [consequence]
3. [Access to systems/data will be granted by start date] — If not met: [consequence]

Minimum 3 client-side assumptions. If you have fewer, you haven't thought hard enough about what could go wrong.

5f. Change Management

State the process for scope changes in one paragraph:

• How changes are requested (in writing)
• How changes are evaluated (impact on timeline, deliverables, investment)
• How changes are approved (signed change order)

Key point: no scope changes take effect without written agreement from both parties.

5g. Signatures

Include signature blocks for both parties:

• Your name, title, practice name, date
• Client name, title, organization, date
• Statement: "By signing below, both parties agree to the terms described in this Statement of Work."

Do not include legal terms like indemnification, liability caps, or IP ownership. Those belong in a separate MSA. The SOW is an operational document, not a legal one.

5h. SOW Quality Check

Identify the weakest section. Rewrite it. Verify the rewrite added concrete specifics. Review every line of the SOW for accuracy — this is the binding document.

Step 6: Prepare for Delivery

Before assembling the final output, confirm delivery readiness:

• [ ] Proposal includes a clear next step — a decision deadline or a scheduled follow-up call. "Let me know what you think" is NOT a next step.
• [ ] SOW is attached to the proposal for delivery
• [ ] Delivery will happen within one business day of the diagnostic call
• [ ] Pipeline record will be updated with proposal sent date
• [ ] Follow-up trigger is set for 5 business days out

Step 7: Assemble Final Output

Present one unified document containing:

A. Proposal

Output format:

Proposal: [Engagement Name]

Prepared for: [Prospect Name] Prepared by: [Your Name] Date: [Date]

Situation

[2-3 paragraphs. Prospect's words. Their problem. The cost of inaction.]

Proposed Approach

1. [Workstream Name] [What you'll do. Why it matters. What "done" looks like.]

2. [Workstream Name] [What you'll do. Why it matters. What "done" looks like.]

3. [Workstream Name] [What you'll do. Why it matters. What "done" looks like.]

Scope & Boundaries

Timeline

Investment

Total: [Amount]

Payment Terms: [Structure]

[Tier options if applicable]

Next Steps

1. To proceed: [Specific acceptance action]
2. Upon acceptance: [Your first action]
3. Target start date: [Date or scheduling link]

This proposal is valid for 14 days from the date above.

B. Value Justification Brief (if applicable)

If Step 4 was executed, include the complete brief. If Step 4 was skipped, omit this section entirely.

Output format:

Value Brief: [Prospect Name]

Re: [What they pushed back on] Date: [Date]

Your Concern

[2-3 sentences acknowledging the price comparison]

Side-by-Side Comparison

What We Do Differently

[Differentiator 1] [What + why it matters to them + what it replaces]

[Differentiator 2] [What + why it matters to them + what it replaces]

[Differentiator 3] [What + why it matters to them + what it replaces]

Results in Similar Situations

[Example 1]

• Situation: [Context]
• Outcome: [Measurable result]
• Timeframe: [Duration]

The Full Picture

• Our engagement: [Fee]
• [Alternative] + likely additions: [Estimated total]
• Cost of current state (monthly): [Estimate]

[1-2 sentences connecting the math to their decision]

C. Statement of Work

Output format:

Statement of Work: [Engagement Name]

Between: [Your Practice Name] and [Client Name] Effective Date: [Date] Reference: [Proposal Name and Date]

1. Engagement Overview

[3-5 sentences: parties, type, objective, timeframe]

2. Deliverables

Deliverable 1: [Name]

• Description: [What it is]
• Format: [How delivered]
• Revisions: [Number included]
• Complete when: [Criteria]

Deliverable 2: [Name] [Same structure]

3. Timeline & Milestones

4. Payment Terms

Total Investment: [Amount]

5. Assumptions & Dependencies

1. [Assumption] — If not met: [consequence]
2. [Assumption] — If not met: [consequence]
3. [Assumption] — If not met: [consequence]

6. Change Management

[Process for requesting, evaluating, and approving scope changes]

7. Agreement

By signing below, both parties agree to the terms described in this Statement of Work.

[Your Name] | [Client Name] [Title] | [Title] [Practice Name] | [Organization] Date: | Date:

D. Delivery Checklist

E. SOPs to Trigger

• [ ] Follow-Up Sequence Activation — trigger if no response by 5 business days after proposal sent
• [ ] New Client Intake Process — trigger when the prospect signs

Quality Check

Rules

1. Confirm capacity before building anything. A signed SOW for a start date you cannot honor is worse than no proposal at all. Check capacity before the proposal goes out, not after it comes back signed.
2. Collect all inputs in one pass. Do not scatter prompts across multiple turns. Ask once, flag gaps, keep moving.
3. The proposal mirrors the diagnostic call. It should read like a written confirmation of the conversation, not a new pitch. If the Situation Summary doesn't use the prospect's actual words, rewrite it.
4. Every deliverable names what the client holds when it's done. "Strategic assessment" is not a deliverable. "12-page operational audit with prioritized recommendations" is.
5. Send within one business day. Every day of delay dissipates the urgency the diagnostic call created. A proposal that lands a week later competes with a prospect who has already moved on mentally.
6. Never send without a defined next step. "Let me know what you think" produces indefinite silence. Every proposal needs either a decision deadline or a scheduled call to review it.
7. The SOW is not a summary of the proposal. It's the operating manual for the engagement. Every ambiguity you leave in becomes a conversation under worse conditions later.
8. Assumptions must state consequences of violation. "Client will provide timely feedback" is not an assumption. "Client will provide feedback within 5 business days of each deliverable — if not met, timeline shifts by the duration of the delay" is.
9. Never offer a discount in the Value Justification Brief. If the brief doesn't land, the prospect wasn't your client.
10. Dollar amounts use numerals ("\$5,000" not "five thousand dollars").
11. Proposal should fit on 2-3 pages when formatted. If it's longer, you're padding.
12. SOW should fit on 3-5 pages when formatted. Shorter means you missed something, longer means you're padding.
13. Never include legal terms in the SOW. No indemnification, liability caps, or IP ownership. Defer to MSA or attorney.
14. Never badmouth competitors or alternatives, even implicitly. Name differences, not deficiencies.
15. Include the 14-day validity window in Next Steps.
16. Escape dollar signs as \$ for Notion compatibility.
17. Flag inferred details. If an outcome, comparison point, or cost estimate was inferred rather than stated by the user, mark it [INFERRED — verify].

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.