The distinction between Deals and Projects
Pipedrive has a Projects feature for managing onboarding, implementation and other work connected to a deal; projects can be linked to deals, contacts and organisations. Using Projects can make the handover visible. It does not automatically prove that the quoted scope, actual labour, exceptions and customer costs have been captured on a comparable basis.
A supplier can win ten implementation deals with apparently healthy gross margins. During delivery, six need additional site visits because access conditions differed from those assumed in the quote. Pipeline conversion looks strong; whether the extra visits reduce realised contribution depends on who bears the additional cost and whether the extra work is charged.
Which events need to survive the handover?
Price, proposed scope, commercial assumptions and the buyer’s commitments.
Start date, accepted scope, assigned resources, changes and completion.
Extra visits, rework, waiting time, variations and their causes.
Final invoiced value and actual cost, where those figures are reliably available.
The review should follow a sample of won deals into the work actually delivered. Compare the promised scope with the handover record and any subsequent change requests. Separate overruns caused by inaccurate estimates from those caused by client-requested variations: they imply different management actions.
When a report misleads
Won value and pipeline conversion can be valid sales measures. They are not a substitute for delivery performance or customer contribution. Even a Projects duration report answers how long work took rather than how profitable it was. To make a margin claim, the business must link job-level costs and invoicing data with the appropriate unit of work.
More pipeline stages will not repair missing cost records. Equally, it would be wrong to conclude that Pipedrive cannot handle post-sale work: the relevant question is whether the organisation uses Projects, another system or a documented handover process, and whether those records share identifiers.
The management choice
If work is lost between teams, improve the definition of the handover and ownership of exceptions. If the scope is preserved but margins deteriorate, investigate estimating, variation control and delivery capacity. If neither side can trace the contract to the job, the first task is to establish a reliable link between them.
Continue with sales-to-delivery commitments or cost-to-serve analysis.
Platform reference
The product behaviour described here follows the vendor documentation: Pipedrive: deals versus projects. Configuration and feature availability can vary. The business situations are explanatory examples, not documented Unsnag client outcomes.