The small CRM data model that keeps a service pipeline usable

A CRM earns its complexity one decision at a time

Service firms do not need a large data model to run a useful pipeline. They need a small number of records that make ownership, progress, and next actions visible. When those fundamentals are missing, more fields only make the system harder to maintain.

Start with the relationships people already recognise: companies, contacts, opportunities, and activities. A company is the commercial account. A contact is a person with a role in the decision. An opportunity represents a possible engagement. An activity is evidence that something happened and what it changed. Projects belong beside the pipeline only when a signed engagement needs its own delivery workflow.

Make the next action unambiguous

Every opportunity should answer two questions at a glance: who owns it, and what happens next? “Follow up” is not enough. A useful next step names the event, the expected result, and the date. For example, “Send the revised scope after finance confirms the budget on Thursday” gives a manager something they can inspect without reconstructing the conversation.

Stages should describe buyer commitment rather than internal optimism. A stage such as “scope sent” needs an exit rule: recipient, version, value, and review date are recorded. This turns stage reporting from an opinion poll into an operational view.

Protect the model from decorative fields

A field should either change a decision, support a handoff, or explain a report. If it does none of those things, it belongs in a note or should not exist. Review the last thirty opportunities before introducing new structure. The real pipeline will show what people actually need to know.