Project map
All the clinic's projects on one map: dot size shows how much attention a project gets.
You record your meetings: the company's knowledge base builds itself.
You go to trainings. You come back with decks, recordings and checklists.
Six months later nobody remembers where any of it lives.
You record meetings, plug in your Gmail and files. Athena splits it: tasks to check off, decisions into the company model.
All the work flows as one stream: recordings, emails, files, tasks.
Tasks go dark once checked off. Decisions crystallize into procedures.
Every procedure has a version and a team status. The company enforces what it knows.
The company works as usual. Athena turns that work into knowledge.
Athena reads what the company already produces.
From every source, only the decision remains.
AthenaEvery decision updates procedures and price lists.
A document in a folder isn't a rollout. A rollout is a passed quiz.
You write the procedure once: the course always shows its current version.
Three multiple-choice questions, one open-ended: AI grades the open one.
You see who knows it, who needs a refresh, who hasn't started.
You change the price list: one toggle and the whole team comes back to refresh.
Not “I read it.” I know it.
All the clinic's projects on one map: dot size shows how much attention a project gets.
Every procedure change has a version and an author: you see exactly what changed.
One shortcut searches the company's entire knowledge: procedures, decisions, notes.
An AI agent reads the same model: Claude Code connects to it over MCP.
Click through fictional data: overview, revenue, calendar and team: exactly what the owner's panel looks like in Athena.
Every procedure has a course and a quiz in Athena: here you see who actually knows it.
An assistant doesn't need to know what a text file is. Every role gets its own start screen, and only what it needs.
A simple Start: courses and procedures to learn. No files, no tech: she opens it and knows what today looks like.
Back office means procedures, training, meetings, and goals: the company's engine room, not accounting. A documented company can delegate: to people first, to AI over time.
You go to the trainings, you come back with slide decks and checklists, and nobody rolls any of it out. Procedures live on WhatsApp, and knowledge walks out the door.
You record your meetings: the knowledge base builds itself. Procedures get versions, the team passes quizzes, and every answer cites its source. Not “I read it”, I know it.
FAQ
Keep it, a meeting note is the input, not the outcome. Athena turns it into a company model: the essence goes into memory, procedures get versions, the team passes quizzes. Fireflies is integrated today, more on the way; a transcript from any other tool you simply upload.
Yes. She sees a simple Start screen: courses and procedures to learn: no files, no tech. If she can handle patient scheduling, she can handle Athena.
No. No migration: start with people cards, goals, and one procedure. The rest writes itself down as you work: meeting by meeting.
You change the procedure: Athena saves a version and the diff. Mark it a "significant change" and the whole team's statuses reset to "Needs refresh." The "Who knows" block shows who's caught up.
A task disappears once it's done. A procedure is a decision that describes how the company works: Athena fishes them out of your recordings, versions them, and turns each into a course with a quiz.