The CRM is not the pipeline. It is the record everything else hangs off

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 email the customer sent about it this morning. All three 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, leads on a board by stage, logged calls and meetings, follow-ups and saved segments. 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 follows their own orders and asks for a return, 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: one page per customer. Their logged calls and meetings, the mail filed against them, their tickets and their orders sit on the contact’s page, each in a panel of its own, 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

And if you later add Rutba Orders, the customer’s orders arrive on their page 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.

Quotes are the one thing people expect here that lives elsewhere. They are in Rutba Books, next to the invoices, and accepting a quote makes the invoice, so the CRM does not keep a second copy of either.

Play the film

Added 30 October 2026: Rutba CRM on film, with an invented business.