Skip to content
ESP32 IoT Tutorial

Writing Pre-Sales Proposals with SCQA

Writing Pre-Sales Proposals with SCQA

Section titled “Writing Pre-Sales Proposals with SCQA”

Overview

Section titled “Overview”

This section combines the SCQA framework with JTBD methodology and ethnography research to systematically guide writing persuasive IoT pre-sales proposals. After completing this section, you will be able to:

  • Master the structure and writing points of a complete pre-sales proposal
  • Use JTBD + ethnography + SCQA to build a “value narrative” for proposals
  • Adjust proposal expression for different audiences (executives/managers/engineers)
  • Write ROI analysis and risk assessment sections

Prerequisites

Section titled “Prerequisites”

Before starting this section, ensure:

  • Completed sections 01-04 on JTBD, ethnography, and SCQA methods
  • Practiced the needs mapping from section 02
  • Have a real customer scenario or simulated project for practice

Key Concepts

Section titled “Key Concepts”

The Nature of Pre-Sales Proposals

Section titled “The Nature of Pre-Sales Proposals”

A good pre-sales proposal is not a “technical specification” but a “persuasive document.” Its core task is:

Make the customer believe:
1. You truly understand my problems (Empathy)
2. Your solution can solve my problems (Capability)
3. You can deliver the solution (Execution)
4. The investment is worthwhile (Value)

These four trust elements correspond to SCQA narrative + technical architecture proof + ROI analysis.

Complete Proposal Structure

Section titled “Complete Proposal Structure”

A full IoT pre-sales proposal contains these sections, mapped to SCQA/JTBD/Ethnography:

┌─────────────────────────────────────────────────────────────┐
│  Proposal Section     │  Framework         │  Core Question  │
├─────────────────────────────────────────────────────────────┤
│  1. Cover + Executive │  A (Summary)       │  What can you   │
│     Summary           │                    │  do for me?     │
│  2. Project Background│  S + C             │  Do you really  │
│     & Understanding   │                    │  understand me? │
│  3. Needs Analysis    │  JTBD + Ethnography│  Do you know    │
│                       │                    │  my needs?      │
│  4. Solution          │  A (Detailed)      │  How will you   │
│                       │                    │  solve it?      │
│  5. Technical Arch.   │  C4 Model          │  Is it sound?   │
│  6. Implementation    │  Project Mgmt      │  How long?      │
│  7. Investment & ROI  │  ROI Analysis      │  Worth it?      │
│  8. Success Stories   │  Social Proof      │  Used by others?│
│  9. Company Qualif.   │  Trust             │  Are you        │
│                       │                    │  reliable?      │
└─────────────────────────────────────────────────────────────┘

Writing Guide for Each Section

Section titled “Writing Guide for Each Section”

1. Cover + Executive Summary

Section titled “1. Cover + Executive Summary”

Purpose: In 30 seconds, tell the decision-maker “what value this proposal offers.”

Writing tips:

  • Title should include customer name + core value (not just “Technical Proposal”)
  • Summary under 200 words, using SCQA structure

Example:

❌ Bad title:
"XX Company IoT Technical Proposal"


✅ Good title:
"XX Food Processing Plant — 24/7 Smart Environmental Monitoring
 Abnormal response from 4 hours to 5 minutes, annual risk savings 2M+"


Summary (SCQA structure):
[S] Annual output 80M yuan, supplying 3 major supermarkets.
[C] Manual inspection, last month 200K product waste from nighttime temp anomaly,
    supermarket issued supplier qualification warning.
[Q] How to achieve 24/7 automated monitoring to prevent recurrence?
[A] Deploy 12-node smart monitoring system, 2-week delivery, 80K investment,
    annual risk savings 2M+.

2. Project Background & Understanding (S + C)

Section titled “2. Project Background & Understanding (S + C)”

Purpose: Prove to the customer “you truly understand our situation.”

Writing tips:

  • S (Situation): Describe the customer’s current status using ethnography observations + JTBD interview data
  • C (Complication): Reveal pain points and risks with quantified impact

3. Needs Analysis (JTBD + Ethnography)

Section titled “3. Needs Analysis (JTBD + Ethnography)”

Purpose: Present customer needs using JTBD and ethnography insights, showing “we know what jobs you need to accomplish and how you actually work.”

Writing tips:

  • List Job Statements (functional/emotional/social)
  • Present key ethnography findings (“what users actually do vs. what they say”)
  • Show priority ranking results
  • Define MVP scope and long-term goals

4. Solution (A — Detailed)

Section titled “4. Solution (A — Detailed)”

Purpose: Show how the solution addresses each conflict and need.

Writing tips:

  • One-paragraph solution overview (elevator pitch)
  • Each feature module mapped to specific JTBDs and ethnography findings
  • Use “Feature → Resolved conflict → Created value” three-part description

5. Technical Architecture (C4 Model)

Section titled “5. Technical Architecture (C4 Model)”

Purpose: Layered technical architecture to prove feasibility.

📌 Detailed C4 model drawing methods covered in sections 07-12

6. Implementation Plan

Section titled “6. Implementation Plan”

Purpose: Show timeline and milestones to build confidence in timely delivery.

Template:

| Phase | Timeline | Deliverables | Acceptance Criteria |
|-------|----------|-------------|-------------------|
| Requirements | Week 1 | Requirements spec | Customer sign-off |
| Hardware | Week 2-3 | Sensor nodes online | Data uploading normally |
| Software | Week 3-5 | Platform features live | Function tests pass |
| Integration | Week 6 | Test report | Acceptance tests pass |
| Pilot | Week 7-8 | Operations report | 7 days fault-free |
| Handover | Week 9 | Operations docs | Training complete |

7. Investment & ROI

Section titled “7. Investment & ROI”

