The Business Planner.

Worked Example

From Idea to Business: A Real Example Breakdown

Theory is easy to nod at and hard to apply. So this is a worked example: a fictional but realistic founder, a vague starting idea, and the exact sequence of structural decisions that turn it into a business. Read it like a transcript. The same sequence works for almost any early-stage idea.

The starting point

Maya is a former operations lead at a Series A startup. She left last year and has been freelancing since. Her current pitch:

"I help startups with operations. Like, systems, processes, hiring, whatever they need."

She's getting referrals, but every project is custom, every quote is a fresh negotiation, and her calendar is full while her bank account is flat. She has an "idea" of the business but no structure.

Decision 1 — Pick a customer narrowly

"Startups" is not a customer. After 30 minutes of guided narrowing, Maya lands on:

"Seed-stage B2B SaaS founders, 5–15 employees, post-product, who just hired their first non-founder ops or RevOps person and need the operating system written down."

That sentence has role (founder), situation (5–15 employees, post-product), and trigger (just hired first ops person). It's uncomfortably narrow. Good.

Decision 2 — Define the outcome in their words

Not "I'll improve your operations." The outcome from the customer's point of view:

"In 30 days, you'll have a documented operating system—weekly cadence, decision rights, hiring scorecards, and an SOP library— so your new ops hire can run the company without you in every meeting."

Now the customer can picture the finished state. That's an outcome.

Decision 3 — Productize the offer

Maya structures her offer as a single productized engagement she calls the Operating System Sprint:

  • Scope: weekly cadence design, RACI, hiring scorecards for next 3 roles, top-15 SOPs.
  • Timeline: 30 days, fixed.
  • Deliverables: a Notion workspace handed over to the new ops hire.
  • Guarantee: if the ops hire can't run the weekly cadence solo by day 35, Maya runs it free for 30 more days.

The offer is now a structured promise—not a vibe. (See how to create a profitable offer.)

Decision 4 — Price it deliberately

Old pricing: hourly, around $150/hr, 30–50 hours per project. Effective price: $4,500–$7,500 per engagement, fully variable.

Outcome value: for a Series A SaaS company, freeing the founder from operating in every meeting unlocks weeks of founder time per quarter—worth tens of thousands of dollars in opportunity cost.

New price: $15,000 flat for the 30-day Operating System Sprint. Anchored to the outcome, not the hours. (See how to price your offer.)

Decision 5 — Pick one channel

Maya considered LinkedIn, Twitter, cold email, partnerships with VC firms, and a podcast. She picked one: warm intros from 2 specific seed-stage VC firms whose portfolios match her narrow customer.

Reason: that's where her customer already gathers, and her offer is explainable in a single intro email. Once that channel produces 2 engagements/month consistently, she'll add a second.

Decision 6 — Map the delivery

Before selling the new offer, Maya wrote out the 30-day delivery plan:

  1. Week 1: discovery + cadence design.
  2. Week 2: RACI + decision-rights doc + first 5 SOPs.
  3. Week 3: hiring scorecards + next 5 SOPs + ops hire shadow week.
  4. Week 4: ops hire runs cadence; Maya observes and adjusts; final 5 SOPs; handover.

Templates for each artifact already exist (or get built once and reused). Delivery is now repeatable—not heroic.

Decision 7 — Pressure-test with 5 prospects

Maya pitches the new offer to 5 fit founders from her network. Results:

  • 2 want to start within 30 days.
  • 1 says "love it, not yet—Q3."
  • 1 pushes back on price ($15K feels high). Maya holds.
  • 1 isn't a fit (too early-stage; no ops hire yet).

Signal is strong enough to commit. She doesn't change the price. She adjusts the language on the offer page based on how the 5 described the problem.

Decision 8 — Write the model on one page

Maya's one-page model now reads:

  • Customer: seed-stage B2B SaaS founders post-product, 5–15 employees, just hired first ops/RevOps person.
  • Problem: founder is the operating system; new ops hire has nothing to inherit.
  • Outcome: documented OS handed to ops hire in 30 days.
  • Offer: Operating System Sprint, 30 days, fixed scope, fixed price.
  • Price: $15,000 flat, 50% on signing, 50% on day 15.
  • Channel: warm intros from 2 seed-stage VC firms.
  • Delivery: 4-week sprint, templates + handover.
  • Bottleneck: maintaining intro flow from VC partners; she sets a monthly cadence with both.

What changed in 14 days of structuring

  • The pitch went from a sentence she dreaded saying to one she could finish.
  • Pricing tripled, with no pushback from fit prospects.
  • Delivery became repeatable instead of heroic.
  • Channel went from "everywhere" to one focused source.
  • The business stopped feeling foggy and started feeling like a system.

The point of the example

Maya didn't get a better idea. She made the structural decisions her existing idea required. Every founder has a version of these eight decisions waiting to be made. Most never make them—not because they can't, but because no one walks them through it.

If you'd rather not do those eight decisions alone, that's the work. Apply when you're ready.

Next step

Stop guessing. Get your business structured.

If your idea feels unclear, unstructured, or stuck—this is where that changes. Apply to work directly with a startup business strategy consultant who builds the model, the offer, the pricing, and the launch plan with you.

Back to home →

Keep reading