The path Watch Tomo work For teams Pricing About Jay Book an intro call
For hands-on team leads

One colleague for the whole team. You say “prep the weekly”.

Your team no longer runs on your head — it runs on a shared working layer that thinks along: meeting prep, action capture, drafts, handovers. You set the direction and give the sign-off; Tomo takes care of the recurring work.

You can have your own Tomo at your level too — not just the board. The same path, one level closer to the day-to-day.

Team lead level Default route · Hero / Tier 2 Same path, your language
The shift

From a team that runs on your head to a working layer that keeps running.

Your team today
  • Meetings without prep, minutes nobody writes.
  • Action items that sink into the chat.
  • The team runs on your memory.
  • You administer instead of leading.
With your Tomo
  • The meeting prep is ready and waiting on the table.
  • Every decision is captured as an action.
  • A shared layer carries the team memory.
  • You lead — your Tomo handles the recurring work.
Your own Tomo at your level

What your team Tomo takes off your plate.

Four pieces, the same mechanics in every domain. That’s why Tomo feels the same doing weekly prep as it does with handovers or status updates.

Meeting prep

Agenda, templates and the open items from last time — ready before the meeting starts.

Action capture

Every decision and every task captured. Nobody has to take notes.

Drafts

Status updates, team emails and handover notes, prepared for you to read over.

Handovers

Knowledge secured when someone moves on or is out. The team never loses context.

See it at your level

One quick ask on Monday. The weekly is ready for your sign-off.

Click through: one sentence becomes a fully prepped weekly waiting for your yes. You only ever talk to Tomo — behind the scenes, three threads are running.

TomoTeam working layer
Ready
The whole situation in one sentence

You hand off the weekly in one quick ask. No barrage of follow-up questions.

YouPrep the team weekly for tomorrow.
On it. I’ll build the agenda from the open items, follow up on the action items from last time and draft the status update to the team. You read it over and sign off — nothing goes out without you. One moment, I’m pulling three threads.
Where the team memory gives me solid ground, I use it. Where I’m not sure, I flag it for you.
A team without a fleet · Tomo’s thinking made visible

“I’m pulling three threads.”

Three stations work in parallel. You still read only Tomo — they never talk to you directly.

Meeting prep

I’m building the agenda from the five open items and attaching the templates.

Action capture

I’m following up on the seven action items from the last weekly: four done, three open.

Writing desk

I’m drafting the status update to the team, in your voice: brief, clear, no filler.

Checked before you see it

One open action was still assigned to Lukas, who’s been on vacation since Friday. I’ve moved it to Mara, following your cover rule. Tell me if I got that wrong.

The calm gate

Three finished pieces. Each one waits for your yes.

Full texts, nothing hidden. Release each one individually — or edit first.

Released: 0 of 3 Tip: tap a receipt to see the source.
Meeting prep
Agenda team weekly · Week 24
For: 6 participants · Tuesday 9:30
1. Review: open actions from last week (3 open, 4 done) 2. Status of running topics: release 2.4, onboarding flow, support backlog 3. Decision: priority for the next sprint week 4. Quick round: vacations, cover, dates 5. One thing that should go better this week
Edit first
Action capture
Open actions, followed up
As of the last weekly
Open: • Work through the support backlog, Mara (taken over from Lukas, vacation) • Final read of the release notes 2.4, Jana • Meeting with procurement about the tooling budget, you Done since last time: • Onboarding checklist updated • Retro actions documented • Dashboard access handed out • Feedback round on quarterly goals
How I know this: The seven actions come from the minutes of the last weekly. Source: protokoll-weekly-kw23, section “Decisions & tasks”. The cover switch comes from your absence list — nothing invented.
Edit first
Writing desk
Status update to the team
To: team-produkt@…
Hi everyone, a quick status before the weekly: release 2.4 is on the home stretch, Jana is giving the notes a final read. Mara is covering the support backlog this week while Lukas is on vacation. Bring your open items — I’ll keep the round short. Agenda attached. See you tomorrow at 9:30
Edit first
Step 0 of 2

Everything in this demo is placeholder content with made-up names and numbers.

The path · four stages, one journey

The same path at every level — here in your language.

You start at the bottom and climb as far as makes sense for your team. Each stage builds on the one below it.

AI as chat

Asking

You ask questions and get answers. AI as a better Google.

At your level: You ask how to structure a tricky feedback conversation instead of staring at a blank page.
AI as a tool

Repeating

You pour what works into fixed prompts and templates.

At your level: The same-every-week agenda becomes a template that delivers the draft in thirty seconds.
AI with a role

Setting up

You give the AI a role, a memory and a routine. A workplace of its own.

At your level: A “team weekly” station: a fixed role, your notes as its memory, one routine from agenda to action items.
AI as a colleague

Orchestrating

A colleague takes your quick asks, pulls the threads, sums things up and lays them out for your sign-off.

At your level: “Prep the weekly.” Tomo pulls together actions and status, drafts the agenda and the follow-up email, and lays it all out for you.
The ladder · three routes

The path says where. The ladder says how.

The same Tomo, three routes to get there — chosen by budget and your own time. For your level, the middle route is usually just right.

Door opener · Tier 3

Built by you, guided

We show you the path and guide you step by step. The building is yours.

Smallest budget. The lightest entry, maximum independence.
✦ Your level Hero · Tier 2

Built for you

We build your team Tomo and hand it over turnkey. Fast value, little effort on your side.

Mid-range budget. The fastest route to the first real result in your team.
Anchor · Tier 1

Built together

We build hand in hand, several stations, and enable you to keep building on your own.

The biggest investment, the deepest transformation: system and skill at once.

Default for your level: Hero · Tier 2 — handed over turnkey into your team’s everyday work. See pricing & range

You sign off

You stay the conductor. Tomo takes over work, not decisions.

Nothing leaves the system without your yes: no sending, no publishing, no deleting. You keep the direction, the priorities and the last ten percent — the judgment, the relationship, the room.

The question that carries it all: Where does the freed-up attention go now?

Built, not claimed

Jay walked exactly this journey.

30+ stations across completely different fields, all on one mechanic, conducted by one colleague. Jay’s own working day — not an invented number.
  • The start: Claude as a better Google — single questions in single sessions.
  • Today: Tomo, the one point of contact who breaks work down, conducts it and lays it out for sign-off.
  • In the first real-world run: seven out of ten threads completed in one session.
  • Built by Jay Manuzon, former DAX-40 intrapreneur and humanistic coach. You get both: the system, and the person who knows where it would bypass the human.
Other levels

The same colleague, one level up or down.

Every level has its own language and its own default route. It’s not a different product — just a different scope.

The first step

Build your first team agent.

We take one recurring team ritual — the weekly — and build the first shared agent, visible in everyday work. Handed over turnkey, in use from day one.