Stay top of mind
They'd use you again. They forgot.
The customers you already earned, contacted properly — segmented by what they bought, when, and what it was worth.
What is a win back campaign?
A win back campaign contacts past customers who haven't bought in a while. It's the closest thing most businesses have to money sitting in a drawer — these people already know you, already trust you, already paid you once, and cost nothing to reach again.
A couple of platforms we specialize in
We are flexible and like to use already existing infrastructure if possible!
The list first, then the message
Most reactivation fails at the boring end. The names are in three places, half of them are duplicates, and nobody knows what anyone bought. Fix that and the campaign almost writes itself; skip it and you've sent a generic blast to a broken list.
Cleans and merges your customer list before anything sends.
Segments by what they bought, when, and what it was worth.
Gives each segment a reason to hear from you, not a coupon.
Four steps, no mystery
The Blueprint
Ninety minutes with your systems open. We find what's leaking, and you leave with a written plan, a build order, and a fixed price. Free for the first five.
The build
We build it in the tools you already pay for, in your accounts, under your name. You approve every message before a single one goes out to a customer.
Switch-on
It goes live in stages, not all at once. We watch the first week closely, fix what the real world breaks, and tune the timing against real replies.
We watch it
Nothing we build is left running unwatched. Skip monitors it and alerts us, not you — you shouldn't hear your system is down from an angry customer.
It's weird to email after two years
It is, if it opens with a discount code and reads like it came out of a system. It isn't weird if it sounds like the person who did the work remembering them — and for most trades, two years is roughly when they need you again anyway, so the timing does half the work.
The list is usually the problem
QuickBooks, the CRM, an old spreadsheet, and a notebook. Merging those into one list you can actually segment is unglamorous and it's most of the job.
It's the fastest-paying thing we build
It's often where we start, because it uses customers you've already paid for and shows a return in weeks rather than quarters.
Automation isn't here to remove the personal touch.
It's here to make it possible. The business that remembers you is usually just the one with a system behind it.
Your old list becomes an asset
Right now it's a folder. Every name in it cost you money once and has been sitting there since, depreciating quietly. The change is that it becomes something you use on purpose, a few segments at a time, instead of something you feel bad about.
The customer from fourteen months ago books again.
Your old list becomes an asset instead of a folder.
You find out how many past customers you'd lost track of.
Find out what's in your old list
Ninety minutes with your systems open. You leave with a written plan, a build order, and a fixed price — not an estimate.
Win back campaign FAQs
The questions owners ask before contacting customers they haven't spoken to in a while. Ask us if yours isn't.
That's the normal starting point and cleaning it is part of the build. Exports from QuickBooks, the CRM, and whatever spreadsheet exists, merged and de-duplicated before a single message goes out.
Depends what you sell. For a roof, five years is recent. For a lawn service, eighteen months is cold. We set the windows against your actual repurchase cycle rather than a rule of thumb.
No, and usually you shouldn't. A discount trains people to wait for one and tells the customer the message was about you. A reason — the season, the service interval, the thing you now do — works better.
The Blueprint is free for the first five businesses, then $500 credited to the build. The build gets quoted after we've seen inside your system — anyone quoting before that is guessing. Then a monthly fee.
Skip watches everything we build and alerts us, not you. Automations do break — passwords change, APIs update. The difference is who finds out first. You shouldn't hear it from an angry customer.