Revenue Intelligence & CRM Pipeline Operations3 min readUpdated September 2026

Scratchpad vs Dooly for AI Agency Pilot-to-Contract Sales

For an AI or automation agency, Scratchpad keeps concurrent pilots visible in one grid, and Dooly captures the technical debrief details that decide whether a pilot converts. The deal rarely closes off a demo: it starts with a scoped pilot against a real workflow, and becomes a contract once the client's champion shows a result to someone with a budget.

Scratchpad and Dooly do not change how long a pilot takes to prove itself. What they change is whether the opportunity record still makes sense by the time it is ready to close.

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.

Why do pilots never quite become contracts?

The most common failure mode for an automation agency's pipeline is a stack of opportunities stuck at 'pilot in progress' for two months past when the pilot should have wrapped. Nobody moved the stage because nobody was sure whether it had actually stalled or was just waiting on the client's engineering team, and updating the record felt like a distraction from the technical work itself.

That ambiguity is exactly what a stale pipeline looks like from the outside, and it is why a weekly review of open pilots matters as much as a weekly review of net-new opportunities. A founder-led sales motion makes this worse rather than better, since the same person running the pilot is also the one who is supposed to remember to update Salesforce about it.

What Gets Lost Between the Pilot and the Statement of Work

The details that decide whether a pilot converts, which specific workflow steps the automation replaced, how much manual review time it actually saved, and who on the client side needs to sign off, are usually discussed in a technical debrief call, not a sales call. If that debrief never gets typed up anywhere structured, the person writing the statement of work is reconstructing it from a Slack thread days later.

Dooly fits that debrief call directly: a solutions engineer can run a note template built around pilot outcomes, link the measured time savings to the opportunity, and push it straight into the Salesforce record the account executive is working from.

Scratchpad for Tracking Concurrent Pilots

An agency running six or eight pilots at once needs a fast way to see which ones are approaching their review date and which have gone quiet. Scratchpad's grid view lets a founder or BD lead scan every open pilot's stage and next step in one sitting, rather than opening each opportunity separately to check on it.

Its Deal Spotlight view is useful here specifically because it flags opportunities with no recent activity, which for a pilot-based sales motion is often the earliest warning that a champion has gone cold or moved to another project.

Scan open pilots each week for these signals:

  • Pilots approaching their review date, so nobody is surprised when the client expects a result.
  • Pilots whose stage has not moved even though the work continues, which usually means nobody confirmed whether they stalled or are waiting on client engineering.
  • Pilots with a blank or outdated next step in the opportunity record.
  • Pilots where the technical debrief was never typed up, leaving the statement of work to be written from memory.

Watching Burn While Pilots Convert Slowly

Running unpaid or discounted pilots costs real engineering time before any revenue lands, which is exactly the kind of spend a burn multiple is meant to catch. For an automation agency under $10 million in ARR, a burn multiple under 1.1x is the good end of the range, and anything approaching 3.8x signals that too much is being spent for too little net new revenue1.

A pipeline full of stalled, unpriced pilots is one of the fastest ways to push that number in the wrong direction, since engineering time keeps getting spent while nothing converts.

When should you skip both tools and fix qualification?

Say a firm's pilots convert at a healthy rate once they are approved, but half of them never get approved to start in the first place. That is not a CRM tooling problem; it is a qualification problem, and neither Scratchpad nor Dooly will fix a sales process that agrees to run pilots for prospects who were never going to buy.

If pilots that do start convert reliably, the actual bottleneck is visibility into which ones are stalling and why, which is the problem both tools are built to solve, starting with whichever one, capture or bulk editing, is currently costing the most account executive time.

A useful gut check before buying either tool: list every pilot that has gone quiet for more than two weeks and ask whether the agency actually knows why. If the answer is usually a specific, remembered reason, the team is tracking pilots fine and just needs a faster place to log it, which points to Scratchpad. If the answer is usually a shrug, the information was never captured in the first place, which points to Dooly.

Executive Capability Standard

What Good Looks Like

A well-run pilot pipeline has a clear review date and owner on every active pilot, with stalled ones flagged and escalated within a week rather than left open indefinitely.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Pull every pilot opportunity older than sixty days and check whether each one still has an active, engaged champion.
2. Do Manually:Require a written debrief after every technical pilot call, logged against the opportunity before the next call happens.
3. Delegate:Have someone other than the account executive review stalled pilots weekly and decide whether to escalate or close them out.
4. Automate:Put Dooly in front of whoever runs technical debriefs and use Scratchpad to scan pilot status across the full pipeline.
5. Buy:Bring in a revenue consultant to redesign pilot qualification criteria so fewer pilots start without a real path to a contract.

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.

Frequently Asked Questions

Should the engineer or the account executive use Dooly during a technical debrief?

Whoever is actually in the conversation with the client's technical team should own the notes, since Dooly's value comes from capturing details firsthand rather than having an AE relay a secondhand summary into the record afterward.

Can Scratchpad track pilot-specific fields like measured time savings?

Yes, as long as those fields exist on the Salesforce opportunity object already. Scratchpad edits whatever fields your org has configured; it does not add new pilot-tracking fields on its own, so that setup happens in Salesforce first.

How many concurrent pilots justify adding a tool like this?

A grid view starts paying off once a founder or BD lead tracks more than four or five pilots at different stages. Past that point, manually opening each Salesforce record to check status gets slow enough that Scratchpad saves real time every week.

Sources

Where we quote a benchmark, we show its source. Other figures in this guide are estimates or general guidance, so check them against your own numbers.

  1. Burn multiple guidance bands by ARR (net burn / net new ARR). a16z Growth burn multiple framework (Kahl & George, 'A Framework for Navigating Down Markets', May 2022), table transcribed by Kruze Consulting, 2022.

Related Guides