Ten minutes of reading in place of ninety of tab archaeology. Usage, tickets, CRM history and company news compiled before the call, and the follow-up drafted after it.
The renewal call is at two. Ten minutes before it you get the account: six weeks of CRM history, the open tickets, the usage trend, the company news, and the fact that the champion changed her LinkedIn title last month. Ninety minutes of tab archaeology, done while you were on the previous call.
A book of thirty or sixty accounts assumes you hold all of them in your head at once. Your companion holds them instead, assembling the picture on demand and sweeping the whole book between calls.
01
The pre-call brief, every call
Before a renewal or check-in, a companion pulls the threads together: CRM history from HubSpot or your platform of choice, recent tickets, usage trends from the dashboard, company news, and who is actually attending. The QBR gets the same treatment at deck-input depth.
A routine sweeps the whole book on schedule, detecting job changes and title updates on LinkedIn, account news and upcoming renewal dates, so Monday opens with a digest naming which accounts moved and why.
Deeper account research runs the same way as our research workflows, and how companions serve a whole team’s shared accounts is covered in Strawberry for teams.
03
What happens after the call?
Built-in transcription turns the call into notes, and the companion drafts the follow-up email and stages the CRM update with next steps, risks and commitments for your confirmation. Nothing reaches a customer’s inbox without your approval; the model is on the security page.
Filing happens during the call, so the next person to open the account reads notes from this week rather than from six weeks ago.
Yes. A companion compiles CRM history, support tickets, usage, news and attendee context into a brief before the call, on demand or on a schedule. It works in your logged-in session, so it reads the same tools you do.
Yes. Companions detect job changes and title updates across your contacts and flag them in a scheduled sweep of your book, so a departure surfaces in Monday’s digest rather than on the renewal call.
Yes. After a transcribed call, the companion stages the CRM update and the follow-up draft for your confirmation. See the HubSpot page for how the integration works.
No. Sending is a consequential action, and consequential actions always wait for explicit approval. The model is documented on the security page.
Strawberry is a free download for Mac and Windows, including 2,000 credits a month. Paid plans start at $20/month for 8,000 credits. See pricing.