RunRate · operated through Telegram
You don't need a dashboard. You need one message at 7am.
The six RunRate engines, operated through a single Telegram thread. The owner reads one card in the morning and replies in the same place — no login, no tab, no seat licence.
Book a discovery callPrices are quoted after the audit, not printed here.
01 — The engines
Six roles. One thread.
RunRate installs the work, not the software. Each engine has one job, and each one reports into the same thread you answer from.
The Answerer
Picks up the call or message the second it arrives — including after hours.
The Qualifier
Asks the two questions that decide whether this enquiry deserves your time.
The Booker
Confirms, reminds, and handles the reschedule without you touching it.
The Follow-Up
Chases the quote, the no-reply, the "I'll think about it".
The Recoverer
Finds the no-show, the abandoned booking, the lapsed customer.
The Reporter
Tells you what happened, what it converted, and what it cost to run.
02 — The promise
If the 30-day number isn't there, we take it out and you owe nothing.
That is the whole guarantee. Not "guaranteed revenue" — nobody can guarantee that — but a system that has to justify itself in thirty days against a number we agree on before we build.
We run it inside your tools. If we stop, it stops with a handover document, and nothing of ours keeps a key.
- One system, measured against one number, agreed in writing first.
- Engines installed in your account, on your tools.
- Telegram is a surface, not a lock-in: the flows live in n8n.
- No seat licences, no per-message markup, no bundles.
- We take it out if the number fails — in writing, on day 30.
03 — Boundaries
What we will not do.
Written down so nobody has to discover it later.
- Promise a revenue lift we can't show lever by lever.
- Put you on a waitlist to manufacture urgency.
- Lock your data in — it's yours, exportable whenever.
- Resell someone else's bot and call it a system.
- Do clinical work. Scheduling and documentation, full stop.
- Start with one engine — the biggest leak — not six.
- Show you the build in shadow mode before it touches a real customer.
- Name the dependency we don't control, on day one, in writing.
- Measure in your units: appointments, jobs, chairs filled.
- Hand over everything if you leave.
04 — How it ships
Three stages. Thirty days to a number.
Audit
We watch your real process for seven days and tell you exactly what leaks, in your units. Free — you keep it either way.
One engine
We build the single biggest leak first, in shadow mode, before it touches anything real. Then it goes live in your account.
The number
A measured report: what came in, what converted, what it was worth, what it cost to run. Then we talk about the next engine — or we leave.
05 — Questions
The ones that get asked first.
Why Telegram instead of a dashboard?
Because the owner already replies on a phone. A dashboard is one more place to log into, and the second engine that fails is the one nobody looks at. Telegram puts the daily card where the decision already happens. The data still lives in n8n and in your tools — the thread is a surface, not the system.
Is this the same as RunRate?
Same engines, same guarantee, one difference: how you operate them. If you want a dashboard and a manager, that is RunRate. If you want the morning card on your phone, that is this. We will tell you on the call which one fits.
Who owns what?
The engines run in your account, on your licence. The Telegram bot is created on your token. We hand over the credentials and a document that says where every piece lives.
What if the number fails?
We take the system out and you owe nothing for it. The removal is in writing before we start, so nobody argues about what "it worked" means at the end.
Do you need my patients' or customers' data?
Only what the job needs, and only inside your own tools. We do not diagnose, we do not advise, and we do not hold the record.
What does it cost?
Not published. There is a build number and a monthly number, quoted after the free audit, with everything included named. Until we have paid builds measured, RunRate Bot prices match RunRate's — and this page will say what they are once they exist.
06 — Start
Book the audit. It is the honest part.
Four fields. A person replies within one working day. If the answer is "don't automate this yet", you get that in writing, and you keep the audit either way.
- 30 minutes on the call, no pitch deck.
- Seven-day audit, free, yours to keep.
- No follow-up sequence. One reply, then it's your move.
One thread. One number. Thirty days.
If the number isn't there, we take it out.
Book a discovery call