You have probably evaluated a CRM system at some point. Maybe even introduced one. And at some point, someone on the team stopped using it. Not because the software was bad — but because it was never built for the way you work.
This is not a story about bad software. CRM systems are good at what they were designed for. So is ERP. The problem is that technical sales in manufacturing sits in a gap between the two — and every team in that gap has built the same workaround.
The workaround everyone has built
Ask a sales rep in a technical trade or manufacturing company how they know what price to quote. The honest answer usually sounds like this:
I have an Excel file I built myself. Some of it comes from ERP exports — I pull invoices when I need to check what we sold something for last time. Some of it I wrote down from memory after calls. Some of it I piece together from old email threads when I can find them.
That Excel file is not a failure of discipline. It exists because no system connected the dots. ERP has the invoice data — it knows what was actually sold, to whom, at what price. But ERP was built for order processing and finance. Finding a clean price history for a specific product, for a specific customer, at the moment an enquiry lands in your inbox? That is not what ERP was designed to show you.
So the data exists. It just lives in the wrong place, in a format that doesn't answer the question you are actually asking.
What CRM does well — and where it stops
CRM systems are strong at what they were developed for: managing contacts, moving deals through stages, building forecasts. For software sales or transactional B2B selling, that model works.
But technical sales thinks in products and prices, not contacts and deals. When an enquiry arrives, the question is not “where is this in the pipeline” — it is: what did we sell this product for last time? Is this customer price-sensitive on this material? What has the price been doing over the past six months?
No CRM answers these questions. It wasn't built to think that way.
On top of that: your team works in Outlook. Enquiries come in, quotes go out. A system that lives in a separate tab competes with the actual work. Sooner or later it becomes a data graveyard — not from laziness, but because the friction is real.
What ERP does well — and where it stops
ERP is the backbone of manufacturing. Without it, nothing runs.
But ERP looks backwards and speaks a different language. It knows what was ordered, invoiced, and delivered. It doesn't surface what matters at the moment of quoting: what did we win this product for, and when? Is that price holding or sliding?
The data is there — buried in invoice history. But accessing it takes time, requires the right system access, and returns a result that still needs to be interpreted. In a busy quoting situation, nobody does that consistently. So the data sits unused, and the Excel file fills the gap instead.
The gap in between
Between CRM and ERP, there is a space where the actual sales work happens. An enquiry arrives. You need to know what you last sold this product for — not the list price, but the real price, the one that won the deal. You build a quote with tiered pricing and technically correct specifications. The project continues: samples, approval rounds, specification changes, order confirmation. When you are on holiday, a colleague needs to take over without starting from zero. And at the end of the quarter, you want to know whether your prices on this product are holding or eroding.
Neither CRM nor ERP handles this cleanly. So every team builds its own infrastructure: Excel for prices, Outlook folders for project history, memory for the rest. That works — until someone leaves, a customer disputes a price, or the team grows past the point where everything fits in one person's head.
What technical sales actually needs
When you strip away the workarounds and look at what the daily work actually requires, it is always the same things.
A real price history per product and customer — not the list price from a catalogue, but the actual selling price from closed invoices, visible to the team, searchable at the moment it is needed. Quote templates that are technically correct from the start, not Word documents formatted differently by every rep. Project tracking that begins with the first enquiry and follows through samples, approvals, and changes — not just a won/lost flag in a pipeline view. And analytics at the product level: how is this price moving over time, what volumes are shifting, where is margin being given away?
This is not a wish list. It is what every technical sales team already does — just scattered across three systems and a spreadsheet.
Why we built PipeGenius
We come from manufacturing ourselves. We sat in sales offices, pulled invoice exports to reconstruct price histories, maintained Excel files that only made sense to us, and wondered why there was no system that simply connected the data that already existed to the moment it was needed.
We looked at CRM and found it thinks in contacts, not products. We looked at ERP and found the data we needed — locked away from the quoting workflow. The gap was consistent across every team we talked to. So we closed it.
PipeGenius is a web app and an Outlook add-in for technical sales teams. Invoice-based price history, quotes, project tracking, analytics — one system that works where your team already works. Fully developed in-house, hosted in Germany, no data shared with third-party services.