A revenue operations platform, not just a contact list
Deal health scores, an enterprise account 360, a five-scenario forecast, field-sales tracking and deterministic AI assistants — a full RevOps layer on top of your real billing data. Part of the cloud edition.
Score deals, learn from every close
Every open opportunity gets a 0–100 health score with risk band, confidence, the drivers behind it and recommended next actions — plus structured win/loss reasons and competitor battle-cards that keep a live win-rate per rival.
See the whole account, forecast the quarter
Roll a group → subsidiary → branch account tree into one 360 view — billed, collected, receivable and pipeline across the subtree — then read a five-scenario sales forecast, a revenue-leak scan and a morning executive brief in the RevOps cockpit.
Run the field, close with AI you can trust
GPS visit check-ins, expense claims and a “who to visit + best route” planner; reusable playbooks and collateral; and deterministic AI meeting briefs and proposal drafts that reproduce exactly — an LLM only polishes the wording when you switch it on.
What this actually means in practice
The pipeline is a lead, an opportunity with an amount, a probability and an expected close date, and the activity trail against it. Above that sits a deal health score, which is not the probability restated: it starts neutral and moves on days since last contact, meeting count, whether a proposal has gone out, whether the decision maker, budget and timeline are confirmed, whether a competitor is in the room, and how close the date is. Every driver is shown with its signed contribution.
What it shares with the ledger is the customer. Account 360 rolls a group, its subsidiaries and their branches into one tree, then reads finalised sales invoices for billed, receipts for collected, the difference for receivable, and open opportunities weighted by probability for pipeline — across every member customer of the subtree. So the same party is one record: a salesperson sees what is owed before promising terms, and the collections desk sees what is in play before pressing too hard.
The forecast works the same seam. Weighted pipeline, won-but-not-yet-invoiced revenue and your own average monthly finalised revenue produce five scenarios — worst, conservative, expected, aggressive and best — each a stated haircut or upside on the weighted figure, with the historical run rate returned beside them as an independent sanity line. The boundary is firm: CRM reads your billing data and adds to it, but a won deal is not revenue until you raise the invoice that posts it.
| RevOps figure | Read from | Shared with the ledger |
|---|---|---|
| Deal health score | Activity recency, qualification flags, competitor presence, close-date pressure | No — CRM data only |
| Billed | Finalised sales invoices across the account subtree | Yes — the same invoices as your P&L |
| Collected | Receipts recorded against those customers | Yes — the same receipts as your bank book |
| Receivable | Billed less collected | Yes — ties to your debtors ledger |
| Open pipeline | Open opportunity amounts weighted by their own probability | No — nothing is posted |
| Sales forecast | Weighted pipeline plus committed revenue plus run rate | Partly — run rate reads finalised revenue |
| Win rate per competitor | Structured win and loss reasons on closed deals | No — CRM data only |
What’s included
- Deal health scoring (0–100) with risk & recommended actions
- Win/Loss analysis + competitor battle-cards
- Enterprise Account 360 with billed/collected/pipeline rollups
- Five-scenario sales forecast + revenue-leak detection
- RevOps cockpit + AI executive morning brief
- Field visits (GPS check-in), expense claims & route planner
- Sales playbooks, a knowledge library & per-deal collateral recommendations
- Follow-ups and workflow tasks, filtered by assignee and status
- Customer-journey timeline per account
- Loyalty programmes and campaign tracking
- Contracts, subscriptions (MRR/ARR/churn) & customer success
- Team discussions with @mentions, data-quality center & global search
- AI meeting brief + AI proposal generator (deterministic)
- Approval matrix, customer merge & a dealer/distributor claims portal
What it does not do
- · The RevOps CRM is Cloud-edition only. It does not run in, and does not sync to, the offline Desktop app.
- · A won opportunity does not raise an invoice or post anything by itself. Converting it is a deliberate step you take, and until you do, nothing has reached the ledger.
- · Third-party integration connectors and a native mobile app remain roadmap. Today the field cockpit is a responsive browser screen, not an installed app.
- · There is no payroll or HRMS behind the field-sales module. Visit expenses and claims are recorded and approved, then settled as ordinary expense vouchers.
Frequently asked
Is the CRM part of the offline desktop app?
No — RevOps CRM ships in the cloud edition. It layers on your existing customers and billing data without replacing anything; it does not run in, or sync to, the offline desktop app.
Does the AI invent numbers?
No. The health scores, forecasts, briefs and proposals are deterministic computations over your own company data, so they reproduce exactly. An LLM only polishes the wording when you enable it — the underlying figures never change.
What data can the AI see?
Only your company’s own data and any installed industry packs — there are no external data sources.
Will it disturb my accounting?
No. The CRM is purely additive — even the customer-merge tool deliberately leaves your accounting records in place. Note that the third-party integration grid and a native mobile app are still on the roadmap; today you get a responsive mobile “My Day” cockpit in the browser.
Does the deal health score replace the win probability I set?
No — it sits above it. Probability is your judgement of the odds; health is a reading of how the deal is actually being worked. A deal at eighty per cent probability with no contact for three weeks, no confirmed budget and a competitor present will score poorly, and that disagreement is the point. Both are shown together.
Can I merge two customer records without breaking my accounts?
Yes. The merge tool consolidates the CRM view — contacts, activities, opportunities and the account tree — while deliberately leaving accounting records where they are. Historic invoices, receipts and journals keep pointing at the party they were raised against, so no posted figure moves and no statement changes. You get one relationship to work with and an audit trail that still reconciles.
What exactly is included in CRM · RevOps · Cloud edition?
deal health scoring (0–100) with risk & recommended actions, win/Loss analysis + competitor battle-cards, enterprise Account 360 with billed/collected/pipeline rollups, five-scenario sales forecast + revenue-leak detection, revOps cockpit + AI executive morning brief and field visits (GPS check-in), expense claims & route planner, and 8 more. Every item on that list is a working screen you can open in the trial rather than a capability described in the abstract.
How is crm · revops · cloud edition handled differently here?
It rests on score deals, learn from every close, see the whole account, forecast the quarter and run the field, close with AI you can trust. The distinction that matters is that these are structural rather than cosmetic — the behaviour is built into how records are posted, not layered on as a report you have to remember to run.
How does CRM · RevOps · Cloud edition affect my GST?
It feeds it directly rather than sitting alongside it. CGST/SGST and IGST are split from HSN or SAC and place of supply as each document is raised, so whatever crm · revops · cloud edition produces is already correct when GSTR-1, 3B and 2B reconciliation are drawn off the same books. The return matches the accounts because it was never a separate exercise.
Does CRM · RevOps · Cloud edition cost extra?
No. CRM · RevOps · Cloud edition is part of the accounting core rather than a paid add-on, so see the whole account, forecast the quarter is there on the entry tier exactly as it is on the highest one. What the tiers change is reach and depth — devices, multi-branch and multi-warehouse reporting, and whether the conversational AI copilots are switched on.