Take command

Incontro · The operator's desk

Everything routes through one person.

The COO. The GM. The owner. They hold the whole picture, so nothing moves without them. Incontro is that person's desk.

See it on your operation →What the desk does
11surfaces, one desk
7financial areas, each stating its own source
5project states, four priority bands
0actions taken without your call
1gold row — where to start
12modules on one platform

Capability figures. What Incontro does, not a measured customer outcome.

One input · the whole company

assign “draft the Q4 renewal SOW” to A. Reyes by Friday, P1RUNACTION ITEMDraft the Q4 renewal SOWOWNERA. Reyes · notifiedDUEFri 25 SepPRIORITYP1 · This weekNo form. No field-by-field. The same command bar sits on every surface, and every surface understands its own records.

01

The bottleneck

You are the integration layer.

One name carries 163 open items. Two carry none. Nobody chose that. On one screen, the imbalance stops being a feeling.

WORKLOAD · NEXT 7 DAYSPERSONOPEN ITEMSOVERDUEMEETINGSCONFLICTSM. Okonkwo16306h0J. Park903h0A. Reyes814h2D. Halvorsen101h0S. Brightno open work00h0T. Coleno open work00h0

And the week they are in

Three calendars, one week.

Elyon events sit alongside Outlook and Google mirrors, in your timezone. Conflicts are found across the team, not just your own row.

Tick assign and you are scheduling people in, not inviting them.

WEEK · AMERICA/CHICAGOMONTUEWEDTHUFRIStandupDecisionsCustomerReviewVendorCLASHBooked inELYON · CANONICALOUTLOOKGOOGLEOne clash found across two sources on someone else's row, before it cost anyone the morning.

02

The desk

Not a dashboard. A next move.

What is past due, what is waiting on a call, what still owes a recap. Each with its action beside it. One row is gold. Start there.

Never a count you have to decode.

Sign the ratification block (§22)Overdue 27 days · blocks 11 itemsOpen
Answer O23 — architecture or leftover copyBlocks S23 / S28Decide
Train the new AE on the platformEnablement · P2Assign
Delete the stray draft sequence in GHL0 enrolled · inert leftoverOpen
END OF DAY · DIGEST34m ago3 decided · 2 slipped · 1 recap still owedTwo items crossed their due date without a status change.Nothing outstanding flagged on the vault or the ledger.

03

The decision record

A tracker records what was assigned. This records what was decided.

A title is all it takes. The team shapes it, agents enrich it, evidence lands on the record. The moment nothing is unanswered, it walks itself into the decision room.

The call, its evidence, and who made it outlive the person who made it. A chat thread does not.

What it actually is

Adding people does not fix this.

The load is downstream of decisions only one person can make. Another coordinator moves the queue without shortening it.

IdeaDiscussedAssignedIn progressDoneA TRACKER STOPS HEREDecidedRecordedAcknowledged

The decision never got made.

Three weeks in a thread. Eleven items downstream quietly stopped.

The meeting happened. The recap didn't.

What was agreed lives in four memories, in four versions.

One person is carrying the company.

163 items on one name, two people at zero. Nobody is looking across the room.

Each has a right answer the system already holds. Each waits on one person noticing. Incontro is the layer that notices — so you spend judgment, not attention.

04

Built on the operation

A work tracker cannot read your dock appointments.

Incontro is not an app your data gets copied into. It is one of twelve modules on the same platform as your dock, your TMS, your tracking and your sales engine. The desk reads the operation because the operation is already there.

ONE PLATFORM · ONE STATEARRIVO · DOCKappointments, gate, yardTMSloads, tenders, exceptionsIOT TRACKINGassets, shipments, telemetrySALES ENGINEpipeline, conversationsINCONTRO · THE DESKdecisions · projects · people · the record · the ledgerreads every module above, nativelyTHE STANDUP BRIEFfrom loads, not from a task boardTHE DECISION QUEUEexceptions that need a human callTHE NUMBERagainst the ledger, sources stated

Bolt a work tracker onto a freight company and you get a second place to type what already happened.

05

The record

The vault opens deliberately.

Pricing, SOPs, comp, policies, contracts — versioned, access-tiered, acknowledged. Comp and contracts land leadership-only. You open them up deliberately, not lock them down.

Notes stand alone, hang off a project, or serve as a recap — linked from both directions.

06

The ledger

Seven areas, and whether you can see them yet.

Each area states what it is reading from. A blank that admits it is blank beats a chart built on nothing.

Runway

Connected

Net burn

Connected

Cash flow forecast

Connected

Profit & loss

Connected

Commitments awaiting approval

Connected

Receivables aging

Connected

Budget vs actual

No source yet — and it says so

Your number, not ours

By design

07

The dials

Agents propose. You decide.

AEGIS reads your meetings, notes, projects and items, then drafts what needs a decision. Each proposal carries its records, its model and its confidence — and waits.

Advise is the resting posture. Halt is one click. Governance is a control on the screen, not a document in a drawer.

08

The five that differentiate

Most of a work tracker is table stakes. These five are why this is not one.

01

The decision queue fills itself.

Evidence on the record, nothing unanswered, and it walks into the decision room on its own. The list maintains itself.

02

Every proposal carries the records it was built from.

You are never asked to trust a recommendation. You are shown what it was built from.

03

The desk tells you what it cannot see.

Connected, empty, or no source at all. No tile guesses, no chart drawn over a gap.

04

The vault is closed on arrival.

Comp and contracts land leadership-only. Opening one up is the deliberate act.

05

The same action your team clicks, an agent can call.

One code path, one audit trail, whoever takes it. A platform property, not a bolt-on.

09

Feature set

Nine groups, one desk.

The desk

4
  • Desk brief written from live records
  • Named next action, not a number
  • "On you" queue with overdue ageing
  • "You're waiting on" — what you assigned

Workbench & decisions

5
  • Anyone captures an idea; a title is enough
  • Capture → shape → enrich → validating
  • Agents research and enrich
  • Evidence lands on the record
  • Auto-promotion to the decision room

Projects & items

4
  • Five states, proposed to archived
  • Four priority bands, P0 to P3
  • Item provenance — who and from where
  • Rollup: open, overdue, % complete

Meetings & calendar

5
  • Canonical events plus Outlook and Google
  • Read the calendar from any timezone
  • Conflict detection across the team
  • Assign a meeting, don't just invite
  • Recap tracking — who still owes one

The record

5
  • Vault: pricing, SOPs, comp, contracts
  • Versioned, with acknowledgements
  • Access tiers per document
  • Closed by default, opened deliberately
  • Recap ↔ meeting linked both directions

People

4
  • What each person is carrying right now
  • Projects, leads, open, overdue, due today
  • Meeting time and conflicts per person
  • Seven-day workload horizon

The ledger

4
  • Seven areas, each stating its source
  • Connected / no records / no source
  • Runway in months of operating cash
  • Commitments awaiting approval

AEGIS governance

6
  • Proposals drafted from your own records
  • Nothing sent, nothing changed
  • Each proposal shows its sources
  • Stated model and confidence, every answer
  • Per-module governors with Halt
  • Logged and reversible, without exception

Platform

4
  • Natural-language command bar
  • Command palette across every surface
  • Notification centre with daily digest
  • One of twelve modules

The capability list runs longer than this. These are the forty-one a buyer actually weighs.

Next step

See it on your operation.

Ninety minutes on your operation: your decision backlog, your projects, your people and what each is carrying. You keep the configuration.

Request a briefing →See Arrivo, the dock module

Incontro is the ELYON company operating module. Every capability here is live in the product today. No figure on this page is a customer outcome.