Your next deal is
already in your CRM
It stopped answering two years ago. You have a few thousand customers who bought once and went quiet, and your team can properly work about sixty a week. Madara works the rest — messages every dormant account, reads what comes back, and hands your reps the ones who want to talk.
Thirty minutes, free. We open your CRM, not ours.
Where those
rates come from
One reference account, live since 11 June 2026. Read straight out of the production database on 22 August 2026 — every figure below is engagement and pipeline the system produced itself.
How it
actually works
Fifteen steps, from a record nobody has opened in a year to a rep on a call. This is the whole thing — there is no part of it we are keeping back.
Find the right account
Nothing is written until we know who is worth writing to.
- Connect to your CRM. Pipedrive, HubSpot, Salesforce, or the spreadsheet you have been meaning to replace.
- Find everyone who has gone quiet. No activity in thirty days or more, in the pipeline you choose, at the stages you choose.
- Take out the ones who should be left alone. Dead-end stages, and anyone already contacted inside your dedup window.
- Pull the context that makes a message specific. What they bought, the details on the deal, and the short brief your rep wrote for it.
Pick the channel, write the message
The channel is a decision we make with you, not a default.
- Work out where your customers actually answer. WhatsApp, SMS or email, decided on who they are, where they are, and what they have responded to before. WhatsApp is what our accounts run on today. It is not a hammer we bring to every job.
- Draft one message per account,from that account’s own record. Not a template with a name dropped into it.
- Check it against your rules. No prices, no claims you have not made, no apologising. If a message breaks one, it rewrites itself and tries again, up to three times, before a human ever sees it.
- Queue it for approval. You see every message before it sends. For the first month that is every single one, and you can leave it that way permanently.
Handle the reply
Where most reactivation projects quietly fall over.
- Read the reply and work out what they meant. Interested, a real question, not interested, wrong number, or stop. Judged on the content of what they wrote, not on keywords.
- Answer the real questions. Directly, in their language, aiming at getting a call in the diary rather than winning the exchange.
- Write it back into your CRM. Activity logged against the deal, the deal reassigned to the rep who owns that relationship.
- Tell that rep. A message with the name, the number and the link straight to the deal, while the interest is still warm.
Keep it running
The part that is a service rather than a piece of software.
- Follow up on the ones who go quiet again, on a schedule, without anybody on your team having to remember.
- Your reps can just message it. What is in my queue, hand that one to Signe. It confirms before it changes anything.
- Honour every stop request permanently. Immediately, automatically, and across every future campaign. Nobody gets contacted twice by mistake.
I built it, and I am
the one who installs it.
I am Ronalds Palacis. I run Klyiro out of Ventspils, Latvia, and I wrote Madara myself.
It started as a client problem I could not stop thinking about. A forestry company had around a hundred and fifty people who had told them, in writing, that they were interested in selling — and nothing traceable had happened to any of them. Not because anyone was lazy. Because seven salespeople with full calendars cannot also work two thousand old records, and no software they already owned was going to do it for them.
So I built the thing that would. It went live in June 2026 and has since worked 2,009 accounts nobody had touched.
I am not an agency reselling somebody else’s tool. I write the code, I design it, and I run the setup for every client personally. When something breaks you are not filing a ticket — you are messaging the person who built it.
Ronalds on LinkedIn →I found it in a real account
A hundred and fifty warm leads that had gone nowhere, in a company that was doing nothing wrong.
I built the system myself
Not configured out of somebody else’s platform. Written, from the CRM connection to the reply classifier.
I install every one personally
You deal with me, not with a support queue and not with an account manager who has never opened the code.
Organisations with a CRM full of accounts that bought before and have not been contacted in a year, where a single deal is worth having a salesperson call about. Forestry is where it runs today, though nothing about it is specific to that sector.
A contact list with a purchase history, and one person who can take a call when a hot account comes back. That is the whole requirement on your side.
A cold list you bought. Madara works accounts that already know you. Without a prior relationship the rates above do not transfer. We will tell you so on the call rather than take the work.
What your
company gets
The system, installed on your CRM and adapted to how your team sells — and us running it after that.
Your real dormant count
In week one, before a single message goes out. How many accounts have genuinely gone quiet, what they are worth, and what is realistically recoverable from them. If that number is too small to be worth working, we say so and stop there.
The sequences, in your voice
Written per segment and per stage, in the language each contact actually uses, referencing what they bought. You approve every sequence before anything sends, and you set the rules it may never break.
A verified sender on the right channel
Set up and approved under your business, with the message formats registered where the channel requires it. This is the part most companies do not know they need, and the part that takes longest, so we do it.
The system connected to your CRM
Which pipeline it works, which stages it must never touch, how long an account has to be quiet before it counts, and how long before anyone can be contacted again. Configured with you, changeable any time.
The approval queue and the operator view
Every outgoing message waits for a yes for as long as you want it to. Run history, every contact and what they said back, and the settings, in one place. Nobody on your team is required to open it.
Rep alerts and a line they can talk to
Each salesperson hears the moment one of their accounts comes back, with the number and the link to the deal. They can also just message Madara to ask what is in their queue or hand an account to someone else.
Opt-outs, logging and an audit trail
Every stop request honoured permanently and automatically. Every message sent, every reply received and every handover logged with a timestamp, so you can always answer what was said to someone and when.
Us running it, every day
This is not a build we hand over and leave. It runs twice a day, we watch it, we fix it when it breaks, and we rewrite the sequences as we learn what your buyers actually respond to. Every month you get a report: what went out, what came back, what reached a rep, and what is sitting in pipeline because of it.
Running inside
four weeks
Two weeks to read the list and build it, two weeks to test it on real accounts and hand it to your team. You are involved in the first week and the fourth.
We read the CRM
Connect it, work out who is genuinely dormant, and give you the real count out of your own system. We agree the buyers, the channel and the rules before anything is written.
Build and install
Sequences written, sender verified and approved, the system connected and configured to your pipeline. You approve the first messages at the end of this week.
Test on real accounts
A controlled run against a small live group. We read what comes back and change the sequences on the evidence, not on a hunch.
Open it up and train your team
Widen the audience, walk your reps through what they will receive and how to talk to it, and switch on the daily schedule.
We operate it
It runs twice a day. We watch it, tune the sequences and send you the report. If it breaks, that is ours to fix.
What people
ask first
These come up on nearly every call. Here they are answered before you have to ask them.
“Could it embarrass us in front of a customer?”
Every message is written from what is in that account’s own record, and nothing sends until someone approves it. For the first month that is every single message, one by one. You can leave it in approval mode permanently if you would rather.
“Will my reps hate it?”
It takes no accounts off anyone. It works the part of the list they were never going to reach, and when someone answers it hands that account to the named rep with the thread attached. It is the SDR they have never had budget for.
“Has it actually closed a deal?”
€30,000 is in closing right now, off an account that had gone quiet. Behind it: 205 qualified conversations and €932,300 of pipeline from the reference account since June, at the client’s own deal values. Forestry runs a months-long cycle, so the rest is still working.
“Is this an agency retainer?”
No. An agency sells you hours and hands back a deck. We build the system, install it on your CRM and operate it every day — the running of it is the product. What that looks like for you depends on the size of your list and what we are operating, so we work it out together on the call.
“Do our reps have to learn software?”
No. They get a message when one of their accounts comes back, and they can reply to Madara if they want to ask it something. There is no dashboard anybody is required to open, and nothing changes about how they already work their deals.
“What happens to our data?”
It reads the fields it needs to write a relevant message and nothing else — internal deal notes are excluded from the model by design, because they hold things that should never leave your company. It writes back activities and stage changes, and nothing is deleted.
“How long before it is actually running?”
Four weeks, and the week-by-week is above. Week one is reading the CRM and giving you the real dormant count, which is worth having on its own even if you stop there.
“What if our list is a mess?”
Normal, and it is week one’s job. If the data turns out to be too thin to write anything specific from, we will tell you and we will not start. A bad campaign on a bad list costs you the relationships you still have.
How we
count
Every figure on this page is read out of a live production database on a stated date, not assembled for a slide. Here is exactly what each one counts.
Every rate is a floor, not a best case
3,316 of those 4,183 people are still inside the follow-up cycle and have not answered yet. We divide by all of them anyway. The real reply rate can only be higher than the one printed above.
“Qualified” means a human was asked to pick it up
The person asked for a call, asked about price, or asked a real question. Not an open, not a click, not a positive sentiment score. 205 accounts reached a named salesperson.
Pipeline is the client’s own deal values
Taken from the figures already in their CRM, not our estimate of what an account might be worth. We report the pipeline the system created, and we do not multiply it by anything.
€30,000 in closing, from an account that had gone quiet
Madara found it, wrote to it, and handed it to a named rep with the thread attached. Behind it sits €932,300 of qualified pipeline off the same run, at the client’s own deal values. Forestry parcels run a months-long cycle, so the rest of that pipeline is still converting.
All figures read from the production database on 22 August 2026.
See what is actually sitting in your CRM
Thirty minutes, free. We open your system, not ours, and count the accounts nobody has touched. Then we tell you what is realistically recoverable from them — and if the answer is not much, that is what we will say.