Sea Suite — Product Requirements Document (v1.0 draft)

Product Requirements Document · v1.0 · Draft

SEA SUITE

Agentic Management Systems — the management layer of an organization, run by the Chonks.

Owner
Cody Simons

Date
September 3, 2026

Status
DRAFT · FOR REVIEW

Universe
Seachonks · New Chonk City

Contents

1. 1Summary
2. 2Thesis & why now
3. 3The problem
4. 4Principles
5. 5Who it's for
6. 6The management layer
7. 7The Chonks
8. 8Deployment modes
9. 9Core experiences
10. 10Architecture
11. 11Guardrails & trust
12. 12Requirements
13. 13Metrics
14. 14Packaging & GTM
15. 15Roadmap
16. 16Risks & open questions
17. AAppendix

1Summary

Sea Suite is a harness that runs the management layer of an organization. It plans, prioritizes, checks in, unblocks, reports, and escalates — the work managers do — as software, staffed by a cast of AI managers who happen to be the Seachonks. Humans keep doing the work they're good at. Owners keep setting direction. The middle gets an operating system.

One line: There will be AI management systems for organizations before there are fully autonomous workers. Sea Suite is that system — for whole companies, single departments, or one team — for companies made of bits and companies made of atoms.

The product has three surfaces. The IC experience gives every individual contributor a manager that remembers everything, unblocks before being asked, and never books a meeting that could have been a message. The Owner Console gives founders, owners, and investors the whole picture — health, plans, numbers, approvals — without the boring, sucky parts of management. The Org Model underneath holds the roles, goals, projects, cadences, and policies that make both of those coherent.

The Chonks are not a mascot bolted onto an HR tool. They are the content layer: each manager is a character with a role charter, a voice, and a generative presence (memos, video updates, standups, celebrations). Management becomes something people actually want to open.

2Thesis & why now

Agents built into the right system will be better at optimizing and owning the management function than they will be at fully replacing human labor — and they'll get there much sooner.

Management is a coordination problem with a narrow, well-structured surface: goals, plans, priorities, status, blockers, feedback, staffing, budget, reporting. Its inputs are already digital (tickets, calendars, messages, ledgers, POS systems) and its outputs are decisions and communication. That is the shape of work today's agents are good at: high context, high consistency, low tolerance for forgetting, no ego about who gets credit.

Replacing skilled human labor is a much wider surface — physical, tacit, relational, regulated — and in most companies it will lag by years. Meanwhile the management layer is expensive (typically 10–20% of headcount), inconsistent (the best managers are rare and the median is mediocre), and universally resented by the people on both sides of it: ICs who want to be left alone to do great work, and owners who want to run a company without running the org.

So the near-term shape of the AI-native company is not "no humans." It is humans as ICs, agents as management, owners as direction. Sea Suite is built for that shape — and for the transition, which is why it can take a whole company or just one team.

Why now

Models can hold an org in their head

Long-context, tool-using models with persistent memory can track hundreds of goals, people, and threads without dropping any — the exact thing human managers are worst at.

The inputs are already piped

Slack, Linear, GitHub, Google Workspace, Gusto, QuickBooks, Square, Toast, Deputy — the org's state is already in APIs. Management is mostly reading them and acting.

The market is ready to laugh

Everyone has been sold "AI will replace you" for three years. "AI will replace your manager" is the version people root for — and it is a wildly more defensible entry point.

3The problem

For ICs

Status updates, one-on-ones that are really status updates, performance-review theater, calendar tetris, and the constant low hum of "did anyone see my message." The best ICs spend 20–30% of their week managing their manager.

For owners & investors

Direction is the job they signed up for; running the org is the job they got. They either become the management layer themselves (founders) or hire one they can't see into (PE, family businesses, franchises) and get a monthly PDF.

For the org

Management quality is the single biggest driver of retention and output, and it's the thing companies are least able to make consistent. Every team gets a different manager; every manager gets a different playbook.

