For business owners new to Claude Code

New to Claude Code? Brainfile sets it up safely for your business.

You paste one line and answer ten plain questions. Claude writes down how your business works, so it knows it at the start of every session, and its safety settings keep it away from your passwords and out of your other folders. After that, one command brings a signed weekly update (Basic).

Not ready for the trial? Get the free Brainfile email: a Claude Code tip every Tuesday and Thursday, plus a Sunday recap of the week.

✓No card to start✓Runs on your machine, not ours✓You keep every file, always

Everything on this page is in the product today. If it has not shipped, it is not listed and it is not sold.

How you start

No coding. You paste one line and answer ten questions.

Brainfile is for people who want Claude Code working for their business without learning how to set it up. If you can open Claude Code in a folder, you can do this.

  1. Start the free trialType your email. No card. Your setup line appears on the next screen and in your inbox.
  2. Paste the line into Claude CodeOpen Claude Code in the folder you work from and ask it to run the line. Claude does the setup for you.
  3. Answer 10 quick questionsClaude usually starts the questions by itself. They are in plain English and take about 5 minutes, then Claude writes your Brainfile from your answers. If they don't start, type start.
Start free — 30 days, no card

New to Claude Code itself? It runs on your existing Claude plan. Follow the five-guide Start-here path

Start here

New to Claude Code? Five guides, in order.

Plain-English guides for people who don't write code. Read them in order. Each one ends with a link to the next.

  1. Install it and open it in a folderWhat Claude Code is, how to install it on a Mac or Windows, and what to type the first time.
  2. Tell it about your businessThe CLAUDE.md file it reads before every conversation, so it stops starting from zero.
  3. Keep passwords and keys out of your filesWhat Claude can read in your folder, and how to keep keys in a password manager instead.
  4. Connect the tools you already useMCP servers let Claude Code reach tools like GitHub, Slack and Google Drive. Which to add, and how.
  5. Hand it your first real taskEveryday jobs people who don't code give it, like customer emails and market research.
Start with guide 1

Rather skip the manual setup? In the free trial, Claude sets up Brainfile in your folder from ten questions. Start free, no card

This is not a mockup. It is a real excerpt of the sanitized operating file this business runs on, served from this site.

CLAUDE.mdreal excerpt — read the whole file
### Law #19: Build-and-Verify (owner directive 2026-03-20)
After building ANY script, feature, or pipeline component, verify the FULL chain — not just "it exists":
1. **Runs:** Does it execute without errors? (`python3 script.py` succeeds)
2. **Output correct:** Does it produce the expected output? (Spot-check, not just "no errors")
3. **Consumed:** Is the output read by something downstream? (Dashboard, email, another script)
4. **Wired:** Is it scheduled to run automatically? (LaunchAgent, cron, pipeline hook)
- **"Script exists" ≠ "script runs" ≠ "output consumed."** All four must be true.
- Root cause: 3+ `ep_had_to_ask` entries from build-and-forget pattern (ITC pipeline, dashboard generators, scripts not wired to cron).
- After EVERY build task: verify all 4 links in the chain before marking done.
The difference, in one exchange

The same request. With your Brainfile, and without.

A capable assistant with no memory of how you work will do what you literally asked. The same assistant, running on your Brainfile, does what you actually needed — because the rules it loaded remember your setup and make it check its own work before it says done.

1 · It remembers your business. It catches your mistakes.

You ask, in plain English:“Update our pricing on the site to the new $49 plan.”
No BrainfileA capable assistant, no memory of how you work

Done. I opened the homepage, found the price, and changed it to $49.

  • Edited a page that is generated from a source file — the next rebuild silently wipes the change.
  • Changed one place; the price also appears on the pricing page, the FAQ and the checkout.
  • Said “done” without opening the live pages to check.
With your BrainfileThe same assistant, running your loaded rules

Your prices live in one source file, and the pages are generated from it — hand-editing the HTML would be wiped on the next build, so I updated the source.

Rebuilt the 3 pages that display a price.

Then checked the rest: an FAQ answer still quoted the old $99. Fixed that too.

All four places now read $49 — confirmed on the live pages before calling it done.

  • Knew where your prices actually live, and that the pages are generated — memory of how you work.
  • Caught the leftover $99 you didn't mention — it checks its own work.
  • Verified against the live pages before claiming done — the build-and-verify rule shown above, applied.

