Every weekday at 07:50, a companion runs your rules over the whole inbox and leaves the finished pass. Nineteen newsletters archived, four threads flagged, drafts attached.
Thirty-four new threads on a Monday. Four of them matter. Finding out which four costs you the first hour of the week.
A companion reads all thirty-four, applies the rules you gave it once, and hands you the result: what it archived, what it labeled, and the four that need you with drafts already written. It can draft anything and send nothing.
01
What does the 7:50 pass leave you?
You state the rules once, in plain language rather than filter syntax.
Paying customers outrank everything. Newsletters you have ignored for a month get archived without asking. An intro gets a same-day draft.
By 7:50 the pass has finished:
19 newsletters archived, none of them opened in the last month.
9 cold pitches labeled and kept out of the inbox.
4 internal threads marked read, because they resolved themselves overnight.
2 customers mentioning renewal, one intro owed a same-day reply, one invoice question. Flagged, each with a draft attached.
02
Replies with the homework already done
A prospect asks about pricing for twelve seats.
The right answer depends on the deal stage in your CRM, what you quoted in March, and which plan changes have landed since. All three sit in other tabs.
A companion reads the thread, checks the CRM you are signed into, and drafts with the numbers in it. Drafts land as real Gmail drafts. You edit and send, or approve and let the companion send. That is the drafting half of sales prospecting.
03
How do commitments reach your calendar?
“Let’s talk Thursday” is a calendar event that currently depends on your memory.
A companion sweeps the week’s threads, finds the calls agreed to and the follow-ups promised, and stages each one as an event through the native calendar integration, with the thread linked.
Before a meeting it runs the sweep backwards. Everything both sides have written, on one screen, including the part where you agreed to something in April and have not thought about it since.
04
What a Gmail add-on cannot reach
An add-on sits in a sidebar with one message loaded.
The reason your reply is hard is almost never inside that message. It is in the CRM record, the shared doc, the other thread, the LinkedIn tab you opened and lost.
A companion works the browser, so it reads the logged-in tabs you read and carries the context to the draft instead of asking you to ferry it across one copy-paste at a time. You connect Gmail once and see exactly what it can reach before you allow it.
Yes. Gmail is a native integration you connect once, and you see exactly what it can reach before you allow it. Chats, passwords, history and cookies stay on your device, and anything that sends email waits for your approval.
Describe your triage rules once and schedule them as a routine. The pass runs in Gmail itself: noise archived, the important threads flagged, drafts written. No zap chains and no API keys.
A companion reads the whole thread plus the surrounding tabs before drafting, and picks up your preferences as you correct them. Every draft is yours to edit and every send is yours to press.
A companion reads, labels and drafts freely. Sending stops at an approval card. The work happens on your own machine in the session you already signed into, so your password is never exposed to Strawberry or to an LLM provider.
Yes. State the rules once, schedule the routine, and the 07:50 pass runs daily: noise archived, the four things that matter flagged, a draft waiting on the ones that need one.
Gmail Strawberry