SOP-REV-proposal-followup-generation-v1.0

1. Purpose

Define how the CRO generates, sends, and tracks follow-up communications after an Assessment™ proposal has been delivered. Ensures no proposal sits without a structured response sequence — and that stale proposals are resolved, not left in limbo.

Context: Once a proposal is sent (Prospects board stage = "Proposal out"), the clock starts. This SOP governs the window between proposal delivery and resolution (Closed-won, Closed-lost, or Nurture).

2. Response Window and Follow-Up Sequence

Day from proposal sent	Action
Day 0	Proposal sent. sales.ops logs date in Prospects board. 7-day reminder set in Monday.com.
Day 7	No response → CRO sends Follow-up Touch 1 (see Section 3). sales.ops logs. 7-day reminder reset.
Day 14	Still no response → CRO sends Follow-up Touch 2 (final). sales.ops logs.
Day 14 + 1	If no response to Touch 2 → CRO moves to Nurture or Closed-lost per Section 4.
Any day	Prospect responds → CRO advances to Closed-won, Closed-lost, or Nurture per SOP-REV-opportunity-inspection-v1.0.

Two follow-up touches max. Do not send a third. Persistence past two touches signals disrespect for their process; move them appropriately and focus on active pipeline.

3. Follow-Up Format

Follow-up communications are sent by CRO from info@ecomonetize.com. They are: - Brief — 3-5 sentences maximum - Specific — reference the prospect's situation, not a generic template - Value-reinforcing — one sentence on why this is worth their attention now - Low-pressure — open question, not a close

Follow-up Touch 1 template (Day 7):

Subject: Following up — Ecosystem Revenue Architecture Assessment™

Hi [Name],

I wanted to follow up on the Assessment™ proposal I sent last week. 
[One specific sentence connecting to their situation or a relevant signal you've noticed.]

Is now still a good time? Happy to answer any questions or adjust scope if needed.

— [CRO name]

Follow-up Touch 2 template (Day 14):

Subject: Re: Following up — Ecosystem Revenue Architecture Assessment™

Hi [Name],

One last check-in before I close out this thread. Completely understand if timing isn't right — I'd rather know now than leave this hanging.

If now isn't the moment, happy to reconnect in [suggested timeframe]. Just let me know.

— [CRO name]

Both templates are living documents. CRO may adapt language; the structure and tone principles are non-negotiable.

4. Resolution After Follow-Up

Outcome	Action
Response received — moving forward	CRO advances stage to Closed-won; triggers SOP-REV-assessment-handoff-v0
Response received — timing mismatch	CRO moves to Nurture; logs "check back {date}" in Prospects board
Response received — explicit decline	CRO moves to Closed-lost; logs reason code
No response after Touch 2	CRO moves to Nurture (default) or Closed-lost (if disqualification criteria met); logs "no response after 2 touches — {date}"

Default for no-response is Nurture, not Closed-lost. Silence is not the same as rejection. Re-engage in 90 days with a new signal or context.

5. Logging Requirements

sales.ops logs every follow-up touch in the Prospects board item:

[YYYY-MM-DD] Follow-up Touch [1/2] sent by CRO.
Subject: {subject line}
Response received: [Y/N]
Next action: {stage advancement or next touch date}

All entries timestamped. No verbal-only follow-up — if CRO calls, the call summary is logged as an update to the Prospects board item.

---

Change Log

Version	Date	Change
v1.0	2026-04-21	Initial draft — sop.manager.

---

Owner: sales.ops Executive sponsor: cro Drafted by: sop.manager Status: Draft — pending CRO review + approval Version: v1.0