Scratchpad vs Dooly for Engineering Firm RFP Pipelines

A public agency or private developer sets the RFP release date, the pre-bid meeting date, and the submission deadline, and a firm's pipeline has to bend around that schedule rather than the other way around. That means a lot of opportunities sit in a genuinely inactive state for weeks between the pre-bid meeting and the submission deadline, which can look like a stalled deal in a normal CRM view even when nothing is actually wrong.

The practical effect is that a firm's pipeline review has to distinguish between an opportunity that has gone quiet because the relationship cooled, and one that is simply waiting on a deadline that has not arrived yet, a distinction most out-of-the-box Salesforce views were never built to make.

A pre-bid site visit often surfaces details that never make it into the RFP document itself: an access constraint, a preference the agency's project manager mentioned informally, a competing firm's reputation on a similar project nearby. Whoever writes the technical proposal weeks later needs that context, and if the engineer who attended the site visit did not write it down clearly, it gets reconstructed from memory or left out entirely.

Dooly's note templates can be built around a firm's own pre-bid checklist, capturing what was said at the site visit and linking it to the opportunity, so the proposal writer has more than the RFP document alone to work from.

Record these details after every pre-bid site visit:

• Any access constraint on the site that the RFP document itself never mentions.
• A preference the agency's project manager mentioned informally during the visit.
• A competing firm's reputation on a similar nearby project, if it came up in conversation.
• Who attended from the firm, so whoever writes the technical proposal knows whom to ask for context.

A firm pursuing eight or ten RFPs at different stages benefits from seeing every bid's stage and submission deadline in one grid, rather than checking each opportunity separately to confirm what is due this week. Scratchpad's bulk editing makes it fast to update stage and next steps across a batch of bids after a round of pre-bid meetings, which for a firm running several pursuits at once during a busy RFP season can save real time in a single sitting.

Its Deal Spotlight view is also useful for flagging bids with a submission deadline approaching and no confirmed go or no-go decision logged, which is a specific, fixable gap in an RFP-driven pipeline.

Unlike a SaaS sales team that can roll out a new tool at any point in a steady weekly cadence, an engineering firm should time a rollout around its RFP calendar. Introducing either tool in the middle of a heavy submission week, when every engineer is focused on finishing a proposal, guarantees low adoption. A quieter stretch between major bid deadlines is a better window to get the team comfortable with a new note template or grid view before the next busy cycle starts.

Start with whichever gap is costing more bids: if proposals routinely miss detail from the site visit, start with Dooly; if bids are well understood but the pipeline looks stale by submission week, start with Scratchpad. Either way, give the whole team a full pursuit cycle to adjust before judging whether it actually stuck.

Sales and business development spend for a services firm is a real cost even without a dedicated sales team, since it comes out of billable engineering hours instead. A general pipeline coverage baseline of 3x to 4x is a reasonable target for firms that can measure it, though many engineering firms track win rate on RFPs directly instead¹. Either way, the practical payoff of fixing a proposal-detail gap or a stale pipeline is the same: fewer bids lost to a competitor who simply captured the site visit better and wrote a more specific proposal.