Sales Calls Growth Strategy for Climate Tech Using StoryBrand

# Sales Calls Growth Strategy for Climate Tech Using StoryBrand **Category:** Sales → Sales Calls | **Audience:** Professionals or practitioners using AI for sales calls tasks. | **Delivery:** User-specified channel or workflow **Job:** Improve the named business/performance outcome using a measurable, testable intervention. ## SOURCE INPUT Use this source brief as the authoritative task/scenario. Preserve its supplied numbers, constraints, assets, frameworks and requested deliverables. Separate facts from assumptions; never invent missing evidence. > Treat this as the authoritative source brief. Preserve useful specifics; do not invent facts or turn scenario values into verified claims. > > > Act as Senior Sales Calls Strategist for Sales (experienced, scaled Climate Tech to 8-figures, experienced technology/product background, generated substantial commercial experience with this system). CONTEXT: Business: Climate Tech - $500k ARR, team 36, targeting Gen Z, stage pre-seed Current: CAC $91, LTV $1766, churn 7%, traffic 42767/mo, conversion 3.0% Assets: Notion docs + SOPs Goal: increase conversion 32% in 90 days Constraint: Budget $15k/mo, solo founder Tone: scientific McKinsey FRAMEWORK: StoryBrand + structured 4-step. TASK: Complete Sales Calls system for Sales / Climate Tech. - common failure modes about sales calls for Climate Tech - 5 Whys root cause for increase conversion 32% - Hidden cost of failure - Contrarian insight advanced practitioner insight ## Sales-message experiment variants > Variant A — PROBLEM / PAIN: Build the sales approach around a verified customer problem and quantify its business impact. > Variant B — PROOF / AUTHORITY: Build the approach around evidence, credibility, proof and risk reduction. > Variant C — OBJECTION / DECISION: Build the approach around the strongest buying objection and a low-friction next step. > For each, specify audience, hypothesis, message, CTA, qualification signal and success metric. Do not produce three cosmetic rewrites. ## METHOD **Workflow:** Situation → ICP/segment → diagnosis → value proposition → objection handling → execution → measurement → decision **Execution** - Diagnose the actual task before prescribing when diagnosis changes the answer. - Make the key strategic/technical/creative decision explicit. - Use concrete instructions, structures, examples, thresholds or implementation details. - Distinguish supplied facts, assumptions and validation needs. - Do not invent capabilities, results, claims or evidence. **Model / delivery** Target model(s): ChatGPT-4o, Claude 3.5, Gemini 1.5. Keep the core solution portable; adapt only relevant model behavior. Delivery context: User-specified channel or workflow; respect its real format, audience and constraints. **Output contract** Return the smallest complete deliverable that solves the job. Include the result, material assumptions, measurable/verifiable success criteria where relevant, and next decision/action when useful. **QA** - buyer and buying stage are clear - value proposition matches buyer pain - objections are concrete - next action is explicit - claims are evidence-aware Also check for contradictions, generic recommendations, unusable outputs and constraint violations. ## CONTROLLED VARIANTS Use variants only as real experiments; never as paraphrases. **A — Value framing:** change value proposition framing; preserve buyer and offer. Preserve core identity/facts. Define the hypothesis, changed variable, expected effect and decision criterion. **B — Objection handling:** change the dominant objection mechanism; preserve core offer. Preserve core identity/facts. Define the hypothesis, changed variable, expected effect and decision criterion. **C — Decision enablement:** change proof/decision support; preserve buyer stage. Preserve core identity/facts. Define the hypothesis, changed variable, expected effect and decision criterion. ## FINAL GATE Before answering, ask: Is this specific to the supplied scenario? Is every important instruction actionable? Are assumptions labeled? Is the output genuinely usable? Would a professional get a better result from this than from a generic prompt? If not, revise the weakest part before delivering.