Your next customers may already be in your data. This system finds them, works out why they stopped buying, and brings them back without lowering your average ticket.

What "without discounts" means. A discount is your last move, not your first. Start by solving the customer's pain, adding value, or offering something different. If a discount or a lower first-months price is what it takes to win back the right customer, use it, set an end date, and return to full price.

How to use this guide

You don't have to read all of it first. Claude can use this PDF as its manual.

1. Create the Project in the setup section below.

2. Upload this PDF to the Project.

3. Paste Prompt 0 into the Project instructions and fill in your company details.

4. Open a chat in the Project, attach your data, and write start.

5. After each step, review the result and write next.

Prefer to control each step? Every prompt is printed where you need it, ready to copy. Download each file Claude gives you, and stay in the same chat when you can. If you open a new chat, upload the latest files listed in the table below.

Only have payments and a CRM? Run Steps 1, 2, 3, 5, 6 and 7. Add Step 4 when you have transcripts. Claude will mark what it can't know as "unknown".

Step

Prompts

Uses

Creates

1. Load your data

1

Your exports and connectors

master_customers.xlsx

2. Split the base

2, 3

master_customers.xlsx

segments.xlsx, first_50.xlsx, payment_recovery.xlsx

3. Build records

4

first_50.xlsx, conversations

customer_records.xlsx

4. Find the pain

5, 6

Transcripts, content_log.csv, Step 1 and 3 files

content_dna.xlsx, origin_analysis.xlsx

5. Diagnose

7, 8, 9

customer_records.xlsx

diagnosis.xlsx, unknown_reasons.xlsx, competitor_offers.xlsx

6. Offers and messages

10, 11

Step 1, 4 and 5 files

offers.xlsx, revival_messages.xlsx

7. Test and learn

12, 13

Step 2, 4 and 6 files

revival_test.xlsx, revival_results.xlsx

Why we use Claude for this

Reviving customers means connecting information that lives in different tools: payments, CRM records, product usage, emails, calls and content. Claude is very good at crossing that data.

It connects to your tools. The Connectors Directory is a catalog of MCP connectors. It includes HubSpot, Attio, Close, Gmail, Microsoft 365, Fathom, Grain, Fireflies and Granola, and you can add custom MCP connectors for other tools.

It takes a lot of files. You can upload up to 20 files per chat, each up to 500 MB.

It works across formats. One analysis can combine CSV and Excel exports with PDFs, documents and transcripts.

It runs the numbers. With code execution on, Claude can calculate from your spreadsheets and hand you back a file.

One customer, start to finish

This is the kind of trail the system builds. The company, customer and details are fictional.

Step

What the system finds

Split

Brightline canceled a $1,000/month plan seven months ago.

Record

On her sales call, Ana said her team was "losing a full day every month closing reports." Evidence A.

Origin

Her first contact came 12 days after a webinar on closing the books faster. Evidence C, because only the timing links them.

Diagnosis

A competitor replaced the product, as Ana said in her last email. Evidence A.

Offer

The competitor costs less but doesn't offer the multi-entity reports Ana needs. Normal price, plus free migration and report templates.

Message

"Hi Ana, when we spoke last year, you said your team was losing a full day every month closing reports. Is that still a problem?"

Learning

Customers who arrived around that webinar stayed longer, so the team makes another one on the same pain.

Before you start: set up Claude

1. Create a Claude Project called Customer Revival.

2. Turn on code execution and file creation. Excel uploads require them.

3. Turn on web search from the "+" menu in the chat, if your account shows that option. Steps 5 and 6 use it to research companies and competitors.

4. Add your tools in Customize > Connectors. On Team and Enterprise, an Owner has to enable each one first. Check the directory for your payment and support tools.

5. Upload this PDF and paste Prompt 0 into the Project instructions.

Protect your customers' data

