You want to run a hygiene pass on your HubSpot CRM: standardize the company descriptions, tighten deal notes that drifted last quarter, fill the blanks that make filters behave badly. What stops you is the CRM itself. Contacts, deals, and sequences are live. Workflows watch every field. An agent with a direct write path can fire automations, corrupt records, and leave your reps cleaning up the damage before you have had a chance to review anything.
Scratch pulls the CRM into a folder Hermes can open. It rewrites the records on your laptop, not in HubSpot. Scratch shows every change as a diff and writes back only what you approve. Workflows, lists, and Marketing assets never move. And because Hermes carries memory across sessions, it builds a skill from the first pass. The second time you run the same job, it starts from that skill and moves faster.
How it works
- Scratch pulls your CRM into files. Contacts, companies, deals, tickets, and the rest land in a folder on your laptop, one file per record.
- Hermes edits the records. Point Hermes at the Scratch folder and describe the pass. It uses its built-in tools to work through the records, building a reusable skill as it goes. Standardize every company description and tighten the deal notes from last quarter. Hermes works the files, never the live CRM.
- You review every diff and publish. Scratch shows each changed field beside the original, word by word. Approve what holds up, and Scratch writes only those records back through the HubSpot CRM API.
What people use it for
The CRM hygiene that never gets prioritized because it means opening records one by one:
- Standardize company descriptions across every account.
- Tighten deal notes and next steps after a quarter of drift.
- Reconcile custom-object copy that diverged between teams.
- Normalize the formatting on a property so reports and filters behave.
- Fill the blanks on a field by reading what is already on the record.
Run it on a few hundred records to feel the loop, then point Hermes at the whole object. On the second pass, it already has the skill.
Why not an MCP server?
A HubSpot MCP server or app wires Hermes straight to your live CRM. One pass rewrites every record at once, fires the workflows watching those fields, and leaves your reps cleaning up by hand. Hermes is a capable agent with 40-plus tools and its own scheduler. That power needs a gate, not a direct line to production data.
Scratch gives Hermes the same full read and write access against a local copy instead. The write-back is lifted out and handed to you. Hermes can change anything; only you can commit it. On a CRM the whole company runs on, that gap is the whole point.
What Hermes edits in HubSpot
- Contacts and companies
- Deals, tickets, quotes, and line items
- Notes, tasks, calls, and meetings
- Custom objects and the associations between them
Workflows, lists, and Marketing Hub assets stay where they are, and emails are pulled for context but stay read-only. The full picture lives on Scratch for HubSpot.
Questions people ask
Is this an MCP server or a HubSpot app?
Neither. An MCP or an app hands Hermes the write button. Scratch keeps it. Hermes gets the same access, and writing back is a separate step you approve, one record at a time.
What does it mean that Hermes has memory?
Hermes stores skills from previous sessions. After the first Scratch pass on your HubSpot data, it has a skill describing your catalog structure, your naming conventions, and the shape of the job. The next pass starts from that skill. The first run costs the most; every run after that is faster.
Will it touch my workflows, sequences, or lists?
No. Workflows, sequences, lists, and Marketing Hub assets are never exposed for editing, and emails are pulled read-only. Hermes edits records and the associations between them.
Will editing records fire my automations?
Edits in the local copy fire nothing. When you approve a record, Scratch writes it back like any CRM update, so a workflow watching that field can fire, the same as a hand edit would. The difference is you pick which records write back, instead of one pass tripping every workflow at once.
Can I roll a change back after it writes?
Yes. Scratch keeps the original beside the rewrite, so every written record reverts per row. You decide which version stays.
See it on your own CRM
The fastest way to trust it is to watch it run on your records. See it run on your HubSpot CRM →, or download Scratch free and take the first pass yourself.