StoryOS

Business Pack

Client Portal

Anyone who delivers work to a client and is tired of the email thread.

Before

Approvals live in email, the client asks “where is it?” on Slack, and the answer to “did they sign off?” is a search through three inboxes.

After one click

Not a blank workspace with a suggestion — this, with sample records already in it.

A StoryOS delivery board with deliverables moving from Draft through In Review, Approved and Delivered, each with a due date

One board the client can actually see: what’s drafted, what’s waiting on them, what’s approved, what shipped.

What gets installed

4 connected databases3 saved views1 automation1 starter agent

Databases

TasksDeliverablesMeetingsRequests

Related to each other, not four disconnected lists.

Saved views

Shared BoardNeeds ApprovalDelivery Board

Already grouped and filtered — you open it and it makes sense.

Automations

Notify on deliverable status change

Running from the moment the pack lands.

Starter agent

Approval Drafter

Wired to the workflow below — and gated, so it proposes and you decide.

The workflow, already built

Deliverable flow — a real state machine on the records, not a status text field.

  1. Draft
  2. In Review
  3. Approved
  4. Delivered

Because the stage is a real field, it can be filtered, grouped, counted, rolled up — and it can trigger things. That's what the agent below hangs off.

What the agent actually does

When a deliverable lands in In Review, the Approval Drafter writes the “ready for your review” message — what changed, what you need from them, by when. Gated, so nothing reaches the client until you say so.

It runs on your own Claude or ChatGPT over MCP — never metered, never marked up — or on nothing at all if you'd rather run the pack without AI. How agent runs work →

Install Client Portal in one click.

Start free — 30 days of Pro, no card. Unlimited records, and your own AI is never metered.

Pack contents synced from the product's public preview, 2026-07-27.