2 · It stays current.

Six weeks later:“The platform changes. The way your setup was wired is no longer the way it is done.”
No BrainfileRules written once, on the day you wrote them

Nothing tells you. The setup keeps running the old way until something quietly stops working, and the first sign is the thing that didn't happen.

  • The rules describe the platform as it was the day they were written, and nothing revisits them.
  • You find out from a missing output, not from a notice — often weeks later.
  • Catching up means re-reading release notes and re-doing the setup yourself, every time.
With your BrainfileThe same rules, on a maintained pull

Your next pull carries the updated pattern, and the weekly freshness note says in plain English what changed and what it means for your setup.

  • Maintained against a platform that ships weekly — you are not the one tracking releases.
  • Changes arrive as versioned pattern files you pull, not a blog post you have to go find.
  • You can read the most recent freshness note on this page, unedited, before you buy.

Two illustrations of what the shipped pattern files and the weekly freshness feed produce — the same kind of rule you can read in full above, applied to a real request, and the maintenance that keeps it true afterwards. Not testimonials, not mockups.

Why a subscription and not a download

A file does not retain you. A running system does.

You can download a set of rules today for nothing. Here is the honest argument for paying for one instead.

What you download decays

Claude Code ships roughly weekly. A configuration pointing at a retired model or a removed setting does not throw an error — it quietly stops working, and there is no way for a non-technical owner to know. Perishability is the whole reason antivirus is a subscription.

What you accumulate is yours

Your decisions, preferences and context build up in plain files on your own disk. After six months that folder is genuinely yours and could not be recreated in an afternoon. It is the one asset in this product a competitor cannot copy, because it is not ours.

Someone keeps it true

Claude Code changes most weeks. We check those changes against the files you run and ship the fixes as a versioned weekly feed you pull. With a downloaded rule set nobody does that for you; you would be the one reading release notes.

No marketing here

What ships today

Everything below is live right now and verifiable. This list is the product: if something is not on it, we do not sell it.

✓Free for good, plus a 30-day Basic trialEmail only. No card, no sales call. The setup and the safety settings are free for good; the trial adds 30 days of Basic. One email address, one trial. You keep every file you pull.
✓One command, then signed updatesYour setup arrives through one line you paste into Claude Code. Run the same line again, or ask Claude to, whenever you want the newest version; on Basic that brings the weekly update. Every update checks our signature before it changes anything in your folder. No zips, no download links to keep track of.
✓Interview onboarding (free)Open the folder in Claude Code and type start: it asks you 10 quick questions and writes your personal Brainfile from the answers. About 5 minutes.
✓Safety settings (free)Every pull sets Claude in that folder so it cannot read your keys or password files, use sudo, run rm -rf, switch to bypass mode, or read and write outside the folder. SAFETY.md says it in plain English.
✓10 pattern filesA never-empty backlog, a ledger that tracks every ask until it is done, conversation history and a memory starter (free), plus the Autopilot run protocol and an end-of-run brief (Basic).
✓Starter skills (free)A skill is a short instruction file Claude follows when you ask for a specific job. The free starter has one today: say “help me with my resume” and you get five short questions, a before-and-after you approve, nothing invented, and a Word file and a PDF out. Your resume never leaves your computer.
✓Never lose a conversation (Basic)Say one sentence to turn it on, and every Claude Code conversation is kept as a readable, dated page on your own computer, with keys and passwords removed and a where-I-left-off note for each project. Nothing is sent anywhere.
✓A weekly freshness feed (Basic)Versioned updates that keep your setup current with a platform that ships weekly. The most recent one is printed below, unedited.
✓15 role packs (Pro)Role-shaped operating profiles, released to an active Pro subscription.
✓A stay-current rule (Pro)When a new model is greyed out after an update, Claude checks which version this session is really running and tells you to relaunch, update or wait. It never says you are up to date from a check that did not run.

This is the actual payload, not a mock-up:

brain/freshness/2026-11-16.mdactual freshness feed · v23 · the retention mechanic
# Brainfile update — v23 (2026-11-16)

Merged from the Brainfile Freshness Feed. These are cadence updates to apply to how
Claude works in this project.

