Wake up the leads you already paid for.

Your old enquiries are sitting in a spreadsheet. This texts them, reads what comes back, answers only from facts you supply, and hands you the ones worth your time.

Book a 30-minute call

$1,500 to build it, $500 a month to run it · vendor costs paid direct, never marked up · your database, your number

0 leads. Zero pulse.

0 recoverable after costs, on the assumptions below.

Pick a trade and it runs.

Dana Whitfield
#2261 · roof replacement quote · dormant 154 days
dormant
—
Engaged
—
Converted

Two acts, about nine seconds: one lead comes back, the next asks to be left alone.

Book a 30-minute call

Would it run on your list?

Three questions, the same three the engine asks about every lead before it sends anything. No email needed to see the answer.

01 How did these people get on your list?
02 How many are sitting dormant?
4,000
03 What do you sell?

Answer all three and the same gate the engine uses runs on your list.

consent_basis: — · list: —

Your list clears the gate.

—

—
to run the first campaign, all in — carrier, model, and my fee
—
leads worth a conversation, on the assumptions below
—
closed deals covers the whole cost

If it goes the way the assumptions say, the projection is — in gross profit, and — at a pessimistic 6% reply rate. Treat both as an upper bound on stated assumptions rather than a forecast: they are arithmetic on numbers you can change in the calculator below, not a measured result from anyone's list.

Your figures, the cost lines behind them, and the date each rate was last checked, in a form you can forward to whoever else has to agree.

Whether it is worth doing on your list is arithmetic. Whether your records prove consent is the part that needs a conversation.

Book a 30-minute call

Then this is not for you. No setting changes that.

A bought or unattributable list is the one input this system refuses. US carriers reject A2P campaigns described as cold prospecting, and the TCPA exposure on undocumented consent runs $500 to $1,500 per message. Sending to that list would put the liability on your business, not on mine.

If some of it is legitimate, past customers or people who enquired, that part may still qualify. Splitting the list by how each record was collected is the work, and it is worth doing before anyone texts anybody.

Two pages: what counts as a documented prior relationship, what carriers actually check, and how to split a mixed list into the part that can be texted and the part that cannot. No pitch in it.

What is actually running.

Four moves, and a set of rules underneath all four. The rules live in the database rather than in the automation, so there is no path through the system that skips them.

  1. 01

    Your list is filtered before anything sends

    Consent, do-not-contact, suppression, quiet hours in the recipient's timezone, daily cap. A lead that fails one is never returned to a send node at all.

  2. 02

    First touch goes out from your own number

    Step one of your sequence, personalized. Each message claims a key before it goes, so a retry or a duplicate webhook loses the race and stops.

  3. 03

    The reply is read, opt-outs first

    STOP is matched by keyword before any model runs, and a trigger gates every future campaign. Everything else waits out a short window, so three texts in ten seconds are one conversation.

  4. 04

    An answer from your facts, or a handoff to you

    Drafted only from your company profile and the campaign's knowledge base. Anything outside them gets "let me check on that" rather than a guess. Leads worth your time are marked engaged and handed over.

Every outbound message clears the same five checks

  • ConsentHow the lead was collected must be recorded. Unknown never sends.
  • Do not contactA flagged lead is excluded from every campaign.
  • SuppressionOne STOP anywhere suppresses the number everywhere.
  • Quiet hoursEvaluated where the recipient is, not where you are.
  • Daily capA ceiling on sends per day, counted against what has gone already.

Built for lists with a documented prior relationship. Not for cold lists, and no setting turns it into that.

What it costs. What it returns.

Published carrier and model rates, applied to your numbers. The cost is arithmetic; the return is a projection.

Your list did not clear the gate, so these numbers are not yours yet. They are here for the part of the list that can be shown to have asked for something — split it, and this is what that part is worth.

Dormant leads —
Average deal value —
You pay now, monthly —
This campaign costs
—
— per lead contacted, then — a month to keep running.
Projected gross profit, net of cost
—
— deals covers it. At a pessimistic — reply rate it is still —.
Show the mathsHide the maths

Where the money goes

Total—

Where the return comes from

Replies—
Worth pursuing—
Closed—
Revenue—
Gross profit—
Less your follow-up time—
Net—
Twelve months here vs your platform — —
Adjust the assumptionsHide the assumptions

