A business model explains who receives value, what they exchange, how the business delivers, when cash moves, which costs follow activity, and what limits capacity. Compare a few plausible models against customer behavior and operating reality. Choose a testable starting model, not the model with the most attractive spreadsheet outcome.
Who this is for: Founders and small business owners comparing practical ways to deliver value and receive revenue from a clearly defined customer group.
- Connect customer value, payer, payment event, delivery system, cost behavior, and capacity in one model.
- Compare alternatives using the same assumptions and include cash timing, support, risk, and founder fit.
- Pilot the weakest link before committing to systems, contracts, or forecasts built around the model.
Map value and payment
The user, beneficiary, buyer, and payer may be different people, especially in business and institutional markets. The decision is which value-delivery and payment pattern deserves a limited operating test. State assumptions and separate direct observations from interpretation.
Name each role, the value received, purchase trigger, payment event, frequency, terms, and reason the exchange may stop. Look for customer purchase behavior, delivery trials, supplier terms, cost records, payment timing, support demand, and capacity observations. Record support, contradictions, unknowns, and the next decision this evidence can change.
Model delivery and capacity
Revenue logic must fit how work is produced, delivered, supported, and repeated. The decision is which value-delivery and payment pattern deserves a limited operating test. State assumptions and separate direct observations from interpretation.
Map labor, tools, inventory, partners, quality checks, support, bottlenecks, and what changes when volume changes. Look for customer purchase behavior, delivery trials, supplier terms, cost records, payment timing, support demand, and capacity observations. Record support, contradictions, unknowns, and the next decision this evidence can change.
Compare cash and risk
Two models with similar accounting revenue can create very different cash timing and obligations. The decision is which value-delivery and payment pattern deserves a limited operating test. State assumptions and separate direct observations from interpretation.
Compare collection timing, refunds, direct costs, fixed commitments, concentration, cancellation exposure, and operational failure points. Look for customer purchase behavior, delivery trials, supplier terms, cost records, payment timing, support demand, and capacity observations. Record support, contradictions, unknowns, and the next decision this evidence can change.
Test the weakest connection
The model should be tested where an unsupported assumption could break the whole exchange. The decision is which value-delivery and payment pattern deserves a limited operating test. State assumptions and separate direct observations from interpretation.
Choose a manual pilot, real offer, supplier quote, workflow trial, or payment test and define the decision rule beforehand. Look for customer purchase behavior, delivery trials, supplier terms, cost records, payment timing, support demand, and capacity observations. Record support, contradictions, unknowns, and the next decision this evidence can change.
Compare project and retainer models
A research specialist is deciding between fixed projects and an ongoing monthly service for small product teams. Every quantity in this worked example is a hypothetical input used only to show the method. It is not a benchmark, forecast, validation rate, or claim about likely results.
- Map the buyer, recurring need, deliverable, approval process, payment timing, and stopping condition for each model.
- Use hypothetical workload, price, direct cost, and collection timing inputs to compare capacity and cash exposure.
- Ask buyers about recent purchasing behavior and offer limited versions of each model without claiming either will retain clients.
- Select the model whose risks can be tested with the smallest responsible commitment and record contrary evidence.
Business model comparison canvas
Use one column per model and keep assumptions linked to evidence.
- User, beneficiary, buyer, payer, trigger, value, and alternative.
- Offer unit, payment event, frequency, terms, refund, and collection timing.
- Delivery workflow, labor, tools, partner, support, quality, and capacity.
- Direct cost, fixed commitment, cash exposure, concentration, and failure risk.
- Evidence, weakest assumption, pilot, decision rule, and review point.
Common mistakes
- Choosing subscriptions, marketplaces, or retainers because the label sounds attractive rather than because behavior supports the exchange.
- Ignoring who pays, when cash arrives, and what service obligation continues after payment.
- Using hypothetical model outputs as forecasts of growth, retention, or profitability.
Try one
A founder prefers a subscription because recurring revenue looks predictable, but customers buy only during occasional projects. Evaluate the fit.
The observed purchase pattern conflicts with a continuing payment assumption. The founder should identify recurring value that genuinely warrants recurring payment or test a project, credit, maintenance, or support model instead. Spreadsheet smoothness is not customer evidence, and a subscription does not create retention by itself. A strong response names uncertainty and avoids predicting outcomes from assumptions. Professional advice may be needed for contracts, recurring billing, automatic renewal, refunds, taxes, licensing, insurance, or regulated delivery obligations.
Sources
- SBA business plan guideOfficial guidance on traditional and lean startup business plans.
- SBA business finance guideOfficial overview of bookkeeping, balance sheets, cost-benefit analysis, and business finance management.