The CRM is not the pipeline. It is the record everything else hangs off
Pipeline stages are the easy half of a CRM and every product has them. The half that decides whether anyone can answer the phone is whether the quote, the ticket, the invoice and the call are on the same row.
· 3 min read
Every CRM on the market can draw a pipeline with stages you define. It is a solved problem, it takes a competent team a fortnight, and it is not why CRM projects fail.
They fail at the moment somebody picks up the phone. A customer rings about an invoice they are disputing, and the person answering can see the deal — but not the ticket their colleague opened last Tuesday, not the order it relates to, and not the fact that the account is 40 days overdue. Three of those four facts live in other software. The call ends with "let me find out and call you back", which is the sentence a CRM was bought to eliminate.
The gap is between systems, not inside one
The usual answer to this is integration: connect the CRM to the helpdesk, the helpdesk to the accounting package, and the accounting package back to the CRM. It works, in the sense that data eventually arrives. What it cannot do is make the four systems agree about which customer they are talking about.
Each one has its own idea of a contact. One keys on email, one on an account number, one on a company name somebody typed. Sync them and you get the thing every business with integrated software recognises immediately: two records for the same customer, both partly right, and an argument about which is the real one.
Integration moves data between systems. It cannot make them agree about what a customer is.
What we did instead
Rutba CRM ships four applications — contacts and pipeline, a helpdesk, a customer portal, and marketplace listings — and they are not four systems that talk. They are four views of one row. A ticket does not reference a customer by email; it is attached to the customer, because there is only one place a customer exists.
- CRM — contacts, companies, leads and the deal pipeline. The system of record for who your customers are.
- Helpdesk — ticket queues, threads and response targets, written against that same record.
- Customer Portal — a self-service window where your customer checks their own quotes, orders and tickets, with no extra login for you to manage.
- Marketplace — listings tied back to the catalog, for selling through channels you do not own.
The consequence is small and it is the whole point: the shared timeline. Calls, emails and tickets in one thread, in the order they happened, on the customer they happened to. Anyone who picks up the phone starts the conversation knowing the story.
What this costs you
It is worth being straight about the trade, because there is one. A best-of-breed helpdesk that has done nothing but helpdesk for twelve years will out-feature ours on helpdesk. If your support operation is the business — a hundred agents, macros, deflection, CSAT benchmarking — buy that instead, and we will say so on the comparison page.
What it costs
| Plan | Price | What it is for |
|---|---|---|
| Starter | $18 / user / month | A small team getting off spreadsheets. |
| Growth | $39 / user / month | The full desk — sales and support together. |
| Enterprise | Custom, annual | Custom terms, dedicated infrastructure. |
And if you later add Rutba Books or Rutba Orders, the invoice and the order arrive on the customer record without an integration, because they were never in a different system to begin with. That is the only reason to buy two things from one vendor that has ever been worth anything.
Look at the product page
Every capability, every application, the availability label on each one, and the full price list.
Rutba CRM