Rates verified — against Twilio SMS, its A2P 10DLC fees, OpenRouter, Supabase, Vercel and DigitalOcean. Carrier surcharges use the highest major-carrier rate, so the cost lands at or above the real invoice. Reply and close rates are assumptions, not measured results.

The cost is arithmetic. Whether your list qualifies is the part that needs a conversation.

Book a 30-minute call

No case studies. The machine instead.

I am taking my first clients, so I cannot show you someone else's results. Here is what exists instead: a running instance, branded to the practice it belongs to.

Every message in and out, with the classification the model gave it. The red line is a send that failed — logged, not swallowed. The two STOP rows are opt-outs, matched before any model ran. This is the record you would need if a complaint arrived.
The suppression list, with why each entry is on it and when. One STOP anywhere puts a number here, and every future send in every campaign checks it before anything is drafted.
What the practice sees day to day: where the pipeline actually is, and what was said to whom. Note the sidebar count against System — five failures, surfaced rather than buried.

A working instance with test data in it, the same build a client is handed. When there is a client campaign worth showing, that will replace this, labelled as what it is.

Have a list going cold?

Thirty minutes. Bring how many dormant leads you have, what they originally asked about, and how they were collected. That last one decides whether this is legal to send at all, so it is where we start.

Nabeel Ahmed I build and run these systems myself, so you will be on the call with me rather than a sales team. $1,500 to build your instance and hand it over, then $500 a month to run it, on top of the vendor costs above, which you pay direct and I never touch.

If your list cannot legally be sent to, I will say so on the call and we are done. No charge, no follow-up.

  • Early, and priced that way I am taking the first few clients. You get the founder building it, and if your first campaign produces no engaged leads at all, the setup fee comes back.
  • Your data stays yours Every account is in your name and the database is standard Postgres. Export it or walk away whenever you like. There is nothing to hold hostage.
  • Cancel any time No contract, no notice period, no minimum term. The monthly fee stops when you say it stops.

Do not book yet.

On what you have told me, that list cannot be sent to, and thirty minutes will not change it. Two things are worth doing instead.

  1. Split it. Past customers and people who enquired are a different list from the rest, and that part may be entirely sendable.
  2. Take the note above — it is what carriers actually check, in two pages, with no pitch in it.

If the sendable part turns out to be a few thousand records, come back and run the numbers on that. Or email nabeelahmed0294@gmail.com and I will tell you for free whether it is worth the work.

loading available times…

Booked. Two things to bring.

  1. How many dormant records you have, roughly. A count out of your CRM or booking system is enough; nobody needs the file.
  2. How those people got onto the list — bought from you, enquired and never bought, or you inherited it and cannot be sure. This decides whether any of it is legal to send, so it is where we start.

If the answer to the second one turns out to be "we cannot show consent", I will say so and we will stop there — that is a five-minute call rather than a thirty-minute one, and you will not be charged for anything.

Calendar not loading? It is blocked on some corporate networks. Email nabeelahmed0294@gmail.com with a couple of times that suit you and I will confirm one.

Who bills you.

Five accounts, all in your name, at each vendor's published rate, plus one thing that is switched off. Nothing is resold and nothing is marked up. My fee is the separate line in the ledger above.

  • Twilio The number, and every message in and out of it. A2P registration is filed under your EIN — unregistered senders get filtered. —/segment · —/mo
  • Supabase Postgres: every lead, message and opt-out, and the rules that decide what may send. One project per client, pooled with nobody. —/mo · free while small
  • Vercel The dashboard, behind a login you control. Its key is read-only; the one that bypasses the rules never reaches a browser. —/mo
  • n8n Runs the automations. They hold no rules of their own: they ask the database what is allowed, which is why a compliance change is one edit. —/mo · or n8n Cloud
  • OpenRouter Two models, metered per token: a small one reads every reply, a stronger one drafts for the few who answer. Neither sees a suppressed lead. — reads · — drafts
  • Ringless voicemail Built, and shipped switched off: the FCC treats a voicemail drop as a call requiring consent. It is not a feature you are being sold. shipped off

Rates verified —, from the sources the calculator lists. Cancel any of them and the leads, messages and opt-out list stay yours, in standard Postgres.