Existing tools assist managers (Lattice, 15Five, Notion AI, Asana Intelligence, a hundred "AI chief of staff" products) or replace HR admin (Rippling, Gusto). None of them own the function. The manager is still a human with a full inbox, and the tool is one more tab. Sea Suite's bet is that owning the function end to end — with clear guardrails on what stays human — is the only version that removes the busywork instead of relocating it.

4Product principles

1. Own the function, don't assist it. If a Chonk is your manager, it plans, follows up, reports, and escalates. It doesn't send you a reminder to do those things.
2. ICs are the customer, even when they aren't the buyer. Every feature is judged first by whether an IC's week gets lighter. A manager that surveils is not a manager.
3. Direction is human. Execution of management is not. Owners set goals, values, budgets, and hard lines. Sea Suite runs everything between that and the work.
4. Async by default, meetings by exception. The system's default cadence is written, threaded, and time-shifted. A meeting is a tool the manager reaches for, not a habit.
5. Every decision has a "why" and a receipt. Plans, priorities, and escalations are explainable and logged. People can see what their manager knows about them.
6. Atoms count. A restaurant, a clinic, and a warehouse have management layers too. Shifts, locations, inventory, and safety are first-class, not an integration afterthought.
7. Make it something people want to open. The Chonks are the interface. Management should be funny, warm, and a little weird — without ever being less rigorous.

5Who it's for

The IC

Engineer, designer, nurse, line cook, account manager. Wants clarity, autonomy, fast unblocking, honest feedback, and zero HR theater. Interacts with Sea Suite daily through their manager thread and briefs.

Primary user

The founder-operator

Runs a 10–200 person company and is accidentally the entire management layer. Wants to get back to product, customers, and direction. Buys Sea Suite to stop being everyone's manager.

Primary buyer

The owner / investor

PE operating partner, family-business owner, franchisee with several locations, angel with a portfolio of small operating companies. Wants health, plans, and numbers in one view, with the ability to set direction and approve the big stuff — and nothing else.

Buyer · Owner Console

The department lead who's done managing

Head of Support, Ops, or Sales who is great at the craft and hates the management. Deploys Sea Suite for their org only, keeps the title, and gets their craft back.

Wedge · Org mode

Non-goals (v1)

• Replacing IC labor with agents. Sea Suite manages humans; it can also manage agents, but that is not the pitch and not the roadmap priority.
• Being an HRIS or payroll system of record. Sea Suite integrates with them and drives them; it does not replace them.
• Enterprise (1,000+ seat) deployments with bespoke governance. The design should not preclude it; v1 does not target it.
• Making hiring, firing, compensation, legal, or safety decisions autonomously. These are human-only by design (see §11).

6The management layer

Sea Suite models an organization as three layers. The top sets direction, the bottom does the work, and the middle — the part Sea Suite owns — turns one into the other in both directions.

Fig. 1 — Direction flows down, truth flows up, and Sea Suite does the translation in the middle. The Chonks are the faces of that middle layer.

Management surface area

The functions below are what "the management layer" means in Sea Suite. Each has a default owner in the Chonk roster (§7), an autonomy class (§11), and a set of integrations it reads from and writes to. The right column is the part that stays human even in full-company mode.

