How it works

Reads your tools. Acts in them. Remembers in between.

Viti runs on a schedule, not on request. Nobody opens it. It arrives as a card in chat or a mail in the inbox, from a dedicated identity you authorise.

The loop

Four verbs, one loop.

Every case Viti opens goes round this loop until it is closed. A meeting-prep assistant runs the first verb and stops.

Your toolsViti · on a scheduleOperating MemoryChatEmailCalendarCRMProjectsDataREADSACTSREMEMBERSDECIDESStarts. Stays.Escalates.PrioritiesRulesCommitmentsDecisionsPrecedentsOutcomesReads on a schedule, not on request.Acts as cards and mail, in the same tools.Decides at the lowest rung that can close it.
Reads

Chat, mail, calendar, CRM, project and data tools, on a schedule you can see below. It looks for promises, plans, decisions and silence.

Decides

Against the rules and precedent in Operating Memory, and against who has the authority. It picks the lowest rung that can close the case.

Acts

One card to the owner, in the tool they already use, with what to reply. It checks the answer and asks again if the answer is vague.

Remembers

Owners, open work, rules, decisions and outcomes stay in Operating Memory, so the next case starts from what is known.

Viti's week

On a schedule, not on request.

From the production schedule at Tatvic, August 2026. Times IST. Weekends: clients, decisions and meetings stay on; plans and projects rest.

MonTueWedThuFriSatSun
Clients, decisions, inboxevery 30 min, 7 AM–11 PM
Meetings readevery two hours, 8 AM–8 PM
Carry-over, then weekly plans become tasksMonday morning
Projects reconciled, portfolio digestMonday morning
The CXO briefingMonday, around 8 AM
Project health and nudgesweekdays, every 30 min
Sponsor status mail per live projectweekdays, 10 AM
The follow-up card to every ownerweekdays, 6:05 PM
Week closed with each lead · pipeline cardsFriday 6 PM · 7 PM
Sales, account and marketing reportsSaturday, by mail
Objective health, one mail per objectiveSunday
Memory maintenanceevery night, 2 AM
Reaches youReaches the teamsRuns unseen

The escalation rule

To the owner first. To you only when nothing below you can close it.

There is no clock. A case climbs a rung when severity or silence crosses the rule you set at setup, never on a timer.

  1. Starts

    with the responsible owner.

    The ownerVitiOne question. Not a meeting.
  2. Stays

    with the issue until reality is known.

    TueWedFriReality known.
  3. Escalates

    what remains unresolved. To the owner's lead first. To you only when nothing below you can close it.

    OwnerOwner's leadYouOnly if nothingbelow can close it.

Operating Memory

What it keeps, so it never asks twice.

Encrypted at rest, decrypted only in memory, the key split three ways. Trust and control → What a company brain is, and is not → Company brain questions →

Priorities
The objectives and the plans that serve them.
Rules
The standing rules a request is checked against, for example no staff placed at a client.
Commitments
Every promise made to a client or a colleague, with its owner and date.
Decisions
Each decision under one ID: the request, the options, who decided, what was decided.
Precedents
Past decisions Viti checks before asking a person the same question twice.
Outcomes
What happened after: closed, carried, escalated, or dropped with a reason.

In your tools

You don't go to Viti.

It works inside the tools your people already use, from one dedicated identity you can revoke in one action.

  • Google WorkspaceLive at Tatvic
  • Zoho CRMLive at Tatvic
  • BasecampBy API
  • BigQueryBy API
  • SlackTested · set up in the pilot
  • Microsoft 365Tested · set up in the pilot

Start here

Give it one function for four weeks.

Watch its week run in your own tools before you decide anything.

Give Viti one function

Four weeks, one function, inside month one.

Real capture · names and clients redacted