Check the training setting. On Free, Pro and Max, Anthropic trains on your chats when the model training setting is on and keeps that data for up to five years. Review it in Privacy Settings before you upload anything. Team and Enterprise run under the Commercial Terms, so this setting doesn't apply to them.

Upload only what you need. Remove card details, government IDs and anything this process doesn't use.

Use IDs when you can. Replace names and emails with a customer ID, and keep the file that matches them on your computer. Claude will write messages with placeholders.

Check your obligations. Rules vary by country, especially for customers in the EU and UK. Have someone qualified confirm how you may process and contact your customers.

Prompt 0: Project instructions

You are my customer revival analyst.
COMPANY
Name: [company]
What we sell: [main products, services or plans]
Prices: [price of each one]
Average ticket: [amount and currency]
Typical sales cycle: [e.g., 30 days]
Customers we want: [ideal customer]
Customers we don't want back: [bad-fit customers]
What we can deliver without much extra work: [e.g., audits, setup, training]
HOW WE WORK
The PDF in this Project, "The 7-Step System to Revive Lost Customers Without Discounts", is our
operating manual.
- When I say "start", run Step 1. When I say "next", run the next step. If I name a step, run
that one.
- Before each step, list the files and connectors it needs and check what you can access.
- If something is missing, tell me exactly what to export and from where. Continue with what you
have and state the limitation.
- If a prompt names a file from a step we skipped, leave it out and tell me.
- Run each prompt in the manual as written. Ask me only for bracketed values you can't find in
the Project or the data.
- End each step with the files to download, a summary of up to 5 lines, and what you need from
me next.
RULES
1. Use only the data I give you or facts you find in public sources. Never invent a fact,
reason, quote, name, price or result.
2. Label every conclusion about a customer:
A = the customer said it
B = recorded in a system
C = inferred
Never present C as fact.
3. Do calculations with code. Don't estimate when the data allows an exact answer.
4. Protect our average ticket. Recommend offers in this order:
a. Solve the pain with what we already sell
b. Add value this customer cares about
c. Propose an upsell or a different offer
d. Time-limited competitive pricing, only when a competitor replaced us
e. A separate low-ticket offer
f. A discount, as a last resort, and explain why
5. Every recommendation and message must start from the customer's pain, not our product. The
only exception is a failed payment.
6. Use customer_id as the key across all files.
7. Research companies only. Don't search for or collect personal information about individuals.
8. Draft only. Never send anything or change any record without my approval.

Step 1: Load your data

Start with what you have. Payments and customer contacts are enough for a first pass, and you can add the rest later.

Source

What to get

How to load it

Payments

Customer ID, email, purchase dates, amounts, plan, failed payments, cancellation date and reason

Connector or CSV

CRM

Contacts, company, deal stage, lost reason, competitor, notes

HubSpot or another connector, or CSV

Product

First use, last use, monthly usage, features used, active users

CSV

Conversations

Sales calls, emails, support tickets, chats

Gmail, meeting tool connector, or TXT files

Content and campaigns

Publish date, channel, title, link, views, leads, ad spend

CSV, plus transcripts in Step 4

In the chat: CSV and Excel files that Claude has to calculate from.

In the Project: transcripts and documents you want in every chat. Project files can be up to 30 MB each, and their total content must fit in Claude's context window.

Very large exports: a file can be small enough to upload but too large to read at once. Keep only the columns and dates you need.

Attachments: the Gmail connector can't open them, so upload the ones you need.

Prompt 1: Audit and merge the data

I've attached or connected these sources: [list files and connectors].
1. List the useful fields in each source.
2. Find what links the same customer across sources: customer ID, email, company domain or
company name.
3. Create one master table with one row per customer, using customer_id as the key. If I've
replaced names and emails with IDs, match on those IDs and don't ask for the originals.
4. Flag uncertain matches. Don't force them.
5. Flag duplicates, missing dates, invalid emails and conflicting records.
6. List missing data, ranked by how much it limits this analysis. For each item, tell me exactly
where to export it from.
Deliver master_customers.xlsx and a short summary of what we can and can't answer yet.