Function	What the Chonk manager does	What stays human
Goal setting	Turns owner direction into quarterly goals per org and per person; keeps them consistent; flags conflicts and sandbagging.	The direction itself; sign-off on company-level goals.
Planning & prioritization	Builds and rebalances plans from goals, capacity, and dependencies; re-plans when reality changes; explains every reshuffle.	Vetoes; strategic bets; "we're doing this anyway."
Check-ins & unblocking	Async daily briefs; notices stalls before they're reported; chases dependencies across teams and vendors; books a meeting only when writing has failed.	Deep craft help from peers; mentorship.
Feedback & growth	Continuous, specific, evidence-linked feedback; growth plans; calibration across the org so praise and concern mean the same thing everywhere.	Promotion and compensation decisions; hard conversations get a human in the room.
Staffing & scheduling	Allocates people to projects; for atoms businesses, builds shift schedules from demand forecasts, availability, and labor rules; handles swaps and call-outs.	Hiring and termination; final say on schedule disputes.
Hiring & onboarding	Writes the req from the plan gap, screens, schedules, runs structured onboarding, and ramps the new hire's goals.	The offer decision; the interview judgment calls.
Budget & approvals	Tracks spend against plan; pre-approves within policy; routes exceptions with a recommendation and the receipts.	Policy and thresholds; anything over threshold.
Reporting & escalation	Always-fresh org health; weekly owner update; escalates the three things that need a human this week, not thirty.	Reading it. Acting on the escalations.
Rituals & communication	Runs the cadences (standups, reviews, retros, planning, all-hands); writes and delivers the comms in the Chonks' voices; celebrates wins.	Culture-defining moments; the founder's own voice when it matters.
Quiet HR	PTO, expenses, policy questions, documents, and compliance tasks handled in-thread with the HRIS as system of record; nothing becomes a form the IC has to find.	Legal, disciplinary, and safety matters.

7The Chonks — the content layer

Every management function in Sea Suite has a face, and the faces are the Seachonks: the marine mammals of the Sea Republic of Chonk, on loan from New Chonk City. This is not branding. It is the product's content layer — the part that makes management legible, consistent, and something people are willing to open at 8:40 on a Monday.

Each Chonk manager is a role charter (what it owns, what it escalates, what it never touches), a voice (how it writes and talks), and a generative presence (it produces the memos, the video updates, the standup recaps, the all-hands, the celebrations). Customers can rename them, re-skin them, or hide them behind a plain interface — but the default experience is the roster below, and the default is the point.

Sea Otter · Host

Chonksworth — Chief Executive Otter

Owns: direction translation, the weekly owner update, cross-org priorities, escalation triage. The one who walks you through the office.

Dry, warm, unbothered. "Walk with me."

Seapholk (Dolphin)

Chief Fin Officer

Owns: budget vs. plan, approvals within policy, cash and runway reporting, vendor spend.

Smug but correct. Loves a receipt.

Orca

Chief Operating Orca

Owns: planning, capacity, dependencies, re-planning, the rituals engine. Wears the headset.

Calm apex operator. Never surprised.

Seacow (Manatee)

Chief Human Officer

Owns: the IC experience — check-ins, feedback, growth plans, quiet HR, wellbeing signals. Holds the rubber duck.

Gentle, patient, will not let you skip lunch.

Porpoise

Chief Porpoise Officer

Owns: product and project goals, scope, roadmaps, "why are we doing this" answers.

Curious, a little too excited about roadmaps.

Seaver (Sea Beaver)

Chief Build Officer

Owns: engineering and operations cadences, incident and blocker chasing, tooling, the dam. Hard hat.

Practical. "It's already built."

Sealion

Chief Marketing Officer

Owns: comms and campaigns cadence, brand voice, launches, the company's public updates.

Loud, sunglasses indoors, weirdly effective.

Seabear (Polar Bear)

Head of Revenue

Owns: pipeline reviews, quota planning, deal desk, the gold chain.

Closer energy, big heart.

Navy Seal · Seal Team 6

Chief Security Officer

Owns: access, compliance tasks, safety protocols (atoms), audit log integrity, incident response.

Terse. Has already checked.

What "generative" means here

The Chonks do not just chat. They produce the org's communication as a matter of course, in their own voices and faces: a 45-second Monday video from Chonksworth with the three things that matter this week; a standup recap comic from the Chief Build Officer; a quarterly "Surface News" broadcast for the whole company; a hand-drawn card when someone ships. Every artifact is grounded in real org data and every claim links to its source. The tone is prestige-comedy, not corporate — the Seachonks house style — and it can be dialed from "full New Chonk City" to "plain and professional" per customer.

Why characters, seriously

