Build a Follow-Up Rhythm That Keeps You Front of Mind

You are a retention-communications planner for an Australian small business. Design a follow-up rhythm that keeps the business front of mind between purchases — timed to the customer's cycle, weighted toward giving, never nagging.

BUSINESS: [TYPE]
PURCHASE CYCLE: [HOW OFTEN A CUSTOMER SENSIBLY BUYS — e.g. lawn care 3 weeks, framing 18 months]
CHANNELS + PERMISSION: [WHAT CONTACT DETAILS AND CONSENT YOU HOLD, PER CHANNEL]
VALUE YOU CAN OFFER BETWEEN BUYS: [TIPS, SEASONAL REMINDERS, CHECK-INS, USEFUL CONTENT YOU CAN ACTUALLY PRODUCE]
CAPACITY: [WHO WRITES/SENDS AND HOW MANY MINUTES PER WEEK]
SEASONAL PEAKS: [WHEN CUSTOMERS NATURALLY NEED YOU]

Before designing, derive the rhythm from the cycle: long-cycle businesses earn fewer, richer touches; short-cycle businesses earn brief, useful ones. Reject any 'weekly because weekly' default.

Requirements:
1. The rhythm map: how many touches per cycle, at what intervals, on which channel — with reasoning from MY cycle and capacity, not best-practice folklore.
2. Giving-to-asking ratio of at least 2:1; label every touch G or A. Sales asks cluster just before natural need (cycle timing, seasonal peaks).
3. Each touch must pass the 'glad it arrived' test: state in one line why a customer would be glad, drawing only from my stated value inventory.
4. Quiet rules: pause the rhythm when a purchase just happened, a complaint is open, or the customer opts out — opt-outs honoured immediately and every commercial message identifies the sender and carries an unsubscribe, per Australian spam rules (fact, not commentary).
5. A 90-day calendar instance: actual dates from [START DATE], each entry with channel, G/A tag and a one-line brief.
6. Three full message skeletons (one per touch type) in the business's voice — short, specific, personalised only with data actually held.
7. Workload check: total minutes per week versus stated capacity, shown; trim the rhythm if it exceeds capacity rather than assuming discipline.

Output: rhythm map with reasoning → 90-day calendar → skeletons → quiet rules → workload arithmetic.

Rules: only contact people whose consent status supports it; anything unknown becomes [NEEDED: …]; en-AU idiom.

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