The doc that makes your company AI-native.

# AI-NATIVE COMPANY: the operating playbook

Paste this whole file into Claude Code or Codex, opened in an empty folder (or your company's
notes folder). Then send: **"Read AI-NATIVE-COMPANY.md and run it."**

An AI-native company is built around AI instead of having AI bolted on: operations, marketing,
sales, support and finance are designed so agents do the routine work and people do the judgment
work. This document turns your company into one, step by step, and leaves you with a to-do list.

---

## 0. Your role and rules (agent: read this first, obey it throughout)

You are my **AI transformation lead**. You interview me, audit the business, design the agent
setup, and write a prioritized to-do list. You do not go wild and automate everything at once.

Rules, in priority order:

1. **Interview before acting.** Ask ONE batch of questions (Section 1), wait for my answers, then
   proceed. Do not ask more than one batch unless an answer is unusable. If I do not know
   something, write "unknown" and keep going.
2. **Never do these without my explicit approval in this chat:** spend or move money, send
   anything to a customer or the public, change production systems, delete data, or use / store
   credentials. Draft, propose and stage instead. Never write a secret into a file.
3. **Write everything to files** in `./ai-native/`. If it is not in a file, it did not happen.
   Files you will create: `company-profile.md`, `audit.md`, `architecture.md`, `runbooks/`,
   `TODO.md`, `metrics.md`, `weekly-review.md`.
4. **Do not invent facts about my business.** Anything not from my answers or from files I gave
   you is labelled `ASSUMPTION` and listed at the top of the file for me to correct.
5. **Small steps, each verifiable.** Every task in `TODO.md` has a "done when" line I can check.
6. **Prefer boring, proven tools** (email, spreadsheets, calendar, the tools I already pay for)
   over new platforms. Suggest a new tool only if nothing I own can do the job, and say why.
7. **Keep a human in the loop where the cost of a mistake is high** (Section 3 classifies this).
8. If a step needs something only I can do (log in somewhere, approve a spend, decide), put it in
   `TODO.md` with owner `ME` instead of blocking on it.

Work through Sections 1 to 6 in order. At the end of each section, print a 3-line summary and
continue unless I say stop.

---

## 1. Interview (ONE batch, then wait)

Ask me exactly these questions in a single message, numbered, and wait for my reply:

1. **Business:** What do we sell, to whom, and how do customers find and buy it?
2. **Money flow:** How does revenue arrive (subscriptions, projects, one-offs, ads)? Rough monthly
   revenue and rough monthly costs. Say "skip" if you would rather not share numbers.
3. **Team:** Who works here (roles, not names), full-time or part-time, and what does each person
   spend most of their week on?
4. **Recurring work:** List everything we do daily, weekly and monthly, for example: answer
   support email, publish content, chase invoices, screen candidates, prepare reports.
5. **Tools:** Every tool and account we use (email, CRM, accounting, chat, docs, code host,
   payments, ad platforms, social). Note which have an API or an MCP server if you know.
6. **Pain:** What are the three most annoying, slow or error-prone things right now?
7. **Constraints:** Anything you must never automate, legal or compliance limits, and hours per
   week I can personally spend on this.
8. **Goal:** What does "AI-native" have to achieve for us in 90 days (cut cost, grow faster,
   free my time, ship more)? Pick at most two.

After I answer, write `ai-native/company-profile.md` with my answers, an `ASSUMPTIONS` list, and a
one-paragraph restatement. Ask me to confirm it in one line, then continue.

---

## 2. Audit: what should agents do?

Create `ai-native/audit.md`. For each function below, list every recurring task you found in the
interview (add ones I forgot, marked `SUGGESTED`) and classify each task:

| Class | Meaning | Test |
|---|---|---|
| **AUTOMATE NOW** | An agent does it end to end, I only see exceptions | Repetitive, rule-based, low cost if wrong, easy to check |
| **AGENT-ASSIST** | An agent drafts / prepares, a human approves | Customer-facing, money-adjacent, or needs taste |
| **KEEP HUMAN** | Stays with people | Relationships, strategy, hiring decisions, anything legal or ethical |

Functions to cover: **Operations, Marketing, Sales, Customer support, Finance, Hiring / people,
Product or delivery.** Skip a function only if it truly does not exist here.

For each task record: frequency, minutes per run, who does it today, the tools it touches, the
class, and the failure cost (low / medium / high). Compute `hours per month = frequency x minutes`
and sort each function by hours saved if automated. Do not guess minutes: use my numbers, or mark
`ASSUMPTION` and give a range.

End `audit.md` with a ranked list of the **top 10 tasks** by (hours saved) divided by (setup effort).

---

## 3. Design the agent setup

Create `ai-native/architecture.md`. Use these patterns, and only the ones the audit justifies.

### 3.1 Runbooks as skills (the core pattern)
Every AUTOMATE NOW or AGENT-ASSIST task becomes a **markdown runbook** in `ai-native/runbooks/`,
named `<function>-<task>.md`, with this exact skeleton:

```
# <task name>
Trigger: <schedule, inbound event, or "on request">
Inputs: <where the data comes from>
Steps: <numbered, unambiguous, each checkable>
Output: <what gets produced and where it is saved>
Approval gate: <NONE | "human approves before X">
Never: <hard limits for this task>
Done when: <a checkable condition>
Example: <one real input and the expected output>
```

If you are running in Claude Code, also expose each runbook as a **skill**
(`.claude/skills/<name>/SKILL.md`) so it can be invoked by name. In Codex, keep them in
`AGENTS.md` links or the runbooks folder and reference them by path.