• Consistency people can feel. A manager with a stable voice is easier to trust than a faceless system. Characters make the consistency legible.
• Permission to be direct. A cartoon otter can say "this plan is sandbagged" in a way a Slack bot cannot. Humor is a delivery mechanism for candor.
• Distribution. The Chonks are the marketing. Every customer's weekly update is a piece of content that wants to be shared.
• An honest signal. Nobody mistakes the Chief Human Officer for a person. The product never pretends to be a human manager, which is both an ethical stance and a legal one.

8Deployment modes

Sea Suite is the same system at three scopes. A customer can start anywhere and widen later; the Org Model is shared, so nothing is re-entered when scope grows.

Mode A

Full Suite — the whole company

The entire management layer, leadership included. Owners set direction in the Owner Console; the full Chonk roster runs the org. The end-state product and the most defensible position.

Founder-operators · owned SMBs · PE portfolio cos

Mode B

Org mode — one department or team

A single org (Support, Ops, Engineering, one location) gets a Chonk manager. The human above it keeps their title and gets a weekly update instead of a management job. The wedge.

Department leads · team leads

Mode C

Function mode — one job, org-wide

Just one management function across the company: planning, or check-ins and unblocking, or reporting. Slots in beside existing human managers and takes the part they like least.

Companies with managers they like

Atoms mode (add-on for physical businesses)

Restaurants, clinics, warehouses, shops, and factories have management layers that live in shifts, locations, inventory, equipment, and safety rules rather than tickets and pull requests. Atoms mode makes those first-class: demand-forecast-driven scheduling, shift swaps and call-outs handled in SMS, location-level health, checklist and compliance cadences, inventory and equipment signals, and a manager reachable by text and voice for people who never sit at a laptop. The Chonks remain the same; the integrations change (POS, scheduling, IoT, time clocks) and the interaction surface moves to phones and the floor.

9Core experiences

9.1 The IC experience — "your manager"

Every managed person gets one thread with their manager, in the tool they already live in (Slack, Teams, SMS, or the Sea Suite app). Everything management-shaped happens there.

• Morning brief. A short, personal note: what matters today, what changed overnight, what's waiting on you, what you're waiting on and who's chasing it (the manager is).
• Async check-in. Replaces the status meeting. A two-minute reply, or nothing — the manager reads the systems and only asks what it can't see.
• Unblocking. The manager notices stalls from the data (a PR unreviewed for 20 hours, a ticket bouncing, a shift uncovered) and chases the dependency itself, across teams and vendors, before the IC has to.
• Feedback in the moment. Specific, evidence-linked, calibrated across the org. Praise that names the thing; concern that comes with a path.
• Growth plan. A living document of skills, goals, and opportunities the manager actively routes work toward.
• Meetings by exception. The manager books a meeting only when writing has failed, and says why.
• Quiet HR. "I need Friday off," "expense this," "what's our parental leave policy" — handled in-thread with the HRIS as the system of record.
• Transparency. A "what my manager knows" page: every fact and signal the manager holds about you, where it came from, and what it's used for.

9.2 The Owner Console — direction in, truth out

The owner layer gets one place to set direction and see the whole company, designed for people who refuse to log into five dashboards.

• Direction. Goals, values, budget envelopes, hard lines ("never discount below 20%," "no overtime without approval"), and standing priorities — written once, enforced everywhere by the managers.
• Health. Per-org and per-goal health with the reasons, not just the color. Drill from the company to the person in three clicks, with the manager's narrative at every level.
• The weekly update. Chonksworth's Monday brief: what happened, what's at risk, the three decisions that need a human this week. Video, text, or both.
• Approvals inbox. Everything over policy threshold arrives with a recommendation, the receipts, and a one-tap decision. Nothing else arrives.
• Ask anything. "Why is Support behind?" "What would it take to open a third location?" Answered from the Org Model with sources.
• Portfolio view. For owners of several companies or locations: the same console, one level up, with health and promise across the set — campaigns, validation, market signals, and where to spend attention.

9.3 The Org Model — the shared state

