01
The dilemma
Selling engineered air handling units into pharmaceutical plants is a long, technical, multi-stakeholder process. The client's sales team was managing all of it in spreadsheets, and the previous system they had used captured progress only at a coarse stage level, enough to say a deal existed, not enough to say anything useful about it.
What was breaking
- Pipeline lived in spreadsheets. Deal status depended on who last updated a file, which meant the pipeline was always slightly out of date and never fully trusted.
- Tracking stopped at stage level. The existing engagement recorded that a deal had moved, but not what had actually happened, who was involved, or what was required next.
- No revenue projection worth the name. Because billing detail was not captured against closed deals, the business could not forecast revenue from its own pipeline.
- Sales productivity was invisible. Management had no reliable view of activity levels, response times or where deals were stalling.
- The buying experience did not match the product. A manufacturer supplying research-grade equipment was running its commercial process on tools its own customers had outgrown.
The cost of standing still
In engineered-to-order manufacturing, a lost deal is not a lost transaction, it is a lost production slot and a competitor's reference site. Without pipeline visibility the business could not tell which deals deserved engineering time, and technical pre-sales effort was being spent on opportunities that were never going to close.
02
The idea
The temptation with a technical manufacturer is to start customizing immediately. We did the opposite. We first demonstrated the platform in both its standard editions so the client could see exactly where configuration ended and customization began, then designed the sales process on paper and only then built it. The result was a system the sales team recognized as their own process rather than a tool imposed on them.
The principles we worked to
- Show before build. Capability demonstrated in both Professional and Enterprise editions so the commercial decision was informed, not assumed.
- Design the process, then configure it. Lead, account and deal management defined as an agreed process first.
- Capture billing detail at close. The single change that made revenue projection possible.
- Automate the follow-up, not the judgment. Tasks trigger automatically; what to do about them stays with the salesperson.
What we ruled out, and why
| Option considered | Why we did not take it |
|---|---|
| Heavy custom development from day one | Would have encoded the old, unexamined process into new software. Configure first, customize only where the business is genuinely different. |
| Rolling out the top-tier edition by default | Unnecessary license cost for capability the team was not yet ready to use. We demonstrated both and let the requirement decide. |
| Sales force automation without process redesign | The failure mode we see most often, new system, same behavior, no adoption. |
03
The build
The implementation had five components.
Leads and Deals configured to the real process
Custom fields and workflows reflecting how engineered equipment is actually sold: technical qualification, specification, quotation, negotiation and order.
Billing capture at close
Billing detail recorded against every closed deal, which turned the pipeline from a list of opportunities into a revenue forecast the finance function could use.
End-to-end process definition
Comprehensive lead, account and deal management processes, documented and enforced in the system rather than held in individual memory.
Automated task generation
Follow-ups, reminders and stage-entry actions created automatically, so nothing depends on a salesperson remembering.
Reporting for revenue and productivity
Reports covering both sides of the question management actually asks: what is the pipeline worth, and how hard is the team working on it.
04
The impact
| Measure | Before | After |
|---|---|---|
| Lead to customer conversion | Baseline | +30% |
| Pipeline record | Spreadsheets, stage-level only | Full-detail CRM with defined stages |
| Revenue forecasting | Not possible from pipeline | Projected from captured billing detail |
| Follow-up discipline | Dependent on individual memory | Automated task generation |
| Sales productivity | Not measured | Reported per representative |
| Management view | Assembled on request | Standing reports on pipeline and estimates |
Beyond the numbers
- Conversion improved by thirty percent from lead to potential customer. Achieved through process discipline and follow-up automation, not additional headcount.
- Forecasting became possible. The business can project revenue from its own pipeline for the first time.
- Engineering time is now spent on qualified work. Technical pre-sales effort follows the pipeline rather than the loudest request.
05
What comes next
The engagement continues. These are the next moves on the table.
- Quotation configuration for engineered-to-order variants.
- Service and AMC pipeline built on the same customer records.
- Integration between won deals and production scheduling.
Engagement delivered by the Ideentrix founding team. Technologies, scope and outcomes as recorded at project close, published with the client's consent.