Step 2: Split your customer base

Lost customers aren't one list. Each group has a different problem, so each one needs a different strategy. Work only on your first 50 for now, so you can finish and learn before you scale.

Failed payments. Many of these customers may not have decided to leave, so don't sell to them. Fix the payment first: retry the charge, send a card update link, and warn them before access ends. Handle this group now with Prompt 3, outside the 50.

Inactive customers. They haven't left yet, so reach them before they cancel. Find out why they stopped: they never got set up, the person in charge left, or the pain became less urgent. Help them get a result first, then show them the next step.

Customers who canceled. Compare the reason they gave with their usage and last conversations, because the stated reason isn't always the real one. Respond to the real pain, and bring them back only if you can solve it now.

One-time and lapsed buyers. Their first purchase solved one problem and may have revealed the next one. Offer the upsell or complementary purchase that solves it, based on what your repeat customers bought next.

Abandoned trials. They were interested but got stuck or never saw the value. Find the step where they stopped and remove that obstacle. A done-for-you setup can work better than another reminder.

Lost deals. Separate budget, competitor and no decision, because each needs a different response.

Do not contact: closed companies, bad-fit customers, and anyone who asked you to stop.

Prompt 2: Split the base and pick your first 50

Use master_customers.xlsx. Assign every customer to exactly one segment. If more than one fits,
use the first match in this order:
1. Do not contact: closed company, bad fit, or asked not to be contacted
2. Failed payment: a failed charge not recovered, with no request to cancel
3. Active: paying and using the product normally, or bought within [period]
4. Inactive: account still open, with no use in [30/60/90] days
5. Canceled: they ended a paid plan
6. One-time or lapsed buyer: no subscription and no purchase in [period]
7. Abandoned trial: started a trial and never paid
8. Lost deal: reached a sales opportunity and never bought
If a customer fits none of these, mark them "Needs review". Don't force a segment.
For each customer, add the segment, evidence (A, B or C), lifetime revenue, last purchase date
and days since last activity.
Then pick the first 50 customers for this campaign:
- Leave out Do not contact, Active, Failed payment, Needs review, and anyone without a valid
contact.
- Rank the rest by value at stake: lifetime revenue, or the plan or deal value if they never
paid. Break ties by quality of evidence, then by most recent activity.
- Take no more than 25 from one segment, unless the other segments run out.
- If there are fewer than 50, use all of them.
Don't predict who will come back. Explain the ranking in 3 lines.
Deliver segments.xlsx with every customer, a summary of customers and revenue per segment, and
first_50.xlsx.

Prompt 3: Recover failed payments

Use segments.xlsx and filter for Failed payment.
1. For each customer, show the amount, failure date, failure reason if recorded, and date access
ends. Sort by value.
2. Tell me which retry and card-update settings to check in [billing tool] so we don't duplicate
its automatic emails.
3. Write 3 short messages: today, 3 days later, and just before access ends. Rules: no selling,
no guilt, one clear action, and the placeholder {{card_update_link}}.
4. Flag the 10 highest-value accounts for a personal message from me, and draft it.
Deliver payment_recovery.xlsx.

Step 3: Build a record for each customer

Every later decision comes from this record. A customer who didn't cancel can still be lost, so the record tracks their current status instead of assuming they left.

Field

What Claude captures

Origin

First known contact and the content or campaign that may have brought them in

Pain at purchase

What pushed them to buy, in their exact words when available

Result

Whether they got value, and when

Current status

Inactive, canceled, one-time buyer, abandoned trial or lost deal

Reason

Why they stopped using, paying or moving forward

Pain today

Solved, still active, changed or unknown

Replacement

Competitor, internal tool, manual process, nothing or unknown

Key contact

Whether the person who bought or used it still appears to be there

Evidence

A = they said it, B = recorded, C = inferred

Prompt 4: Build the customer records

