Scratchpad vs Dooly for Data Consulting Scoping Calls

A prospective client rarely knows the full state of their own data before the scoping call happens. An architect on the consulting side has to ask pointed questions about source systems, data volume, existing pipelines, and where the quality problems actually are, and the answers shape whether the eventual engagement is a two-week diagnostic or a six-month build.

That means the opportunity record needs to hold real technical detail, not just a stage and a close date, for a proposal built weeks later to still make sense against what was actually discussed. A firm that treats the scoping call as a purely technical exercise, disconnected from the CRM entirely, often finds itself re-asking the client questions it already answered once.

An architect running a scoping call is focused on understanding the client's systems, not on typing notes into Salesforce, so specifics, a legacy database nobody wants to touch, a compliance constraint on where data can live, tend to end up in a personal notebook or a shared doc that never makes it into the CRM record.

Dooly's note templates can be built around a firm's own technical scoping checklist, capturing that detail as the call happens and linking it to the opportunity, so whoever drafts the SOW, sometimes a different person than the one who ran the call, is working from the actual technical picture rather than a secondhand summary.

Log these details from every scoping call:

• The client's source systems, data volume and existing pipelines.
• Where the data quality problems actually are, as the client described them.
• Any compliance constraint on where the data can live.
• A legacy database nobody wants to touch, since it can change the approach and the price.

A firm running scoping calls across six or eight prospective engagements at once needs a fast way to see which ones are waiting on a follow-up technical question, which are ready for a proposal, and which have gone quiet. Scratchpad's grid lets a business development lead or managing partner scan every active opportunity's stage in one sitting, rather than opening each Salesforce record separately between calls.

Its Deal Spotlight view is useful for flagging opportunities where a scoping call happened weeks ago but no proposal has followed, which for a technical sale is often a sign the write-up got deprioritized behind billable client work rather than a sign the client has actually lost interest.

If SOWs routinely miss technical detail that came up on the scoping call, an undocumented data source, a constraint that changes the approach, the gap is on the capture side, and Dooly addresses it directly. If scoping calls are thorough but proposals sit unwritten for weeks because nobody notices the delay, the gap is on the tracking side, and Scratchpad's grid is the faster fix.

A firm can check which gap matters more by reviewing its last few lost or stalled deals: a proposal that clearly reflects the client's actual data environment and still did not close points to pricing or timing, not tooling. A proposal that reads generic against what the scoping call actually uncovered, missing a system the client specifically flagged as a mess, points squarely at a capture problem instead.

Unlike a pure software sale, every hour a senior architect spends reconstructing a scoping call from memory to help someone else write a proposal is an hour not spent on a billable engagement. Sales and business development spend eating into a firm's capacity is a real cost even without a dedicated sales team, since it comes directly out of the same technical staff who would otherwise be delivering client work. A pipeline coverage baseline of 3x to 4x pipeline coverage is a reasonable target where a firm can measure it, but the more immediate savings here is simply not re-running a scoping call the firm already paid for once¹.