The record gets enriched from the tab you are already reading, the call gets logged against the right deal, and every change arrives as a diff you approve.
You finished four calls today and logged none of them. The record on the deal moving fastest is three months stale.
A companion does that work where the selling happens. It reads the prospect’s page, stages the update on the contact and company records, drafts the call log and the follow-up task, and shows you the diff before anything lands. Pointed at a list instead of one record, the same loop becomes batch hygiene.
01
How do you enrich a record from the tab you are on?
You are on a prospect’s LinkedIn profile and the HubSpot record is two tabs over and three months stale. A companion pulls what is public, role, company, recent announcements, and stages the update on the contact and company records with the diff shown.
Give it the list instead and it works through every row, researches each one, and queues the updates for a single review. That is data extraction with your CRM as the destination.
02
Activity logging that actually happens
After a call, say what happened in one sentence, or let a companion work from the meeting transcript. It drafts the call log, the note and the follow-up task against the right deal. You skim and approve.
Because the same companion reads your inbox through the native Gmail and Outlook integrations, “log the thread with Acme and set a follow-up” is one instruction rather than an export.
03
Build a list of companies you do not have yet
HubSpot filters segment the contacts you already have. A companion works upstream: it researches companies matching your ICP across the open web, qualifies them against your criteria, and stages new company and contact records with sources attached. The sales prospecting playbook runs this end to end.
New records arrive as a batch you review, so nothing enters the CRM silently.
04
Why does a companion beat a HubSpot workflow?
A workflow inside HubSpot moves data HubSpot already has.
The expensive part of CRM upkeep is everything outside it: the LinkedIn page, the pricing page, the email thread, the call.
A companion stands exactly at that boundary, signed in as you, reading your open tabs, carrying context from the web into the record. You connect HubSpot once and see exactly what it can reach before you allow it, and the credential is kept encrypted where Strawberry never receives it.
Yes. A companion stages record updates, call logs, notes and new contacts, and you review and approve the diff before it lands. HubSpot connects as an account you authorize, through HubSpot’s own MCP server, or in the tab you are already signed into.
Run the automation where the context is. A companion researches a company in one tab and stages the HubSpot update in another, so enrichment, logging and list building need no CSV export and no middleware.
Three ways. Connect the HubSpot account and the credential is kept encrypted where Strawberry never receives it. Connect HubSpot’s own MCP server. Or let a companion work the HubSpot tab you are signed into. All three end with changes staged for your approval.
Record changes are staged for your approval, so nothing edits your pipeline silently. Chats and passwords stay on your device, and chats are not saved on Strawberry’s servers.
Yes. A companion reads the public profile you are browsing and stages the matching HubSpot update, role, company, context for the next touch, with you approving the diff. It works one record at a time or across a list.