Use first_50.xlsx and every available source: payments, CRM, usage, emails, tickets and call
transcripts.
Create one row per customer with these columns:
customer_id, company, segment, first_contact_date, purchase_date, origin, origin_evidence,
pain_at_purchase, exact_customer_words, result, first_value_date, current_status,
last_activity_date, reason, reason_evidence, pain_today, replacement, key_contact_status,
value_to_recover, confidence, unanswered_question.
Rules:
- Use the customer's exact words for pain whenever they exist.
- Write "unknown" when the data doesn't show the answer. Don't guess.
- If they are inactive rather than gone, explain what changed in their usage and when.
- In unanswered_question, write the one thing we still need to learn from this customer.
Deliver customer_records.xlsx. Then summarize the most common pains and reasons, using revenue
as well as customer count.

Step 4: Find the content and pain that made them buy

Remove "How did you hear about us?" from your forms, onboarding and customer conversations. In 2026 it's unnecessary, and even more so with existing customers. Payments, your CRM, UTMs, emails, call transcripts and content dates already hold the answer, and Claude can cross them. Prompt 6 also looks for referrals in your emails and calls.

This step does two jobs: it shows you what to replicate to win more customers, and it helps you find the customer's real pain.

1. Transcribe your 10 most likely pieces of content. Start with the videos, podcasts, webinars, newsletters, posts and ads published before your best months. Use your video tool's transcript, or a tool such as Descript or Whisper. Name each file YYYY-MM-DD_channel_title.txt and upload it to the Project.

2. Create content_log.csv. Use these columns: date, channel, title, link, type, views, clicks, leads, ad_spend, offer. If you don't have everything, start with the date, channel and title.

Prompt 5: Extract the pain from your content

I've added content transcripts and content_log.csv.
For each piece of content, extract:
- Hook: the opening idea that grabs attention
- Pain: the specific problem it touches
- Trigger: the moment that makes this pain urgent
- Promise: the result it offers
- Proof: the evidence or example it uses
- Exact language used to describe the pain
Group similar pains under one clear name, without losing the original wording.
Deliver content_dna.xlsx.

Prompt 6: Cross content with customers

Cross content_dna.xlsx and content_log.csv with master_customers.xlsx and customer_records.xlsx.
1. Link customers to content:
- Evidence A: they mentioned it in an email, call, DM or ticket
- Evidence B: UTM, referrer, campaign, code or CRM source records it
- Evidence C: they first appeared within [typical sales cycle] after publication, and the
timing or topic fits
2. Search emails, calls and tickets for referrals: anyone who says a person or company
recommended us.
3. For each week, compare new leads and customers with the average of the previous 8 weeks. Flag
spikes and what was published or launched just before them. If there are few customers, say the
pattern is weak.
4. Compare three pains for each customer in customer_records.xlsx: the pain in the content, the
pain in sales conversations, and the pain when they stopped or left.
5. Rank content and pains by customers won, revenue, 12-month retention and repeat purchases.
6. Tell me:
- The content to replicate, and why
- The content that brought leads or views but not good customers
- The real pain behind our best customers
- 5 new content ideas using their exact language
- Where the evidence is too weak to act on
Deliver origin_analysis.xlsx and add the best-supported origin and pain to
customer_records.xlsx.

A date match can suggest a link, but it doesn't prove one. Treat Evidence C as a lead to test, not a fact. When you judge content, look at the customers who stayed, not just the leads it produced.

Step 5: Diagnose what happened

The right offer depends on what happened to this customer and whether their pain still exists.

What happened

What to do

They solved the pain or outgrew it

Find their next pain, then propose an upsell or a different offer built for customers at this stage. A referral request is a secondary step.

The pain remains, but something was missing

If you've built it, show them. If not, send it to your product team and don't pitch yet.

No budget, or the price felt too high

Offer a custom low-ticket option for the same pain, not only a cheaper version of your main product.

Bad experience

Acknowledge what went wrong, explain what changed, and offer to make it right.

