Extract Copyable Lessons From How Similar Businesses Grew Online

Coding & Technical Claude intermediate

Get each example business deconstructed into its growth mechanism, a transferability verdict, and your own adapted version.

When to use it: When a competitor or similar business is clearly winning online and you want the mechanism, not just envy.
You are a marketing analyst who reverse-engineers how comparable small businesses grew, and turns it into moves an Australian owner can copy this quarter.

<context>
[MY BUSINESS — e.g. "family butcher, regional NSW town of 8,000"]
[EXAMPLES I'VE NOTICED — describe 1-3 businesses that seem to be winning online: what you've actually seen them do (posts, ads, Google presence, email), in as much detail as you can]
[MY CURRENT MARKETING — e.g. "Facebook page, sporadic posts, no email list"]
[RESOURCES — e.g. "5 hours a week, $150 a month, my daughter can film"]
</context>

Before analysing, strip each example to its mechanism: what actually causes a stranger to become a customer (the offer, the proof, the channel, the repetition) — not surface tactics like "they post reels".

<task>
1. For each example I gave, break down: audience — hook — channel — proof — conversion step — what repeats weekly. Use only what I described; unknown links in their chain become [CHECK: watch what they do here].
2. Rate each example's transferability to my business (high/medium/low) with one line of reasoning — town size, margins and buying frequency matter.
3. Add up to two well-established small-business growth patterns relevant to my trade, described as patterns — no invented business names, no fake statistics.
4. Choose the ONE most copyable mechanism and adapt it to my business in full: what I post, send or offer, the cadence, and who does what within my stated resources.
5. Define what "working" looks like at 30, 60 and 90 days in numbers I can count (enquiries, bookings, list signups).
</task>

<output_format>
A deconstruction per example (six rows each), the transferability verdicts, then "Your version" as a week-by-week starter plan, then the 30/60/90 measures. Under 650 words.
</output_format>

Rules:
- Never fabricate a named case study, a revenue figure, or a "grew 300%" claim; patterns must be described generically and honestly.
- Stay within my stated hours and budget; AUD only.
- Plain Australian English, no hype.

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.