Completeness Enforcement

Completeness enforcement is the set of mechanisms that ensure required fields are populated at the right time. The key insight is "at the right time" — not all fields need to be populated at deal creation. Industry and company size matter at qualification. Decision-maker contact matters at discovery. Budget range matters at proposal. Progressive enforcement asks for data when the rep has it, not before.

1. Stage-Gated Requirements Define which fields become required at which stage. To move from Lead to Qualified, company name and estimated deal size are required. To move from Qualified to Discovery, decision-maker contact and use case are required. Each stage gate adds fields the rep should know by that point in the sales process.
2. Completeness Scoring Assign a completeness percentage to every deal based on populated fields. Display it visibly in the CRM. A deal at 45% completeness is a signal to the rep and manager that data is missing. Gamify it if needed — reps respond to visible scores, especially when managers reference them in pipeline reviews.
3. Automated Reminders When a deal has been in a stage for more than 3 days and required fields for the next stage are not yet populated, send the rep a reminder. Not a nag — a specific message: "Deal X is missing decision-maker contact, which is required to move to Discovery. Update the record to advance the deal." Specific reminders produce action. Generic ones get ignored.