Never got set up

Offer a guided or done-for-you restart around the result they wanted.

Key contact left

Reach out to their replacement, and to your former contact at their new company if it fits.

A competitor replaced you

Research the competitor, then prepare a personalized offer. Use added value first, and a competitive price for the first month or three if needed.

Reason unknown

Look for signals, then ask one simple question.

Prompt 7: Diagnose each customer

Use customer_records.xlsx. For each customer, choose the most likely situation:
- Pain solved or outgrown
- Pain remains, something was missing
- Budget or price
- Bad experience
- Never set up
- Key contact left
- Replaced by a competitor
- Reason unknown
For each customer, add:
- Diagnosis and evidence (A, B or C)
- The exact quote or data point behind it
- Their likely pain today
- The recommended next step from the Step 5 table in the manual
- What would prove this diagnosis wrong
Don't force a diagnosis. If the evidence is weak, mark it "Reason unknown".
Deliver diagnosis.xlsx. Summarize customers and revenue by diagnosis, and point out any pattern
that also suggests a retention problem.

When you don't know why they left

This will probably be your most common case, because many customers leave without explaining. You can narrow it down with the signals you already have, then ask them directly.

Signal

Possible reason

Never reached first value

Setup or onboarding problem

Usage stopped suddenly

Key contact left, or they moved to another tool

Usage declined over months

Value faded, or the pain became less urgent

Usage was steady, then they canceled at renewal

Budget or price

They stopped after an unresolved ticket

Bad experience

They pause around the same time each year

Seasonal use, so they may not really be lost

Email bounces or the website is gone

Contact left or company closed

These are clues, not answers. Each one stays Evidence C until the customer confirms it. We'll cover this problem in depth in a separate guide.

Prompt 8: Investigate unknown reasons

Use diagnosis.xlsx and filter for "Reason unknown".
For each customer:
1. Review their last 90 days of usage and classify the pattern: never activated, sudden stop,
gradual decline, canceled at renewal, stopped after an issue, seasonal or no data.
2. Review their last 3 emails, tickets or calls for any complaint, competitor, budget issue or
change at their company.
3. Check public company sources for relevant changes, such as closure, acquisition, a new tool
announced or a change of direction.
4. Give me the top 2 possible reasons, the evidence for each, and a confidence level.
5. Write one short question about the pain, with no offer in it. Use this format:
"Hi [name], quick question about [pain in their words]. When you stopped using [product], was it
closer to:
1. It stopped being a priority
2. You moved to something else
3. Budget or price
4. Something didn't work as you needed
5. The person running it moved on
Just reply with a number. That's all I need."
Deliver unknown_reasons.xlsx. When a customer replies, I'll paste the answer and you'll update
diagnosis.xlsx.

When your key contact left

Look for a bounced email, a new name in your CRM, or a reply saying they've moved on. Then check their LinkedIn profile yourself, or use a job-change tool such as UserGems or Champify. Use only professional information. Prompt 11 drafts one message for their replacement and one for your former contact.

When a competitor replaced you

Compare yourselves on this customer's pain, not on a generic feature list. If you win, you have an offer. If you lose, you have a product and retention priority.

Prompt 9: Research competitors and build the offer

Use diagnosis.xlsx and filter for "Replaced by a competitor". Group the customers by competitor.
If the competitor isn't known, list those customers for me to ask.
For each competitor:
1. Research its public feature pages, pricing pages, documentation, changelog and customer
reviews. Link every claim to its source and include the date you checked it.
2. Compare us only on the pains these customers have.
3. Tell me honestly where we win, where we lose and what you couldn't verify.
4. Build a personalized offer for each customer using:
- What we solve better for their pain
- Added value this customer would care about, such as free migration, setup or training
- A competitive price for the first month or first 3 months, only if needed, followed by our
normal price
5. Write what we should tell our product team where the competitor is better on this pain.
Don't invent competitor weaknesses, and don't make claims we can't prove.
Deliver competitor_offers.xlsx.

