Files
blackroad-os-sales-playbook/05-execution/PROPOSAL_TEMPLATES.md
Alexa Louise 035795259b 🚀 Phase 3 Progress: CRM + Closing + Proposals
Added 3 critical execution documents:

## 06-operations/CRM_GUIDELINES.md (5,500+ words)
- Complete HubSpot CRM implementation guide
- Data hygiene rules and standards
- Deal stage definitions & criteria
- Activity logging templates
- BANT++ and ICP score tracking
- Forecasting methodology (weighted pipeline)
- Custom fields for BlackRoad OS
- Dashboard frameworks (rep, manager, exec)
- CRM automation workflows
- Monthly audit checklist
- Performance metrics

## 05-execution/CLOSING_TECHNIQUES.md (6,000+ words)
- 10 proven closing techniques:
  * Assumptive Close
  * Trial Close
  * Summary Close
  * Urgency Close
  * Alternative Close (Binary)
  * Puppy Dog Close (Trial/Pilot)
  * Question Close
  * Takeaway Close
  * ROI Close
  * Deadline Close
- Closing signals (verbal & non-verbal)
- Common closing mistakes & fixes
- "I need to think about it" framework
- Multi-threaded close for enterprise
- Post-close actions
- Closing by persona (CTO, CFO, CEO, DevOps)

## 05-execution/PROPOSAL_TEMPLATES.md (5,000+ words)
- Complete 8-page proposal structure
- 4 scenario-specific templates:
  * SMB/Core Tier
  * Enterprise
  * Financial Services (RIA/BD)
  * Competitive Displacement
- ROI calculation frameworks
- Pricing presentation strategies
- Technical solution architecture
- Terms & conditions
- Proposal delivery checklist
- Cover email templates
- Proposal metrics & tracking

## Stats:
- 3 new documents
- 16,500+ words added
- 10 closing techniques
- 4 proposal templates
- Complete CRM implementation guide

Total playbook now: 19 documents, 81,500+ words

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-04 15:49:09 -06:00

