Outbound Sequence from ICP and Trigger Events (No Fake Social Proof)

Prompt

Act as a B2B outbound copywriter who writes only from the pasted ICP and the pasted trigger events. You write a short sequence that opens on the trigger, not on your product. You never invent customer logos, case-study metrics, awards, funding, headcount, or social proof that is not in [Inputs]. You never make a performance promise or use pressure tactics and fake deadlines.

You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- What I sell, one line: [Offer]
- ICP: role, company size, industry, geography: [ICP]
- The pain I solve, in the buyer's words: [Pain]
- Trigger events I can observe, with dates and sources: [Triggers]
- Proof I may cite, verbatim: [Proof]
- One-line differentiator, from [Offer] only: [Edge]
- Call to action: [CTA]
- Channel and cadence: [Channel]
- Number of emails: [Count]
- Words or claims I must not use: [Banned]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Trigger ledger: list each [Trigger] with its date and source as pasted. Mark any trigger with no date as UNDATED. Forbidden: invented triggers, invented dates, invented funding or hiring signals.
2. ICP fit check: for each [Trigger], state in one line why the [ICP] you pasted is the right target for it. If a trigger fits a different role, say so and score it lower.
3. Sequence: [Count] messages on [Channel]. Each: day, subject line under 45 characters, body under 110 words, one ask. Message 1 opens on the earliest [Trigger]. Messages 2-4 add one new fact each from [Proof] or one new angle on [Pain]. The final message is a clean close-out, not a guilt trip.
4. Personalization slots: the exact lines each message needs from the prospect, so the sender knows what to look up. No fabricated lines.
5. Objection prep: the three most likely objections from [Pain] or [ICP], each with a one-line answer that only uses [Proof].
6. Proof pass: quote every proof claim in the sequence and its source. Cut anything not in [Proof]. Confirm no logo, metric, or award appears that is not in [Inputs].
7. Reply routing: which reply types go to a meeting, which to a nurture list, which to a no.
8. Gaps: what I still owe you.

Constraints:
- Every claim, number, and company name traces to [Inputs]. Quote or drop.
- No invented social proof, no invented urgency, no fake deadlines, no performance promises, no manipulative openers.
- Honor [Channel], [Count], [Format], and [Lang].
- Missing-data policy: if a field was blank, write NOT IN INPUTS.
- End with a five-bullet list of what the user still owes you.

Instructions

Paste only triggers you actually observed, with the date and where you saw them, and only proof you can send if asked. Replace every [bracket] before running. Works on ChatGPT, Claude, and Gemini. Blank fields become NOT IN INPUTS, and the sequence will say so instead of inventing proof.

Examples

Example Input

Offer: A two-week implementation of automated invoice reconciliation for mid-market AP teams
ICP: VP Finance or Controller, 200-800 employees, B2B software and manufacturing, US and Canada
Pain: "Month-end close takes eleven days because we reconcile invoices by hand in spreadsheets."
Triggers:
- 08/14, their careers page: two new Controller-level job postings (source: company careers page, saved screenshot)
- 09/02, LinkedIn company page: post announcing a new ERP go-live (source: LinkedIn post link)
- 09/20, press release: opened a second distribution center in Ohio (source: press release on their site)
Proof: "For a 400-person B2B software company we cut close from eleven days to six" (case study, name withheld, shared on request). "Implementation is fixed at 14 days with a named engineer" (our service page).
Edge: We only do invoice reconciliation, so implementation is scoped in days, not months
CTA: Would a 20-minute screen-share of the six-day close be useful?
Channel: Email, four touches over ten business days
Count: 4
Banned: guaranteed ROI, industry-leading, 10x, best in class, act now
Format: day-by-day table + objection prep
Lang: English

Example Output

1. Trigger ledger, date and source as pasted.
- 08/14, two Controller-level job postings on their careers page (saved screenshot).
- 09/02, ERP go-live announcement on their LinkedIn company page (post link).
- 09/20, second distribution center in Ohio (press release on their site).
No trigger is missing a date. No funding or headcount signal is claimed, because none was pasted.

2. ICP fit check.
- 08/14 job postings: strong fit. Controllers own the close this offer shortens.
- 09/02 ERP go-live: strong fit. A new ERP changes the invoice data a Controller reconciles.
- 09/20 new distribution center: medium fit. More invoices to reconcile, but the decision sits with AP or the Controller rather than VP Finance directly. Score lower than the other two.

3. Sequence, four email touches over ten business days.
| Day | Subject | Body | Ask |
| 1 | Two controller postings on your careers page | "I saw two Controller-level postings on your careers page on 08/14, so I guessed close is a live topic. A VP Finance I work with told me month-end took eleven days because invoices were reconciled by hand in spreadsheets. If your close runs the same way, a 20-minute screen-share of a six-day close might be useful. If not, I will stop." | 20-minute screen-share |
| 4 | After an ERP go-live, invoices change | "Your LinkedIn post on 09/02 said the ERP went live. Invoices usually look different after that, and reconciliation is where teams get stuck. Our scope is narrow: invoice reconciliation only, so implementation is scoped in days, not months. Open to a look at how one team runs it?" | Reply yes or no |
| 7 | Eleven days to six, one close | "In one case, a 400-person B2B software company moved month-end close from eleven days to six. Implementation was fixed at 14 days with a named engineer. Happy to walk you through what changed on their side. Worth 20 minutes?" | 20-minute screen-share |
| 10 | Closing the file on this | "I have not heard back, so I will assume the timing is wrong and stop writing. If your close ever takes longer than you want, the offer stands. No sequence after this one." | None. Clean close. |

4. Personalization slots.
Message 1 needs: the exact careers-page URL and posting titles from 08/14.
Message 2 needs: the LinkedIn post link from 09/02 and, ideally, which ERP.
Message 3 needs: no personalization; it uses only [Proof].
Message 4 needs: nothing.

5. Objection prep, answers from [Proof] only.
"We are mid-ERP, so now is bad." - Implementation is fixed at 14 days with a named engineer, and the scope is invoice reconciliation only.
"We have tried automation tools." - The scope here is one process, not a suite, so implementation is scoped in days.
"Send me a case study." - The 400-person B2B software case is available on request, name withheld.

6. Proof pass.
Quoted claims and sources: "month-end took eleven days because invoices were reconciled by hand in spreadsheets" (buyer quote in [Pain]); "cut close from eleven days to six" ([Proof] case study, name withheld); "Implementation is fixed at 14 days with a named engineer" ([Proof] service page); "invoice reconciliation only" ([Offer]).
Cut: nothing, but no logo, no metric, no award, and no headcount beyond the 400-person figure appears, and no phrase from [Banned] appears.

7. Reply routing.
Meeting interest: route to a 20-minute call. Timing objection: move to a 90-day nurture and stop the sequence. Clear no: log it and stop. No reply after day 10: close the file, no further touches.

8. Gaps.
The 09/20 distribution-center trigger is not used in the sequence because it scores lower on ICP fit. There is no proof for the Ohio site specifically, and none is invented.

What you still owe me:
- The name of the ERP from the 09/02 post, if you want message 2 to name it
- Whether the 400-person case study can be shared under name
- Any proof you have for the new Ohio site's invoice volume
- The sender's name, title, and calendar link
- Whether your email platform allows a no-ask final message