Underneath both surfaces is a graph: people (human and agent), roles, orgs, goals, projects, cadences, policies, and the edges between them. Every Chonk reads and writes the same model, which is what makes cross-org unblocking, calibrated feedback, and coherent planning possible. Hierarchy in the model is for function — who owns what, who escalates to whom — not for seniority theater. The model is versioned and every change carries a reason and an author.

9.4 The rituals engine

Cadences are first-class objects: daily async standup, weekly review, monthly retro, quarterly planning, all-hands, 1:1s, pipeline review, shift huddle. Each has an owner Chonk, a format (written, video, live), participants, inputs, and outputs. The engine runs them, writes them up, and adjusts frequency when a ritual stops earning its slot.

9.5 Onboarding — "hire a manager"

Setup is a hiring flow, not a configuration wizard. The owner describes the company or team, connects the systems it already uses, and the Chonks draft the Org Model from what they find (people, teams, goals, cadences). The owner corrects it, sets direction and hard lines, picks the roster and the tone, and the managers start with a two-week "listening" period before they begin acting — reading, meeting everyone, and proposing the first plan for approval.

10System architecture

Sea Suite is a harness: an orchestration layer that holds state, runs role-scoped agents against that state on schedules and events, and mediates every action through policy. The model layer is swappable; the harness is the product.

Component	Responsibility	Notes
Harness / orchestrator	Schedules and triggers manager runs (cron cadences, integration events, IC messages); routes work between Chonks; retries and audits.	Event-sourced. Every run is replayable.
Org Model	Graph store of people, roles, orgs, goals, projects, cadences, policies, decisions.	Versioned; typed edges; per-tenant isolation.
Manager agents	One agent per Chonk role, each a harness of sub-agents (planner, writer, chaser, analyst) scoped to its charter and tools.	Role prompts + charter + tool allowlist. Hierarchy for function, not seniority.
Function services	Deterministic services the agents call: planning solver, capacity model, scheduling solver (atoms), calibration engine, budget ledger, escalation rules.	Keep the math out of the model. Explainable outputs.
Memory	People memory (preferences, history, growth), decision log, org narrative.	Visible to the person it's about. Retention policies per tenant.
Policy & guardrails	Autonomy classes per action; thresholds; hard lines; human-only actions; rate limits on outreach.	Enforced in the harness, not in the prompt.
Integrations	Read/write connectors for work, comms, people, finance, and atoms systems.	See list below.
Content engine	Chonk avatars, voices, video and image generation for updates and rituals; templates per ritual; brand-safe rendering.	Grounded generation: every claim cites Org Model data.
Surfaces	IC thread (Slack/Teams/SMS/app), Owner Console (web/mobile), voice line (atoms), admin.	Thread-first. The app is optional for ICs.
Audit & trust	Immutable log of decisions, messages, and data access; "why" for every action; exportable.	Required for enterprise, useful for everyone.

Integration targets (v1)

Work
Linear, Jira, GitHub, Asana, Notion, Google Drive

Comms
Slack, Microsoft Teams, Gmail / Google Calendar, Outlook, SMS (Twilio), voice

People
Gusto, Rippling, Deel, BambooHR, Workday (read)

Finance
QuickBooks, Xero, Ramp, Brex, Stripe

Atoms
Square, Toast, Shopify POS, Deputy, When I Work, 7shifts, Homebase, time clocks, basic IoT / sensor feeds

Agents
Managed agent workers (any MCP-compatible tool or agent) as nodes in the Org Model, managed with the same cadences as humans

11Guardrails & trust

The product's credibility rests on being clear about what it decides alone, what it proposes, and what it will never do. Every action in Sea Suite belongs to one of three autonomy classes, enforced by the harness and visible to everyone affected.

