Attio Home

No tabs. No nav. The page reads top to bottom the same way a day does - composer, meetings, tasks.

Each section earns its position by urgency, not by category. The closer to the top, the closer to action.

The composer sits at the top because it's the fastest path to anything in the product - ask a question, draft a follow-up, run a prompt, trigger a workflow.

Putting it above the fold is a small decision that changes the posture of the whole page. You don't arrive at Home to read. You arrive to act.

The layout is built around hierarchy and rhythm.

Meetings, tasks, and context are structured to be scanned instantly — with clear prioritisation and minimal noise.

Everything has a place, so nothing competes for attention.

Meetings are the most time-sensitive thing on anyone's day. They start cold and end lossy - context missing on the way in, follow-ups missing on the way out.

We designed each meeting as a card, not a row, because a card can hold context. Prep is already there when you land. Expand to see the brief, the attendees, the recent touchpoints. Collapse and the page returns to rest.

Before each meeting, users can generate an instant briefing.

Relevant context is pulled together automatically: who's involved, what's been discussed, and what matters now.

No reconstruction. Just readiness.

After the call, the meeting evolves into a recap.

Key outcomes, decisions, and next steps are captured automatically — so context doesn't disappear.

The system keeps the memory.

Tasks live below meetings, intentionally lightweight. No projects, no priorities, no statuses. Just a list to move through.

We resisted every instinct to make this section more capable. The moment tasks become a system to manage, they stop being a thing you finish. The friction had to stay low enough that checking one off feels like momentum, not admin.