SFR 10-Year OPORD · The Framework
SFR runs on mission command — the military's answer to a question every growing company faces: how do teams execute correctly without waiting on the commander? The answer is a clear order, a weekly rhythm, and a loop that always closes.
Orders that spell out every step break the moment reality changes. Orders built on intent — why we're doing this, what done looks like — survive contact. When everyone knows the intent, anyone can make the right call on the spot. That's how SFR runs through growth, through surprises, and through the owner's deployment.
Commander's intent, standing: fix it forever for every customer · grow every person who gives us their best · let the system do the managing so leaders coach instead of chase. If the plan and reality disagree, act on the intent.
| Order | Cadence | What it does |
|---|---|---|
| 10-Year OPORD | revised rarely | The base order — mission, intent, doctrine, horizons. This site. |
| Annual OPORD | each year · refreshed quarterly as "Change 1, 2, 3" | The year's version of the five paragraphs: this year's rocks, each leader's lane, the budget and hiring plan. Broken out of the 10-year order. |
| Weekly FRAGORD | every week | A fragmentary order — never re-states the whole plan, only what changed and what to do about it this week. |
| Weekly AAR | opens every huddle | The after-action review — the loop-closer. Nothing new is ordered until last week is honestly accounted for. |
Every OPORD — the 10-year and each annual — answers five questions in the same order. The format is the discipline: if a paragraph can't be filled in, the plan isn't done.
| ¶ | Paragraph | Answers | At SFR that means |
|---|---|---|---|
| 1 | Situation | What's true right now? | Market, competitors, our numbers, the binding constraint, named threats — including the owner's deployment as an operational fact |
| 2 | Mission | What must become true? | One sentence, measurable: who we are, what we hit this year, in which markets |
| 3 | Execution | How do we make it true? | Commander's intent · the year by quarter · rocks as phase objectives · each leader's lane · coordinating instructions |
| 4 | Sustainment | What feeds the fight? | Cash & budget, materials & inventory, the hiring plan, fleet & tools, pay & benefits |
| 5 | Command & Signal | Who decides, and how do we stay connected? | Decision rights by size & type · succession & continuity · which channels, which dashboards, which cadence |
The base order carries the intent; the annexes guarantee no function got left out. Each annex has one owner who keeps it current. A weekly FRAGORD cites the annex it changes — "Change 2 to Annex D" — so everyone knows exactly what moved.
| Annex | Covers | Owner |
|---|---|---|
| A · Task Organization | The org chart, the huddle roster, who owns which rock and lane | CEO |
| B · Market Intelligence | Market, competitors, demand signals, financing climate | Director of Sales |
| C · Production Operations | Install capacity, scheduling, quality control, the main effort by quarter | Ops — KC & DFW |
| D · Demand & Sales Effects | The ad calendar (TV, digital), appointment targets, massing leads where we need them | Marketing + Sales |
| E · Protection | Safety, insurance, compliance, warranty reserve, data security, legal | Ops + Finance |
| F · Sustainment | Cash, budget, AP/AR, materials, fleet — with the Personnel appendix: pay, onboarding, HR | Finance + Admin & HR |
| G · Systems & Infrastructure | The technology spine — SmartOS v3, the data platform, every integration | Business Systems & Technology |
| H · Signal | Communication standards, dashboards, the information flow | Business Systems & Technology |
| J · Brand & Reputation | Brand identity, PR, reviews, crisis communication | Marketing |
| K · Customer & Community | The customer is the center of gravity — experience, referrals, partners, permitting | Customer Success + Ops |
| L · Measurement | The scorecard — the few numbers that trigger a decision when they move | Business Systems & Technology |
| M · Assessment | How we judge progress against the order — the AAR, rock scoring, quarterly review | CEO |
| R · Reports | The standard report set and its schedule — scorecard, P&L battle plan, CEO letter | Finance + Systems |
| V · Entity & Partner Coordination | Between our two companies, our partner, CPA, counsel, key vendors | CEO + Finance |
| Step | Who | What happens |
|---|---|---|
| 1 · Draft | AI Chief of Staff | Reads the annual OPORD (the plan) vs. the weekly scorecard (reality) vs. open issues (friction) vs. last week's tasks — drafts "what drifted, and a proposed top-3 per leader to close the gap" |
| 2 · Tighten | Business Systems & Technology | Ten-minute review so the huddle starts from a clean order, not raw output |
| 3 · Decide | The command huddle | Leadership decides each leader's real top-3 for the week — the AI proposes, people decide |
| 4 · Delegate | Each leader | Top-3 items get owners and dates on their teams — mission orders, not micromanagement |
| 5 · Execute | Everyone | The week happens; the Watchfloor tracks every commitment |
| 6 · Report | Next huddle | The AAR opens the next huddle — then the loop begins again |
| # | Question |
|---|---|
| 1 | What was supposed to happen? (the order's intent) |
| 2 | What actually happened? (grounded in the scorecard, not memory) |
| 3 | Why the difference? |
| 4 | What do we sustain, and what do we improve? → feeds this week's FRAGORD |
Every decision has a defined owner by size and type, so the company never waits on one phone. The standing thresholds:
| Decision size | How it's handled |
|---|---|
| Small | For info — decide and inform. Speed is the point. |
| Medium | For feedback — post the memo; 24 hours of silence is consent. |
| Large / irreversible | For vote — leadership decides together, on the record. |
| AI systems | Every automated system has explicit limits: what it may do alone, what it must propose to a human. The FRAGORD is drafted by AI, decided by the command — that pattern everywhere. |
Continuity: the rhythm is designed to run without any single person — including the owner. During the deployment, the huddle meets, the FRAGORD issues, the AAR closes, and only the genuinely owner-level decisions travel.
