How to Generate Sales-Aware Content

Audience: Fractional CMOs working with sales prospects

Time estimate: 3–5 minutes to read; applies to all /cmo-write content on sales minds

Prerequisites: Active sales/prospect mind; stored deal context (optional but recommended)

What's New

When you switch to a sales (prospect) client mind, Armbrain now automatically enriches your content generation with sales context. This means:

• /cmo-write works on sales minds (it used to fail). You can now generate proposals, objection-handling emails, and sales decks without switching back to a client mind.
• /cmo-write adapts its structure to the deal stage. A follow-up after discovery looks different from a follow-up after a proposal—Armbrain handles the stage-specific scaffolding for you.
• New "Objection Handler" expert joins your content panel when you have stored objections, reviewing proposals for proactive answers to known concerns.

This guide walks you through the patterns that unlock these capabilities.

Understanding Sales Minds vs. Client Minds

Sales client minds (also called prospect minds) represent deals in progress. They have a pipeline_stage that tracks where you are: lead → discovery → proposal → negotiation → closed_won/closed_lost.

When you switch to a sales mind, /cmo-write (and its follow-up mode) behaves differently:

Step 1: Populate Sales Context (Memories)

The magic of sales-aware content lives in stored memories. Before running /cmo-write, make sure you've captured:

Key Memory Types

Objections — what the prospect has said "no" or "I'm concerned about"

store_memory(
  content="The prospect said budget is constrained until Q3",
  memory_type="objection"
)

Buying Signals — green lights indicating momentum

store_memory(
  content="Mentioned they need this solved 'ASAP' and asked about implementation timeline",
  memory_type="buying_signal"
)

Pain Points — what the prospect needs solved

store_memory(
  content="Their current process requires manual outreach to 50+ accounts every Monday",
  memory_type="pain_point"
)

Competitive Alternatives — what else they're considering

store_memory(
  content="They're also evaluating Competitor X; interested in how we differ on reporting",
  memory_type="prospect_alternative"
)

These memories are optional—content generation works without them—but your output quality multiplies with stored context. The more you capture, the more specific and persuasive your content becomes.

Step 2: Understanding Pipeline Stages

Every sales mind has a pipeline_stage that tells Armbrain what stage of the deal you're in. When you run /cmo-write, the stage determines the follow-up structure:

Lead

Prospect is interested but unqualified. Follow-up should:

• Briefly recap their stated pain points
• Propose a discovery call agenda
• Keep tone helpful and low-pressure

Discovery

You've had an initial conversation. Follow-up should:

• Summarize key discussion points back to them (proves you listened)
• List their pain points (reference specific things they said)
• Address 1–2 objections they raised
• Propose the next step (strategy session or proposal)
• Keep tone consultative

Proposal

You've sent a formal proposal. Follow-up should:

• Reference the proposal directly
• Proactively address the top objection (from memories)
• Highlight buying signals ("You mentioned X was urgent—we prioritize that")
• Provide clear timeline and next steps
• Keep tone confident, action-oriented

Negotiation

You're working through terms. Follow-up should:

• Focus on resolving remaining objections
• Reference commitments from both sides
• Propose a specific close date
• Keep tone direct, collaborative

Closed Won

You've won. Follow-up should:

• Celebrate the win
• Reference the pain points that led to engagement
• Set expectations for the first 30 days
• Mention onboarding next steps
• Note: once the engagement starts, say "convert this prospect to a client" to upgrade the client mind

Closed Lost

Deal didn't close. Follow-up should:

• Close professionally
• Ask for feedback: "What could we have done differently?"
• Leave the door open for future engagement
• Store learnings as memories

Step 3: Run /cmo-write on Sales Minds

You can now draft proposals, sales emails, and objection-response content directly without switching to a client mind.

Example 1: Writing a proposal

Switch to the sales mind for Acme Corp.
/cmo-write a proposal that covers their three stated pain points, addresses the budget objection, and includes a 60-day implementation timeline.

Armbrain will:

1. Load objections, buying signals, pain points, and competitor context from memories
2. Surface these to the expert panel alongside your brand voice
3. Include an "Objection Handler" expert if you have stored objections
4. Generate a proposal that references specific pain points and addresses known objections proactively

Example 2: Writing an objection-response email

/cmo-write an email that addresses their concern about vendor lock-in. Reference our three-year partnership agreement and the escape clause.

The Objection Handler expert will review the draft to ensure you've acknowledged the concern, reframed it, provided evidence, and asked for the next step.

Example 3: Writing a sales deck one-pager

/cmo-write a one-pager for the Acme deck that leads with the pain points we've discussed, shows how we address each, and includes a clear CTA.

Step 4: Run /cmo-write on Sales Minds

After a meeting, call /cmo-write to generate a stage-appropriate follow-up email.

Switch to the sales mind for Acme Corp.
/cmo-write after today's discovery call.

Armbrain will:

1. Look up the pipeline stage (from the client mind's metadata)
2. Load recent objections and buying signals from memories
3. Generate a follow-up email with the stage-specific structure
4. Include a deal health score (for your reference, not shown to the recipient)
5. Suggest advancing the deal's pipeline stage if the follow-up implies one

The draft email will include:

• A header with the stage and deal health score (internal reference only)
• The stage-appropriate follow-up structure (from the table above)
• Specific references to objections, pain points, and buying signals from memories
• A nudge to advance the pipeline stage if progression is implied

Step 5: Advancing the Pipeline

When a follow-up email signals a stage change (e.g., you just sent a proposal), tell Armbrain to advance the deal in plain English:

"Advance Acme to the proposal stage -- $50K annual contract, 3-year commitment"

This updates the deal's pipeline status, so future follow-ups reflect the new stage automatically.

Edge Cases & Tips

No objections stored yet? The Objection Handler expert won't appear, but /cmo-write still works with whatever context is available. It gracefully adapts.

Pipeline stage is null? If a new sales mind doesn't have a stage set yet, /cmo-write defaults to "lead" behavior (brief intro, propose discovery call).

Updating a prospect to a client? Once you've closed the deal and migrated to a paid engagement, say "convert this prospect to a client" (or use /cmo-convert) to upgrade the prospect mind into a full client mind. This unlocks client features like content on campaigns, Business OS rocks/sprints, and cross-client summaries.

Can I write non-sales content on a sales mind? Yes. You might run /cmo-write a blog post about our methodology on a sales mind. Armbrain will still load sales context—having extra prospect pain points won't hurt, and the expert panel will use or ignore it as appropriate.

Quick Reference: When to Use What

What You'll Notice

Faster iterations: No need to switch client minds or manually look up prospect context. It's all loaded automatically.

Stage-appropriate language: Your follow-ups will reference what matters at each stage. Post-discovery is consultative; post-proposal is confident and action-oriented.

Objection-proactive content: Proposals and emails address known concerns before the prospect brings them up, shortening negotiation cycles.

Deal transparency: Deal health scores and stage context keep you informed of pipeline momentum without extra lookups.