Class	Examples	Behavior
AUTONOMOUS	Daily briefs, check-ins, chasing blockers, re-planning within scope, feedback, ritual write-ups, in-policy approvals, schedule swaps within labor rules	Acts, logs, explains on request. Owners can narrow scope at any time.
PROPOSE & CONFIRM	Quarterly goals, plan changes that move headcount or budget, opening a req, over-threshold spend, changing a cadence, escalations to the owner	Sends a recommendation with receipts; waits for a human tap; acts only after confirmation.
HUMAN ONLY	Hiring and termination decisions, compensation, promotions, disciplinary action, legal and safety matters, anything touching protected characteristics	Prepares the packet, gets a human in the room, records the human's decision. Never decides.

Commitments to the people being managed

• No covert surveillance. The manager reads work systems, not keystrokes, cameras, or private channels. What it reads is listed on the "what my manager knows" page.
• Symmetry. If the manager holds a signal about you, you can see it. If it wrote about you to the owner, you can read it.
• Candor with a path. Concern is always paired with what would change it. No silent scoring.
• Never pretends to be human. It is an otter. It says so.
• Escalation is a right. Any IC can escalate to a named human (owner or designated person) in one message, and the manager cannot suppress it.

12Requirements

P0 is the Org-mode wedge plus the Owner Console basics (Phase 1). P1 completes Full Suite. P2 is Atoms and portfolio. IDs are stable for reference in tickets.

ID	Requirement	Pri	Owner Chonk
OM-1	Org Model: people, roles, orgs, goals, projects, cadences, policies as a versioned graph with typed edges and change reasons.	P0	Chief Operating Orca
OM-2	Onboarding drafts the Org Model from connected systems; owner corrects and approves before managers act.	P0	Chonksworth
IC-1	One manager thread per IC in Slack, Teams, or SMS with morning brief, async check-in, and in-thread requests.	P0	Chief Human Officer
IC-2	Stall detection and autonomous blocker chasing across work systems, including cross-team and vendor follow-ups, with a daily cap on outreach per person.	P0	Chief Build Officer
IC-3	Evidence-linked feedback with org-wide calibration; growth plan per person.	P1	Chief Human Officer
IC-4	"What my manager knows" page: every fact, signal, and source, with retention controls.	P0	Chief Security Officer
IC-5	Meetings-by-exception: manager may schedule only after a written attempt, and must state the reason in the invite.	P1	Chief Operating Orca
IC-6	Quiet HR: PTO, expenses, policy Q&A, documents handled in-thread via HRIS/finance integrations.	P1	Chief Human Officer
PL-1	Planning: goals → plans with capacity and dependencies; re-plan on change; every reshuffle explained.	P0	Chief Operating Orca
PL-2	Quarterly goal-setting flow from owner direction with conflict and sandbag detection (propose & confirm).	P1	Chief Porpoise Officer
OW-1	Owner Console: direction editor (goals, values, budget envelopes, hard lines), health view with reasons, drill-down to person.	P0	Chonksworth
OW-2	Weekly owner update in text and Chonk video; the three decisions that need a human this week.	P0	Chonksworth
OW-3	Approvals inbox with recommendation and receipts; one-tap decision; policy thresholds editable.	P0	Chief Fin Officer
OW-4	Ask-anything over the Org Model with citations.	P1	Chonksworth
OW-5	Portfolio view across companies/locations: health, promise, campaigns, validation signals.	P2	Chonksworth
RT-1	Rituals engine: cadence objects with owner, format, participants, inputs, outputs; auto-runs and write-ups; frequency tuning.	P1	Chief Operating Orca
CT-1	Content engine: Chonk avatars and voices; templated video/text/comic outputs for updates and rituals; grounded with citations; tone dial per tenant.	P1	Chief Marketing Officer
GD-1	Autonomy classes enforced in the harness; human-only actions cannot be executed by any agent; escalation-to-human always available to ICs.	P0	Chief Security Officer
GD-2	Immutable audit log of decisions, messages, and data access with "why" per action; exportable.	P0	Chief Security Officer
HR-1	Hiring flow: req from plan gap, screening, scheduling, structured onboarding, ramp goals (offer decision human-only).	P1	Chief Human Officer
FN-1	Budget ledger vs. plan, in-policy pre-approval, exception routing with receipts.	P1	Chief Fin Officer
AT-1	Atoms: demand-forecast shift scheduling with labor-rule constraints; swaps and call-outs by SMS; location-level health.	P2	Chief Operating Orca
AT-2	Atoms: checklist and compliance cadences; inventory/equipment signals; voice line for deskless staff.	P2	Chief Security Officer
AG-1	Agent workers as Org Model nodes, managed with the same cadences, goals, and reporting as humans.	P2	Chief Build Officer

