CRM and FlightPath
When CRM adoption is an architecture problem
What a resistant sales rep can reveal about stages, required fields, reporting, and the design of project-based CRM workflows.
Suppose a sales rep says directly that he will not use the CRM. The first reaction may be to focus on compliance. The more useful question is different: what about the system is making the work harder?
His day may not match the model. Required fields may not help him qualify a project. Generic stages may not reflect specification review, bidder activity, quotes, or award. Management reports may not explain the commercial work taking place between those milestones.
Resistance can be evidence
When a capable seller avoids a system, the behavior may point to unnecessary entry, unclear ownership, duplicated project value, or reporting that serves oversight without supporting action.
That does not mean every request should become a customization. It means the current-state process should be observed before fields and automation are prescribed.
Rebuild around the commercial decisions
- Model the physical project once, then relate bidder and quote paths to it.
- Define stages by real decisions and evidence, not generic labels alone.
- Require information only when it supports qualification, handoff, or forecasting.
- Give sellers a useful next-action view before adding management reporting.
- Document the model so governance does not depend on one administrator.
Adoption follows usefulness
Training matters, but it cannot repair a data model that contradicts the way work is sold. A configuration-first CRM architecture should reduce duplicate effort, make ownership visible, and return useful information to the people entering it.
The design test is simple: can the team see the project, its commercial paths, each legitimate revenue-bearing scope forecast once, and the next decision without reconstructing the story outside the CRM?
Test the architecture with one real project story
Choose a representative project with more than one bidder or quote path. Ask a seller to show where the specification review, stakeholder activity, pricing revisions, award status, forecast, and next handoff live today.
If the story can only be reconstructed from duplicate opportunities, spreadsheets, and private notes, the problem is larger than training. The model is asking people to translate project-based selling into a structure that does not preserve the relationships they need.