Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Inventory of where deal data lives today
Before changing anything, find out where the pipeline really is: a partner's spreadsheet, three inboxes, a shared drive of teasers and half a CRM nobody updates. A one-page inventory of every source, its owner and how current it is shows what the system has to replace and what it must never lose. This is a team plan, best installed into a shared workspace so each role can own its tasks.
First tasks
- CRM owner lists the spreadsheets, inboxes and drives holding deal data
- Ask each deal team member to walk the CRM owner through their deals
- Mark each source as current, partly current or abandoned
- Note the fields that exist in only one source
Pipeline stage definitions with entry and exit rules
When one partner's "live" is another's "looked at the teaser", every pipeline count is an argument. Writing each stage with a plain entry rule and exit rule, such as NDA signed, management meeting held or IOI submitted, makes the numbers mean the same thing to everyone who reads them.
First tasks
- Write down the stages the team uses today in their own words
- Draft an entry rule for each stage tied to a real event
- Agree how on-hold and paused deals are shown
- Take the stage list to a partner meeting for sign-off
Minimum required fields for a deal record
Records with forty optional fields end up with four filled in, and never the same four. Choosing the eight to twelve fields every deal must carry, such as source, sector, deal lead, stage, enterprise value band and next step, gives reports something to stand on and keeps entry under two minutes.
First tasks
- Pull the fields used in the last three partner meeting reports
- Cut the list to the twelve fields every deal must have
- Write a one-line definition and picklist for each field
- Turn on required-field rules in the system