Guide · founder role pack
An AI chief of staff that brings decisions, not chat
Founders don't lack information — they lack a filter with initiative. The chief-of-staff job is watching everything, doing the preparable work, and interrupting you only with decisions that are actually yours.
The inbox is the wrong shape
Everything a founder must react to arrives shaped like a message: Stripe emails, support threads, dashboards' alert digests. None of it arrives shaped like a decision. So triage — the actual chief-of-staff work — happens in your head, forty times a day, from cold context.
Flip the shape. A decision-ready item says: what changed, why it matters in money or risk, what was already done about it, and the one thing only you can decide — with the evidence attached:
What a founder-side agent watches
The signals with money attached: billing failures (webhook outages, dunning, involuntary churn), churn risk (usage cliffs, champion departures — each matched to a playbook with outreach pre-drafted), deadlines (the enterprise renewal call on Thursday, brief already prepared), and opportunities (seats maxed out, upsell window open). Most items resolve themselves in the delegated lane; the queue only interrupts for the few that need you.
Initiative needs guardrails
The reason chief-of-staff products default back to chat is that initiative without policy is terrifying. The fix is structural, not promissory: outbound messages hold for your approval by policy, money moves need dual sign-off (you, then finance), and every act — including the denials — lands in an append-only audit trail. You delegate in one sentence; the system decides what may happen without you.
Try the shape of it
VIVUU's terminal ships with a Founder role pack you can flip on in Settings — the renewal outage, the churn playbooks, the prepared brief, the dual approval — running live on realistic mock data. It is the interface thesis made testable: five minutes in an attention queue explains the job better than any comparison table.
FAQ
- What does an AI chief of staff actually do?
- The job is triage plus preparation: watch the systems a founder cares about (billing, CRM, inbox, product analytics), detect what matters (a webhook outage eating renewals, an account going quiet before churn, a renewal call two days out), do the preparable work (drafts, briefs, recovery runbooks), and present a decision with evidence. The measure of a good one is how few things reach you — and how ready they are when they do.
- How is that different from an AI executive assistant?
- An assistant mostly responds to you: schedule this, draft that, summarize this thread. A chief of staff watches the business and comes to you — unprompted — with 'this needs a decision, here is the work already done, here is the evidence.' The direction of initiative is reversed, which is why a chat window is the wrong shape for it.
- Why not just use ChatGPT or Claude as a chief of staff?
- A chat model only knows what you paste and only acts when you ask. The chief-of-staff job is continuous: signals arrive at 3am, SLAs tick, approvals expire. That takes standing connections to your systems, a policy layer for what may happen without you, and an interface built around a queue of decisions rather than a conversation. The model is the easy part.
- What should it never do without approval?
- Anything external or financial: sending email to customers or investors, touching money (refunds, captures, discounts beyond policy), changing access. A useful default ladder: reads and drafts run free; reversible internal changes run with constraints; external messages and deploys wait for your approval; money movement takes dual approval; security changes are denied outright.
see the whole flow, live
Everything on this page — the queue, the evidence, the hold-to-approve, the audit trail — is working in the VIVUU terminal as an interactive preview on realistic mock data. No sign-up.