Emerging managers and family offices
Family offices and new GPs running single‑LP funds, who want institutional operating cadence (sourcing memory, diligence support, LP correspondence) without standing up a back office.
Made in SF · © 2026 Steward
By invitation
A private operating layer for small firms that need to move like much larger ones. Operated quietly on client-owned hardware. By invitation.
Mac mini or Mac Studio where appropriate. Read-only by default. Write access by principal consent. Everything logged. Your data stays in your tenancy.
I
A small number of firms whose work compounds, and who would rather own an operating layer than rent a dozen tools.
Family offices and new GPs running single‑LP funds, who want institutional operating cadence (sourcing memory, diligence support, LP correspondence) without standing up a back office.
Strategic and corporate investors who want deal intelligence and thesis tracking on the surface area they care about, written back in plain prose.
Operators who would otherwise assemble a patchwork of fractional roles and point‑tools, and want one compounding team instead: finance, operations, and the glue between them.
II
Venture funds are paid to recognize innovation, but most still run on old rules of thumb, human handoffs, and expensive repetition. Steward is built from the opposite premise: if you expect founders to use automation, your own investment practice should speak that language too.
A family office, single‑LP fund, or new GP should not need a full back office to keep pace. Steward gives the principal a coordinated agent desk so the firm can cover more surface area without pretending headcount is strategy.
General models will converge. The advantage moves to private context: the firm's relationships, inbox, documents, decisions, portfolio history, and operating cadence. Steward earns that memory carefully, one permission at a time.
The old pattern is waiting days for a lawyer, accountant, analyst, or consultant to return a draft. Steward starts with the draft, the tie-out, the brief, or the ticket, then asks the principal what deserves more agency.
III
Steward is not a login to someone else's workflow. The operating base is a machine the firm owns, usually a Mac mini or Mac Studio, configured for the firm's own models, tools, documents, and access rules.
Client names, memos, ledgers, board materials, and meeting history should not become training exhaust for a vendor. Steward keeps sensitive context inside the firm's own environment unless the principal chooses otherwise.
Cloud models are still useful for selected work. They should not be the only way the firm thinks, remembers, or operates. Steward gives the firm a private baseline that keeps working when rate limits, policy changes, or invoices get in the way.
The hardware matters because it anchors control. The product is the configured agent desk around it: permissions, memory, review gates, artifacts, and the working cadence of a real firm.
IV
Steward does not begin by pretending autonomy is trust. The early agent should feel like a very sharp second-year analyst: useful, fast, and supervised.
The first job is to understand the firm: documents, deal history, calendar context, inbox patterns, portfolio facts, and recurring obligations. Read access comes before write access.
Agents prepare the email, memo, ticket, analysis, or briefing. The human reviews, edits, and sends. The loop builds trust without letting the system run ahead of the principal.
Only after the work is predictable does Steward receive more degrees of freedom. Each new permission is explicit, logged, and reversible.
V
Steward is organized around roles because roles are how firms already reason about work. Each role is a set of loops, with goals, review gates, and artifacts that roll up to the principal.
A lead agent routes the work, keeps the memory straight, and decides which specialist should act. The principal sees the result, not the machinery.
Finance, diligence, relationships, portfolio support, sales, tax, compliance, and operations can each become narrower agents with sharper context and clearer boundaries.
The work can show up where the firm already lives: email, WhatsApp, Telegram, Line, Linear, or a private Studio page. The interface follows the firm, not the other way around.
VI
Agents that hold the long memory of who you know, what you owe them, and what they owe you. Briefings before meetings. Correspondence in your voice. The small obligations a serious practice generates each week, routed without theater.
Agents that scan the surface area you care about and write back in plain prose. Daily orientation. Weekly synthesis. A read on the names and filings that move your thesis. Short, sourced, quiet enough to read on a phone before the day starts.
Agents that handle the boring side of a small firm: inbox triage, calendar logistics, document handling, vendor follow‑up, the small accounting glue between systems.
In an engagement these become working artifacts, not slideware: term‑sheet and cap‑table math, unit economics, fund‑return models, deal briefs. Produced in your tenancy and delivered privately.
VII
By invitation. We work with a small number of firms at a time. Each engagement is bespoke.
Engagements begin in the low five figures monthly.
The product is in beta. Each engagement begins with a private dispatch: a short note about the firm, read by Casper, answered within two business days with a private link or a polite no.