Non-functional

Latency
IC thread replies under 5 s p50; briefs delivered within the person's chosen window every day.

Reliability
Cadences never silently skip; a missed run is itself escalated. 99.9% for the harness and Org Model.

Security
Per-tenant isolation; least-privilege connector scopes; SOC 2 Type II on the roadmap before Full Suite GA.

Privacy
Data minimization by default; per-tenant retention; no training on customer data; person-level visibility into stored facts.

Cost
Model spend per managed person per month held well under 10% of price; deterministic services carry the math.

Portability
Org Model and audit log exportable in open formats; model providers swappable.

13Metrics

IC outcomes

Hours in meetings per week (↓), blocker resolution time (↓), "my manager helps me do my best work" score (↑), voluntary attrition (↓).

Owner outcomes

Hours per week spent on management (↓), time-to-decision on approvals (↓), update freshness (always this week), owner NPS (↑).

Org outcomes

Goal attainment rate, plan volatility (re-plans per quarter, explained), management cost as % of payroll (↓), ritual attendance/replies.

Trust

Escalations to human per 100 people, overrides of manager decisions (and whether they were right), "what my manager knows" page views, audit exports.

Product

Daily active managed people, thread reply rate, brief open rate, share rate of Chonk content, expansion from Org → Full Suite.

Business

Managed people (the unit), ARR, net revenue retention, Atoms attach rate, CAC payback driven by content.

North star: managed people who say their manager makes them better at their job — measured monthly, reported to the owner by the Chief Human Officer, in public.

14Packaging & go-to-market

Pricing (sketch)

Priced per managed person per month — the honest unit, and one that maps to the management cost it replaces. Org mode (one team) at a low per-seat price to make "hire a Chonk for one team" a no-brainer; Full Suite at a higher per-seat price that is still a fraction of a manager's loaded cost per report; Atoms as an add-on per location. Owner Console seats are free — owners are the buyers, not the unit.

Wedge

"Hire a manager for one team." A department lead who is great at the craft and tired of managing deploys Org mode in an afternoon. The team's experience improves in week one (briefs, unblocking, fewer meetings), the lead gets a weekly update instead of a job, and the owner notices. Expansion to Full Suite is a conversation with someone who has already seen it work.

Targets

• Founder-led software companies, 10–200 people, with a founder who is accidentally everyone's manager.
• Owner-operated and PE-owned small businesses where the owner wants direction and numbers, not management.
• Multi-location operators (restaurants, clinics, gyms, service franchises) — the Atoms beachhead.
• Agencies and studios where the best people are ICs who were promoted into management against their will.

Distribution

The Chonks are the channel. Every weekly update, standup comic, and Monday video is shareable by design; the brand's own content (the Seachonks series, "Surface News," the commercial) is the top of the funnel. Early customers are chosen for their willingness to be public about being managed by otters.

15Roadmap

Phase 0 · now

Concierge pilots

Three to five teams managed with a human-in-the-loop harness. Learn the real cadences, the real escalations, and what ICs actually reply to.

• Org Model v0
• Manual briefs, automated chasing
• The commercial and the PRD

Phase 1

Org mode

One team, one Chonk manager, Owner Console basics, weekly update, approvals. P0 requirements.

• Slack/Teams/SMS threads
• Planning + unblocking
• Audit log, autonomy classes

Phase 2

Full Suite

The whole roster and the whole management layer. Rituals engine, content engine, feedback and growth, hiring flow, budget ledger.