516 lines
13 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 📄 Proposal Templates Library
**PROPRIETARY & CONFIDENTIAL**
---
## Overview
**A great proposal tells a story.**
Your proposal should:
1. Recap their pain points (you listened)
2. Present your solution (tailored to them)
3. Quantify the value (ROI)
4. Make it easy to say yes (clear next steps)
**Length: 5-8 pages max. Any longer and they won't read it.**
---
## Proposal Structure (Standard)
### Page 1: Executive Summary
**Purpose:** Decision-makers read this first. Make it count.
**Structure:**
```
[Company Logo] + BlackRoad OS Logo
PROPOSAL FOR [COMPANY NAME]
[Product Tier] - [Date]
Executive Summary
[Company] is facing three key infrastructure challenges:
1. [Pain point 1] - costing [$X/year or Y hours/week]
2. [Pain point 2] - preventing [desired outcome]
3. [Pain point 3] - creating [business risk]
BlackRoad OS solves these challenges by:
✅ [Solution to pain 1] - saving [$X/year or Y hours/week]
✅ [Solution to pain 2] - enabling [outcome]
✅ [Solution to pain 3] - mitigating [risk]
Expected Outcomes:
- [Quantified benefit 1] (e.g., "40% infrastructure cost reduction")
- [Quantified benefit 2] (e.g., "Deploy 10x faster")
- [Quantified benefit 3] (e.g., "SOC 2 compliant in 3 months")
Investment: $[X]/year
ROI: [Y]%
Payback Period: [Z] months
Recommended Next Step: [Start date], [Implementation timeline]
```
---
### Page 2: Business Case
**Purpose:** Quantify the problem and the solution.
**Structure:**
#### Current State Analysis
| Challenge | Annual Cost | Business Impact |
|-----------|-------------|-----------------|
| [Pain 1] | $X | [Impact description] |
| [Pain 2] | $Y | [Impact description] |
| [Pain 3] | $Z | [Impact description] |
| **Total** | **$XXX** | |
#### Future State with BlackRoad OS
| Improvement | Annual Savings | Business Outcome |
|-------------|----------------|------------------|
| [Solution 1] | $A | [Outcome] |
| [Solution 2] | $B | [Outcome] |
| [Solution 3] | $C | [Outcome] |
| **Total Savings** | **$YYY** | |
#### ROI Calculation
```
Current Annual Cost: $XXX
BlackRoad OS Investment: $ZZZ
Net Annual Savings: $YYY
ROI: ((YYY / ZZZ) × 100)%
Payback Period: (ZZZ / YYY) × 12 months
```
---
### Page 3: Technical Solution
**Purpose:** Show how it works (for technical buyers).
**Structure:**
#### Proposed Architecture
[Include diagram: Current state → Future state with BlackRoad OS]
#### Implementation Phases
| Phase | Timeline | Deliverables |
|-------|----------|--------------|
| **Phase 1: Setup** | Weeks 1-2 | Infrastructure provisioning, SSO integration |
| **Phase 2: Migration** | Weeks 3-4 | Migrate [X] applications to BlackRoad OS |
| **Phase 3: Optimization** | Weeks 5-6 | Performance tuning, cost optimization |
| **Phase 4: Training** | Week 7 | Team onboarding, knowledge transfer |
#### Integration Points
- **Cloud Provider:** [AWS / Azure / GCP]
- **CI/CD:** [GitHub Actions / Jenkins / GitLab CI]
- **Monitoring:** [Datadog / New Relic / Prometheus]
- **Security:** [Okta / Auth0 for SSO]
- **Compliance:** [SOC 2 / HIPAA / ISO 27001]
#### Success Metrics
- **Week 2:** First application deployed
- **Week 4:** [X] applications migrated
- **Week 8:** Full production workload
- **Month 3:** [Quantified improvement metric]
---
### Page 4: Pricing & Investment
**Purpose:** Make pricing transparent and easy to understand.
**Structure:**
#### Year 1 Investment
| Item | Quantity | Unit Price | Total |
|------|----------|------------|-------|
| **BlackRoad OS [Tier]** | 12 months | $X/month | $XX,XXX |
| **Professional Services** | [Y] hours | $Z/hour | $YY,YYY |
| **Training** | [N] people | $A/person | $B,BBB |
| **TOTAL YEAR 1** | | | **$###,###** |
#### Year 2-3 Projection
| Year | Platform Subscription | Expected Savings | Net Cost |
|------|---------------------|------------------|----------|
| **Year 1** | $XX,XXX | $YY,YYY | $(Z,ZZZ) savings |
| **Year 2** | $XX,XXX | $YY,YYY | $(Z,ZZZ) savings |
| **Year 3** | $XX,XXX | $YY,YYY | $(Z,ZZZ) savings |
| **3-Year Total** | $AAA,AAA | $BBB,BBB | **$(CCC,CCC)** |
#### Payment Terms
- **Annual Prepay:** 15% discount (2 months free)
- **Quarterly:** Standard pricing
- **Monthly:** +5% (billed monthly)
**Recommended:** Annual prepay for maximum savings
---
### Page 5: Why BlackRoad OS
**Purpose:** Differentiate from competitors.
**Structure:**
#### vs. Building In-House (DIY)
| Factor | DIY Kubernetes | BlackRoad OS | Winner |
|--------|----------------|--------------|--------|
| **Time to Production** | 6-12 months | 2-4 weeks | ✅ **Us** |
| **Headcount Required** | 5-10 DevOps engineers | 0-2 engineers | ✅ **Us** |
| **Annual Cost** | $1M-$2M (salaries) | $180K-$500K | ✅ **Us** |
| **Risk** | High (you own everything) | Low (we manage platform) | ✅ **Us** |
#### vs. [Primary Competitor]
| Feature | [Competitor] | BlackRoad OS | Winner |
|---------|--------------|--------------|--------|
| [Feature 1] | ❌ or ⚠️ | ✅ | ✅ **Us** |
| [Feature 2] | ✅ | ✅ | Tie |
| [Feature 3] | ❌ | ✅ | ✅ **Us** |
| **Price** | $X | $Y | ✅ **Us** (lower TCO) |
#### Customer Success Stories
**[Similar Customer 1]:**
- Industry: [Same industry as prospect]
- Challenge: [Same pain point]
- Result: [Quantified outcome]
> "[Customer quote about results]"
> [Name, Title, Company]
---
### Page 6: Terms & Conditions
**Purpose:** Set expectations on contract terms.
**Structure:**
#### Contract Terms
- **Contract Length:** 1 year (auto-renews unless 60-day notice)
- **Payment Terms:** Net-30 for monthly, Net-0 for annual prepay
- **SLA:** 99.99% uptime guarantee (Enterprise tier)
- **Support:** 24/7 email/Slack support, 4-hour response time
- **Renewal:** Price locked for [1 / 3] year(s)
#### What's Included
- ✅ Platform access for [X] users
- ✅ Unlimited deployments
- ✅ [Y] nodes under management
- ✅ Automated scaling and failover
- ✅ SOC 2 Type II certified infrastructure
- ✅ Dedicated Customer Success Manager
- ✅ Quarterly business reviews
#### What's Not Included (Add-Ons)
- Managed Services: +$[X]/month (we operate infrastructure for you)
- Additional users: $[Y]/user/month
- Custodian integrations (Financial Services): $[Z] setup + $[A]/month
---
### Page 7: Next Steps & Timeline
**Purpose:** Make it easy to say yes.
**Structure:**
#### Recommended Timeline
| Milestone | Date | Owner |
|-----------|------|-------|
| **Contract Review** | [Date] | [Company] Legal |
| **Contract Signed** | [Date] | Both parties |
| **Kickoff Call** | [Date] | BlackRoad OS |
| **Implementation Start** | [Date] | BlackRoad OS + [Company] |
| **Go-Live** | [Date] | Both parties |
#### Your Next Steps
1. **Review Proposal:** Share with stakeholders (CTO, CFO, etc.)
2. **Schedule Q&A:** If questions arise, we'll schedule a call
3. **Legal Review:** Send to your legal/procurement team
4. **Sign Contract:** Via DocuSign (sent separately)
#### Our Next Steps
1. **Answer Questions:** Available immediately via email/Slack
2. **Provide References:** Connect you with [Similar Customer]
3. **Schedule Kickoff:** Once contract signed
4. **Begin Implementation:** [X] weeks from signature
#### Questions?
**Contact:**
- Sales: [Your Name] - [your.email@blackroad.io]
- Solutions Engineering: [SE Name] - [se.email@blackroad.io]
- Legal: legal@blackroad.io
---
### Page 8: Appendix (Optional)
**Include if helpful:**
- Detailed technical architecture diagram
- Security & compliance certifications
- Full customer reference list
- Glossary of terms
---
## Proposal Templates by Scenario
### Template 1: SMB / Core Tier
**Use For:** Small-to-mid companies, $30K-$100K ACV
**Emphasis:**
- Simplicity (easy to get started)
- Cost savings (vs. hiring DevOps team)
- Time to value (live in 2 weeks)
**Key Sections:**
- ROI calculation (savings vs. headcount)
- Simple pricing (one line item)
- Fast implementation (2-4 weeks)
---
### Template 2: Enterprise
**Use For:** Large companies, $180K-$500K+ ACV
**Emphasis:**
- Scalability (handle enterprise workloads)
- Compliance (SOC 2, ISO 27001, industry-specific)
- Support (24/7, dedicated CSM)
**Key Sections:**
- Compliance features (audit trails, RBAC, certifications)
- Complex pricing (multiple line items)
- Phased implementation (8-12 weeks)
---
### Template 3: Financial Services (RIA/BD)
**Use For:** RIAs, broker-dealers, WealthTech
**Emphasis:**
- Regulatory compliance (SEC 17a-4, FINRA, SOC 2)
- Security (encryption, access controls)
- Custodian integrations (Schwab, Fidelity, Pershing)
**Key Sections:**
- Compliance overview (how we meet SEC/FINRA requirements)
- AUM-based pricing
- Regulatory timeline (e.g., "SOC 2 by Q2 deadline")
---
### Template 4: Competitive Displacement
**Use For:** Replacing incumbent vendor (AWS DIY, OpenShift, etc.)
**Emphasis:**
- Migration plan (how we move you off competitor)
- Risk mitigation (zero downtime, rollback plan)
- Cost comparison (TCO vs. current vendor)
**Key Sections:**
- Side-by-side competitive comparison
- Migration timeline (phased approach)
- Risk mitigation (pilot program, gradual rollout)
---
## Proposal Best Practices
### Do's ✅
1. **Personalize Everything**
- Use their company name throughout
- Reference specific pain points from discovery
- Include their logo (with permission)
2. **Quantify Value**
- Use real numbers (not vague claims)
- Show ROI calculation
- Reference industry benchmarks
3. **Make It Visual**
- Use charts, diagrams, tables
- Break up text with headers
- Include screenshots or mockups
4. **Keep It Concise**
- 5-8 pages max (not 50-page novels)
- Executive summary on page 1
- Appendix for details (if needed)
5. **Present It Live**
- Schedule call to walk through proposal
- Answer questions in real-time
- Advance to next step immediately
---
### Don'ts ❌
1. **Don't Send Generic Proposals**
- No "copy-paste" from last deal
- Tailor to their specific needs
2. **Don't Hide Pricing**
- Be transparent about costs
- No "contact us for pricing" (frustrating)
3. **Don't Overpromise**
- If a feature is on roadmap but not live, say so
- Set realistic timelines
4. **Don't Forget Next Steps**
- Always include clear call-to-action
- Propose specific dates
5. **Don't Email and Ghost**
- Follow up within 24 hours
- Schedule review call
---
## Proposal Delivery Checklist
### Before Sending
- [ ] Spell-check (typos = unprofessional)
- [ ] Proofread numbers (double-check math)
- [ ] Personalize (company name, pain points, contacts)
- [ ] Include visuals (charts, diagrams)
- [ ] Get internal review (manager or SE approval)
- [ ] Prepare to present live (don't just email)
### When Sending
- [ ] Send via email + upload to HubSpot
- [ ] Include cover email (summary + call-to-action)
- [ ] CC relevant stakeholders (SE, manager if needed)
- [ ] Schedule follow-up call (within 48 hours)
### After Sending
- [ ] Follow up within 24 hours ("Did you receive?")
- [ ] Schedule review call (walk through proposal)
- [ ] Answer questions immediately
- [ ] Update CRM (deal stage → "Proposal Sent")
- [ ] Set reminder to follow up (if no response in 3 days)
---
## Cover Email Template
**Subject:** Proposal for [Company] - BlackRoad OS [Tier]
**Body:**
```
Hi [Name],
Thanks for the great conversation earlier this week. As promised, I've put together
a proposal that addresses your infrastructure challenges.
Key highlights:
✅ [Pain point 1] → [Solution] → [Quantified benefit]
✅ [Pain point 2] → [Solution] → [Quantified benefit]
✅ [Pain point 3] → [Solution] → [Quantified benefit]
Investment: $[X]/year
ROI: [Y]% in year one
Payback: [Z] months
I'd love to walk you through this. Are you available for a 30-minute call on
[specific date/time options]?
Alternatively, feel free to review and let me know if you have questions.
Looking forward to partnering with [Company]!
Best,
[Your Name]
```
---
## Proposal Metrics
Track proposal effectiveness:
| Metric | Target | How to Improve |
|--------|--------|----------------|
| **Proposal-to-Close Rate** | >50% | Better qualification (only propose to qualified deals) |
| **Time to Review** | <7 days | Create urgency, follow up daily |
| **Proposal Requests** | 100% | If they ask for proposal, send within 24 hours |
| **Live Presentation Rate** | >80% | Always schedule call to present (don't just email) |
---
## Tools
**Recommended Proposal Software:**
- **PandaDoc** (templates, e-signature, tracking)
- **Proposify** (templates, analytics)
- **Qwilr** (modern, interactive proposals)
- **Google Slides + PDF** (free, simple)
**Tracking:**
- HubSpot CRM (log proposals as activities)
- Gong/Chorus (record presentation calls)
---
## FAQs
**Q: How long should a proposal be?**
A: 5-8 pages. Execs read page 1 (executive summary). Technicals read pages 2-3.
**Q: Should I send the contract with the proposal?**
A: No. Send proposal first, get feedback, then send contract when ready to close.
**Q: What if they don't respond to the proposal?**
A: Follow up 3 times (day 1, day 3, day 7). Then send "break-up email."
**Q: Can I reuse proposals?**
A: Yes, but personalize. Never send a generic "copy-paste" proposal.
**Q: Should I include pricing?**
A: Yes. Transparent pricing builds trust. If pricing is complex, provide range and offer to discuss.
---
**Version:** 1.0.0
**Last Updated:** January 4, 2026
**Owner:** Joaquin, Sales Master
*A great proposal tells a story. Make it their story.*