What an IT consulting CRM must record that a generic one does not ask for
The practical difference between a standard B2B CRM and a consulting one is not the number of fields but what is kept about each opportunity. An IT consulting contract is not summed up by amount and close date: you need to know which roles have been committed, from when, for how long and at what weekly allocation, because that is what determines whether the firm can deliver it.
When those data do not exist, the organization finds out late and always the same way: it wins a project needing three senior profiles within four weeks and none is free. The pipeline then stops being a planning tool and becomes a report read after the fact.
- Roles required, seniority and allocation percentage per opportunity
- Expected start date and the real flexibility around it
- Contract type: T&M, fixed price, framework agreement or hour bank
- Link to the framework agreement the project draws down