top of page

What Is a Value Engine? Mapped for a Solo Business, With a Worked Example

Writer: Brian Lathe
Brian Lathe
6 days ago
6 min read

Updated: 5 days ago

What Is a Value Engine? Mapped for a Solo Business, With a Worked Example

Of all the tools in Ryan Deiss's Scalable Operating System, the Value Engine is the one I'd call genuinely his: the one he builds everything else on, first. Scorecards and accountability charts exist in every system going back decades. It also survives translation to a business of one with the least damage. So: what it is, how he draws it, and a full worked example.


What a value engine is

A value engine is a visual map of how the company creates and captures value, drawn on a whiteboard with sticky notes.


Deiss's case study uses two. The Growth Engine is how customers are acquired: it starts at the first touch (an ad view, a search result, a referral mention) and ends at the sale. The Fulfillment Engine is how customers are served: it begins where Growth ends and ends at the testimonial or referral.


The method, as his case study gives it: (1) sticky-note the starting point, (2) sticky-note the ending point, (3) fill the gap by repeatedly asking "Then what?", and (4) connect the notes with arrows. And it's step one because in his design everything else is derived from this map — which steps get procedures, who is accountable for what, which numbers go on the scorecard.


His claim, testable against your own wall: Deiss says owners at companies with teams, mapping for the first time, typically find that 20–30% of the team's activity connects to no engine at all — work leading neither toward a sale nor toward a delivered, referring customer. A solo operator audits something else: your week. Hold your calendar up against the map and see how much of it is spent on steps that appear nowhere on it. That gap is the solo version of the finding, and it's rarely small.


A worked example: a one-person coaching business

Take a solo coach selling a one-to-one package. No staff: the owner markets, sells, delivers, and answers the email.


The Growth Engine — first touch to sale:

  1. First touch — an article, post, podcast appearance, or past client's mention.

  2. Contact captured — the stranger takes a free resource or joins a list; there's now a name and a way back to them.

  3. Nurture — a short email sequence, while the stranger decides if the problem is urgent.

  4. Conversation booked — the stranger books a discovery call.

  5. The call — the problem diagnosed properly, whether or not it ends in an offer.

  6. Offer made — a proposal goes out: package, price, start date.

  7. Follow-up — the proposal chased, questions answered, a decision reached — yes or no, but reached.

  8. Sale — payment and agreement. The engine ends here, on purpose: a sale is not a delivered result.

The Fulfillment Engine — sale to referral:

  1. Onboarding — intake form done, kickoff scheduled, expectations in writing.

  2. Starting-point audit — the client's measured starting point, so "progress" later means something.

  3. Delivery sessions — the weekly calls, run from the plan made at the audit.

  4. Between-session support — homework reviewed, messages answered, work kept moving between calls.

  5. Midpoint check — progress compared to the starting point, plan adjusted while there's time.

  6. Wrap-up — final session, results summarized against the audit, next steps named.

  7. Testimonial ask — asked directly, while the result is fresh.

  8. Referral ask — asked who else has this problem. And notice: this last step feeds the Growth Engine's first one. The two engines are a loop, not a line.


What the map shows you: the three leaks

Drawn honestly, a solo operator's map shows the same three leaks — steps never given a place on the map, so they happen by mood instead of by system.


Leak one: the follow-up gap between conversation and offer. The call happens. Then the proposal sits in a drafts folder for three days because delivery is louder, or goes out unchased because chasing feels like bothering people. Strangers rarely leak out at "nobody's heard of me." They leak here — after raising a hand, having a conversation, and asking the price. The most expensive place to lose them, and invisible until that ownerless gap between steps 6 and 7 was written down.


Leak two: the delivery step that eats the week. Fulfillment step 4 has no edges: messages at all hours, homework reviewed whenever guilt strikes, prep reinvented per client. One sticky note; ten hours in the week — hours meant for Growth steps 1 to 3, which is how a full delivery calendar produces an empty future pipeline. The map only makes that trade visible — the precondition for giving the step a boundary, a time slot, and a written procedure, because it's a power step: high-stakes and repeated.


Leak three: there is no referral step at all. Most solo fulfillment stops at step 6 — last session, warm goodbye, done. Steps 7 and 8 never happen, not because the work isn't good, but because asking was never made a step. The engine's endpoint is a referral; the real process ends two steps short. So every new client must be found from zero, at full effort, forever, while the cheapest source of first touches walks out unasked.


What changes once the map exists

Your scorecard writes itself. A useful weekly scorecard counts what happens at the engines' important stages. From this map, the numbers pick themselves: conversations booked, proposals sent, follow-ups completed within your standard, onboardings finished, referral asks made. (The template version is Article 7, "The Weekly Scorecard for a One-Person Business.") Before the map, picking metrics is guesswork. After it, a reading exercise.


Every stage gets one owner. On a team, this is Deiss's question: who is uniquely responsible for this step? In a system like mine, the same question is asked of desks — named functions that run whether I'm at my job or not. Content owns first-touch assets; the contacts desk owns capture and the follow-up reminders that close leak one; the deals desk owns conversation to offer to decision; the knowledge desk owns the map itself, so the recorded map is the one being run. If a stage's owner is "me, when I get to it," the map just told you which desk or rule doesn't exist yet.


Your procedures go where the stakes are. Document everything and you get Deiss's binders nobody read. Mark the few steps both high-stakes and easy to get wrong — the offer and its follow-up, the onboarding, the referral ask — and write those down word for word. The rest stays light.


The honest line: if you run a business at Deiss's stated fit — $2M–$20M with a real team — look at his install with my blessing. But the tool doesn't need the team. It needs an evening, a wall, and the discipline to keep asking "then what?" past where the answer gets uncomfortable. That's where the leaks live.


The scorecard runs inside SuccessBrian OS — and it is free

SuccessBrian OS is the system I run my own one-person business on. The weekly scorecard from this article works inside it.


In plain words: once a week, you type in five numbers — new leads, sales talks, work delivered, things shipped, cash in. The system keeps them, shows you which ones hit your target and which ones fell behind, and remembers the plan and the promise you made. You do not have to keep a spreadsheet alive. You do not have to remember anything. The system remembers for you.


It costs nothing. There is no form to fill out and nothing to buy. Download it and use it:



Rather start on paper? The scorecard template is printed in full on this blog, in "The Weekly Scorecard for a One-Person Business." Start there if you like. Just start this week.


Not affiliated with Scalable.co or Ryan Deiss. The Value Engine method and the 20–30% claim are Deiss's, from Scalable's public case study, read in November 2026; the worked example and translation are mine.


Read more from Brian Lathe on Substack


This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.

 
 
 

Recent Posts

See All
Do You Need an Integrator If You're a Team of One?

Do You Need an Integrator If You're a Team of One?If you've read anything about EOS — Gino Wickman's Entrepreneurial Operating System, from Traction — you've met the famous pair. The Visionary is the

 
 
 

Comments


Talk to Brian

on WhatsApp

Appointment booking opens soon.

Questions about this article — or about SuccessBrian OS? Text me here.

Texting is best — please don't call. Calls are by confirmed appointment only.

Talk to Brian

Questions, or want a system like this working for your business? Message me directly.

What is SuccessBrian OS?

One system that runs a solo business while its owner lives his life: a checked second brain, a crew of AI agents, and one calendar that never forgets. The whole system is free and open.

Get new posts by email

I build this in public and post the progress. Follow along on Substack.

bottom of page