Module 07 — Journal

The qualitative context
that lives nowhere else.

How it felt matters. Now it's connected to everything.

01 — The signal that gets lost

Every other module captures
what happened.

The journal captures how it felt.

Rebecca seemed disengaged on a Thursday in January. You felt drained after the Meridian call. You were energised after the SaaStr meeting with Sarah. These signals never make it into a CRM record or a project status — but they're real, they're meaningful, and over time they tell a story.

A relationship health score doesn't know that you've felt uneasy about this client for three weeks. A project tracker doesn't know that you were sharp and energised when you wrote that proposal. Context that lives only in your head doesn't compound — it evaporates.

Until now, it lived nowhere. The journal module fixes that.

02 — How you use it

Write it once.
Find it forever.

Journal as you would naturally — in Claude's chat window, as part of your daily workflow. You don't format anything. SoY handles the rest.

you → claude
"Journal: Had a draining call with the Meridian team today. Rebecca seemed checked out. Wondering if the timeline is too aggressive."
Entry logged. Mood: drained. Energy: 4/10. Auto-linked: Rebecca Chen (CRM), Meridian Rebrand (Project).
you → claude
"How have I been feeling about the Meridian project over time?"
6 journal entries reference Meridian. Tone arc: cautiously optimistic → anxious → drained. Notable: 3 of 4 recent entries mention timeline concerns.
you → claude
"Show me my energy levels this month"
February average: 6.2/10. Best week: Feb 3–7 (avg 8.1). Lowest: Feb 17–21 (avg 4.4). Pattern: Mondays consistently 7+, Fridays drop.
you → claude
"When have I felt most energised at work in the last 90 days?"
Top 3 energy entries: (1) Jan 14 after SaaStr — "sharp, ideas flowing" (2) Feb 3 after deep work block (3) Dec 22 after closing the DataVault deal.
you → claude
"What patterns show up in my low-energy days?"
Common factors in low-energy entries: fragmented meeting schedules (8/12 entries), Meridian calls (5/12), late starts with no exercise logged (7/12).

03 — Auto cross-referencing

You write. The connections
form automatically.

When you mention a name in a journal entry, SoY links the entry to that contact's record. When you mention a project, it links to the project. You don't tag. You don't categorise. You just write.

Rebecca's contact page shows every journal entry you've written about her, in context. The Meridian Rebrand project page shows every time you've mentioned it — including how you felt when you did.

This is the layer that a CRM will never have. Salesforce tracks what happened in a meeting. SoY tracks what it was like to be in the meeting. Those are different things, and only one of them changes how you show up next time.

Contact links
Any name mentioned in an entry auto-links to their CRM record. Sentiment surfaces in their contact page.
Project links
Project names link automatically. Every "I'm worried about Meridian" entry becomes part of the project's history.
No manual tagging
Claude infers relationships from what you wrote. You never have to categorise after the fact.
Retroactive linking
Add a new contact or project and past journal entries that mention them are linked immediately.

04 — Mood and energy markers

A chart of how you've actually
been doing.

Each entry captures a mood signal (positive, neutral, drained, energised) and an energy level. You don't fill in a form — Claude infers it from what you wrote, or you can state it directly.

Over time: a chart of your energy through the week, the month, the year. Not vanity metrics. Actual signal. The kind that helps you understand why Q3 felt harder than Q2, or why you always feel depleted on Thursdays.

Energy — February 2026
3
4
5
6
7
10
11
12
13
14
17
18
19
20
21
high energy
neutral
low / drained

05 — Relationship intelligence

The layer that changes
how you show up.

The fact that you felt something about a meeting is exactly the kind of signal that would change how you approach the next one.

When you ask SoY for a pre-meeting brief, your journal entries about this person are one of the layers it draws from. Not just interaction count. Not just open commitments. What it's actually been like to work with them.

Pre-meeting brief — Rebecca Chen · Feb 22
Last contact 4 days ago via email. Relationship score: 6.1 / 10, trending down.

Note: you've described Rebecca as "checked out" in your last 2 journal entries. Entry from Feb 18: "Rebecca seemed disengaged — wondering if the timeline is too aggressive." You may want to address timeline concerns directly before discussing next steps.

That insight doesn't come from a CRM. It comes from you — from something you wrote in thirty seconds after a difficult call. SoY just made sure it was there when you needed it.

06 — Example entry

What a journal entry looks like
in SoY.

Written in a sentence. Structured and connected automatically.

Tuesday, February 18, 2026 · 4:47 PM
Had the Meridian check-in this afternoon. Rebecca was barely present — one-word answers, didn't engage on the deliverables. Marcus asked about pushing the Phase 2 deadline again. I left the call feeling like we're building toward a conversation nobody wants to have. Something needs to shift on the Meridian Rebrand before the next review.
Mood drained
Energy
4 / 10
✦ · A real example

What you wrote.
What it automatically became.

A journal entry typed in plain language. No tagging. No formatting. The cross-references happened on their own.

mood 3/5 energy 4/5

Had a draining call with the Meridian team today. Rebecca seemed checked out — didn't engage with the roadmap questions at all. Starting to wonder if the timeline we agreed to is too aggressive, or if there's something else going on.

Also had a good 1:1 with Marcus about the infrastructure side of the Build Canada Homes project. He's confident we can hit March 1 if the spec lands this week.

Auto-linked by the system
Contacts mentioned
Rebecca ChenEntry indexed on her profile — visible in next relationship review (3rd consecutive mention with low mood)
Marcus WebbEntry indexed — positive signal logged against interaction history
Projects mentioned
MeridianSentiment signal added to project history — "timeline concern" pattern forming
Build Canada HomesSpec dependency + March 1 deadline noted — links to open commitment tracker
Mood context stored
Mood 3/5 on a day you had a Meridian call — third such entry. When you ask "how have I felt about Meridian?" this entry surfaces.
Ready to start

The context that matters
is the context you've already written.