Operational leak detection
Find the money your business is accidentally losing.
RadarCipher finds what should have happened by now, but hasn’t. The lead nobody chased. The customer still waiting on a reply. The quote that went quiet. It reads the systems you already use and tells you what has slipped, with the evidence.
14-day trial · no card to start · connect one system and see your own data
Where it goes
You do not lose revenue because you have no systems. You lose it between them.
The CRM is fine. The inbox is fine. The task list is fine. What nobody owns is the space between them — and that space is where a lead goes cold, a quote goes quiet, and a customer decides you are not interested.
Each one is small enough to miss. Together they are the difference between a good quarter and an average one, and the only reason they are invisible is that nothing is looking for them.
A new lead came in, someone replied once, and then nobody went back to it.
No outbound contact since the first reply
crm.unanswered_lead
A customer asked a question and is still waiting for an answer.
Elapsed working hours against your own hours
email.customer_awaiting_reply
Somebody promised to send something and never sent it.
A commitment in writing with nothing after it
email.promised_followup_missed
A quote went out and the conversation simply stopped.
Quote issued, no acceptance, no activity
crm.proposal_abandoned
An opportunity is sitting in the pipeline that nobody has touched for weeks.
Days since the last activity of any kind
crm.stale_opportunity
A deal has no owner, or an owner who has not been near it.
No assigned owner while the record is open
crm.unassigned_lead
A meeting produced an action, and the action was never written down anywhere.
Commitment detected, no corresponding task
meeting.commitment_without_task
A quote is about to expire and nobody has chased it.
Expiry date approaching, no recent contact
finance.quote_expiring
Eighteen detectors ship today. Which of them apply depends on the systems you connect.
How it works
It finds the problem. You decide what happens next.
Six stages, and the fourth one is a person. That is not a limitation waiting to be automated away — it is the product's position on what software should be allowed to do to your customers on its own.
Detect
Detectors read the systems you have connected and look for the thing that has not happened — no reply, no follow-up, no movement, no owner.
suggested
Explain
Every finding shows what it is built from: the messages, the dates, the elapsed time, the record it concerns. If you disagree with a finding, you can see exactly why RadarCipher raised it.
evidence
Recommend
RadarCipher proposes what to do about it and drafts the wording where a reply is the right answer. A recommendation is a suggestion and is labelled as one.
recommendation ≠ approval
A person approves
Nothing consequential leaves RadarCipher until somebody reads it, edits it if they want to, and approves exactly what is on the screen. Approving a version that a colleague has since revised is refused rather than guessed at.
the line the product will not cross on its own
Execute
The approved action is carried out through the connected system, once. Repeating the same approval does not repeat the action.
queued ≠ sent
Verify
RadarCipher reports what actually happened rather than what it attempted. An action that was queued says queued. One that failed says so, and why. The finding then moves to the state the action really implies — a follow-up that went out means the wait moved to them, not that the problem is over.
sent ≠ received
RadarCipher will not email your customer because it thought that was a good idea. It will tell you it thinks somebody should, show you why, write a draft, and wait.
What it actually looks like
No customer logos. We do not have any yet.
RadarCipher is new, so this page has no testimonials, no ratings and no counts of anything. What it has is the product. These are screenshots of the real application running against its demo dataset.
One list, ordered by what it will cost you
Not a dashboard. A queue of specific things that have gone quiet, worst first, each one naming the company it concerns and how long it has been silent.
And the reason it is on the list
Every finding shows the records and dates it was built from, and a score itemised into the reasons behind it rather than asserted. The draft underneath goes nowhere until somebody reads it and approves it.
Demo data. Every organisation, person, quote and amount in these screenshots is fictional, and the figures are there to show how the interface works rather than to represent anybody’s results.
Connects to
Three systems today. Read-only, and only what a detector needs.
RadarCipher does not ask for write access to your mailbox or your CRM in order to look for what is missing. Every scope below is a read scope, and every one of them exists because a specific detector needs it.
Google Workspace
Available now
- Gmail
- Customer email waiting on a reply, and promises made in writing.
- Google Calendar
- What was committed in a meeting, and whether it happened.
gmail.readonly · calendar.readonly
Microsoft 365
Microsoft
Available now
- Outlook Mail
- Customer email waiting on a reply, and commitments in writing.
- Outlook Calendar
- Meetings, attendees, and what was promised in them.
Mail.Read · Calendars.Read
HubSpot
HubSpot
Available now
- Deals and quotes
- Pipeline that has stopped moving, and quotes nobody chased.
- Companies and contacts
- So a finding names the customer rather than an address.
- Tasks and activities
- What was meant to happen next, and whether anyone did it.
crm.objects.deals.read · crm.objects.contacts.read · crm.objects.quotes.read
Nothing connected yet? RadarCipher ships with a demo source that generates fictional activity, so you can see how findings, evidence and approvals behave before you connect anything real. It is marked as demo data everywhere it appears.
Security and control
What we can prove, and nothing we cannot.
RadarCipher reads your customer conversations and your pipeline, which is a serious thing to hand over. Here is exactly what protects it — and, at the end, what this page is not claiming.
Your data is separated in the database, not just in the code
Every table holding a customer’s data is under PostgreSQL row-level security, and the role the application connects as cannot switch it off. A query that forgets to filter by organisation returns nothing rather than somebody else’s findings. The rule is enforced by the database and tested against it.
forced row-level security
Permission is checked on the server, every time
What a person can do is decided by their role in that organisation, and it is decided by the API rather than by which buttons the interface happens to show. Billing and team controls are not visible to an ordinary member, and are refused if requested directly.
capability checks, not hidden buttons
Nothing consequential happens without a person
RadarCipher drafts, recommends and waits. Approving a draft a colleague has since revised is refused rather than guessed at, and approving the same thing twice does not do it twice.
recommendation ≠ approval ≠ execution
It tells you what happened, not what it attempted
A queued message says queued. A failed one says why. An action carried out by a system that contacts nobody says exactly that, rather than reporting success. If RadarCipher cannot prove an outcome, it does not claim one.
queued ≠ sent ≠ received
Every consequential action is written down
Who approved what, when, and what came of it — kept as an append-only history that the application cannot rewrite. Changing a role, connecting a system, or ending a subscription all leave a record.
append-only audit history
Support access is granted, not assumed
Nobody at RadarCipher can open your organisation by default. Support access is an explicit, time-limited, read-only grant that is recorded, visible, and revocable — and while it is open, the person using it sees a banner naming whose data they are looking at.
time-limited, read-only, audited
Your account is yours
Password changes sign out every other device. Two-step sign-in with an authenticator app is supported, and removing it requires the password. You can see every device signed in as you and end any of them.
two-step sign-in supported
Detection is a judgement, and it shows its working
RadarCipher can raise something you decide is not important. That is why every finding carries the evidence it was built from and the reasons behind its score — so you can disagree with it on the specifics rather than on faith.
evidence, not a black-box score
What RadarCipher does not claim
RadarCipher holds no SOC 2 report, no ISO 27001 certification, no third-party penetration-test certificate and no compliance attestation of any kind, and it publishes no uptime guarantee. It is a new product and those things take time and independent auditors. This page will say so when they exist and not before. If your procurement process needs any of them today, tell us at support@radarcipher.com and we will give you a straight answer about where we are.
Pricing
Priced by how much of your operation it watches.
The difference between the plans is how many people use it, how many systems it reads, and how often it looks — because how often it looks is what decides whether a problem reaches you today or on Thursday.
Starter
For small teams who cannot afford to drop a lead.
$49
USD per month · 3 seats included
$490 per year
- People
- Up to 5
- Connected systems
- Up to 3
- Looks every
- 2 hours
- Full detector set
- Essentials only
- Automation rules
- Not included
Growth
For teams where a missed follow-up costs real money.
$149
USD per month · 10 seats included
$1,490 per year
- People
- Up to 20
- Connected systems
- Up to 8
- Looks every
- hour
- Full detector set
- Included
- Automation rules
- Included
Professional
For operations teams running the whole revenue process.
$399
USD per month · 25 seats included
$3,990 per year
- People
- Up to 75
- Connected systems
- Up to 20
- Looks every
- 15 minutes
- Full detector set
- Included
- Automation rules
- Included
Enterprise
Custom limits, SSO, and data residency options.
Talk to us
Negotiated limits and terms
- People
- Negotiated
- Connected systems
- Negotiated
- Looks every
- 5 minutes
- Full detector set
- Included
- Automation rules
- Included
Every paid plan starts with a 14-day trial. You create your organisation and connect a system before any payment details are asked for, so the first findings you see are from your own data. Prices are shown in USD; RadarCipher also publishes prices in EUR, GBP and ZAR, and bills your organisation in its own currency.
Cancelling stops the renewal and leaves your account readable rather than deleting anything. Payment is taken through PayFast by VirtualCoreX, the company that develops RadarCipher — so that is the name you will see on the transaction. RadarCipher never sees or stores a card number.
Questions
The things people ask before they trust it.
Is this another CRM?
Is it an AI chatbot?
Will it email our customers without us approving it?
How does it know something was missed?
Can it get something wrong?
Do we need technical people to run it?
How long does setup take?
Can the whole team use it?
How is our data kept apart from other customers?
What happens if an email provider or a connected system fails?
Is there a trial, and do we need a card?
Why does the payment say VirtualCoreX?
Can we cancel?
Where do we get help?
Something in your pipeline has been quiet too long right now.
Connect one system and RadarCipher will tell you what it is, why it matters, and what to do about it. You decide whether it is right.
14-day trial · no card to start