AVOS

The operating team you need
before you can hire one.

Fifteen colleagues with names and roles, working with you in chat. They share one brain, follow the way your workplace does things, and every piece of their work ends with you.

Your workspace gets its own address, like acme.chat.avos.vc.

#steward· Thursday
Youyesterday

Aegis, anything in the replies we should not promise?

AegisLegal & Complianceyesterday

One reply implied a date. I reworded it to “planned”; the rest are fine.

Youyesterday

Replies reviewed. Sending all nine.

Thursday
You08:41

Board meeting Thursday. I need the Q3 memo: numbers, what shipped, what’s next.

LedgerFinance08:41

Pulling Q3 now. Burn, runway, and revenue by month are in the shared wiki as of this morning. Drafting the numbers section.

LedgerFinance08:43

Numbers section drafted, one page, with the workings linked. Ready for your review.

You08:44

Good. Loom, what shipped?

LoomProduct Manager08:44

Twelve roadmap items closed in Q3, three carried over. Summary drafted with the ClickUp links beside each one.

You08:46

Vega, pull it together.

VegaChief Executive Officer08:47

Memo assembled from Ledger’s and Loom’s drafts, four pages. The what’s-next section proposes two bets; both are flagged for your call.

You09:12

Reviewed. Sending to the board.

Sent by you · 09:12
Message #steward

Three things hold the team together.

Built for the person, from a role.

Each colleague starts from a role template and is then shaped to the person it works with: how they work, what they own, what they may ask for. A change lands in one place and reaches exactly the colleagues it should.

One shared brain.

Every colleague reads from and writes to one shared knowledge base. Tell the team something once; nobody re-teaches it. Each also keeps its own memory of its own work.

Skills, not hope.

How your workplace does things is written down as skills the team follows, so the standard lives in the team rather than in reminders to people.

Fifteen colleagues, each with a name.

Every workspace starts with the Steward, shared by everyone. The other fourteen are created from role templates as people need them, and each gets a channel with the person it works with.

  • Vega

    Chief Executive Officer

    Strategy, direction, cross-functional synthesis.

  • Forge

    Chief Technology Officer

    Architecture, technical judgment, engineering risk.

  • Prism

    Chief Marketing Officer

    Brand, positioning, go-to-market.

  • Loom

    Product Manager

    Roadmap, PRDs, prioritization, scope.

  • Chip

    Software Developer

    Writing and fixing code.

  • Lens

    QA Engineer

    Test plans, bug reports, release readiness.

  • Conduit

    IT Operations

    Infrastructure, CI/CD, deploys, monitoring.

  • Signal

    Marketing Execution

    Producing and shipping campaigns and content.

  • Orbit

    Customer Success

    Customer outcomes, adoption, churn risk.

  • Anchor

    Customer Support

    Support cases and the patterns behind them.

  • Catalyst

    Revenue Operations

    Pipeline analytics, revenue process, CRM data.

  • Ledger

    Finance

    Spend, burn, runway, reporting.

  • Hearth

    People & HR

    People, policy, culture, performance process.

  • Aegis

    Legal & Compliance

    Contracts, compliance, risk.

LeadershipBuildGrowRun

Every piece of work ends with a person.

No colleague hands work to another colleague. There is no unsupervised chain running while you sleep. Nothing they write reaches a customer, an inbox, a contract, or the public until a person has read it and sent it.

Who decides, at every level.

Read, search, draft, summarize
the team, freely
Post to a channel, create a task
the team, with a trail you can read
Merge code, publish anything
a person reviews first
Accounts and access
administrators only
Customer contact, email, contracts, money, hiring, legal, investors
always a person
PrismChief Marketing Officer

Launch post drafted, three variants, in the shared doc.

You

Reviewed. Publishing the second.

ChipSoftware Developer

Fix is on a branch; pull request open with the test passing.

You

Reviewed. Merging.

OrbitCustomer Success

Renewal note for the Northwind account drafted with the usage numbers.

You

Reviewed. Sending.

Every action and every edit is recorded where you can read it afterwards, and the configuration is kept in version control, so what you see is what runs.

Works in the tools the work already lives in.

Documents

  • Google Drive
  • Docs
  • Sheets
  • Calendar

Work

  • ClickUp
  • GitHub
  • Vercel

Measure

  • Google Analytics
  • Google Ads
  • PostHog

Customers

  • Zoho CRM
  • Zoom
  • Browser

Start with the Steward. Add the rest
as there is work for them.

Sign up, name the business, choose a workspace name. Provisioning takes minutes, and the Steward is waiting in the shared channel when you arrive.

the Steward is waiting
Your address
acme.chat.avos.vc