The Revenue AI Report

AI Tech Landscape · Productivity & Task Automation

Scratchpad

Sales Productivity

Visit Scratchpadscratchpad.com

All-in-one workspace for sales teams to update their CRM, take notes, and manage tasks without switching between tools.

Journey stage
Operations and data
Ambition level
Optimize
Owning seat
RevOps and GTM engineering

What it claims to do

  • CRM Integration
  • Data Refresh
  • Notes & Tasks
  • Pipeline Management
  • Workflow Templates

Claimed benefit. Reduced tool switching, improved CRM adoption, time savings

Reported use case. Sales reps saving 5+ hours per week on administrative work

Source: the vendor and the capability mapping work behind this map. The Revenue AI Report has not independently verified these figures. Verified findings live in Research, with method, sample, and field date attached. Unfamiliar terms are defined in the AI and Revenue Dictionary.

Published case studies

We found a minimum of 3 published case studies here. There may be more we have not found. Case studies are published by the vendor. Customer names, figures, and outcomes are the vendor's claims. The Revenue AI Report has not audited them. Independently checked findings live in Research, with method, sample, and field date attached.

How to read these claims

The sample is chosen by the seller
A case study is the best result the vendor is allowed to publish. It is not a sample of all customers. The accounts that churned do not get a page.
There is no control group
Almost no vendor study compares the team using the tool against a matched team that did not. Without that comparison, the lift reported cannot be separated from headcount changes, pricing changes, seasonality, or a good quarter.
The baseline is usually missing
A percentage gain means nothing without the starting number. A 300% increase in meetings from two meetings a week is eight. Ask for the absolute figures and the time window.
Activity is not revenue
Most published gains are activity metrics: emails sent, replies, hours saved, meetings booked. Closed revenue, win rate, and retention are the metrics that survive a board meeting. Ask which one the study actually measured.
Named logos are not always customers
Logos and case studies have been published for accounts that had already churned or had only run a pilot. Ask the reference directly, by name, and ask how long they have been live.

Field notes: what users say in public

Independent feedback from review sites and practitioner forums, not vendor marketing. This is what a buyer would hear from a peer who has already run the tool.

4.8G2, 1472 reviews, observed May 2025Check the live score ↗

What holds up

  • No repeated praise found in independent sources.

What people complain about

  • No repeated complaint found in independent sources.

Fits Salesforce-heavy sales teams wanting a faster update layer for reps; unnecessary if reps already work efficiently inside native Salesforce.

Ask these on the call

  1. 01How does Scratchpad handle conflicting edits when multiple reps update the same Salesforce record simultaneously?
  2. 02What is the migration effort if we need to move off Scratchpad back to native Salesforce workflows?

How to read review evidence

Review sites are a biased sample
Most reviews are collected by the vendor, often with an incentive attached. Scores cluster high across the whole category, so a 4.6 average is closer to par than to proof. Read the one and two star reviews first, and read the most recent ones, because product and pricing change faster than the average score does.
Forums show the failure modes, not the base rate
Reddit and Hacker News threads surface what breaks, which is exactly what a business case needs. They do not tell you how common the problem is. Treat a repeated complaint as a question for the vendor, not as a verdict.
Complaints about price are usually complaints about structure
Seat minimums, credit packs that expire, annual lock-in, and per-action pricing produce most of the pricing anger in public reviews. Get the structure in writing, not the headline number.
Ratings are a snapshot
Every score here is dated. Check the live page before you cite it in a board deck.

The friction above is the tool level version of a pattern the Report has already measured. See Rollback for the method, sample, and field date behind it.

Claims versus the record

No citable discrepancy between this vendor's public claims and independent reporting was found at the time of the last check. That is not verification. It means nothing has been published either way, so the claims above still rest on the vendor's own account.

Also mapped to

The mapping work lists this tool in more than one place. Categories: Productivity & Task Automation, Revenue Operations & Forecasting. Journey stages: Operations and data, Deal management.

What has to be true before you buy

The Report does not review tools in isolation. Every tool on this map is connected to three things we publish elsewhere on the site: a decision framework that tells you how to evaluate it, a research theme that shows what we have measured in the market around it, and an essay that applies both to a real case. Those links appear at the bottom of this section so you can verify our reasoning instead of taking this page at face value.

Ambition level: Optimize

Same process, less time. Judge it on hours returned and data hygiene, not revenue.

Decide the data model, access control, and rollback plan before the first agent goes live.

Friction at this stage

  • Data trapped in disconnected systems
  • Manual transfer between tools
  • No governance over who can deploy what

The framework to apply

SCALE is the decision framework the Report uses for tools at this stage. Chart Friction is the step almost every failed rollout skipped.

The research behind it

Rollback is the market evidence we have published for this category, with method, sample, and field date attached. What got turned off, and what the teams said broke.

The essay that applies it

CRM data readiness for AI agents shows this framework and this evidence applied to a real situation, so you can see the reasoning end to end.

Common questions about Scratchpad

What does Scratchpad do?
All-in-one workspace for sales teams to update their CRM, take notes, and manage tasks without switching between tools. It sits in the Productivity & Task Automation category and maps to the Operations and data stage of the revenue journey.
Where does Scratchpad fit in a revenue team?
Scratchpad maps to the Operations and data stage at the Optimize level of ambition, and is usually owned by the RevOps and GTM engineering seat. Reported use: Sales reps saving 5+ hours per week on administrative work
Does Scratchpad publish customer case studies?
Yes. 3 named customer stories are published, including Recharge, MaintainX, G2i. These are vendor claims, not figures verified by The Revenue AI Report. A case study is the best result a vendor is allowed to publish, not a sample of all customers.
What do buyers say about Scratchpad?
Public score 4.8 on G2 from 1472 reviews, observed May 2025. Fits Salesforce-heavy sales teams wanting a faster update layer for reps; unnecessary if reps already work efficiently inside native Salesforce.
What should we ask Scratchpad before buying?
How does Scratchpad handle conflicting edits when multiple reps update the same Salesforce record simultaneously? What is the migration effort if we need to move off Scratchpad back to native Salesforce workflows?

Answers are assembled from the vendor material, published case studies, and independent evidence shown on this page. Terms are defined in the AI and Revenue Dictionary.