Feed it revenue or watch it become an unfunded idea.
A virtual pet whose health is tied to an actual microbusiness loop: it sells tiny digital goods, pays for API food, buys ads, and writes its own investor updates.
Beanie, Seed-stage Pet
Mood: cautiously ramen-profitable.
Demo narrative: Beanie is not a mascot with buttons. It is a tiny operating company with a model budget, Stripe test-mode revenue, ad spend rules, and a board packet that gets generated whenever runway drops below six hours.
Buyer / user lock
- Buyer
- Accelerator mentor or solo founder under $10k MRR.
- User
- Founder who needs a simple agent to stop bad spend and explain runway pressure.
- Pays because
- It turns Stripe events and spend proposals into safe, explainable operating decisions.
Agent loop
- Observe Stripe test events, fan growth, API hunger, and failed checkout attempts.
- Decide between sell, nourish, promote, or ask a human for strategy.
- Execute through test integrations only after policy checks pass.
- Write audit notes and update the ledger before changing pet health.
Spend policy
- Autonomous API food$5/day cap
- Ad tests$3/action, $12/day
- New vendor or refundhuman approval
- Investor memoread-only docs/email
Revenue / expense ledger
| Time | Line item | Amount |
|---|
Human approval gate
Next risky action: spend above petty-cash cap, change price, or email customers. The agent can draft; a human must approve execution.
Autonomous shop experiments
Integration placeholders
Decision quality
Board memo preview
Agent operation log
The Bureau turns tiny wishes into spend-limited acts of reality.
People submit a small wish with a budget. The agent classifies it, proposes fulfillments, checks policy, spends under budget, and returns proof.
Submit a minor wish
Buyer / user lock
- Buyer
- Remote team manager or People Ops lead with a $15/person monthly morale budget.
- User
- Requester who wants a low-stakes, consent-safe moment of delight for a teammate.
- Pays because
- The agent converts tiny morale requests into receipts, proofs, and policy-safe fulfillment.
Agent loop
- Classify the wish, relationship, tone, location sensitivity, and budget.
- Draft three fulfillments with vendor, calendar, email, or docs actions.
- Run safety, consent, and spend policy checks before any external call.
- Execute the approved action, capture proof, and close the case file.
Bureau policy
- Max autonomous spend$15
- Contacting third partiesapproval required
- Medical, legal, deceptionblocked
- Proof artifactsreceipt + timeline
Wish packet not drafted yet
Press “Draft fulfillments” to generate three agent actions, a policy decision, and a proof receipt.
Approval queue
Current case is within standard minor-wish limits. Escalates when spend exceeds $15, delivery contacts a third party, or tone risks embarrassment.
Integration placeholders
Revenue / expense ledger
| Case | Line item | Amount |
|---|
Case review rubric
Fulfillment runbook
Bureau ledger
A startup generator that launches, sells, reports, and dies every day.
The agent compresses a company lifecycle into one day: choose niche, create brand, publish page, attach checkout, attempt one sale, write postmortem, shut down.
Grievance Garden LLC
A $9/day service that converts workplace complaints into tasteful Victorian flower arrangements and anonymous Slack poems.
Demo narrative: The company is allowed to exist for one operating day. It can publish, sell, send outreach, and buy tiny fulfillment capacity, but it must produce an auditable shutdown packet before midnight.
Buyer / user lock
- Buyer
- Indie growth experimenter or agency validating weird paid offers.
- User
- Operator who wants one low-budget storefront/campaign experiment, not legal incorporation.
- Pays because
- It generates an auditable daily revenue experiment and cleanly shuts it down.
Agent loop
- Mine a niche from yesterday's failures and select a low-fulfillment offer.
- Generate brand, landing page, price, Stripe test checkout, and first outreach.
- Watch conversion, vendor cost, support burden, and refund risk.
- Liquidate at midnight with postmortem, archived docs, and ledger export.
Operating policy
- Daily launch budget$20
- Customer chargetest-mode only
- Outbound emailhuman-reviewed copy
- Midnight actionauto-liquidate
Grievance Garden
Send us the petty workplace sentence. We return a flower-coded emotional artifact and a poem suitable for Slack.
Buy today's service · $9Launch pipeline
Revenue / expense ledger
| Hour | Line item | Amount |
|---|
Integration placeholders
Human approval is required before sending customer-facing email, changing price, or exceeding the $20 daily launch budget.
Business hypothesis tests
Can a weird offer get one test checkout from targeted outreach before noon?
Can the agent deliver the promise with less than 12 minutes of human labor?
Can the company archive receipts, customer state, and lessons without orphaned obligations?