Nothing gets chased. Enquiries go cold.
Someone fills in your form while you're mid-job. You mean to reply tonight. Maybe three days later they've bought from whoever replied first. I don't know your week without having a look, but that's roughly the shape of it: the follow-up is running on memory, and the memory is yours.
I have never run a multi-touch outbound sequence to a real list, for anyone. Nobody's follow-up currently runs through me.
What I have built and run is everything around the chasing: capture that can't forget, confirmations that fire on their own, and one live flow that chases its own queue. That's below. If you want the sequence itself, you'd be the first, and the price will say so.
The parts I've already built and run
Enquiries written straight to a database
Every form on Skool of Drool and The Vivi Frequency is written to one database the moment it's submitted, and the customer gets a confirmation without anyone touching it. Nothing depends on memory to exist. In most businesses I look at, the follow-up dies at capture, so capture is the half I'd fix first, and it's the half I've already proven.
A live flow that chases its own queue
The certificate reissue service takes payment, then watches its own applications. If one stalls for three days it expires itself and emails the applicant. Small, but it's chasing, in production, with money on it.
First piece is fixed price, typically £750 to £1,500. Then we extend or stop. How pricing works →