The field team is the product — not the dashboard
Executives buy software for reporting. Field teams use it to close deals. When the two are in tension, the field team wins by default — they just stop using it. Design for them first.
Walk into any 50-person operator and ask two people the same question: what does the CRM do? The CFO will talk about pipeline visibility and revenue forecasting. The field rep will talk about the eight taps it takes to log a call. Those two answers describe completely different products.
Why the office usually wins the roadmap fight
The office pays for the tool, sits in the demos, and writes the requirements. The field team is busy — generating revenue. So the software gets built for the people who asked for it, not the people who have to use it. Six months later nobody understands why adoption is at 30 percent.
A simple test before any CRM decision
- Sit next to a field rep for one full day. Count the taps per deal update.
- If it is more than three, the software is already fighting you.
- Ask what they would need to update five deals while walking from car to front door. Build that.
- Then show the CFO the dashboard — but only with data the field team can actually produce in three taps.
A CRM is not the system of record. It is the system of action. If it is not easier than what came before, nothing gets recorded.
This is the lens behind Philly. The dashboards came after we got the field flow right. If you reverse the order, you get a museum.