The challenge
Documentation lived scattered across several tools. They all did their job, but the team kept adapting to them: every new feature ended up behind a different plan, and the space for pages, documents, and images did not scale with the growth. What was missing was a system built around the way the team works, not the other way around.
Our approach
We took what worked in the existing tools, organized pages and local Markdown notes, and moved it into a system of its own: no plan limits, with chat, calendar, and meeting transcription unified instead of scattered across Slack, Google Calendar, and ElevenLabs. Designed, too, to avoid depending on a single cloud: it keeps everything locally as well as syncing, with a desktop version underway.
The whole project, at a glance
Opening a workspace doesn't mean hunting for anything: the overview shows pages, upcoming events, and unread conversations on one screen. It's the first thing you see, not something you have to go looking for.
Everything that used to live scattered
The team already had Slack for chat, Google Calendar for scheduling, and ElevenLabs for transcribing meetings. Each did its job, but they lived apart, and none of them knew what was happening in the others. We unified those three things inside Tropos: per-project chat, synced calendar, and AI transcription, all linked back to the same page, and responsive for whenever it needs to be opened from a phone.
Not depending on a single cloud forever
Adapts to the phone
It was not the starting point, but it is there: everything Tropos does also works from the phone, without losing functionality.
Why it's called Tropos
The name comes from "polytropos," how Homer names Odysseus in the Odyssey: the man of many turns. It describes exactly what the product had to be: a tool that adapts, not the other way around. That same reference runs through the brand: every new workspace opens with a page about the Odyssey.
“Tell me, O muse, of that ingenious hero who travelled far and wide after he had sacked the famous town of Troy.”
The Odyssey, Homer. Samuel Butler translation, 1900.
Still evolving
We add pieces every few weeks: calendar, AI transcription, new integrations. The idea was never to finish it all at once, but to have it grow at the pace of the team using it.
Tropos is now where the studio, its projects, and its clients are documented. We keep building on the same idea: the tool adapts to the team, not the other way around.
See it live