◆ Idea Factory
← All resources

The Plan-As-You-Go Business Plan

Tim Berry · 2008 · Entrepreneur Press

Lean PlanningIterative

Overview

The Plan-As-You-Go Business Plan by Tim Berry challenges one of the most persistent myths in entrepreneurship: that a business plan is a document you write once, hand to a bank or investor, and then file away. Berry, founder of Palo Alto Software and the business planning resource Bplans.com, argues that this static, document-first view of planning is exactly what makes planning feel pointless to so many entrepreneurs. His alternative is a philosophy and a process rather than a template: start small, iterate constantly, and let the plan grow with the business.

Berry is one of the most experienced practitioners in the field. Palo Alto Software, which he founded, built Business Plan Pro, for many years the best-selling business plan software in the United States. His proximity to thousands of real plans gave him a clear view of what works in practice versus what looks good in theory. The book reflects that experience: skeptical of elaborate plans that take months to write, pragmatic about what planning can actually accomplish, and insistent that the value of planning lies entirely in what it does for the business — not in what it looks like on paper.

Published by Entrepreneur Press in 2008, the book arrived at a moment when lean startup thinking was reshaping entrepreneurship. Berry’s ideas were an early articulation of the same instincts — keep plans light, assume change, iterate fast — applied to business planning specifically.

The core framework: the PRRR cycle

The book’s central contribution is reframing planning as an ongoing management cycle rather than a one-time deliverable. Berry describes this as the PRRR cycle: Plan, Run, Review, Revise.

  • Plan. Build the minimum plan your business actually needs — not a comprehensive document for outsiders but a set of interlocking components for internal use: a strategy summary, key tactics, essential financial forecasts (sales, costs, cash flow), and execution specifics (milestones, task assignments, deadlines, assumptions).
  • Run. Execute the business. Let the plan inform decisions and resource allocation in real time.
  • Review. At a scheduled interval — Berry recommends monthly reviews of 60 to 90 minutes and quarterly reviews of two to three hours — compare actual results to the plan. Were the assumptions valid? Were milestones hit? Where is cash behaving differently from the forecast?
  • Revise. Update the plan based on what the review reveals. New assumptions rise to the top. Strategies are adjusted. Milestones are reset. Then the cycle begins again.

The PRRR cycle is Berry’s lean-planning adaptation of the classic Plan-Do-Check-Act (PDCA) cycle from manufacturing. The key word is cycle: a plan that is not reviewed and revised is not a plan-as-you-go plan — it is just a plan.

Key concepts

Start with the review schedule. Berry’s most counterintuitive instruction is to build the review schedule into the plan from day one — before most of the content is even written. If no review dates exist, no review will happen, and without reviews the plan is inert. Establishing who meets, when, and for how long is not an administrative detail; it is what separates planning-as-process from planning-as-document.

Keep assumptions visible. Every plan contains assumptions — about market size, pricing, conversion rates, hiring timelines, customer behavior. In a static plan those assumptions are buried in the prose and forgotten. In a plan-as-you-go approach they live at the top of the document, explicitly listed, so they can be challenged at every review. The plan is a navigation tool: if the map’s assumptions turn out to be wrong, the map must be updated.

The heart, flesh, and bones of a plan. Berry uses this metaphor to describe what a lean plan must contain. The heart is strategy: market need, differentiation, competitive focus. Without a clear strategic heart, there is nothing to execute toward. The flesh and bones are the operational specifics: milestones, tasks, dates, deadlines, responsibility assignments, and — most critically — cash flow planning. Both are required; neither alone is sufficient.

Good plans are never finished. A completed business plan signals a finished business. Living companies continuously revise their plans as they learn. The goal is not a polished document; it is a continuously calibrated view of where the business is headed and how it intends to get there.

The lean plan vs. the formal plan. Berry distinguishes sharply between the internal lean plan — a collection of bullet points, tables, forecasts, and milestones kept for the management team — and the formal business plan required occasionally for external audiences. The lean plan is the real tool; the formal plan is a presentation layer built on top of it when needed.

Start anywhere. Because the lean plan is a set of interlocking blocks rather than a sequential document, there is no required starting point. Some founders begin with a sales forecast; others begin with the strategy statement. Either is valid. The imperative is to start — not to wait until everything is ready.

How to apply it to your blueprint

Begin by identifying the smallest plan that would actually be useful to you this week: a one-paragraph strategy statement, a rough twelve-month sales forecast, and the five milestones that matter most in the next quarter. Write those down. Then immediately set a review date — a specific day, one month from now, when you will compare actuals against expectations.

At that review, ask three questions: Which assumptions held? Which did not? What does the plan need to say now that it did not before? Update accordingly and set the next review date. Repeat.

As the business develops, the plan grows organically. Financial forecasts become more detailed as revenue becomes more predictable. Hiring milestones appear as the team grows. The plan-as-you-go approach means you always have a current, useful plan because you are always maintaining it.

Strengths and limitations

The approach’s core strength is that it breaks the planning paralysis that afflicts many entrepreneurs. By starting small and emphasizing process over document, it makes planning immediately accessible rather than a deferred obligation. The PRRR cycle is also grounded in real management practice: the plan-versus-actual review is the same discipline that finance teams in large organizations use every month. Berry brings that discipline to small business in a form that requires neither a large team nor complex software.

The limitation is that the book’s value is proportional to the discipline of the founder. The PRRR cycle only works if the reviews actually happen on schedule. Entrepreneurs who are easily consumed by execution often find that the monthly review slips, the plan drifts out of date, and the lean plan becomes as inert as the traditional plan it was supposed to replace. The book also does not provide a detailed template for the external formal plan that lenders and investors request; entrepreneurs who need to raise capital may need to supplement it with more investor-focused guidance.

Key takeaways

  • A business plan is a process, not a document; its value lies in the regular cycle of reviewing and revising it, not in the quality of any single version.
  • The PRRR cycle — Plan, Run, Review, Revise — is the central management discipline; without scheduled reviews, planning has no feedback loop.
  • Keep assumptions explicit and visible at the top of the plan so they can be challenged at every review.
  • Start with the minimum useful plan and let it grow naturally from the questions that regular reviews surface.
  • The lean internal plan and the formal external plan are different artifacts; most businesses need only the former most of the time.
  • Cash flow planning is the highest-priority component of the flesh-and-bones layer; it is where plans most commonly break down in reality.

How it maps to the Business Idea Factory

Berry’s plan-as-you-go philosophy is the intellectual backbone for the app’s emphasis on revisiting and refining an idea across multiple frameworks rather than producing a single definitive output. The milestone and assumption concepts map directly to the Business Blueprint questionnaire’s execution and risk sections. The PRRR cycle’s plan-versus-actual discipline provides the rationale for tracking how a business idea evolves as market feedback accumulates. Entrepreneurs using the Lean Canvas and SWOT frameworks are, in Berry’s terms, doing the Review and Revise steps — surfacing new assumptions, adjusting strategy, and updating the plan. This book argues that the habit of regular review is more valuable than any single framework output.

References