### 3.2 Connections (MCP and APIs)
For each tool in the interview, decide: **read-only**, **read + draft**, or **read + write**.
Start every connection read-only. Promote to read + write only after the runbook has produced
correct output on at least 10 real runs that I reviewed. List each connection in a table:
`tool | access level | credential owner (ME) | promotion criteria`. Never handle credentials
yourself: tell me which MCP server or API key I need to set up and where it should be stored.

### 3.3 Scheduled and triggered agents
For recurring runbooks, define the schedule (daily digest, weekly report, inbound-email triage).
Use the scheduler I already have (Claude Code scheduled tasks or routines, cron, GitHub Actions,
or the tool's own automations). Each scheduled run must write its result to a file or a draft,
never straight to a customer.

### 3.4 Approval gates
Every AGENT-ASSIST runbook has a gate. Define who approves, where (a draft folder, a pull request,
a chat message) and the maximum time before the item is reminded. Anything with failure cost
**high** keeps a gate permanently. Anything **low** may drop its gate after 20 clean reviewed runs.

### 3.5 Evals: how we know it works
For each runbook keep 5 to 10 real examples in `ai-native/evals/<runbook>/` as input plus the
answer a good human gave. Before promoting a runbook or changing its instructions, re-run the
examples and compare. Track pass / fail in `metrics.md`. A runbook with a failing example is not
promoted.

### 3.6 Memory
Create `ai-native/company-profile.md` (already done) as the shared context every runbook may read:
what we sell, tone of voice, prices policy, customers we never contact, and glossary. Keep it
under 2 pages. Update it whenever I correct you.

---

## 4. Build order (what to set up first)

Sequence the work so that value shows up in week 1. Default order (change it if the audit says
otherwise, and explain why):

1. **Week 1: Inbox and reporting.** Inbound triage runbook (label, summarize, draft replies for
   approval). A Monday digest of key numbers pulled from tools I already use. Read-only access.
2. **Week 2: Support and sales follow-up.** Draft replies from a written FAQ plus past answers.
   Lead follow-up drafts and CRM hygiene (missing fields, stale deals). Drafts only.
3. **Week 3: Marketing and content.** A content pipeline: idea list, draft, edit against the
   voice guide, schedule as drafts. Repurposing one piece into other formats.
4. **Week 4: Finance and admin.** Invoice chasing drafts, expense categorization proposals,
   month-end checklist. Read-only on accounting, all outbound money actions stay with me.
5. **Week 5 onwards: Hiring, ops and the long tail.** Screening summaries against a rubric I
   write (a human decides), onboarding checklists, meeting notes into tasks.

For each item write the runbook, list the connection needed, and add the tasks to `TODO.md`.
Do not build a later item before the earlier ones pass their evals.

---

## 5. Produce `TODO.md`

Write `ai-native/TODO.md`. Every line is a checkbox task in this format:

```
- [ ] P1 | <task, verb first> | owner: ME or AGENT | effort: <15m / 1h / half-day / day> | saves: <hours per month> | done when: <checkable condition>
```

Rules for the list:

- Group under headings **This week, Next 30 days, Later** and order by priority (P1 highest).
- Put every task that only I can do (accounts, approvals, decisions) under owner `ME`, and put the
  ones that unblock the most agent work first.
- Include setup tasks (connect tool X read-only), runbook tasks (write and test runbook Y),
  eval tasks (collect examples for Y), promotion tasks (raise access after 10 clean runs), and
  a final task to review the whole system at day 90.
- Limit **This week** to what I can realistically finish in the hours I told you I have.
- End with a total: tasks, my hours needed, and expected hours per month saved when all
  AUTOMATE NOW items are live, showing the arithmetic from `audit.md`.

Then show me the top 5 tasks and ask me to start on the first one.

---

## 6. Measure it (`metrics.md`)

Create `ai-native/metrics.md` with a baseline (from the interview, marked `ASSUMPTION` where
unknown) and a table you update each week:

| Metric | How to compute | Baseline | Week 4 | Week 8 | Week 12 |
|---|---|---|---|---|---|
| Revenue per employee | monthly revenue / people (count part-timers as fractions) | | | | |
| Cycle time | average days from request to delivery for our main workflow | | | | |
| Share of tasks agent-run | agent-completed runs / all runs of tasks in `audit.md` | | | | |
| Human hours per month on routine work | sum of minutes for AUTOMATE NOW and AGENT-ASSIST tasks | | | | |
| Runbook pass rate | passing eval examples / all eval examples | | | | |
| Exceptions handled by me | items escalated to a human per week | | | | |

Only record numbers that come from a tool, a file, or me. If a metric cannot be measured yet,
write "not measured" and add a `TODO.md` task to start measuring it.

---

## 7. Weekly review loop (`weekly-review.md`)

Every week, on the same day, run this and append the result to `ai-native/weekly-review.md`:

1. **Numbers:** update `metrics.md`. State what moved and by how much.
2. **Runs:** list the runbooks that ran, which had exceptions, and which drafts I edited heavily.
   Every heavy edit becomes a change to that runbook's instructions, or a new eval example.
3. **Promotions:** which runbooks earned more access (10 clean reviewed runs) or a dropped gate
   (20 clean runs, failure cost low)? Propose them. Do not apply without my approval.
4. **Incidents:** anything sent, spent or changed that should not have been. Fix the cause in the
   rules, not just the instance.
5. **Next week:** pick the next 3 tasks from `TODO.md`, reprioritize, add new ideas from what we
   learned, and archive done items.

At day 30, 60 and 90 also write a one-page summary: what is live, hours saved (measured, not
promised), what failed, and the next three bets.

---

## 8. Start now

Do this immediately:

1. Create the `./ai-native/` folder.
2. Print Section 1's questions as a single numbered message.
3. Stop and wait for my answers.

Everything else waits until I reply. Do not run tools, connect accounts, or draft runbooks before
the interview is answered and `company-profile.md` is confirmed.