How to Build Systems (So Your Business Runs Without You)

Core message

Don’t document everything with checklists/SOPs. Instead, build visual “value engines” (growth + fulfillment, optionally innovation) that show how the business creates and captures customer value, so teams can run and scale without the owner being in every step.

Three principles / “playbook” to document systems effectively

• Document only what’s critical (“e-myth myth”)

  • Avoid the founder trap of writing checklists/SOPs for literally everything.
  • A full-company documentation project created binders, but nobody used the checklists afterward—seen as wasted time.

• Shift from single advantages to end-to-end systems

  • Value drivers = individual advantages (e.g., marketing strength, sales strength, fulfillment skill, IP).
  • Value chains = a collection of value drivers that combine to produce the business outcome.
  • Goal: move from “we’re good at one thing” to mastering the whole chain.

• Visualize to enable optimization

  • You can’t optimize what you can’t clearly understand.
  • If the company can’t show (diagram/flowchart) how it creates and captures market value, it likely can’t truly optimize.

The “Value Engine” framework (company operating system component)

A value engine is a visual representation of how a company:

1. Attracts and converts new customers
2. Fulfills existing customers’ needs
3. (Optionally) Innovates/improves offerings over time

Types of value engines

• Growth Engine

  • Visualizes how customers/clients become aware and convert.

• Fulfillment Engine

  • Visualizes how promised value is delivered after the sale.

• Innovation Engine (not covered deeply in the video)

  • Visualizes how teams create/update/improve products/features.

Step-by-step process to map a first value engine (sticky-note method → flowchart)

Step 1: Identify which engine you’re mapping

Start with the growth engine (recommended by the speaker).

Step 2: Define start/trigger and end/completion events

• Growth engine start (trigger): how people become aware you exist Examples mentioned:

  • ads (Facebook/Google)
  • event sponsorship
  • bought lists
  • referrals
  • walk-in traffic

• Growth engine end: when the sale is made / contract signed

• Fulfillment engine trigger: begins where growth ends (typically after sale)

• Fulfillment engine end: often when you request testimonial/customer story (i.e., value delivered)

Step 3: Map tasks/activities between start and end

Use only two shapes:

• Square = task/activity
• Diamond = decision/gateway (“then what now?”)

Process:

• Ask the team repeatedly: “Then what happens?”
• Use “depends” as the cue to create a diamond decision point.
• Expect branches (forks)—the journey is typically not linear (e.g., “did they register?”, “did they buy?”).

Concrete example: “Mommy fit” growth engine (e-commerce / DTC fitness)

• Trigger: customers see ads

  • “Facebook ads”, “Google ads”, “Instagram stories & reels”

• Simplified flow:

  • Ads → 7-Day mommy fit challenge registration page
  • Decision: Did they register?
    • No → run retargeting ads back to the registration page
    • Yes → deliver 7-day challenge series
  • Additional decision points include offer engagement:
    • Did they click an offer link?
      • Yes → go to workout kit sales page → sign up/buy
      • No → enroll in follow-up email series → later reattempt to drive to the sales page
  • Decision: Did they purchase?
    • Yes → upsell deluxe kit
  • Completion: handoff to fulfillment

Key point: mapping the full customer journey (awareness → conversion → post-conversion actions).

Step 4: Hold a stakeholder review meeting

• Invite relevant owners (marketing/sales/product depending on engine).
• Prompt: “What did we miss?”
• Example correction from the Mommy fit case:
  • They realized they forgot weekly workout videos/newsletter emails—an additional awareness/re-engagement step.
• Also noted: non-buyers are included in follow-up sequences that feed back into the engine.

Step 5: Convert only “power stages” into checklists/SOPs (value engine audit)

This is where checklists/SOPs come back—but selectively.

• Perform a value engine audit:

  • Identify steps that are unforgivable (can’t afford failure) — call them Power Stages.
  • Example power stages mentioned:
    • running Facebook/Instagram ads
    • weekly workout videos that re-engage prospects who didn’t buy initially
    • critical parts of delivery/automation
    • building/optimizing sales pages

• Assign ownership:

  • “Who on the team owns this stage?”
  • Document while the person performs the work next time (lightweight, practical documentation).

Outcome: only 10–30 checklists/SOPs (speaker’s range), not 100–300 unused artifacts.

Step 6: Finalize into a flowchart tool

Convert the sticky-note map into a standardized diagram.

Step 7: Install into the company operating system

Make value engines:

• reviewable
• clickable
• linkable
• accessible to the team

Business execution implications / actionable recommendations

• Start with growth + fulfillment to cover the whole customer journey.
• Stop writing “everything” documentation; build visual flow first.
• Use the value engine diagram to identify:
  • where conversion drops (i.e., which decision diamonds/forks are failing)
  • where to add steps (e.g., more traffic, more follow-up, improved sales page)
• When a step is truly critical, create SOP/checklists only for those power stages.

Metrics / KPIs / targets mentioned

• No explicit numeric KPIs (e.g., CAC/LTV/churn) or targets were stated.
• The closest performance signals referenced were qualitative optimization triggers like:
  • “customers aren’t converting at a high enough rate”
  • “people are not buying”
  • “need more traffic”

Investing/markets

• No significant investing/market execution content included; the focus stays on internal operating systems.

Presenter / sources

• Presenter: Ryan Dice (manages a 17-company portfolio across a 200M holding group, per the video)
• Source mentioned: The E-Myth (referenced for the “e-myth” documentation misunderstanding)