Purpose: Help decision-makers judge “is this investment worthwhile?”

Writing tips:

  • Clear investment breakdown (hardware/software/implementation/maintenance)
  • ROI calculation using customer-understandable metrics (money, time, frequency)
  • Provide conservative/moderate/optimistic projections

Template:

### Investment Breakdown
| Category | Item | Unit Price | Qty | Subtotal |
|----------|------|-----------|-----|----------|
| Hardware | ESP32 sensor nodes | $30 | 12 | $360 |
| Hardware | Industrial gateway | $120 | 2 | $240 |
| Software | Monitoring platform | — | 1 | $4,500 |
| Services | Installation & config | — | 1 | $3,000 |
| Services | Annual maintenance | — | 1 | $900 |
| **Total** | | | | **$9,000** |


### ROI Analysis
| Metric | Current | After Deployment | Improvement |
|--------|---------|-----------------|-------------|
| Anomaly response time | 4 hours | 5 minutes | 98%↓ |
| Annual waste losses | $90K | $7K | 92%↓ |
| Manual inspection hours | 480 hrs/year | 0 | 100%↓ |


### Payback Period
- Annual risk cost savings: $83K
- Annual labor savings: $12K
- Payback: $9K ÷ $95K ≈ **1.1 months**

8. Success Stories

Section titled “8. Success Stories”

Purpose: Build trust through social proof.

Writing tips:

  • Select cases similar to the target customer’s industry/scale
  • Brief each case using SCQA structure (1-2 paragraphs)
  • Highlight quantified results

Audience-Specific Proposal Strategy

Section titled “Audience-Specific Proposal Strategy”

Different customer stakeholders focus on different aspects:

┌────────────────────────────────────────────────────────────┐
│  Audience      │  Focus                │  SCQA Emphasis    │
├────────────────────────────────────────────────────────────┤
│  Decision      │  ROI, strategic value  │  A (Summary) +   │
│  Makers        │  "Is it worth it?"     │  ROI Analysis    │
│  (CEO/Owner)   │                        │  Answer-First    │
├────────────────────────────────────────────────────────────┤
│  Managers      │  Feasibility, timeline │  S+C + Implemen- │
│  (Dept. Head)  │  "Can it be done?"     │  tation Plan     │
│                │                        │  Standard        │
├────────────────────────────────────────────────────────────┤
│  Engineers     │  Technical details,    │  A (Detailed) +  │
│  (Tech Staff)  │  maintenance effort    │  Tech Arch.      │
│                │  "Is it easy to use?"  │  Feasibility     │
└────────────────────────────────────────────────────────────┘

Proposal Quality Checklist

Section titled “Proposal Quality Checklist”

Before submitting, self-check:

Narrative Logic:

  • Does the summary use SCQA structure, under 200 words?
  • Does S use the customer’s specific scenarios and data?
  • Does C quantify conflict impact (money/time/frequency)?
  • Does Q naturally derive from C?
  • Does A directly respond to each conflict in C?

Needs Coverage:

  • Does every feature map to a JTBD?
  • Are emotional/social jobs addressed in the proposal?
  • Are ethnography findings used to guide solution design decisions?
  • Is there a Requirements Traceability Matrix?

Persuasiveness:

  • Can a decision-maker grasp core value within 5 minutes?
  • Does ROI use customer-understandable metrics?
  • Are success stories similar to the target scenario?

Professionalism:

  • Is technical architecture shown in C4 model layers?
  • Does the implementation plan have clear milestones?
  • Are risks and mitigation strategies included?

Verification

Section titled “Verification”

Verify mastery of pre-sales proposal writing:

  1. Proposal Design

    • Can design a complete 9-section proposal structure for an IoT scenario
    • Can write a 200-word SCQA executive summary
    • Can adjust emphasis for different audiences

  2. Value Quantification

    • Can calculate project ROI and payback period
    • Can present three projections (conservative/moderate/optimistic)

  3. Quality Control

    • Can assess proposal quality using the self-check list
    • Can identify common defects in proposals

Best Practices

Section titled “Best Practices”
  • ✅ Recommended: Write SCQA four-element summary before starting the full proposal
  • ✅ Recommended: Write the executive summary last (after all sections are complete)
  • ✅ Recommended: Use “customer language” not “technical language” for S and C
  • ✅ Recommended: Use conservative estimates for ROI, leave safety margin
  • ✅ Recommended: Prepare a 1-page executive brief (One-Pager) for decision-makers
  • ❌ Avoid: Starting the proposal with technical architecture in chapter 1
  • ❌ Avoid: Opaque cost breakdown (hidden fees kill trust)
  • ❌ Avoid: Success stories that don’t match the customer scenario
  • ❌ Avoid: Only showing benefits without mentioning risks (appears unprofessional)

Summary

Section titled “Summary”

Key takeaways from this section:

  1. A pre-sales proposal is a persuasive document

    • Core task: Build four types of trust (empathy/capability/execution/value)
    • 9 sections combine SCQA/JTBD/Ethnography/C4 methodologies

  2. Section-to-framework mapping

    • Summary = SCQA condensed
    • Background = S + C (informed by ethnography)
    • Needs Analysis = JTBD + Ethnography
    • Solution = A (detailed)
    • Architecture = C4 Model
    • ROI = Quantified value

  3. Adjust expression for different audiences

    • Decision-makers: value and ROI
    • Managers: feasibility and plan
    • Engineers: technical details

  4. Quality self-check is mandatory

    • Four dimensions: narrative logic, needs coverage, persuasiveness, professionalism

References

Section titled “References”
Building a commercial IoT product?

We provide ESP32 ODM design-to-manufacturing services. From prototype to production — the team behind this tutorial can build it with you.

Talk to us →