Field Guide · B3 of 3

# There's the automation you wired last year. And the one that earned the right.

> A Field Guide for the operator whose Zaps broke. Workflows that iterate. Automations that last. Seven chapters, seven Moves. PDF plus AI-Ready Markdown with Companion Guide. $9.

You wired two or three Zaps last quarter. Most of them broke. You're staring at a fourth candidate. The interior is mixed.

FOMO from the influencer who shipped a Make scenario this week. Relief-seeking from work that feels heavy. Sunk-cost ache from the Saturday you spent on the broken automation. Competitive twitch from operators in your feed bragging about how much they automated.

Some of your existing automations feel like jobs you maintain, not flywheels that free you.

Automation that lasts is a timing question, not a tools question. Zapier, Make, n8n, custom code · same question applies. Did the workflow earn the right to be encoded.

Twenty manual reps before automation is on the table. Four validation conditions. A five-question decision tree. The discipline before the automation. The cost of automating too soon is high. The cost of waiting one more month is almost always low.

The Field Guide installs the timing practice. Seven Moves that turn the over-automate reflex into the dancing partner. The automation that knows where you're going to move because the manual reps taught it.

[Get the Field Guide · $9](https://www.sidequesthq.co/products/earn-the-right-to-automate) (a button on the page)

Who this is for

For the operator with Zaps that broke. The discipline before the automation. Third in the business axis, once the framework and the stack are in place.

[Or get all three for $14 (save $13). See the Collection →](https://www.sidequesthq.co/products/business-bundle)

The Practitioner

I'm Lane Belone, a writer on the Infinite Game, a former Green Beret and co-author of _Unleash Your Humble Alpha_. I've wired Zaps and Make scenarios and watched them break the way every operator's broken automations break. Some I shipped before the workflow was stable. Some I shipped because the influencer in my feed made it look easy. Some I shipped because automating felt like progress and the underlying work felt heavy.

The pattern is consistent. The automation breaks because the workflow was never stable enough to encode. The operator never builds intuition because the machine did the work first. Sunk-cost emotion locks the broken automation in place because removing it feels like admitting Saturday was a mistake.

The operators whose automations compound aren't the ones who automated first. They're the ones who ran the manual reps long enough to know the workflow with their body before they taught it to anything else.

This Field Guide is the practice. Seven Moves I've installed in my own workflow maturity. Each one earned through the Saturday-afternoon ache of the broken automation and finding the structure that holds on the other side.

Twenty reps. Then automate. Not before. Every operator who gets there made the same call. Not yet. That's the discipline, and it's a kind of person you choose to be.

![Earn the Right to Automate cover · atmospheric backdrop with the title centered in a cyan-accented Field Guide composition](https://www.sidequesthq.co/covers/earn-the-right-to-automate/cover-print.webp)

The Field Guide

## Seven chapters. Seven Moves. Twenty to forty minutes to read. Weeks to install.

Each chapter names a piece of the practice. Each one ships **The Move**, an install you can drop into your week before the chapter's even fully landed. The Move is the point. The reading is the on-ramp.

Read in order on the first pass. The twenty-rep practice takes as long as twenty reps take. The thirty-day trial is the graduation gate. The structure holds the timing.

Chapter 1\. The Good Idea Fairy.

The over-automate reflex. The cool-idea-with-potential that may be energizing the wrong thing entirely. The flywheel-versus-job diagnostic: if you have to maintain it, it's a job. _The Move:_ the Tuesday-morning automation audit. Mark each as flywheel or job. Three minutes.

Chapter 2\. The Cost of Automating Too Soon.

Three costs that compound. The automation breaks. The operator never builds intuition. Sunk-cost emotion locks the broken thing in place. _The Move:_ the sunk-cost release. Name one automation you maintain only because you built it. Math the cost. The math is the freedom.

Chapter 3\. The Twenty-Rep Practice.

Twenty manual reps before automation is on the table. Not magic. The practical floor. Edge cases surface. The workflow shape mutates. You build the gut the automation will eventually need. _The Move:_ the manual rep log template. One row per rep. The reps are the school. The log is the transcript.

Chapter 4\. The Four Validation Conditions.

Same inputs produce the same outputs across reps. You can describe edge cases without thinking. The workflow has been refined at least twice. You can defend it to a sharp peer without notes. Validation is a state, not a deadline. _The Move:_ the validation checklist. Four boxes. No partial credit.

Chapter 5\. The Five-Question Decision Tree.

Twenty reps hit? Stable across the last five? Math works? Input source stable? Ready to lose the muscle memory? A no on any one sends you back to manual reps. Conservative on purpose. _The Move:_ the tree as a one-page protocol. Copy-paste into your workflow doc. Run before any automation gets wired.

Chapter 6\. The First-Build Practices.

Start small. Automate one step, not the whole workflow. Keep the manual rep as fallback for thirty days. Build observability from day one. Don't chain a second automation onto an unproven first. _The Move:_ the first-build checklist. Five practices. Five boxes. The structure holds you from end-to-end on day one.

Chapter 7\. Invisible Automation.

The arrival. The dancing partner. The automation that knows where you're going to move because the intimate process of creation taught it. Sovereignty over the tool, not subordination to it. _The Move:_ the thirty-day trial close-out review block on the calendar. The graduation moment.

The felt difference after the Moves are installed.

Invisible automation. The dancing partner. The automation that knows where you're going to move. Subconscious muscle memory after conscious repetitive practice. You can be yourself, trust the structure, let the automation go invisible.

From inside the Field Guide

## One Move, whole

From Chapter 3, Twenty Reps. The log you keep while you run a workflow by hand, before anything gets automated. Here it is as it ships.

### The Move

**What you're installing:** The Manual Rep Log.

**The reason:** Capture is the input for every downstream Move. The validation conditions in Chapter 4 check against the log. The decision tree in Chapter 5 references the log. Without the log, the reps still teach you, but unconsciously. With the log, the reps teach you on purpose. The data's right there when you need it for the decision.

**Install this week:**

Open your thinking partner. Paste or dictate the following:

Set up my manual rep log for [name the workflow you're going to run twenty times].

Five columns: Rep Number, Date, What Happened, Edge Case Surfaced, What I'd Refine.

I'll dictate each rep as I run it. For each one, ask me the column values and capture the row in our conversation. Keep the log live in this chat so we can re-query, sort and pattern-match against it as the reps accumulate.

After every fifth rep, surface the patterns you're noticing. The edge cases that have repeated. The refinements I've made. Whether the workflow shape seems to be stabilizing or still mutating.

Run the workflow. Capture each rep right after it's done, while the texture's fresh. Don't batch the captures. Same-day capture is the discipline.

Static-doc alternate: open a spreadsheet titled _Manual Rep Log. \[Workflow Name\]._ Five columns. Same fill-after-each-rep rule. The AI-native version makes pattern-matching easier as the reps accumulate.

**The expansion:** By rep ten, the log starts showing you patterns your memory wouldn't have surfaced. By rep twenty, the log's both your validation evidence and the source material for the automation spec, if the decision tree says wire it. The log is the school's transcript. The school's the reps. The transcript travels with you.

Quoted word for word from the markdown edition that ships with the purchase.

![Earn the Right to Automate - what you receive: the full file set](https://www.sidequesthq.co/covers/earn-the-right-to-automate/bundle-1x1.webp)

What You're Getting

## Two files. PDF and AI-Ready Markdown. Both designed to live in your week.

The Field Guide as a designed reading experience and as an AI-native working tool.

The Field Guide (PDF)

Full-bleed, designed for screen or print. Seven chapters, seven Moves. The reading experience the cover promises.

The Field Guide (AI-Ready Markdown with Companion Guide)

One markdown file. Drop it into Claude or ChatGPT. The Companion Guide section at the top tells your AI how to facilitate the Moves and run the five-question decision tree as a copy-paste protocol before any new automation gets wired. The Field Guide content below gives your AI the installed operating context for every workflow decision.

Voice-brief block, Moves index, decision tree protocol, thirty-day trial close-out review block. Plus the full Field Guide content. End-to-end in one paste.

$9

The full Field Guide. Seven chapters. Seven Moves. Two files designed to install the timing practice into your week.

Built for the operator whose Zaps broke and who wants the next automation to last.

The Move is the point. The reading is the on-ramp.

[Get the Field Guide · $9](https://www.sidequesthq.co/products/earn-the-right-to-automate) (a button on the page)

[Or get all three for $14 (save $13). See the Collection →](https://www.sidequesthq.co/products/business-bundle)

## Common Questions

**I've got Zaps and Make scenarios running. What's different about this Field Guide?**

The Field Guide installs the timing practice. Twenty manual reps before automation is on the table. Four validation conditions. A five-question decision tree. The discipline before the automation. Most operators automate too soon, then maintain the breakage. This Field Guide is for the operator who wants the automation to last.

**How long does it take to work through?**

Twenty to forty minutes for the first read. The Moves themselves install over weeks. The twenty-rep practice takes as long as twenty reps take. The thirty-day trial is the graduation gate for any new automation. The Field Guide holds the timing.

**What's the AI Companion Guide section in the markdown file?**

The markdown ships with a Companion Guide section at the top. Voice-brief block, Moves index, the decision tree as a copy-paste protocol your AI walks you through before any new automation gets wired, the thirty-day trial close-out review block. Drop the file into Claude or ChatGPT.

**Do I need to be technical?**

No. The Field Guide is about the practice, not the platform. Zapier, Make, n8n, custom code. The timing question applies the same way to all of them. Every Move is a one-page checklist or a recurring calendar block. The structure holds you back from automating on day one.

**Who wrote this?**

Lane Belone, a writer on the Infinite Game, former Green Beret and co-author of Unleash Your Humble Alpha. Wired Zaps and Make scenarios. Watched them break. Watched himself maintain them out of sunk-cost ache. The timing practice is what came out the other side.

The Business Collection

[AI for the Business You Actually Want](https://www.sidequesthq.co/products/ai-for-the-business-you-actually-want) · whose voice, whose terms, whose business. The framework before the tool.

[Stack Calm](https://www.sidequesthq.co/products/stack-calm) · your minimum viable AI setup. For the operator drowning in subscriptions.

[See all products](https://www.sidequesthq.co/products) · [About Lane](https://www.sidequesthq.co/about)

Side Quest HQ, the Infinite Game practice of [Lane Belone](https://www.lanebelone.com)