Build a Repeat-Business Plan From the Customer Records You Already Have

Coding & Technical Claude intermediate

Get customer segments, ready-to-send win-back messages and a 90-day calendar built from the records you already hold.

When to use it: When new-customer marketing is expensive and you suspect the cheaper win is hiding in people who already bought once.
You are a retention strategist for Australian small businesses who builds repeat-purchase plans from whatever customer data already exists — no new software.

<context>
[BUSINESS AND OFFER — e.g. "dog grooming salon, average visit $95"]
[WHAT DATA I HAVE AND WHERE — e.g. "Square customer list with last-visit dates, 800 emails in Mailchimp, booking history in the calendar"]
[DATA SUMMARY — describe or paste a de-identified sample: how many customers, how many came once vs repeatedly, typical gap between visits]
[HOW I CAN CONTACT PEOPLE — e.g. "email, SMS through Square"]
[CAPACITY — e.g. "one campaign a month, and I can handle 10 extra bookings a week"]
</context>

Before planning, estimate from my numbers where the money is leaking: roughly how many one-time customers never returned, and what one extra visit a year from even 10% of them is worth. Show this arithmetic — it sets the size of the prize.

<task>
1. Segment my customers into 3-4 groups I can actually identify with my data (e.g. "visited once, 3+ months ago", "regulars gone quiet", "active"), with the selection rule for each.
2. For each segment, design one concrete play: the message (written, ready to send), the channel from my list, the offer if any (with margin impact flagged as [CHECK: your numbers]), and when it goes out.
3. State the natural repeat rhythm for my type of business and build a re-book prompt into the sales moment — script the sentence staff say, or the line on the receipt or email.
4. Define the 3 numbers to watch monthly, computable from my existing data, with a 2-minute method for each.
5. Give the 90-day calendar: which play runs which fortnight, sized to my stated capacity.
</task>

<output_format>
Sections: The leak (arithmetic) — Segments — Plays (with ready-to-send copy) — Rhythm — Scoreboard — 90-day calendar. Under 700 words.
</output_format>

Rules:
- Use only the data I described; if a segment can't be built from it, say so and give the simplest manual workaround.
- Every email and SMS draft must include an opt-out line; note that electronic marketing rules (the Spam Act) are a [CHECK: with your adviser] item — state them as topics to confirm, not legal advice.
- All money in AUD; never invent my margins or prices — missing figures become [NEEDED: ...].
- Plain Australian English.

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.

Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.

Join the free call

More coding & technical prompts

Keep a Two-Minute Daily Engineering Log That Pays Off Later

Turn end-of-day scraps into a structured log entry — decisions with their why, lessons, blockers — capped at 120 words and searchable months later.

Break a Stalled Decision With a Structured Tiebreak

Lay out the options, score them against your own criteria, price the delay, and get a verdict with a 48-hour commitment step — plus what would legitimately reopen it.

Engineer a Distraction-Proof Deep-Work Block

Set up a recurring focus block matched to your energy and team reality — device rules, a status script, an interruption protocol and a two-week bedding-in plan.