The Path Watch Tomo work For Teams Pricing About Jay Request an intro call
For your department's day-to-day

Your department runs half on its own. You lead, instead of administrating.

The recurring department work eats your week: pulling together status, keeping the plan current, securing knowledge, setting up handovers. It's manageable work — and that's exactly why it no longer belongs on your desk.

We pour the one routine that costs you most into your first Tomo — turnkey, straight into your operation. The same path, one level closer to the day-to-day.

Department Leadership level Default route · Hero / Tier 2 The same path, your language
The Shift

From admin that eats your week to a system that runs.

Today
  • You rebuild the status report from scratch every week.
  • Knowledge lives in heads and leaves when someone leaves.
  • Handovers get improvised when things are already tight.
  • You update the plan by hand.
With your Tomo
  • The status report is built on a single ask, straight from the files.
  • Knowledge is captured as you work — and stays.
  • Handovers are prepared before they're needed.
  • The plan keeps itself up to date.
Your own Tomo at your level

Not another tool to log into. A workplace that belongs to you.

Four pieces, the same mechanics as on every level. Here with your department's scope.

Status

The weekly report comes together on one ask, from your bullet points and the files.

Planning

Keeps the department plan current and carries changes through on its own.

Knowledge capture

Writes knowledge down as work happens, so it stays when someone leaves.

Handovers

Sets up handovers before they're needed — no context gets lost.

See it at your level

One ask. The department round-up sits ready for your approval.

Click through: one sentence becomes a prepared round-up waiting for your yes. You only talk to Tomo — behind him, three threads are running.

TomoDepartment operations
Ready
The whole situation in one sentence

You hand over the round-up in one ask. No barrage of follow-up questions.

YouGet this week's department round-up ready.
On it. I'll pull the status from the project files, update the plan and prepare the upcoming handover. I'll lay everything out for your approval — nothing goes out without you. One moment, I'm pulling three threads.
What I know for sure from the files, I use. Where a date doesn't match its source, I flag it for you.
A department without a bot fleet · Tomo's visible thinking

“I'm pulling three threads.”

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

Status station

I'm building the weekly report from your bullet points and the live project files.

Planning station

I'm carrying the changes through: two dates moved, one resource reassigned.

Handover station

I'm drafting the handover doc for the departing process owner — before things get tight.

Checked before you see it

The plan still had the delivery date in week 14. According to the project file it has moved to week 16. I've corrected it and noted the source. Tell me if I've got that wrong.

The calm gate

Three finished pieces. Each one waits for your yes.

Full texts, nothing hidden. Approve each one individually, or edit first. Every date shows where Tomo got it from.

Approved: 0 of 3 Tip: tap a receipt to see the source.
Status station
Department weekly report · Week 24
For: you & division leadership
This week at a glance: • Three projects on track, one moved (delivery week 16 instead of week 14). • Capacity within range, one resource reassigned. • One open point for division leadership: sign-off on the moved delivery. Your bullet points are worked into the report, same structure as always.
Edit first
Planning station
Planning update, carried through
Dates per project file
Changed since last week: • Delivery, Project Nord: week 14 → week 16 • Review meeting: Wednesday → Thursday • Resource: Anna takes over the test track from Tim (parental leave) The rest of the plan stays as it is.
How I know: The dates come from the live project files. Source: projektakte-nord, field “Liefertermin”, updated the day before yesterday. I only carried the plan through — I didn't move anything myself.
Edit first
Handover station
Handover doc · Process owner
For: successor from week 27
So no context gets lost: • Owned processes and their tripwires • Open points with current status and next step • Key contacts, internal and external • Recurring meetings and how to prepare them The doc is complete — it's waiting for your approval and a short handover conversation.
Edit first
Step 0 of 2

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

The Path · four stages, one journey

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

The strongest proof isn't a promise, it's a path already walked. Each stage rests 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 a clean handover protocol is structured, instead of piecing it together from three old documents.
AI as a tool

Repeating

You pour what works into fixed prompts and templates.

At your level: The weekly status becomes a template plus a prompt that turns your bullet points into the finished report in minutes.
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 “department status” station with a fixed role, the project files as its memory, and a routine that runs from bullet points to the briefing you send upward.
AI as a colleague

Orchestrating

A colleague takes your asks, pulls the threads, sums up and lays it all out for approval.

At your level: “Get the department round-up ready.” He pulls the status from the files, updates the plan, prepares the handovers, 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 walk beside you, step by step. The building is yours.

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

Built for you

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

Mid-range budget. The fastest route to a first real result in daily operations.
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 capability in one.

Default for your level: Hero · Tier 2, handed turnkey into your department's operation. See pricing & range

You approve

You stay the conductor. Tomo takes over work, never 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 your 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 approval.
  • In the first real-world run: seven out of ten threads completed in a single 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

Find the one routine that costs you most, week after week.

We pour it into your first Tomo — turnkey, straight into your department's day-to-day. One ask, one finished package, your approval.