Each module works alone. Together, they compound.
Most productivity tools give you buckets — a place to put contacts, a place to put tasks, a place to put notes. They don't talk to each other. You're the integration layer, manually copying context from one app to another, briefing yourself before every meeting.
Software of You works differently. Every module writes to the same database. Every link is a real relationship. A journal entry about a client links to their CRM record. A decision links to the project and the people involved. A calendar event generates a prep brief from emails, past meetings, open commitments, and project status — automatically, because it's all already connected.
The result is a context layer that knows your work the way you do — but never forgets, never loses the thread, and surfaces the right thing at the right moment. This is what Claude becomes when you give it full access to your professional life.
Every person you work with. History, health scores, follow-up nudges. Know your relationships the way a sharp account manager would — except it never sleeps.
"Who haven't I talked to in 30 days?" Deep dive → MODULE 02Tasks and milestones linked to the people driving them. Status, blockers, and next actions — all queryable in plain language.
"What's in flight right now?" Deep dive → MODULE 03Your inbox, linked to contacts and projects. Draft replies with full thread context already loaded. Search across everything you've ever sent.
"Draft a reply to Rebecca about the proposal" Deep dive → MODULE 04Synced events with attendees linked to CRM. Pre-meeting briefs generated on demand from every touchpoint you've had with that person or project.
"Who am I meeting tomorrow and what should I know?" Deep dive → MODULE 05Import call and meeting transcripts. Extract commitments. Track communication patterns across relationships over time.
"What did I commit to in my last call with Marcus?" Deep dive → MODULE 06Structured decision records with options, rationale, outcome, and revisit dates. Stop making the same decision twice.
"What decisions have I made about pricing?" Deep dive → MODULE 07Daily entries with mood markers and energy tracking, cross-referenced to every contact and project you mention. Your work-life, made legible over time.
"How have I felt about the Meridian project over time?" Deep dive → MODULE 08Tagged notes linked to anything you mention — people, projects, decisions. Fast capture with structured recall. Nothing gets lost.
"Show me everything tagged #enterprise" Deep dive →These queries only work because modules share a database. No single module could answer them. Together, they give you compound intelligence — the kind of context a chief of staff would have, delivered in seconds.
Prepare me for my week
Every meeting attendee's relationship history, open email threads, commitments made on past calls, and project status — assembled into a single weekly brief before Monday hits.
What should I be worried about right now?
Surfaces overdue commitments, relationships that have gone cold, stalled project milestones, and decisions past their revisit date — in one honest read.
Draft a proposal for Rebecca
Pulls Rebecca's CRM profile, your full email thread, the relevant project brief, and every pricing or scope decision you've logged — before Claude writes a single word.
Weekly review
Everyone you talked to, what moved and what didn't, decisions made, commitments logged, and what needs attention next week — generated in thirty seconds.
A real follow-up email drafted by Claude with SoY installed. Annotated to show exactly where each piece of context came from.
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
Every module reads from and writes to the same SQLite database. This isn't a metaphor. When CRM records a contact, Projects can query that contact as a team member. When Conversations extracts a commitment, it's linked to the person in CRM and the project in Projects. When Journal mentions a client by name, that entry is indexed against their full relationship history.
This is why cross-module queries work — and why they feel like talking to someone who actually knows your work. The links are real foreign key relationships, not tag matches or fuzzy search. The intelligence is structural, not statistical.
Your data never leaves your machine. The Claude Code plugin connects to a local database at a path you control. No cloud sync. No third-party access. Your context layer is yours.
~/.local/share/software-of-you/soy.db
Configurable. You own the file. Back it up with any file backup tool.
One-time purchase. Yours to own, modify, and extend.