Step 6: Choose the offer and write the messages

Move down this list only when the option above it won't solve the customer's problem. This is how you protect your average ticket.

1. Solve the pain with what you already sell. Same product, same price, better fit.

2. Add value. Include something this customer would actually care about.

3. Propose an upsell or a different offer. This fits customers who outgrew the original pain.

4. Offer a competitive price for 1 or 3 months. Use this when a competitor replaced you, then return to your normal price.

5. Offer something low-ticket. Use a separate, smaller offer to keep the relationship alive.

6. Discount. If this is what it takes for the right customer, do it. Make it specific and time-limited.

The right offer depends on why they left. A study of a large national telecom company found that the best offer changed with both the reason for leaving and the goal. To win back the most customers, it pointed to a bundled offer for those who left over price. For long-term customers, a service offer for those who left over service. For the most profit, a discount for those who left over price. Your market will differ, so test it.

Ways to add perceived value

Add only what connects to this customer's pain:

Free migration from their current tool Custom templates, reports or dashboards

Done-for-you setup An integration they need

Training for their team Extra seats for a limited time

A named contact or direct access to the founder Early access to new features

Priority support or a private Slack channel A results guarantee or an easier exit clause

A strategy review each quarter

Low-ticket offers

Cutting the price of your main product can teach a customer it was never worth full price. Offer something different instead: a small, personalized product with solid perceived value that keeps them satisfied. When they have the budget or the need, they can buy your main offer at full price, or a higher one.

Examples include a paid audit, a one-off report, a setup sprint, a focused workshop or a small custom service.

Fictional example: a customer can't justify a $1,000/month plan. Instead of offering it at $500, you offer a $300 audit of the exact problem that made them buy. They get a result, your main plan stays at $1,000, and you agree on when to talk again.

Prompt 10: Build the offers

Use diagnosis.xlsx, unknown_reasons.xlsx, competitor_offers.xlsx and master_customers.xlsx.
For every customer in diagnosis.xlsx, choose one offer, following the offer order in the Project
rules:
1. Pain solved, outgrown, or one-time buyer: check what repeat customers in
master_customers.xlsx bought next, after how long and at what price. Recommend the upsell or
different offer that fits their next pain. If there are too few repeat customers to see a
pattern, say so.
2. Budget or price: group customers by pain and design up to 3 low-ticket offers for each pain.
For each one, give a name different from our main product, the deliverable, scope, price, what
the customer gets, why it doesn't reduce the perceived value of our main offer, and the trigger
for offering the main product again at full price.
3. Everyone offered full price: suggest up to 2 additions that raise perceived value and connect
to their pain. Rate each addition's cost to us as low, medium or high. Discard anything generic.
4. Never set up: propose a guided or done-for-you restart around the result they wanted.
5. Reason unknown: no offer until they reply.
6. Discounts: flag every discount, explain why nothing else works, set an end date, and
calculate the effect on our average ticket.
Deliver offers.xlsx with customer_id, diagnosis, pain, offer, price, normal_price, added_value,
discount, reason and needs_human_review.

Write from their pain

Every message starts with the customer's pain, in their words. If you could send the same message to anyone else, rewrite it.

Play

When to use it

The angle

Pain Check

You're unsure whether the pain still exists

"Is [pain] still a problem?"

Origin Replay

You know what brought them in

New content on the same pain

Pain Solved

You've built or changed what they needed

"You needed [outcome]. Here's what's different now."

Same Pain Proof

They doubt it can work

A real case of someone with the same problem

Pain Benchmark

The pain isn't urgent right now

A useful number that shows what this pain costs them

Done-For-You Restart

They never got set up

"We can set up [result] for you."

Next Pain

They solved the first problem

The new problem they likely have now

Low-Ticket Fix

They have no budget

A small fix for the same pain

Prompt 11: Choose the play and write the messages

