Forgotten lead
Someone replied once. Nobody followed up.
4 working days silent
No outbound contact since the first reply.
Operational leak detection
Find the money your business may be losing by accident.
RadarCipher watches the systems your team already uses and flags what should have happened by now — but may not have — for your team to review.
- Missed follow-ups
- Quiet quotes
- Unanswered customers
- Stalled deals
7-day trial · no card to start · connect one system and see your own data
At risk
Risk 84 / 100$410,000
Annual supply agreement has gone quiet
Summit Surgical Group · verbal agreement, 90% probability
They agreed. Nobody sent the contract.quiet for 5 weeks
No outgoing contact since, and 2 weeks past the response target for this customer.
Why RadarCipher raised it
- Value at risk — USD 410k
- Past your response target — 2 weeks over
- Late stage — close to a decision
- Quieter than this relationship normally is
Recommended
Send the contract before the close date
Works withHubSpotRead-onlyGoogle Workspace and Microsoft 365: not yet available
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.
Quiet quote
The proposal went out. The conversation stopped.
$14,800 · 11 days quiet
Quote issued, no acceptance, no activity.
Waiting customer
A customer asked a question and never got an answer.
3 unanswered messages
Counted in your working hours, not calendar hours.
Stalled deal
A deal stopped moving, and nobody noticed.
No activity in 21 days
Measured from the last recorded activity on the deal.
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. Eighteen checks ship today; which apply depends on the systems you connect.
How it works
Three things happen. You decide the third.
No new process to adopt, no data to re-enter, and nothing sent to a customer that a person did not read first.
- 1
Connect
RadarCipher reads the systems your team already uses. Read-only, and you choose which ones.
- 2
Find what slipped
It looks for what should have happened by now and did not — the unanswered customer, the quote nobody chased, the deal nobody moved.
- 3
Decide what happens next
RadarCipher shows the evidence, recommends an action, and drafts it where a reply is the right answer. You approve anything consequential.
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.
The full sequence, in the product’s own wordsHide the full sequence
- 01
Detect
suggested
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.
- 02
Explain
evidence
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.
- 03
Recommend
recommendation ≠ approval
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.
- 04
You approve
the line the product will not cross on its own
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.
- 05
Execute
queued ≠ sent
The approved action is carried out through the connected system, once. Repeating the same approval does not repeat the action.
- 06
Verify
sent ≠ received
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.
The product
See exactly what RadarCipher finds.
Three views of the same job: find what slipped, see what it is worth, and understand why it was raised. Real screens, running against a fictional demo organisation.
01Find
Everything that has slipped, worst first.
One queue, ordered by what deserves attention rather than by what happened most recently.
02See
What is at risk, right now.
One number for the money sitting still, and the findings behind it — so the first question an owner asks is answered before they ask it.
03Understand
The evidence, not a black-box score.
Every finding shows what happened, what did not, and how each part of the risk score was earned. Nothing reaches a customer until a person approves it.
How it happens
Nobody did anything wrong.
This is the ordinary shape of a lost deal. Every step is somebody working properly. The loss is in the step that never happened, and there is nothing in a CRM, an inbox or a task list that is looking for a step that never happened.
That is the entire job RadarCipher does.
- Day 0
You
Quote sent for the roof panel replacement.
- Day 1
Customer
“Looks good — send the contract.”
- Day 1
You
Replied to say you would get it over.
- Day 2
Team
A larger job landed. Everyone moved onto it.
- Day 4
CRM
Deal still shows “Proposal sent”. Nobody changed it.
- Day 5+
Nobody
The contract was never sent.
11 working daysand counting
Who it is for
Businesses that sell time, expertise or a relationship.
Anywhere the work arrives through conversations rather than a checkout, the thing that costs you money is the follow-up nobody made.
Managed service providers
“An open deal has nothing scheduled next, and nobody has noticed.”
Agencies
“The proposal went out three weeks ago and the thread just stopped.”
Consultants
“A quote expires on Friday and nobody has followed it up.”
Recruiters
“A client asked about two candidates on Tuesday and is still waiting.”
Professional services
“A customer has chased the same request twice and is still waiting.”
Sales and operations managers
“Four deals in the pipeline have had no activity of any kind this month.”
Connects to
It reads the systems you already pay for.
RadarCipher is not another place to put your work. It connects to what your team uses now, reads it, and flags what may be missing. Read-only, every time.
Google Workspace
Not yet availableGmail · Google Calendar
Find customers waiting on a reply, and requests that have gone quiet.
Read-only detection access
What exactly it readsHide the detail
- Gmail
- Customer email waiting on a reply, repeated chasers, and stale approval requests.
- Google Calendar
- Meetings and who attended them, read-only.
gmail.readonly · calendar.readonly
Microsoft 365
Not yet availableOutlook Mail · Outlook Calendar
Find customers waiting on a reply, and requests that have gone quiet.
Read-only detection access
What exactly it readsHide the detail
- Outlook Mail
- Customer email waiting on a reply, repeated chasers, and stale approval requests.
- Outlook Calendar
- Meetings and who attended them, read-only.
Mail.Read · Calendars.Read
HubSpot
AvailableDeals · Companies · Contacts · Tasks
Find stalled opportunities, forgotten quotes, and records nobody has touched.
Read-only detection access
What exactly it readsHide the detail
- 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
HubSpot can be connected today. The Google Workspace and Microsoft 365 connections are built but not yet available on the live service.
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
Built so your business stays in control.
RadarCipher reads your customer conversations and your pipeline. That is a serious thing to hand over, so here is what protects it.
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
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
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
RadarCipher’s support tools do not show your organisation’s business content by default. Viewing it needs a support session opened with a recorded reason: read-only, limited to your organisation, ended automatically within eight hours or sooner by hand, and recorded — and while it is open, the person using it sees a banner naming whose data they are looking at.
reason required, read-only, time-limited
RadarCipher is a new product and does not currently hold SOC 2 or ISO 27001 certification.
See RadarCipher security and controls →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.
Loading the current price
- People
- Up to 5
- Connected systems
- Up to 3
- Looks every
- 2 hours
- Advanced detectors
- Essentials only
Best fit for growing service teams
Growth
For teams where a missed follow-up costs real money.
Loading the current price
- People
- Up to 20
- Connected systems
- Up to 8
- Looks every
- hour
- Advanced detectors
- Included
Professional
For operations teams running the whole revenue process.
Loading the current price
- People
- Up to 75
- Connected systems
- Up to 20
- Looks every
- 15 minutes
- Advanced detectors
- Included
Enterprise
Limits and terms agreed with you.
Talk to us
Negotiated limits and terms
- People
- Negotiated
- Connected systems
- Negotiated
- Looks every
- Negotiated
- Advanced detectors
- Included
Every new organisation starts with a 7-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 on this page are USD, and they do not change with where you are reading from. When you subscribe, checkout shows the exact amount your payment will be, before you confirm anything.
Cancelling stops the renewal and leaves your account readable rather than deleting anything. Payments are taken through the PayFast merchant account of VirtualCoreX, the freelance service brand RadarCipher is built and operated under, so VirtualCoreX is named at checkout — the detail is in the questions. RadarCipher never sees or stores a card number.
Questions
The things people ask before they trust it.
Is this another CRM?
No, and it is not trying to become one. RadarCipher reads the systems you already have and looks across them for what has not happened. There is nothing here for your team to keep updated — the moment a product like this needs manual upkeep, it becomes the next thing people forget.
Is it an AI chatbot?
No. It is detectors, evidence and a workflow. Detectors check the records in the systems you connect against what should have happened, and where a reply is the right answer RadarCipher drafts the wording for a person to review and approve. None of that sends your data to an AI model today.
Will it email our customers without us approving it?
No. RadarCipher drafts and waits. Nothing leaves it until a person has read the draft, edited it if they want to, and approved exactly what is on screen. If a colleague revised the draft in the meantime, the approval is refused rather than guessed at.
How does it know something was missed?
By what is absent. A detector holds a record against a timing expectation — a customer message with no reply, a quote with no follow-up, a deal with no activity — measured in your organisation’s working hours rather than in raw elapsed days. Every finding shows the records and dates it was built from, so you can check the reasoning rather than trust a score.
Do we need technical people to run it?
No. Connecting a system is an ordinary sign-in with the provider, and everything after that is reading findings and deciding what to do. The people who get the most out of it are owners, operations leads and sales managers, not engineers.
How long does setup take?
Creating an account and connecting a system takes a few minutes. How quickly you see a useful finding after that depends on how much history the connected system holds and how much of it is worth flagging — which is why this page does not print a number. We would rather tell you nothing than promise you fifteen minutes.
Is there a trial, and do we need a card?
Every new organisation starts with a 7-day trial, and you create your organisation and connect a system before any payment details are asked for. Nothing is charged when the trial ends unless you have chosen a plan.
How is our data kept apart from other customers?
Every table holding customer data is under PostgreSQL row-level security, and the database role the application uses cannot bypass it. A query that fails to scope itself to one organisation returns nothing at all rather than somebody else’s data — the database enforces the rule rather than trusting the code to remember it.
Why does the payment say VirtualCoreX?
RadarCipher is built and operated under the VirtualCoreX freelance service brand, and payments are taken through the PayFast merchant account operated under that brand, so VirtualCoreX is named during checkout. How the payment is described on your bank or card statement is decided by PayFast and your bank or card issuer. RadarCipher never sees or stores a card number — card details stay with PayFast.
Something in your pipeline may have been quiet for too long.
Connect one system and RadarCipher will show you what it finds, why it may matter, and what you could do about it. You decide whether it is right.
7-day trial · no card to start
RadarCipher is decision-support software: findings may be incomplete, delayed or incorrect, and you decide what to do with them. Subscriptions are governed by the Commercial Terms.