Start with a problem someone wants to solve
The first decision is to identify a problem important enough to justify a purchase. Before comparing platforms or formats, I want to understand who faces that problem, what they currently do about it and where they lose time, money or opportunities. These answers help define an offer that is useful in a specific situation.
A company may need to organise its sales contacts, but several offers could address that need. It could buy an implementation service, learn to configure the system itself or subscribe to a tool that simplifies part of the work. The need is similar; the seller's responsibility changes considerably between these options.
Write down the expected outcome, the conditions required and who performs each part. If customers need ongoing help to use what they buy, that support belongs in the delivery design and the price. A seemingly simple product may require more service than its founder anticipated. This analysis comes before defining your positioning and value proposition.
Services: proximity and delivery capacity
In a service model, the company takes responsibility for carrying out work or supporting a decision. Close contact helps it understand individual customers and adapt its response, but creates demands on capacity, coordination and scope control. Growth depends on selling work the team can actually deliver to the expected standard within the agreed conditions.
Distinguish selling hours, selling a defined deliverable and selling ongoing support. A fixed deliverable needs acceptance criteria; a retainer needs clarity about recurring work; time billing needs visibility over how that time is used. None of these choices removes the need to manage expectations before and during the engagement.
Before increasing acquisition, estimate how many projects can run simultaneously. Include meetings, revisions, preparation and information handovers, alongside the most visible production work. A full schedule can coexist with weak margins when actual effort regularly exceeds the estimate. The guide to growing a service business develops this relationship between the offer, sales and operations in greater detail.
Training: learning with conditions for application
A training business organises knowledge to help someone develop a capability. Its format may include recorded material, live sessions or support, but its value depends on suitability for the participant's starting point. Define what will be learned, what practice will be required and what assistance is actually included when someone enrols in the programme.
Producing material requires initial work, and keeping training useful requires updates. Questions, access difficulties and differences in participants' experience can also consume regular resources. Being able to distribute the same material many times does not automatically make the operation independent of the team responsible for running it.
Separate learning, implementation and support in the offer. Someone buying a course should not discover afterwards that an additional service is necessary for an outcome they thought was included. Testing a first edition with clear scope helps reveal demand, difficulties and delivery effort before expanding the catalogue. The page on online training businesses explores these decisions further.
Digital products: repeatability with maintenance
A digital product aims to deliver repeatable usefulness through a resource or system that different customers can use. Repeatability may reduce some effort per sale, but does not remove support, updates or responsibility for reliable operation. Consider the complete journey, from the first use to the resolution of problems that arise later in the relationship.
A document template, an application and a resource library have different needs. The template may require completed examples; the application needs availability and fixes; the library needs organisation and updates. Pricing and access arrangements should reflect the commitment the seller is making to the people who purchase it.
Start by observing real use. If everyone needs a lengthy explanation to reach their first useful result, there is unresolved product or support work. Record the difficulties and decide which should disappear from the experience and which justify a separate service. Adding features without understanding those difficulties tends to increase complexity while leaving the value of the purchase unclear.
Recurring revenue: continuing value and work
A recurring model charges for continued access, service or support. It needs a repeating customer need and a delivery that remains useful after the initial purchase. Revenue becomes more predictable only when customers actually stay and the company has the capacity to fulfil its commitment throughout the relationship, rather than simply collecting a regular payment.
A software subscription, a community and a monthly service retain customers for different reasons. Daily usage may matter in one case, relationships and access to guidance in another, and the completion of necessary tasks in the third. Explain that continuity through concrete examples of how customers will use the offer.
Review customer arrivals and departures, cancellation reasons and maintenance effort. A growing customer base may also accumulate requests the team can no longer handle properly. Separate onboarding work from monthly work to understand whether the price and capacity support both. Charging every month is a billing arrangement; remaining useful every month is an operational responsibility that must be designed into the business.
Compare options using a decision matrix
A useful matrix compares models through the same questions, using observations and clearly identified assumptions. Demand, initial effort, effort per customer, acquisition and continuity make the differences visible. The purpose is to choose the next experiment on a reasoned basis, without treating an arbitrary score as certainty about which business will work best for someone.
| Model | What to validate first | Effort to observe | Reason to return |
|---|---|---|---|
| Service | Trust in delegated execution | Hours, revisions and coordination | Another need or ongoing support |
| Training | Willingness to learn and apply | Preparation, support and updates | Another capability or deeper learning |
| Digital product | Usefulness in actual use | Development, support and maintenance | Repeated use or new problems |
| Subscription | A continuing need | Onboarding and recurring delivery | Value that remains over time |
Complete the matrix for your particular offer. Add what you already know, where that information came from and the hypothesis still requiring a test. A model may look more attractive simply because its costs are less visible on paper. Comparing explicit assumptions helps correct that imbalance before you commit further time, money or people to developing the idea.
Test a model before multiplying offers
The first test should address the uncertainty that most affects your choice of model. This might be willingness to pay, delivery capacity, independent product use or willingness to renew. Decide beforehand what you will observe and how the result will change your decision, including the possibility of reshaping or stopping the experiment when evidence supports it.
Avoid launching several formats simultaneously while you cannot distinguish each one's contribution. A service may reveal needs that later justify training or a product, but that development requires its own analysis. Sharing an audience does not mean that all offers have the same sales process, delivery requirements or reasons for repeat purchase.
Through individual business mentoring, we can work on these choices in your context. Use the form to describe the customer, current offer, team and main uncertainty about the model. What you have already tried and learned matters, so the conversation begins with a real business decision and the evidence available to make it.