Revenue Intelligence & CRM Pipeline Operations3 min readUpdated September 2026

Scratchpad vs Dooly for a PE Portfolio Company's Sales Team

A lower-middle-market portfolio company needs two things before a board will trust its forecast: cleaned historical pipeline data, which suits a bulk tool like Scratchpad, and consistent capture of new deals, which suits Dooly. The gap shows up when reps use stages inconsistently and deals lack a next step or real close date.

The board's request is really two separate problems: cleaning up historical pipeline data so a forecast is even possible, and capturing new deal activity consistently enough that the next board meeting's number is trustworthy without a scramble beforehand.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

The scenario: a forecast the board will not trust

Pulling the CRM for the board deck reveals the actual state: deals sitting in the same stage for months with no updated close date, reps using stage names inconsistently so "negotiation" means something different depending on who entered it, and several deals that closed weeks ago still marked open. A sponsor reviewing this for the first time will not trust a forecast built on it, and rightly so, since the underlying data was never disciplined enough to support one.

Fixing the historical mess with Scratchpad

A full bulk cleanup, going through every open deal in a grid view, correcting stale stages, confirming real close dates, and closing out deals that already won or lost, is exactly the kind of one-time, high-volume cleanup Scratchpad is built for. Doing this record by record in a standard CRM interface would take days; in a spreadsheet-style grid, it is realistic to finish in an afternoon, which matters when the next board meeting has a fixed date that is not moving to accommodate a data cleanup project.

Keeping new deals disciplined with Dooly going forward

Once the historical mess is cleaned up, the harder problem is keeping new deal activity from drifting back into the same state. If the root cause was reps not updating records after calls, a call-capture tool that pushes structured fields, like next step and close date, into the CRM automatically addresses the actual behavior gap rather than hoping reps develop better habits on their own.

Building the stage definitions the board actually needs

Neither tool fixes inconsistent stage usage by itself. Before either goes live, write a one-line definition for each pipeline stage that says exactly what has to be true for a deal to sit there, and require every rep to use the same definitions. This single step, agreeing on what "negotiation" actually means across the team, does more to make a board-ready forecast credible than any software purchase, and it costs nothing but a meeting.

Define these stage rules so the board's forecast holds up:

  • Write one clear definition for each pipeline stage, with entry criteria that two different reps would apply the same way.
  • Require a next step and a real close date on every open deal, and clean out deals that already closed or died.
  • Assign realistic close probabilities by stage, based on history instead of the founder's gut feel.
  • Name an owner for pipeline data quality so the standard survives past the first board deck.

What a sponsor typically wants to see that a founder-run CRM often lacks

A sponsor board usually wants pipeline coverage ratio, win rate by deal size, and average sales cycle length, none of which are computable from a CRM where stages are inconsistent and close dates are stale. Getting the underlying data clean enough to produce those three numbers reliably is a reasonable first-90-days target after an acquisition, and it is a good test of whether the pipeline cleanup and new discipline are actually holding, not just looking better for one board meeting.

A caution about roll-up reporting across multiple portfolio companies

A sponsor managing several portfolio companies, each running a different CRM with different stage definitions, cannot cleanly roll up pipeline data across them without someone normalizing the numbers by hand every quarter. That is a real limitation worth naming honestly rather than pretending either tool solves it: Scratchpad and Dooly both operate within a single company's CRM, and cross-portfolio standardization is a separate project the sponsor's operating team typically has to drive directly.

Setting an ownership expectation that survives past the first board deck

The riskiest pattern after a first cleanup is treating it as a one-time project completed for a single board meeting rather than an ongoing standard. Name a specific owner, whether the head of sales or a dedicated operations hire once the company can support one, who is accountable for pipeline hygiene between board meetings, not just in the week before one. Without that ownership, the same stale-data problem tends to reappear by the second or third board cycle, just as convincingly as the first time.

What the sponsor should actually expect in the first two board cycles

The first board meeting after a cleanup usually shows a believable but still rough forecast, since new discipline has not yet had time to produce a full sales cycle of clean data. The second board meeting is the more meaningful test, since by then the numbers should reflect deals that were opened, worked, and closed entirely under the new stage definitions rather than partially reconstructed from old habits. A sponsor who expects a perfect number on the first attempt is setting the portfolio company up to look like it failed at something that was always going to take two full cycles to actually prove out.

Executive Capability Standard

What Good Looks Like

Good revenue intelligence for a PE portfolio company means every open deal has a current stage matching a shared team definition, a real close date, and enough history for the board to see pipeline coverage and win rate without a manual reconstruction before every meeting.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Pull the current pipeline and check how many deals have a stale stage, a missing close date, or are already closed but still marked open.
2. Do Manually:Write a one-line definition for each pipeline stage and require every rep to use it consistently starting immediately.
3. Delegate:Assign a sales operations owner, even part time, to review pipeline hygiene weekly ahead of any board reporting cycle.
4. Automate:Build a simple dashboard that pulls pipeline coverage, win rate, and sales cycle length directly from the CRM so the board deck does not require manual reconstruction.
5. Buy:Add Scratchpad for the initial bulk cleanup of historical pipeline data, and Dooly to keep new deal entries disciplined going forward.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Close

Close fits a portfolio company standardizing its pipeline for the first time, giving a small sales team consistent stages and deal tracking a sponsor can actually forecast from.

Visit Close→

Frequently Asked Questions

How long does a full pipeline data cleanup usually take before a board meeting?

A focused bulk cleanup in a grid-style tool can realistically be finished in a day or two for a portfolio company with a few dozen open deals, correcting stale stages and closing out deals that already won or lost. The bigger time investment is usually agreeing on stage definitions first.

What pipeline metrics does a PE board typically want to see?

Pipeline coverage ratio, win rate by deal size, and average sales cycle length are common requests. All three depend on clean, consistently entered stage and close-date data, which is usually the real work behind producing a credible forecast.

Can Scratchpad or Dooly standardize reporting across multiple portfolio companies?

No, both operate within a single company's CRM. Rolling up consistent pipeline data across several portfolio companies running different systems is a separate standardization project that a sponsor's operating team usually has to drive directly.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides