An honest comparison
The free kit vs. Business OS
The Backbrief Kit is free and complete on its own: it is the whole build team, and nothing below takes anything away from it. The short version of the difference: the kit disciplines your work; Business OS also disciplines your decisions and your money. Here is the honest trade, including where staying free is the right call.
Page updated August 26, 2026.
The trade, side by side
| Dimension | Free Backbrief Kit | $79, one-time Backbrief Business OS |
|---|---|---|
| What you install | The complete build team: orchestrator, specialists, a cheap runner, a fresh-context verifier, project memory, state in files. Whole, on purpose. | The same team, plus the CEO loop and the operations tier. One install, the kit included. |
| Grading an idea | /grade-idea: five advisors, the public six-dimension rubric, one pass, the weakest dimension named. A real grade, free. | The full loop: a brief, a plan in 90-day units, revise loops to a hard three-pass cap, every score citing the plan's own words. |
| When the plan is weak | The score says so and hands it back to you. | The loop stops and gives you proceed, pivot, or kill. It never auto-proceeds. The first business it graded was its maker's; it said no. |
| Stopping outward actions | The escalation rule, as an instruction the team follows. Most of the value is here: the common failure is never considering the question at all. | The optional enforcement layer: Claude Code's own permission engine asks before a matching outward command runs, whether or not the agent remembered the rule, and fails closed in unattended runs. It covers the command path, not script interiors and not connected MCP tools, and it says so plainly. |
| Two people, one repo | Clone the repo and the same files land. /verify-install reports which install is in force and its version. | Team Parity: a parity line that proves the guardrails are live in the running session, a roles template, a decision log built for more than one writer, and a clone-to-first-task onboarding doc. |
| Who executes the business work | You do, with the build team. | cmo, cfo, web, and ops: locked until your recorded go, and outward actions still stop for you after it. Every time. |
| Worked examples | A real build-team run. | That run, plus two graded business runs, unedited: a real C with a recorded pivot, and three revise loops that plateaued at the cap. |
| Price | Free. Complete. Stays free. | $79 one-time, no subscription, updates included. All sales are final: the download is immediate and yours to keep, so try the free kit first. Statutory rights unaffected. |
| What the grade means, on both sides: a passing grade is a stress-test survived, not a success prediction. Neither product claims otherwise. | ||
When the free kit is all you need
Working solo, on projects with no business attached, with no unattended runs? Stay free. That is the design, not a teaser: the orchestration, the verification, and the project memory are the kit, whole. The paid side starts earning its price at a specific seam: the moment the work grows a business attached. It usually announces itself as the /grade-idea moment, when a quick score stops being enough and you want the loop that can tell you to stop, the lock that holds when nobody is watching, and the setup a teammate can clone and prove.
Weighing the kit against building your own setup, or against a pack of skills? Kit vs. DIY · Kit vs. skill packs.