How we work

It sorts. A filtered cut of your customer records goes in, and out comes who has gone quiet, what they own and when they last bought. Its morning read of your ad account is set for 7:30, and it reports what changed overnight. It hunts for the shapes that cost money without looking like anything: an ad group with no real ceiling on it, a conversion action counting something that is not a lead, a listing that quietly drifted. And it drafts. A win-back letter, a review reply, a post, written against the voice profile you signed off on.

That is the mechanical half of marketing. It used to get done at midnight by the owner, or not at all.

Decides what the work is for. Reads the auction report on the week the numbers argue with the instinct. Writes the sentence that only lands because somebody stood on a floor and heard a customer say it first. Approves.

Nothing reaches your customer without a named person approving it, and the approval carries who and when. Nothing goes out because a clock ran out. If the approver is away, the drafts wait.

There is no auto-send anywhere in this. In the reactivation engine there is no send function at all: it writes one draft per customer into a review file, and your team loads the approved ones into your own email platform.

No synthetic people. No invented customer, no stock persona with a name, no machine-written testimonial or review presented as somebody’s words. Our own testimonial slots have sat empty since we built them, and they stay empty until a customer writes one.

No generated equipment imagery. A speaker wearing a badge it does not have, a rack that was never built, a room that does not exist: those are false claims about a product you sell, made to the one audience that knows the gear better than the picture does. Product images come from the manufacturer with the usage rights recorded, or from your room, taken with a camera.

Your customer records stay on your server. Whoever keeps your records runs the filter and puts a cut where we can reach it. We read it in place, over your connection. We do not copy your customer file and we do not write back into your system. What we hold is the drafts we wrote for your approval, and a ledger of ids and dates. Both come back to you. The touch history arrives as a file your administrator routes into the record, so your floor sees it where it already looks.

The working set is capped in code at under five hundred rows. A larger file is refused rather than quietly trimmed.