The path Watch him work For teams Pricing About Jay Request an intro call
For steering your division

Your division delivers more, with the same headspace.

Reporting, stakeholder updates, initiative tracking, briefings for the level above: the recurring division work eats exactly the capacity you need for steering. Your own Tomo takes over that layer — you keep direction and approval.

One main colleague conducts the routine, and your division's memory lives in the system instead of only in your head. The same path, one level closer to day-to-day business.

Division Leadership level Default route · Anchor / Tier 1 The same path, your language
The shift

From routine that eats your steering capacity to a running system.

Today
  • AI only as an occasional chat on the side.
  • Reporting and updates rebuilt by hand every single time.
  • Steering capacity seeps away into routine.
  • The knowledge about your division lives in your head.
With your Tomo
  • One main colleague conducts the recurring work.
  • Reporting and updates on demand, prepared ready to send.
  • Capacity freed up for steering and deciding.
  • Your division's memory lives in the system, not only in your head.
Your own Tomo at your level

He orchestrates the recurring division work.

Four pieces, the same mechanic as on every level. Here with the scope of a whole division.

Reporting

Pulls the division report from the current status — same structure, fresh numbers, ready to send.

Stakeholder updates

Drafts updates upward and sideways, in the right tone for every audience.

Initiative tracking

Keeps the status of all initiatives up to date and flags what needs attention.

Upward briefings

Prepares templates and decision papers for the level above you.

See it at your level

One ask on Monday. The portfolio update sits ready for approval.

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

TomoDivision steering
Ready
The whole picture in one sentence

You hand off the update in one sentence. No barrage of follow-up questions.

YouGet the portfolio update ready for Monday.
On it. I'll pull the division report from the current status, check where every initiative stands and draft the briefing for the level above you. I'll lay everything out for your approval — nothing goes out without you. One moment, I'm pulling three threads.
What I know for certain from the initiative list, I'll use. Wherever a status doesn't match its milestone, I'll flag it for you.
A division without a fleet · Tomo's visible thinking

“I'm pulling three threads.”

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

Reporting

I'm pulling the division report: same structure, fresh numbers, formatted and ready to send.

Initiative tracking

I'm checking the status of all eight initiatives: six on track, two need attention.

Briefing station

I'm drafting the paper for the level above you — right tone, kept short.

Checked before you see it

The initiative “Market Entry South” was reported green. Its milestone has been overdue for two weeks. I've set it to yellow and noted why. Let me know if you see it differently.

The calm gate

Three finished pieces. Each one waits for your yes.

Full texts, nothing hidden. Approve each one on its own, or edit first. Wherever there's a number, you can see where Tomo got it.

Approved: 0 of 3 Tip: tap a source tag to see where a number comes from.
Reporting
Division steering update · Week 24
For: you & the leadership team
The status at a glance: • Delivery reliability 96%, slightly above target. • Two initiatives need a decision (see status list). • Budget on track, one reallocation up for discussion. Details and charts attached, same structure as always.
Edit first
Initiative tracking
Initiative status, brought up to date
Status from the initiative list
Needs attention: • Market Entry South, yellow (milestone 2 weeks overdue) • Tooling consolidation, yellow (budget decision pending) On track: • Efficiency programme, onboarding roll-out, supplier audit, data migration, training series, site expansion
How I know this: The eight initiatives and their milestones come from your initiative list. Source: initiativen-bereich, columns “Status” and “Milestone”. I derived the status change from the overdue date — I didn't invent it.
Edit first
Briefing station
Briefing for the level above
To: divisional board
Short decision paper: We request approval of the budget reallocation in favour of the tooling consolidation (volume attached). Rationale: saves recurring licence costs from Q4 onward, and it unblocks an overdue milestone. A decision paper with two options is attached.
Edit first
Step 0 of 2

The content of this demo is placeholder material with invented 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

Ask

You ask questions and get answers. AI as better googling.

At your level: You ask how to weigh three competing initiatives against each other by impact, instead of piecing the comparison grid together yourself.
AI as tool

Repeat

You pour what works into fixed prompts and templates.

At your level: The recurring division report becomes a fixed template with a prompt. Same structure, fresh numbers, a draft at the press of a button.
AI with a role

Set up

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

At your level: A “division steering” station: a fixed role, the initiative list and KPI definitions as memory, a routine from status pull to steering update.
AI as colleague

Orchestrate

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

At your level: On Monday you say “get the portfolio update ready”. Tomo pulls together the status of every initiative, drafts updates and briefings, and lays it all out for you.
The ladder · three ways

The path says where. The ladder says how.

The same Tomo, three ways to get there — chosen by budget and your own time. At division level sit high leverage and the route into the line.

Door-opener · Tier 3

Built yourself, guided

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

Lowest resources. The lightest entry, maximum independence.
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.
✦ Your level Anchor · Tier 1

Built together

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

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

Default for your level: Anchor · Tier 1, built together, with the rollout into the line in view. See pricing & range

You approve

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 direction, priorities and the last ten percent — the judgement, the relationship, the room.

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

Built, not claimed

Jay walked this exact 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 better googling, 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 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

Pilot it in one division.

Set it up in one division, show the value, then hand it into the line. We build your first Tomo together — you keep the direction.