AI Chief of Staff · for what falls between your L10s
Viti works inside your chat, email, CRM, calendar and project tools, watching in both directions: for drift from your Rocks and Scorecard, and for what nobody decided to watch. It starts the response, stays with it, and brings you only the calls that are genuinely yours.
Not another meeting-prep assistant. Built by Ravi Pathak, Founder, Tatvic Digital Analytics. Running live inside that ~100-person company, and on this page.
A renewal in motion the CRM couldn't see, surfaced in time to act. The full loop, below.
The hidden operating load
Your L10s and Quarterlies can only catch what reaches the agenda — and that's just the part you see.
Between two Quarterlies, the agenda flows on — while a client goes quiet, a promise made in passing never becomes part of the plan, and a pipeline fills with activity but no movement. Each of these falls off the agenda line. Viti catches them before they land.
carries the between-work: the noticing, connecting and questioning. Not the manager's job, and not another dashboard for you — the load, not the accountability.
Where Viti fits
Ninety, Bloom and EOS One hold your V/TO, run your L10 agenda and store Rock status — and that status is self-reported. Viti sits on top and checks it against the daily work in Slack, your CRM and your project tools, so the record you walk into the Quarterly with is corroborated, not just remembered. It doesn't replace your system of record. It makes it trustworthy.
Closed-loop proof · 9 July 2026 · our own company
A live account was five days from its renewal decision and no one owned the risk. Nothing in the system of record flagged it — the CRM showed the wrong stage and zero value. Viti caught it from the silence, found the renewal moving on email, and put it in front of an owner while there was still time to act. This is churn caught between the L10s, not at the post-mortem.
No renewal discussion appeared in the connected systems.
Renewal in motion on email; the operating record didn't show it.
The stated reality and the CRM could not both be true. Viti stated what it couldn't see and asked for the deal link to verify.
Right stage, true value — five days before the renewal decision.
What this proves: a churn risk the record couldn't see — caught from silence and handed to an owner five days before the decision. Signal → owner response → evidence → action in time. It does not claim the renewal was won; it proves the risk stopped being invisible.
The same mechanism, across the company
US expansion existed as an objective. The evidence, emailed to five executives that Friday: no US deals, no international leads.
The original promise, the missed date, the required recovery and the source thread arrived together — so the owner acts from the record, not memory.
A reminder repeats the task; a dashboard shows 25%. Viti asked whether it was time running out or the tasks themselves — the answer changes next week's plan.
A lot of what you just read is red. That's the point. The same scan runs on every client relationship: on one recent weekly read, 8 of 18 accounts sat at-risk, two contracts had lapsed 234 and 623 days earlier, and decision-maker silence spanned six accounts — each surfaced automatically, before a QBR went wrong. This is what open-loop looks like when a company measures itself honestly — Viti didn't create this baseline, it exposed it. Every red signal now has an owner, an action, a deadline, and a closure state. Most companies have the same numbers. They just can't see them yet.
How Viti works
It doesn't wait for anyone to ask the right question. The work itself triggers the loop — filling your Issues List between L10s, not only during them — and each case stays open until its current state is known.
Viti watches in both directions — for drift from what leadership decided, and for what nobody decided to watch. A signal becomes a case with its source attached. The specific question goes to the owner who can answer it, and the answer is tested against the record; 48 hours of quiet brings in the team lead, 72 hours reaches you. Each case stays open until reality is known — resolved by the owner, closed by a rule you set, or routed up to you, prepared. Your call is recorded as precedent, so the same question doesn't come back as if you never answered it.
Intent is a reference — not a limit on what Viti is allowed to notice.
Drift from your Rocks and V/TO — and what nobody decided to watch: silence, contradiction, stalled motion.
Material drift becomes a case. The source stays attached.
The specific question goes to the person who can answer it. 48h quiet → the team lead. 72h → you.
Open until reality is known — resolved by the owner, dropped to the Issues List for IDS, or routed up to you, prepared.
Your call is recorded — the same question doesn't come back as if you never answered it.
Hard on the work, not on people. The team gets their week back.
Calibrated authority
Everything runs at the lowest seat on your Accountability Chart that can resolve it. Autonomy isn't the product — knowing where authority belongs is. Yours is deliberately the smallest.
A week of signals flows in from the left. Most are absorbed at Level one, where a rule already answers them. Most of the rest close at Level two with the owner who can act. Two — this week — pass all the way through to the founder.
Level 01 · Viti acts
hard rule: a deal below your floor → flagged before the thread decides it
Level 02 · the accountable owner acts
the clock: 48h quiet → team lead · 72h → the sponsor's DM
Level 03 · you decide
judgment call: decide either way — Viti keeps the why
What reaches you is a handful, not a feed.
Evidence, context, precedent and a recommendation arrive together. Your call is recorded and becomes precedent — the company remembers why, and needs you less next time.
Trust is part of the product
If Viti can read the company, you must be able to inspect — and evict — Viti. One boundary, everything inside it. The model is a socket, not the brain.
A dedicated Viti user ID, scoped to exactly what you authorize — audited, revocable in one action.
Split-key: three components in separate places. The files alone are useless — to anyone, including us.
Layered stop, instantly. Revoke the license and the deployment shuts down and wipes its own workspace.
People can correct an interpretation, update a rule, reopen an outcome. Judgments stay linked to evidence.
Every department, every week
The Issues that should reach your L10 — surfaced by department, with evidence, before the meeting. Your Scorecard shows the number; Viti shows whether the work behind it is real. Your system of record — Ninety, Bloom or EOS One — covers one row of this readout.
In operating memory 74 people · 6 teams · 77+ deals · 18 accounts · 41+ decisions with rationale · 53 delivery folders — real June–July 2026 editions from the ~100-person company that built Viti
Friday, 7:06 pm
Friday evening, nothing is waiting on you.
The week's slips have owners and next steps, surfaced for the L10 rather than lost between them. The two calls that were genuinely yours are made — and recorded, so they become precedent the company keeps. Not because you found out faster: because the company now recognizes, routes, acts, and learns without routing everything through you.
Commercial model
Hard to find, capped at one person's week — and a hire most 50–200 person companies haven't made yet. That's the point.
Run personally by the builder of Viti — your Operating Map, Signal Logic and authority boundaries built against real work.
The loops run weekly on their own. One avoided miss — a saved renewal, a caught breach — covers the quarter.
Already have a Chief of Staff? Viti carries the drift-detection and follow-up load that eats their week — so it's spent on judgment instead.
Don't evaluate it from a deck
Give Viti the function where leadership still finds things out late. See what it catches, what it works through, and what needs you.
Your boundaryData stays in your environment; access granted, audited, revocable.
ContinueThe pilot rolls into the 90-day setup.
StopYou keep the Operating Map we built.
Your first 90 days are run by Khilav Joshi — the builder of Viti and Strategy Head at Tatvic Digital Analytics, the company whose real outputs you've been reading.
We'll reply personally to find the right function to start with.
Straight answers
Are you an EOS Implementer? Viti is a partner opportunity, not just a tool for your clients. Implementer page coming soon.
Not affiliated with, endorsed by, or certified by EOS Worldwide, LLC. EOS®, Rocks®, Level 10 Meeting®, V/TO®, Scorecard, IDS™ and Traction® are trademarks of their respective owners, used here for descriptive purposes only.