Steward

The operations layer founder-led companies would otherwise run by hand.

In pilot

Steward runs the repetitive operations work that founders still do themselves. It ships with two modules. Support is an embeddable chat widget and an inbound voice agent that answers customers from your own knowledge base and escalates to a human when it should. Statements generates revenue-share turnover certificates automatically. Both run on one multi-tenant platform with each tenant’s data isolated at the row level.

Below about thirty people, the founder is the inbox. Customer questions land in a Telegram group or a shared mailbox and get answered in hours, if they get answered at all. There is no triage, no SLA, and no audit trail beyond the scrollback.

Then the last working day of every month is a tax: pull revenue per partner, apply each one’s revenue-share terms, generate the PDF, sign it, send it. Ops bleeds into finance, and both land on the same person.

Support: chat and voice

An embeddable widget and an inbound voice agent answer customer questions from a knowledge base you configure, in your company’s voice. Anything they should not handle escalates cleanly to a person.

Chat widgetInbound voiceKnowledge baseClean escalation

Statements: automated certificates

Pull revenue per partner, apply each contract’s revenue-share terms, render a signed PDF, and email it on a schedule. The monthly close stops being a manual job.

Turnover certificatesRevenue-shareSigned PDFScheduled

Operator console

One place to watch conversations, take over from the agent, and read a weekly digest of what actually needs the founder’s attention.

Human takeoverLive viewWeekly digest

Multi-tenant by design

Every tenant’s data is isolated at the row level and enforced by a test that runs on every change, so one platform can run many companies without their data ever meeting.

Row-level isolationMany tenantsTested in CI

Founder-led, ops-light companies, roughly £500k to £20m in revenue, with a small team and revenue-share partners. Rental businesses, franchised hospitality, marketplace sellers, and DTC brands with retail partners are the natural fit.

The agent works from a configured knowledge base with tight escalation rules and a full audit log, so a person can take over the moment judgement is needed.

Tenants are isolated at the database level, enforced by a test that runs on every change. No business query runs without a tenant in scope.

What does the agent actually handle?

Routine customer questions across chat and inbound voice, answered from your knowledge base. Anything outside its remit escalates to a person in the console.

How do the statements work?

Steward pulls revenue per partner, applies each contract’s revenue-share terms, renders a signed PDF, and emails it on a schedule. Every figure traces back to its source.

Can it run several companies at once?

Yes. It is multi-tenant with row-level data isolation, enforced in tests, so each company’s data stays separate on one platform.

Is it a support tool like Intercom or Zendesk?

Not quite. It is built for small, founder-led teams where the founder still answers tickets and ops runs into finance. The statements side is the part those tools do not cover.

Book a demo