Milestones, tasks, and blockers — connected to the contacts driving them. Project status and relationship context living in the same place, finally.
01 — The problem it solves
Asana knows your tasks. Your CRM knows your contacts. Your email knows what you said last week. None of them know about each other.
So when you open the Meridian project, you see milestones and tasks. What you don't see: Rebecca is the client, and you last talked to her 4 days ago. There are 2 open commitments from your last call. The proposal task is marked complete but legal review is still blocking you. You were feeling good about this project two weeks ago; you haven't logged anything since.
In SoY, all of that is one project. The brief and the relationship context live together. The task board and the communication history are the same view.
02 — How you use it
No project templates to fill out. No status dropdowns to click through. You describe what's happening, Claude keeps the record.
03 — What a project contains
04 — The full project brief
Ask Claude to generate a project brief and it doesn't summarize what you manually entered. It synthesizes everything the system knows about the engagement.
Client relationship history from CRM — how long you've known them, how the relationship has trended, any open commitments.
Recent communications — the last email thread, the most recent meeting notes, what was said and what was decided.
Current blockers — what's stuck, why it's stuck, how long it's been stuck.
Decision log — every call you've recorded for this project, with rationale.
Journal sentiment — a candid read on how you've been feeling about the project, derived from private entries you logged at the time.
05 — Example output
Ask for any project and this is what surfaces — operational detail and relationship context together.