Use offers.xlsx, diagnosis.xlsx, unknown_reasons.xlsx and origin_analysis.xlsx.
Channel: [email, LinkedIn, WhatsApp or other channel where they gave consent].
Sender: [real person's name and role].
Tone examples: [paste 2 messages you've written].
For each customer:
1. Choose one play from the Step 6 table in the manual, and explain the choice in one line.
2. Write 3 short messages:
- Message 1, day 1: their pain, in their words, plus one easy question
- Message 2, day 5: something useful for that pain, with no repetition of message 1
- Message 3, day 12: a polite close that offers to stop writing
Rules by situation:
- Inactive or never set up: help them get a result first. Don't sell in message 1.
- Key contact left: write one message to their replacement and one to the former contact, to use
if I confirm their new company.
- Reason unknown: use only the question in unknown_reasons.xlsx, with no sequence after it.
Rules for every message:
- Start from their pain, not our company or features.
- Mention only what the customer would expect us to know from working with us. Don't reference
their browsing or viewing behavior.
- If there's a placeholder, name exactly what I must fill in. Don't invent it. Use
{{first_name}} if names aren't in the data.
- No fake urgency and no guilt.
- If the evidence is too weak, leave the sequence out and flag the customer for review.
Deliver revival_messages.xlsx with customer_id, play, offer, why, evidence, message_1,
message_2, message_3 and needs_human_review.

Step 7: Test on 50 customers and learn

Contact your first 50 and see what happens before you touch the rest of your base. Fifty customers will show you direction, not proof, so this first test has no control group. In a simulation we ran, comparing 40 contacted customers with 10 held out caught a real 15% vs. 5% difference in return rate less than 10% of the time. With 160 vs. 40, it was only about half the time. Prompt 13 sets up that larger comparison for your next batch if your base is big enough.

Before you send anything, check that you're allowed to contact each person on that channel. Respect every opt-out immediately. Rules vary by country and channel, so have someone qualified confirm them for yours.

Prompt 12: Build the sending plan

Use revival_messages.xlsx and first_50.xlsx. We start on [date].
1. Separate anyone with needs_human_review, a missing message or no valid contact into a review
list.
2. Add a column showing the permission we have to contact each person on this channel, if the
data records it. Flag anyone where it's missing.
3. Create a sending plan with a date for each message.
4. Add these tracking columns: sent_date, replied, reply_summary, opted_out, meeting, came_back,
offer_used, discount_used, amount, original_amount, return_date.
Deliver revival_test.xlsx, with the review list on a separate tab.

Review every message, then send from a real person's account. When someone replies, stop the sequence and continue the conversation yourself. After 60 days, update the tracking columns and run the final prompt.

Prompt 13: Analyze results and plan the next batch

Here's the updated revival_test.xlsx. The test ran from [date] to [date]. Also use segments.xlsx
and origin_analysis.xlsx.
Calculate with code, and show the formulas:
- Reply rate, opt-out rate and meeting rate
- Return rate and recovered revenue
- Average ticket after returning vs. the original average ticket
- Share of recovered revenue that needed a discount
- Results by segment, diagnosis, play and offer
Then tell me:
1. What worked, and how much we can trust it with this sample size. Remember that some customers
may have returned without our message.
2. Which pains brought customers back
3. Which content we should replicate
4. Which product, onboarding or retention problems we should fix
5. Which offers lowered our ticket, and what to try instead
6. Who to contact next, in order
7. The message and offer changes for the next batch
8. If segments.xlsx has at least 200 more eligible customers, randomly split the next 200 into
160 to contact and 40 to hold out, with a similar mix of segments. Warn me that a hold-out this
size only catches large differences
Deliver revival_results.xlsx and a one-page summary for the team.

When you finish, you'll have more than a list of customers to contact. You'll know which customers can come back, which content is worth repeating, and what to fix so fewer customers leave next time.

Know a founder who could use this system? Share it with your network.

Reply

Avatar

or to participate