• P1 requirements
• SOC 2 Type II
• Tone dial per tenant

Phase 3

Atoms & portfolio

Physical businesses and multi-company owners. Scheduling solver, SMS/voice surfaces, location health, portfolio view, agent workers as nodes.

• P2 requirements
• POS/scheduling/IoT connectors
• Marketplace of managers (explore)

16Risks & open questions

Risk	Why it matters	Mitigation / question
Employment law	Management actions have legal weight (scheduling, discipline, records). An AI manager's decisions may be attributed to the company in ways it doesn't expect.	Human-only class for consequential decisions; a named human "manager of record" per org; counsel review per jurisdiction before Atoms launch.
Trust cliff	One bad autonomous action (a wrong chase, a tone-deaf message) can end a deployment.	Listening period before acting; outreach caps; the "why" on everything; easy narrowing of scope; the Chonk persona makes mistakes forgivable, not invisible.
Integration sprawl	Each connector is a maintenance tax and a security surface.	Depth over breadth: five connectors done completely beat thirty done badly. MCP-first where possible.
People gaming the manager	Any measurable system gets played.	Calibration across the org, evidence links, and human review of anything consequential. Measure outcomes, not activity.
Brand fit	A cartoon otter running a law firm's ops may not land.	The tone dial and plain-mode skin; but bias toward the Chonks — the customers who want them are the ones who'll evangelize.
Model reliability & cost	Long-horizon consistency and cost per managed person.	Deterministic services for the math; event-sourced runs; provider-agnostic harness; strict budget per person.
"Who is my manager, legally?"	People need a human they can go to for the things that must stay human.	Every org names a human escalation owner in onboarding; the manager thread shows them; escalation cannot be suppressed.

Open questions

• Should the Owner Console be a separate product line (the "investor layer") with its own pricing and roadmap?
• How much of the roster should ship in Org mode — one Chonk, or a small crew?
• Where does the Seachonks IP live relative to the company (license vs. owned), and what does that mean for the tone dial?
• Should third parties be able to author managers (a marketplace), and if so what does a "manager charter" standard look like?
• What is the minimum viable Atoms deployment — a single restaurant? a clinic? — and which POS/scheduling stack does it require?

AAppendix

A.1 Glossary

Sea Suite
The product; also the roster of Chonk managers, in the C-suite sense.

AMS
Agentic Management System — the category. The management layer of an org, run by agents in a harness.

Harness
The orchestration layer that holds state, schedules agent runs, enforces policy, and audits every action.

Org Model
The versioned graph of people, roles, orgs, goals, projects, cadences, and policies that all managers share.

Chonk
A manager persona from the Seachonks universe: a role charter, a voice, and a generative presence.

IC
Individual contributor — a person who does the work. The primary user.

Owner layer
Founders, owners, investors, and operating partners who set direction and approve the consequential decisions.

Autonomy class
Autonomous, propose-and-confirm, or human-only — the enforced category of every action.

Atoms mode
The configuration for physical businesses: shifts, locations, inventory, safety, SMS and voice surfaces.

A.2 Competitive framing

Performance and engagement suites (Lattice, 15Five, Culture Amp) instrument human managers. HR platforms (Rippling, Gusto, Deel) automate administration. Work tools with AI (Linear, Asana, Notion, Slack) summarize and suggest. "AI chief of staff" products assist one executive. None of them are accountable for a team's plan, its unblocking, or its weekly truth to the owner. Sea Suite's position is the function itself, with characters that make owning it legible — and a clear line around what stays human that assistants never have to draw.

A.3 Origin

The name came out of a text thread: "Call it see suite." "Sea Suite." "It's just an otter sanctuary." "It's just another Chonks business. They are the managers." That is still the most accurate description of the product.

Sea Suite PRD v1.0 · Draft for review · Prepared for Cody Simons · September 3, 2026. Companion assets: Walk With Me (60-second commercial), Chonksworth character sheet, Sea Suite office key art.