## Apply these patterns
- Stay current: why a new model stays greyed out after you update, and the fix: Pro: the rule is packs/<role>/.claude/rules/stay-current.md. Bring it into your folder's .claude/rules/ (packs/README.md says how), then tell Claude a new model is missing and it runs the check itself.
- The red-green guard rule now ships in every paid role pack (shared-rules layer): Keep shared rules in ONE file and overlay it into every profile you ship or reuse, rather than editing N copies. Then check the drift the same way we do: measure how far each surface trails your newest improvement, and put a heartbeat on the surface with the longest gap so the drift pages you instead of being discovered.

## Awareness (Claude Code / tooling changes)
- Added a spinner tip in VS Code and similar integrated terminals about re-running a notebook cell, shown once Claude has read or edited a Jupyter notebook (https://code.claude.com/docs/en/changelog)
- Added a line under the error shown when your organization's policy blocks a request, saying how to continue: run `/rewind` and change the message, or run `/clear` (https://code.claude.com/docs/en/changelog)
… (full feed ships in the pack)

This is the real v23 feed — the latest one shipping in the pack (2026-11-16). The next feed ships with the next real change — we never backfill fake updates.

Pricing

Free, Basic and Pro

Start free: the setup, the safety settings and the resume skill are free for good. Basic is the running system. Pro adds the library: the 15 role packs and the stay-current rule. Every line on these cards is in the product today.

Start here

Free

$0

Free for good, no card, plus 30 days of the full Basic pull. Every file you pull is yours to keep.

  • ✓Setup: the interview that writes your CLAUDE.md, plus a request ledger and a backlog it fills in
  • ✓Safety settings: Claude cannot read your keys or password files, use sudo or bypass mode, or touch files outside the folder
  • ✓The resume skill: improve a resume and write cover letters, nothing invented, Word and PDF out
  • ✓30 days of the Basic pull on top, no card
  • ✓The Free Starter Kit — 3 ready configurations
Start free — 30 days, no card

Email only. One email address, one trial.

The running system

Brainfile Basic

$19/mo

Billed monthly, cancel anytime.

  • Everything in Free, plus:
  • ✓Never lose a conversation: every Claude Code chat kept as a readable, dated page on your own computer
  • ✓Autopilot: give Claude a goal and a time limit; it picks the work, checks it and can leave you an end-of-run brief
  • ✓One command to update, signature checked first; no zips, nothing to merge
  • ✓It stays current so you don't have to
Try Basic free for 30 daysor subscribe now, $19/mo →

Basic runs the system: weekly updates, Autopilot and the conversation saver. Pro adds the 15 role packs.

Brainfile Setup Audit $249 one-time

Not ready for a subscription? We audit your existing Claude Code or agent setup and send back a scored report and a prioritized fix list, worst first.

See the Setup Audit

Setting this up for a team or a company?

Team and company setups are arranged per organization. There is no public team price and no team checkout. Tell us who it is for and how many people, and a person writes back.

Email hello@brainfile.io
How the trial ends

It downgrades. It never takes anything back.

Most trials end with a locked door. That is a bad fit for a product whose value is a folder of your own decisions — so ours is designed the other way round.

When the 30 days end

You keep every file you pulled, permanently, including your memory folder. Your setup line keeps pulling the free starter (setup, safety settings and the resume skill) for good. The weekly feed stops at the last version you pulled. There is nothing to uninstall and nothing to hand back.

Your fileskeepEvery file you pulled, forever.
Your accumulated memorykeepThe whole folder of your decisions and context. It is on your disk, in plain text.
The free starterkeepSetup, safety settings and the resume skill, for good.
The weekly freshness feedstopsPins at the last version you pulled.
Stay in the loop

Free Claude Code tips, three emails a week

A practical Claude Code tip every Tuesday and Thursday, plus a Sunday recap of the week.

Double opt-in. Unsubscribe in one click. We never sell or share your address.

Questions

Straight answers

A business owner who is new to Claude Code and wants it working on their business without learning how to configure it. If you already write your own CLAUDE.md files, hooks and settings, you probably do not need us; our Free Starter Kit may be all you want.

The delivery part, yes. Your setup line is a small script that downloads your files over a secure connection, the same way git or curl would, and checks our signature before it changes anything. Anyone could move files that way. What you pay for is what is inside them and keeping them current: every week we publish what changed in Claude Code and what it means for your setup, so you never have to follow that yourself.

There is no separate Brainfile app, and you never need a terminal. Brainfile is a set of files in a folder on your computer, and it runs inside Claude Code. The easiest way in is the Claude desktop app for Mac or Windows: open the Code tab, keep it on your computer (not the cloud), choose your Brainfile folder, and paste the one message we send you. Claude Code in a terminal works too. You talk to Claude in plain English either way. Brainfile changes what Claude already knows, and what it is allowed to do, when you open that folder.

It works in the Code tab of the Claude desktop app when the session runs on your computer, and in Claude Code in a terminal. Both read the same Brainfile files: your CLAUDE.md, the skills, the safety settings and the saver. It does not work in the ordinary Claude chat, in Cowork, in claude.ai in a web browser, or in a Code tab session set to run in the cloud, because none of those can see a folder on your computer. Keep the app up to date (Claude menu, then Check for Updates): the app keeps its own copy of Claude Code, and the newest safety settings need a recent one. You do not need to change any permission setting in the app or on your Mac: your Brainfile safety settings live in the folder, the app reads them, and the same file switches off the app's bypass mode so they cannot be skipped by accident. We test on a Mac; on Windows, Claude Code also needs Git for Windows (free).

It does not replace them; it fills them in. Claude Code already reads a file called CLAUDE.md at the start of every session, follows a settings file that says what it may touch, and loads skills. Out of the box those are empty. Brainfile interviews you and writes them: a CLAUDE.md about your business and your goals, safety settings that keep Claude away from your passwords and out of other folders, and a backlog and a request ledger it works from. Claude Code's /goal is a different thing: it keeps Claude on one task until a condition you set is met, inside one session. Your Brainfile backlog is where those tasks come from, and it carries over between sessions.

Files in a folder on your computer, plus keeping them current. Free, with no time limit: the interview that writes your CLAUDE.md, a backlog (brain/backlog.md) and a request ledger (brain/ledger.md), the safety settings with SAFETY.md, and the starter skills. Basic adds the weekly update in brain/freshness/, AUTOPILOT.md for timed runs, an end-of-run brief template, and the conversation saver. Pro adds the 15 role packs and the stay-current rule. The trial gives you 30 days of Basic. Prices are in the Pricing section above.

Some files are yours and some are ours. Yours, never touched by an update: your CLAUDE.md, your backlog, ledger and decisions, your resume notes, your safety settings file, your saved conversations, and any file you create. Ours: the guides, skills, weekly feed and role packs we ship, such as START-HERE.md, SAFETY.md and the packs folder. If you edit one of ours, the next update puts our version back, names the file, and keeps your edited copy in .brainfile/kept-edits, which no update deletes. Every update saves what it is about to change first and prints the one command that undoes it. Type /check-brainfile in Claude Code for a health check: it lists what you changed in our files, helps you move it into CLAUDE.md where it is safe, and tells you if a safety setting was switched off. When you run an update yourself in a terminal it lists what will change and asks first. And if a prompt ever wrecks one of your own files: on a folder installed from 10 November 2026 on, every update first saves a copy of your CLAUDE.md, your notes and my-packs on your computer (the last 5 different versions, nothing sent to us). Type /undo-my-changes, or tell Claude "put my CLAUDE.md back", and it puts back the copy you pick.

You keep them. All of them, permanently — the rules, your accumulated memory folder, and the last freshness feed you pulled. It is plain text on your own disk and we will not try to take it back. Your setup line keeps pulling the free starter (setup, safety settings and the resume skill) for good. What stops is the running service: new feed versions, Autopilot and conversation-saver updates and, on Pro, the role packs.

No. Brainfile runs inside your own Claude Code on your own machine. Your files never leave it. The only thing that crosses the network is the pull that fetches your setup, which is authenticated with a licence token and sends us nothing about your work.

You need to be able to open Claude Code in a folder and paste one line. After that you type start and answer 10 plain-English questions; Claude writes your files from the answers. If you would rather we look at an existing setup for you, that is the Setup Audit.

You should not, if a static file is what you want — there are good free ones, including our own Free Starter Kit. You pay for the part a file cannot do: staying current with a platform that ships weekly, and a memory of your business that builds up in files you own.

Email hello@brainfile.io, or press Cancel on brainfile.io/billing, which writes that email for you. A person cancels it within 1 business day. No retention call, no exit survey, and the refund policy is published.