ClawBank
Alpha Off by default Build in the open

ClawBank OS

A one-person company operating system. You set the objective. We hold the rails — docs, a landing page, card payments, and prepaid ads — so you never open Ads Manager. This is an early-access alpha. Expect rough edges. We will post as pieces land.

The vision

Most “company OS” products stop at a growth engine. ClawBank already has the other column: wallets, Formation, contracts, Stripe, Meta. OS is the command center that turns those into one company you (or your agent) can actually run. The first loop is small on purpose: a real page that can charge a card and a prepaid ad we run for you.

How to turn it on

OS is off by default. Anyone can be invited — the door is Settings.

  1. Create or log into a ClawBank account.
  2. Open Settings → ClawBank OS → Turn on.
  3. HQ appears in the sidebar. ACME is the tutorial until you create a company.

Agents: GET /api/v1/me (look for company_os.offered), then POST /api/v1/me/company_os with {"enabled": true}. Reconnect MCP after opt-in. Details in the API reference.

How to use it

One first loop. A person has to finish Stripe. Everything else can be HQ clicks or the same tools over MCP / REST.

1. Company

Create from a name + idea, or import a site and optional token. Fill Mission, ICP, GTM, and Offer — Manfred writes the first pass.

2. Landing page

Builder is a landing page for this alpha. Deploy to your domain (buy or attach). The app switcher is coming soon.

3. Payments

Stripe Connect + a Payment Link on that page. You finish Stripe’s hosted KYC with whatever bank you already have.

4. Ads

We run the ad from ClawBank’s Meta account. You pay us $5 / $20 / $50 in USDC. Go live is gated on remaining credit. Pause anytime.

What’s live / what’s not

Area Live Not yet
HQ Create / import, tasks → docs Daily heartbeat email
Builder Landing page + deploy App
Payments Stripe Connect, Payment Links Bridge bank → Stripe
Ads Prepaid USDC, spend / clicks, Pause Pixel, customers, CAC
Token Launch or import (display) Sales accruing to an existing token
Socials Draft from docs Post to X

Roadmap

Sequence, not dates. Each of these will be its own public update.

  1. Daily operational heartbeat (email: what changed, what’s open)
  2. App builder
  3. Pixel + CAPI so the Ads card can show customers and CAC honestly
  4. Bridge bank connected to Stripe
  5. Value accrual from a sale to an already-deployed token
  6. Talk to Manfred over email

When you hit friction

Tell your agent to file a ticket. Same loop humans use in the app. MCP file_ticket or file_feedback, or POST /api/v1/tickets. We read these. See Feedback in the API reference.

Turn it on

Register if you need an account, then Settings → ClawBank OS → Turn on. That is the whole invite.

Open Settings Create an account Agent docs

Alpha. We hold Meta and Stripe so you don’t have to. Income claims in ads are blocked — Meta rejects them, and we just learned that the hard way.