Introducing SignalBack: your dead leads, signaling back

What's live today

One thing: the free audit. Upload a CRM or spreadsheet export and get a shareable report of the revenue sitting in your backlog — cleaned, de-duplicated, classified into won, lost, and genuinely unresolved, with your highest-value reactivation candidates ranked. No account required.

You can also walk through a demo of the reactivation workspace — campaigns, the conversation inbox, review-mode approvals, and verified bookings — with example data. It is a demo, not a trial: it runs on sample records so you can see the intended shape of the product before any of it can touch your customers.

Live today: the free CSV audit and the example-data workspace demo. Not built yet: sending (email or SMS), CRM integrations, accounts, and billing. This post is dated — check the update stamp above before treating any of it as current.

What is designed but not built

Reactivation campaigns are the next thing we build: email-first sequences that read like the owner wrote them, reply handling that carries a conversation toward a booked job, SMS gated behind carrier registration, and metering against bookings we can match deterministically rather than infer from a dashboard.

None of that sends mail today. There is no sending path, no CRM connection, and no billing system. We are describing the design we intend to ship with early partners, and we would rather say so plainly than let a roadmap read like a changelog.

The compliance rails we intend to build

The plan is that list hygiene, volume ramp-up, and opt-out propagation are properties of the sending path itself rather than settings a customer can switch off. That is a design commitment, not a shipped feature — there is nothing to turn off yet because there is nothing sending.

The reason to design it that way is that the rules are not ours. CAN-SPAM requires that an opt-out be honored promptly and that the mechanism keep working after the message goes out, and the major mailbox providers publish their own sender requirements — authentication, one-click unsubscribe, and spam-complaint rates kept under a threshold they set. A reactivation list is exactly the kind of aged, low-engagement audience those rules were written about, so the constraints belong in the infrastructure, not in a checklist someone is asked to remember.

Why start with the audit

Because the first honest question is not "what should we send?" — it is "is there anything here worth sending to?" A backlog of forty unresolved opportunities and a backlog of four thousand are different businesses with different answers, and no vendor should be allowed to skip that step by quoting an industry average at you.

Run the audit, get the number, and decide from there. If the number is small, we would rather you find that out for free than after signing something.