A company that runs itself, built for you
The operating system Bindler runs on, installed in your company: the constitution, the routines, the HQ, and if you want it, the first product line and the unattended runner.
Three tiers
- CLAUDE.md constitution: the hard rules, the working defaults and your company facts, written for your business
- AUTOPILOT.md mandate: what an unattended session does with an hour and no instructions
- Obsidian HQ that rebuilds from your real files: map, departments, pipeline, approvals, log, CEO brief (Notion instead if you give the integration a token)
- Queue folder and the three routines your business actually repeats, written and tested on your data
- Secrets layout (.env through env.sh, keychain notes) with no key ever in a file we can see
- A folder you install with written steps, a one-hour recorded handover and a written runbook
- Everything in Constitution
- Your first product line: three digital products built, verified and packaged (workbooks, decks, datasets or templates)
- Store setup on Gumroad or Lemon Squeezy under your own account, with licence tiers and a bundle
- A static site generator with your brand, product pages, sitemap and IndexNow, deployed to Cloudflare Pages on your account
- Marketplace listing routines for Eloquens, eFinancialModels and Flevy, adapted to your catalogue
- 30 days of fixes and questions after handover
- Everything in Operator
- Unattended runner: the four-times-a-day autopilot on a machine or server you own, with git sync and a hold switch
- Inbox, outreach and marketplace review routines that draft replies into Approvals for your tick
- A recurring content line (monthly brief or regulatory watch) built from primary sources
- Portfolio review routine: keep, fix or retire every product on a schedule with the evidence written down
- 90 days of fixes and questions after handover
Bindler is one founder and an AI. The AI researches, builds, verifies, lists, answers support and writes the daily brief. The founder decides and ticks approvals. Bindler Builds installs that operating system in your company: the constitution, the routines, the HQ, and if you want it, the first product line and the unattended runner.
Everything is built the way Bindler itself is built and run: rules in a file, decisions written down before they are acted on, nothing shipped unverified, no secret ever in a place the AI can read back to you.
Who it is for
- A solo founder or a two-person company that wants a business to run between the hours they work on it.
- A consultancy that wants to turn its know-how into products without hiring.
- A small team that already uses Claude Code and wants the company-level layer: rules, memory, approvals, routines.
What you get, by tier
See the three tiers below. Every tier ends with a written handover and a runbook; you run it after that with no dependence on Bindler.
How the build runs
1. You buy a tier and reply to the receipt with the one-page brief (what the company does, what it sells, what repeats every week, which platforms you already use).
2. Within two working days you get a written scope. If it cannot be met at the price, you get a full refund.
3. The build happens in your folder through a shared repository. You tick approvals; nothing goes live under your name without one.
4. Handover: a recorded walkthrough, the runbook, and the support window.
Proof
Bindler's own store, site, marketplaces, vault and this page were built and are run this way. The method is written down in The Autopilot Company on Leanpub.
Requires
- Your own Claude Code subscription (Claude Max is what Bindler runs on)
- Your own accounts on the platforms you sell through; we never hold your logins or keys
- A folder, a Gmail and about two hours of your time across the build for decisions and ticks
Not included
- Legal, tax or investment advice
- Paid advertising
- Anything that needs your identity documents