← All modules
Module 03 — Gmail

Stop copy-pasting your inbox into Claude.

Your emails are already context. Now Claude knows it.

The copy-paste tax

Six steps before you can even ask.

Every time you want Claude to help you write an email, you run the same expensive ritual. Open Gmail. Find the thread. Copy it. Paste it into Claude. Explain who the person is. Summarise what's happened. Then ask.

That's four minutes of context assembly for a two-minute task. Multiplied across every email you write. SoY eliminates every step before the ask.

01 Open Gmail and find the thread 45 sec
02 Select and copy the full thread 30 sec
03 Paste into Claude 15 sec
04 Explain who the person is 60 sec
05 Summarise the relationship history 60 sec
06 Finally ask what you actually wanted 30 sec
Total context tax per email ~4 min

With SoY Gmail: you just ask. No steps before it.

How you use it

You ask in plain English.

Claude has the full picture. These aren't aspirational examples — they're the queries you'll actually type.

Show me everything from Rebecca in the last 2 weeks
Draft a follow-up to Daniel about the proposal — he's the Main+Main guy, real estate AI
Who in my inbox hasn't heard from me in over a week?
Summarise my email thread with the Meridian team
Has Marcus responded to the contract I sent?

How the sync works

No copy-pasting. No manual tagging. No import step.

When you ask Claude about your emails, SoY syncs them as part of the query. The connections are figured out for you.

15m
Syncs when you need it
When you ask Claude about your emails or open a Gmail view, SoY checks freshness and pulls new messages if more than 15 minutes have passed. No separate sync step. No manual pull.
→
Emails link to contacts — no tagging
Anyone in your CRM who matches a sender or recipient gets their thread attached to their record. No manual tagging required. Matching happens on email address and name.
↗
Project threads link to projects
Emails containing project names or shared-contact patterns are connected to the relevant project on sync. The signal is already in your inbox — SoY just surfaces it.
Gmail API
→
SoY sync layer
→
Contact match
→
Project match
→
soy.db (local)

What changes when you write emails

Before: Claude knows nothing. After: Claude knows everything.

Before SoY
  • You paste the full thread manually
  • You explain who the person is
  • You summarise the relationship history
  • You describe what's been discussed
  • You mention any open commitments
  • Then, finally, you ask for the draft
After SoY
  • Claude has the full thread already
  • Claude knows the relationship history
  • Claude knows open commitments on both sides
  • Claude knows the project context
  • You say "draft a reply" and describe what you want to say
  • It writes from the full picture

Cross-module power

Email is the connective tissue.

Nothing is siloed. When emails sync, they enrich every other module they touch. This is how SoY gets smarter the more you use it.

03 — Active
Gmail
Thread history synced and linked. All emails available to Claude as context.
This module
01
Contacts
Rebecca's emails enrich her CRM record. Relationship history builds with every sync.
02
Projects
Project emails attach to the project. All correspondence lives with the work.
04
Calendar
Pre-meeting briefs pull from email history. Last 3 emails from the attendee, auto-included.
05
Conversations
When you import a meeting transcript, email context is one of the layers Claude draws from.
06
Commitments
Promises made over email surface alongside commitments from calls and messages.

A real example

Two things you said.
Everything else, it knew.

A real follow-up email drafted by Claude with SoY installed. Annotated to show exactly where each piece came from.

Pulled from SoY — you said nothing
You provided in the prompt
Following up — materials for the AI proof of concept
To: Alex Brennan <alex@northgatecapital.ca>

Hi Alex,

Wanted to follow up on our conversation from last week. You mentioned you'd send over a couple of presentations and a non-proprietary document so we could build out a proof of concept for you.

Also — I've been thinking about the video production piece for the Build Canada Homes pitch. I have a few people in mind and will put something together for you once I track down the right fit.

No rush on the materials if things got busy — just didn't want it to slip through the cracks on either end.

Kerry

What SoY already knew
CRM
Alex Brennan, President at Northgate Capital — 2 calls logged
Transcript
Call occurred last week — timestamp from transcript
Commitments
Open: Alex to send presentations + doc — extracted, still open
Commitments
Open: Kerry to build proof of concept — offered on the call
Transcript
Build Canada Homes — project from follow-up call summary
Nudge
No contact in 4 days, open commitments on both sides
What you provided
Prompt
The video production piece — that you're thinking about it
Prompt
Tone: no pressure, easy
The point
You said two things. The system supplied everything else — who, when, what was agreed, what's still open, what project it's tied to. That's context engineering.

Privacy

Your emails never leave your machine.

How Gmail sync works, technically

Gmail sync uses OAuth — the same standard your other apps use. You authorize SoY once, and it can read your emails through Google's API. SoY does not store your credentials.

Emails are stored locally in your SoY database on your machine. They are never sent to any SoY server. The sync path is one-directional: Gmail's API to your machine. That's where it stops.

If you uninstall SoY, the soy.db file is on your machine. You can delete it at any time.

Gmail API → your machine → soy.db ✕ SoY servers
Get started

Stop paying the context tax.

Free during early access. Works with Claude today.

Get SoY — Free → Next module: Calendar →