The AI-native CRM
Orblex turns your emails and meetings into structured customer memory, keeps your pipeline updated, and shows your team what matters next.
The problem1.0
What a CRM records
Updated 12 days agoWhat Orblex records
from Technical deep dive
from Re: Security questionnaire
from Re: Security questionnaire
from Technical deep dive
Features2.0
Follow-ups and record updates arrive already written, each with the reason it is there. You read, edit, and say yes — and sending stays a separate decision.
“Actions the AI has prepared. Nothing runs until you say so.”
Every account is ranked by how active the conversation is — replies, meetings, stage changes, new people on the thread — so the first call of the day is the right one.
“Scores and signals are derived from this workspace’s own conversations, meetings and pipeline.”
Ask what a customer wanted and the answer arrives with the message it was read from. The agents behind it are written down too: what each one reads, and what it may not do.
“Never send anything without explicit approval.”
Open pipeline, weighted value, win rate and cycle length, charted from the same records the team works in — nothing to export, and nothing to reconcile.
“Your pipeline, where it came from, and what has closed.”
Platform3.0
Six jobs a sales team usually buys separately, done in one place and all reading the same customer memory. One workspace, one price.
Architecture4.0
Four layers, drawn the way the product is named: everything a customer says, in orbit around one core.
01Capture
Connect a mailbox and a calendar. Mail and meetings become accounts, contacts and a timeline, so the record stays current without anyone finding the time to type it in.
02Memory
Everything a customer told you is stored as a typed fact with a source and a confidence, so an answer traces back to the message it came from and a weak inference never hardens into a truth.
03Agents
The model drafts, ranks and suggests. Changing a record or writing to a customer is graded by blast radius, and the risky end waits for a person.
04Runtime
Mail sync, transcripts and agent runs happen on a queue, so a slow model never becomes a slow page.
Security5.0
Stated plainly, because a row of badges is not an answer.
Every query is scoped in the service layer, and a test suite exists purely to break it.
Mailbox tokens are AES-256-GCM encrypted, never logged, never sent to the browser.
No AI-generated SQL. Every action runs through a typed, permission-checked tool.
A person, the assistant, an agent or a rule — four facts, recorded differently.
Hiding a button is a courtesy. The check runs in the domain service every time.
Export whenever you like. A lapsed plan stops new work; it never deletes anything.
Recorded as it happens
A person, the assistant, an agent or a rule — four different facts, recorded differently.
We do not hold SOC 2, HIPAA or ISO 27001 certification, and we would rather say so than show a badge we have not earned. Ask, and we will tell you exactly where we stand.
Pricing6.0
Your team should not shrink to fit a bill. Every plan includes AI credits; the plan sets the ceiling.
Free
Enough to run the product against real data.
$39/mo
For a working salesperson or a small team.
$99/mo
For a team that runs its pipeline here.
$299/mo
For a company standardising on one system.
Custom
Configured to your requirements.
Annual billing saves roughly 17%. Limits are enforced by the server, and going over one never deletes anything — it stops new work until you upgrade or make room.
FAQ7.0
A traditional CRM is a database that people have to fill in, and the context that decides a deal never makes it there. Orblex reads the mail and meetings you already have, turns them into accounts, contacts and a timeline, and lets you question what was said. The record keeps itself up to date because it is derived from the conversation rather than typed in after it.
No. Every action the model can take is graded by blast radius, and anything at the risky end waits for a person — sending mail to a customer, deleting a record, changing an amount. The floor is enforced in the service layer, not in the interface, so it holds whether the request arrives from the app, the API, an agent or a background job.
It stays in your workspace. Queries are scoped by workspace in the service layer and there is a test suite whose only job is to attempt cross-tenant access and fail. Mailbox credentials are encrypted at rest with AES-256-GCM and never reach the browser. We do not train models on your data.
Gmail and Google Calendar today, through Google OAuth with read and send scopes you can revoke at any time. The integration sits behind a provider interface, so other mail and calendar back ends are a matter of writing an adapter rather than reworking the product.
Not yet, and we would rather say so than show a badge we have not earned. If a formal security review is part of your procurement we will walk you through exactly how the system is built and where we stand.
Going over a limit stops new work of that kind until you upgrade or make room. It never deletes anything. If a subscription lapses your data stays where it is, and you can export it whenever you like.
We’re opening Orblex to a small group of sales teams before public launch. Early customers get founding-customer pricing and a direct line to the people building the product.
Test it against your own pipeline, bring the deals you’re actually working, and help shape what we build next.
Apply for early accessHalf an hour, no slides. Connect a mailbox and the record starts keeping itself. A person replies within one working day.
Book a demo