Sales CRM · lead to cash
Every CRM asks the rep how the deal is going. This one already listened.
A pipeline review is mostly a room of people repeating what they were told by the person with the most to lose from saying it plainly.
The calls happened. They were recorded, with consent, and what was said in them is on the deal — the objection nobody answered, the competitor weighed twice, the thirty-four days of silence. The forecast is weighted by it.
- Every claim quoted, with the second it was said
- Quote to signed contract, no signature vendor
- The close that forecasts is the close that pays
Projected commit · this quarter
20 deals
weighted by what was said
Evidence-backed
9 deals
A commitment on a recorded call, with the second it was said
Contested
6 deals
An objection nobody answered, or a competitor weighed twice
Quiet
3 deals
Thirty-four days since anyone on the buying side spoke
Not called
2 deals
Weighted as it stands. Never marked down for the absence
Every band opens into the calls behind it. Nobody is asked to talk the number up, because the number was not built from what they said about it.
Illustrative
Three answers a competitor does not have
Ask the incumbent these three questions. Watch what happens.
Not features — questions. Each one is answerable here, and each one is a page you can read before you ever speak to us.
What a sales CRM is, and where they stop
They are all competent at the list. They are all guessing at the number.
A CRM is the record of selling — who you are talking to, what you are trying to sell them, what it is worth, and when you think it lands. The category is forty years old and the basics are solved. Nobody needs another list of contacts.
Where every one of them stops is the same place: the moment the rep types seventy-five per cent into a box. From there the forecast is arithmetic performed on a feeling. The manager's job becomes interrogating the feeling, the rep's job becomes defending it, and the number that reaches the board is the output of that negotiation.
The evidence exists. It is in the calls, which were recorded anyway. The question is only whether the product can reach it.
- Not a score —
A deal's risk band opens into the reasons: which objection was left unanswered, which way sentiment moved across the last three calls, how long since anybody spoke. Each carries the sentence that was said and the second it was said at.
- Absence is not evidence —
A deal with no recorded calls is weighted exactly as it stands. It is not marked down for a silence that might just mean the rep sells by email.
- The rep's own number is kept —
The judgement they submitted, the mechanical sum of their team's submissions, and the evidence-weighted projection are three separate figures. Nothing averages them into a fourth.
Honesty by refusal
Most of what makes a pipeline truthful is a gesture the product will not perform.
A stage that is an ending cannot be dragged into. Closing always goes through the path that asks why, stamps the date and tells the rest of the platform — so your loss reasons are worth reading a year later.
A deal that merely stopped has its own ending, separate from lost, and it is deliberately quiet: it tells the owner and nothing else, so nothing downstream ever sees a close that did not happen.
And a suggested update from a call is a suggestion. The path that reads the call never writes to the deal. A person accepts it, and their name is on the row.
A reason, or an honest blank
Nine close reasons ship. The close only demands one if your workspace has configured one — nobody is blocked by an empty picklist.
Stale means both clocks stopped
Not "nobody called" — a deal that moved stage yesterday is not stale. Both the stage and the customer have to have gone quiet.
What the stage requires before it is left
Per stage, configured by you: the fields and the artefacts. Forced through with a written reason, or refused outright — your choice, per stage.
Quote to cash
The document the customer signs is generated, signed and verified here.
A quote drafts from the deal's own lines, prices per line with its own discount and tax, and routes for approval when it breaches the discount or value you set — through a real approval engine, with the definition frozen when the approval starts so editing the workflow cannot reshape an approval already in flight.
The contract is signed with a key belonging to your workspace alone. The signed PDF is re-rendered with the signature block, those exact bytes are signed and stored, and the download returns the stored bytes rather than rendering again. Anyone can verify it without an account — their browser hashes the file locally and sends only the digest.
- 01Dealhands over the lines that were negotiated→ Quote
- 02Quotehands over the total the customer accepted→ Order
- 03Orderhands over what was actually delivered→ Invoice
- 04Contracthands over the term, and when it renews→ Renewal deal
- 05Closehands over the amount the plan is paid on→ Commission
- A certificate, not a typed name —
Sent, viewed and signed as a timeline, the signer's address and browser, the signature, the document's own hash, your workspace key's fingerprint, and the exact consent text captured at the time.
- Voiding kills every link in the same act —
A forwarded signing link stops working the moment the rep voids the contract.
- No third-party signature vendor —
Which is why the evidence bundle is ours to make good rather than whatever a reseller exposes.
The seam
The close that pays the rep is the same close the forecast saw.
A commission plan compiles to a real language, is type-checked, and is frozen at the version every payment pins to — so the arithmetic behind a payment made a year ago can be reproduced from the record of it. Nothing accrues without a dry run first, and the payment uses the figure the dry run produced rather than recomputing it.
Where credit splits and a role has nobody in it, the share is redistributed across the roles that matched rather than evaporating. And where the commission rides payroll, approving the run pays exactly the rows the calculation staged.
- Meridian · platform rollout£84,000 · 75%Healthy ×1.00Two objections raised, both answered on the call
- Halvorsen Group · renewal expansion$52,000 · 50%At risk ×0.75Sentiment fell 19 points across the last three calls
- Okonkwo Industries · migration$140,000 · 75%Critical ×0.40Competitor weighed on two calls · nothing logged in 34 days
- Sandhu & Co · pilot₹18,00,000 · 50%No calls ×1.00No calls recorded — weighted as it stands, not marked down
What it does not do
Said here rather than discovered in month two.
Commission tiers are cliff tiers — the whole amount takes the rate of the band it lands in, not a blend across bands. A clawback writes the reversing entry and does not currently recover the money through payroll. Quotas do not convert currencies, though forecasting does and tells you what it had to exclude. Territories classify; they do not reassign an owner or route a lead. And a sales cadence does not yet stop itself when somebody replies.
None of that is hidden in a footnote elsewhere on this site. Each has a page that says so in the place you would look for it.
›Is this a CRM for agencies or for in-house sales teams?
Both, and the same one. The hiring side of the platform switches mode per requisition rather than per company, and the CRM has no equivalent distinction to make — accounts, deals and quotes work the same whether you are selling software, services or placements.
›Do we have to record calls to use it?
No. Everything except the evidence layer works without a single recording, and the forecast treats a deal with no calls neutrally rather than marking it down. The evidence is what makes the number better; it is not what makes the product work.
›Can we start with the CRM and add the rest later?
Yes — that is the point of it being one platform rather than a suite. The accounts, the people and the documents are already shared, so adding finance or delivery later is a setting rather than a migration.
›We already have a CRM. Why would we move?
Usually you would not, on the CRM alone — the category is mature and migrations are expensive. The three reasons people do move are on this page: the forecast is built from recorded evidence rather than from opinion, the document the customer signs is generated and verifiable here rather than through a third vendor, and the close that forecasts is the same close that pays the rep. If none of those is a live problem, staying put is the right answer and we will say so.
›Will the reps actually use it?
That is the right question, and the honest answer is that mandates do not work. What works is the first screen of the day being worth opening — which is why the cadence, the snooze trail, the calendar and the silence on an account are all derived rather than reported. If a rep has to file yesterday before they can see today, they will file the minimum.
›What if we do not want calls recorded?
Then do not record them. Every part of this works without a single recording, and a deal with no calls is weighted neutrally in the forecast rather than marked down. Consent is confirmed before anything is stored, and the meeting bot appears in the participant list under its own name.
›How long does it take to get running?
Accounts, contacts and leads import from a spreadsheet or from the common recruiting and sales tools, with a preview that tells you what it would create, what it would link to somebody you already have, and what it could not read — before anything is written. A commit can be rolled back for a week afterwards.
›Do we have to buy the whole platform?
No. Start with the CRM. The modules share one record underneath, so adding finance or people later is a setting rather than a migration — which is the point of it being one platform rather than a suite you integrate.
›Is our data used to train anything?
No. Your records are yours. Where a question is answered by a language model, only what that question needed is sent, retrieved under your own permissions — and the assistant is structurally unable to delete, send, approve or move money, because no such capability is exposed to it.
›What does it cost?
We quote rather than publish, because the shape of a sales team varies enormously and a price list would mislead more often than it helps. A thirty-minute session on your own pipeline gets you a number.
Adoption
A CRM gets used when it hands the rep their morning.
Every CRM rollout has the same failure mode: the product asks the rep to file yesterday, the rep files the minimum, and within a quarter the data is good enough for nothing.
The way out is not a mandate. It is that the first screen of the day is worth opening — because the cadence knows who is due, the snooze trail knows what has been slipping, the calendar has already logged the meetings, and the silence on an account was noticed without anybody reporting it.
- Due nowCall Marguerite — step 2 of the cadenceshe has not replied in nine days
- Due nowSend the revised depot pricingyou snoozed this twice; originally due 4 Aug
- TodayTwo bookings, both auto-loggedthe bot joins the second one
- FlaggedOkonkwo has gone quiet for 34 daysand the last call raised an objection nobody answered
- WaitingYour 28% discount is with Rinyou were told that before you submitted it
- Meetings and calls arrive on their own —
Connected mail and calendar log what happened; a recorded call writes its own entry. The timeline fills from work rather than from discipline.
- A follow-up remembers what caused it —
And how far it has slid in total, not just since the last push — so a manager can see a pattern rather than a date.
- The approval chain is shown before it is entered —
Who it would go to, and how long they have. And if nobody resolves, the quote stays in draft rather than sitting pending against a person who left.
Nine months later
Every commercial argument is won by whoever can produce the artefact.
Not by whoever remembers it better. A customer disputes what they agreed to. A rep disputes what they were paid. An auditor asks who approved a discount nobody can now justify. A regulator asks who looked at a record.
Each of those questions arrives long after the people involved have moved on, and each is answerable here because the act itself produced the evidence rather than somebody being asked to keep a note.
- “Why did we lose this one?”→ the reason chosen at the close, from a list you control
- “Who approved that discount?”→ the approval, its written reason, and what it overrode
- “Did the customer agree to this?”→ the signed file, byte for byte, with a public check
- “How was this commission calculated?”→ the plan version pinned to the payment
- “Who looked at this record?”→ a trail the database itself will not let anyone edit
- The audit trail cannot be edited by anyone, including us —
The database rejects the attempt. It is not a policy or a convention, and the retention sweep cannot remove a row either.
- Support access is a two-key process, logged in your workspace —
A written reason, approval by colleagues who are not the requester, a short window, and any administrator able to revoke it. Recorded in your own trail, not only in ours.
- A misconfiguration fails quiet rather than open —
Somebody with no read permission gets an empty list, not an error somebody resolves by granting more than they meant to.
The whole module
Thirty-five capabilities, each with a page that names the screen.
Not a feature list written by marketing. Every one of these was written after reading how it actually behaves — which is why each page tells you what it refuses to do as plainly as what it does.
Pipeline
The working day
Managing the number
Seeing it
Underneath
The half of selling that happens after somebody says yes.
A CRM stops at the closed deal. That is a reasonable place for a product to stop and an expensive place for a business to stop — everything after it is where the money actually arrives.
Finance
The accepted quote becomes the invoice with the lines the customer agreed to, not lines somebody retyped from a PDF.
ExploreServices delivery
A won deal opens the project with its scope already written, so margin reads against what was actually sold.
ExplorePeople & payroll
The commission that close produced is a line on the rep's payslip, computed from the same event the forecast saw.
ExploreCustomer success
The contract's end date opens the renewal as a real deal sixty days out, while there is still time to do something about it.
ExploreSupport
The account a ticket belongs to is the account the deal was won on — so a renewal conversation can see what the last quarter actually felt like.
ExploreCall intelligence
The same engine that returns your sales calls returns your interviews, with the objection and the moment it was raised.
ExploreEvery capability in the sales CRM
Grouped, with a page each, and each page naming the screen it describes.
Book a demo
Bring one pipeline. We will show you its evidence.
A working session on your own pipeline. Thirty minutes, no slides.
- Open the deals that closed without a reason anybody recorded
- Find the ones that have quietly stopped, and how long ago
- Play back what the calls already said about the biggest one