The Operator's Library · The Builder's Brief
Make keeps moving. Your reference needs a maintenance layer.
Make ships changes constantly — after any manual ships. The Builder's Brief is the layer that keeps your reference accurate: when Make changes something material, you get a plain-English briefing — what changed, what it affects, what to check, and what to do next — plus corrected cards and the occasional ready-to-run blueprint.
Start with the current vault — the 15-Minute Make Drift Triage, the first issue, and its corrected reference cards — then a full year of issues, cards, and the occasional blueprint as Make evolves. Everything added during your year is yours to keep.
Annual prepay. Cancel anytime to stop renewal. The vault is yours the moment you join.
Why this exists
A reference book is accurate the day it ships. Then Make moves.
That’s true of any Make manual, including mine — and it’s true of Make’s own documentation. Make renames a module, reprices a plan, deprecates a function, redesigns the agents feature, and the reference everyone’s working from drifts behind the platform. A book is a snapshot; the platform is a moving target. That gap is exactly the problem the book was written to close in the first place — the Brief is how you keep it closed as Make moves.
You could track all of it yourself — watch the release notes, diff the pricing page, re-test the worked examples every few weeks. Most builders don’t, because that’s a part-time job. No static manual can watch a live platform for you. The book is the operating reference; the Brief is the maintenance layer — it watches the moving parts, tells you what changed, and sends corrected cards when the reference needs updating. Me doing the watching, and sending you only the part that matters.
What arrives
What’s in the Brief.
The monthly Brief
A short, scannable issue — what changed in Make this month, which chapter or card it affects, and what to actually do about it. Builder-impact first, not a change-log dump. If a month brings nothing material, I tell you that honestly and send something useful instead of manufacturing noise.
Corrected reference cards: When a change invalidates one of your Companion Kit cards or a section of the book, the corrected card ships in that issue — same design, drop-in replacement. This is the "your reference stays current" promise made concrete.
Breaking-change alerts: If Make deprecated, renamed, or repriced something that affects live scenarios, it leads the issue, flagged — with what to check and what to do, whether the change is coming up or already active.
Occasional ready-to-run blueprints: Every so often, a small importable scenario addressing something topical — built, tested, yours to import. Not every issue. Only when there's something useful to build.
Day one
Day one
You don't wait a month to get value.
The moment you join, you get the current vault: the first issue, its corrected reference cards, and the 15-Minute Make Drift Triage — a fast first pass through the parts of a Make setup most likely to have quietly drifted out of date. Not a full account audit; a quick sweep of where drift usually shows up. Something useful in your hands on day one, not a month from now. Every new issue and corrected card adds to the vault through your subscription year, and everything you’ve received is yours to keep.
The vault is organized so old issues never masquerade as current: a Current Reference Cards set (the latest version of every card — the ones to actually use) sits separate from the Issue Archive (the monthly briefings in order, for history and context). When a card is superseded, the current set updates; the old issue stays in the archive where it belongs.
- 15-Minute Make Drift Triage checklist — usable the day you join
- The first issue of the Builder’s Brief, in operational-briefing format
- Its corrected reference cards — drop-in replacements for your Companion Kit
- A full year of monthly issues, plus new corrected cards and the occasional blueprint as Make changes — yours to keep
Straight talk
What this isn't.
It's not real-time. I'm not going to pretend a feed pings you the instant Make changes a menu — that's not the value, and it would be a lie. What you're getting is curated and checked: platform claims against live sources, operational cautions clearly labeled, the judgment about what actually matters for someone building real scenarios, and every issue reviewed before it ships. Judgment, not a firehose.
And if you only touch Make occasionally, you probably don't need this. The book you already have is enough. The Brief is for people for whom Make is load-bearing — where a platform change you didn't see coming costs real time or real money.
The offer
Join the Builder's Brief.
If one issue saves you a single serious debugging hour, the year has probably paid for itself.
$79 / year
✓ The current vault, immediately — the 15-Minute Make Drift Triage, the first issue, and its corrected reference cards
✓ The monthly Brief — what changed, what it affects, what to do
✓ Corrected reference cards as Make changes
✓ Breaking-change alerts — what to check and do, upcoming or already active
✓ Occasional ready-to-run blueprints
✓ Cancel anytime to stop renewal — keep everything you’ve already received
Annual prepay. Cancel anytime to stop renewal. The vault is yours the moment you join. 14-day guarantee: read the vault, and if it isn't useful for how you use Make, email me for a full refund. Make won't stop changing. This is how your reference keeps up. — Brian
A few honest answers
Before you join.
I already paid $49 for the book. Isn't this just paying again for updates?
No — and the distinction matters. If I found a factual error in the book, fixing that belongs with the book, free. The Builder's Brief is a different thing: ongoing monitoring of a platform that changes constantly, the judgment call on what actually matters, corrected cards when the reference needs updating, breaking-change alerts, and the occasional blueprint. The book is the reference you own. The Brief is the maintenance layer that keeps it accurate as Make moves. No static manual — mine or anyone's — can watch a live platform for you.
How often does the Brief actually come?
Every month, without skipping. If Make ships nothing material in a given month, the issue says so plainly and includes a useful maintenance card, watchlist item, or blueprint instead of padding it with change-noise. You're paying partly for the reassurance that someone checked — so a month never goes silent. You get signal, not volume.
Do I need this if I already bought the book?
Only if Make is central to what you do. The book stands on its own. The Brief is for builders who can't afford to be caught out by a change — it keeps the book you own from going stale.
Is this automated, or is it really you?
The watching is tooled — I monitor the release notes, pricing, and docs with help from software, so I'm not relying on memory or casual browsing. Every platform claim is checked against live sources, and every issue is reviewed by me before it ships. Where something is an operational caution rather than a documented fact — a known bug, observed behavior, a builder report — I say so. The judgment about what matters is the product. That part isn't automated, by design.
What if I cancel?
Cancelling stops the renewal — you won't be charged again, and you keep everything you've already received: the vault, every issue, every card and blueprint to that point. No clawback. And if you join, read the current vault, and decide within 14 days that it isn't useful for the way you use Make, email me and I'll refund the year. After that, you're in for the year but free to cancel renewal anytime.
Monthly billing?
It's annual. Make's changes come in waves, not on a monthly schedule, and annual keeps the whole thing simple for both of us — one payment, a full year, the vault up front. The 14-day guarantee is there so annual prepay isn't a leap of faith: read the vault first, decide after.