Most people who set out to build something around their expertise start the same way: they try to describe everything they know. Thirty years of work goes onto one page, the page gets longer, and by the fourth paragraph the idea has gone vague. Nobody is sure what is being offered, least of all the person offering it.
That is not a confidence problem. It is a scoping problem.
A business is never built around everything you know. It is built around a narrow slice — one problem you understand unusually well, for a person who wants it gone, delivered in a way you can repeat. Everything else you know stays with you, in the quality of your judgment and the questions you think to ask. It just does not go on the label.
So the useful question is not whether your experience has value. It is which part of it to point at first.
Experience is raw material, not an offer
If you have already accepted that your experience is worth more than you think, the next step is less flattering and more useful: raw experience, in the form you currently hold it, is not yet something anyone can buy.
Experience is stored as pattern recognition. You know what a struggling process looks like from across the room, and which shortcut will cost someone six months later. None of that is organized; it surfaces when a situation triggers it.
An offer is the opposite. It is deliberately narrow, described in advance, and repeatable. It names a situation, names what changes, and names what it costs.
Turning one into the other is mostly subtraction. You are not adding credentials or a bigger story — you are choosing what to leave out.
Look for the problems people kept bringing you
One of the most useful signals is not what you are proudest of, but what other people repeatedly came to you for.
Over a long career, people sorted you without telling you. Colleagues learned who to ask about which things; clients learned whose call to return first. That sorting already happened, over years, for free — worth mining deliberately now. Take a blank page and work through a short inventory:
- What did coworkers, clients or managers repeatedly ask you to look at?
- What could you diagnose in ten minutes that took someone less experienced a week?
- What mistake have you now watched a dozen different organizations make?
- What took you years to learn that you could hand someone in an afternoon?
- What did people apologize for bothering you about, because it was outside your job description?
Write down more than you think you need, then read the list for repetition rather than for brilliance. The item that appears in three different jobs, under three different names is often the one worth building on. As a working rule, favour frequency over prestige: a problem you have solved again and again usually tells you more about demand than the impressive thing you did once.
Separate what you know from what you produce
This is the distinction most people never make, and it decides whether an idea becomes an offer or stays a description.
"I know quality management" is knowledge. It tells a buyer what field you are in and nothing about what happens to them.
"I help small manufacturers get ready for ISO 9001 certification without building a paperwork system they cannot maintain afterward" is an outcome. It names who, it names the situation, and it names what is different at the end — including the failure mode the buyer is quietly worried about.
"I know project management" is knowledge. "I help small service companies build a simple handoff between sales and delivery so work stops falling through the gap" is an outcome.
In each rewrite the field name disappears, a specific person appears, and a before-state and after-state appear. The sentence also gets easier to say out loud, because it describes work rather than making a claim about yourself.
A useful test: read it to someone outside your industry. If they can tell you what would be different for the buyer afterward, you have an outcome. If they can only name the subject, you still have knowledge.
Decide who actually has the problem
"Anyone who needs this" is not an audience. It is a way of avoiding the decision.
The reason to choose narrowly is not marketing theory. Problems behave differently depending on who has them. A small manufacturer and a very large one both need quality systems, but they have different budgets, different politics, different people deciding, and different reasons the last attempt failed. An offer that tries to serve both describes neither.
Narrow enough usually means you can picture a specific organization, describe what set the problem off, and name who would sign off on fixing it. You do not need a persona document — only enough specificity that the right person recognizes themselves when you describe the problem.
Two questions do most of the work. What has to be true about someone for this to be a real problem rather than an annoyance? And what usually happens right before they go looking for help — a failed audit, a lost client, a resignation, a deadline? That trigger is often more useful than any demographic detail. The deeper version is covered in finding your ideal audience without guessing.
Choose the smallest useful offer
Once you know the problem and the person, the temptation is to design something comprehensive. Resist it. Your first offer should be the smallest piece of work producing a result the buyer can recognize.
Small does not mean trivial or free. It means bounded. A two-week assessment ending in a prioritized list of what is actually wrong is a real offer. So is a half-day working session that settles a decision the client has been circling for months, or a single documented process written in a form their team will use.
The reasons are practical. A bounded piece of work is easier for a buyer to say yes to, and easier for you to price. It finishes, so you find out quickly whether you enjoy the work and whether they value the result. And it often reveals the next problem — the one the client did not mention, which frequently turns out to be the better business.
The most common mistake is sizing the first offer to your experience rather than to the buyer's appetite. Thirty years of expertise does not oblige you to sell a thirty-week engagement.
Let the problem choose the delivery format
Format follows the problem, not the other way around.
If the problem needs judgment applied to a specific situation, it wants a conversation: a consultation, an assessment, a short advisory arrangement. If it needs a decision from a group, it wants a workshop. If the same work must be done the same way by many people, it wants a template, checklist or documented process. If people need to build a capability, it wants training. If the client wants the thing done rather than explained, it wants an implementation engagement.
It is worth saying plainly that a course is not automatically a better business than consulting, and a product is not automatically better than an engagement. Direct work is often the fastest-learning, lowest-overhead version of an expertise business, and remote consulting has become a realistic way to do it without geography deciding your clients. There is no rule that a real business must eventually become something you sell in your sleep.
Choose the format that fits the problem and suits how you want to spend your week.
Test the offer before you build the machinery
Almost everything that goes wrong early goes wrong the same way: months spent building infrastructure around an offer nobody has agreed to buy.
The website, the course library, the video series, the community, the branding exercise, the automated sequences — none of these teach you whether the problem is real, whether your framing lands, or whether anyone will pay to have it solved. They are all reasonable things to build later, once you know what you are building them around. Built first, they absorb the time and money you need to find out.
The test is smaller and far less comfortable. Describe the offer, in one or two sentences, to a small group of people who plausibly have the problem; former colleagues and old clients are the obvious place to start. Listen for whether they recognize it in your words or quietly rephrase it into something else — the rephrasing is the most valuable information you will get. Then ask what they have already tried, and what it cost them.
One particularly useful signal is someone willing to pay for the small version. A paid engagement, even a modest one, usually tells you more than a run of encouraging conversations, because agreeing that something is a good idea costs nothing and buying it does not. It does not prove the business will work — it tells you the problem is worth money to at least one person, which is more than you knew before. If you want to go further on reading demand before committing, the next step is validating the idea properly.
What you are trying to learn is narrow: does this problem hurt enough that someone will pay to make it stop? Everything else can be worked out later.
Growth is optional, not obligatory
There is a natural progression available if you want it. Direct expertise becomes a repeatable service; the service gets documented; the documentation becomes training or a product. Some of that eventually runs with less of your time in it, and at that point you are building an asset you actually own rather than a job you invented.
But treat that as a menu, not a staircase. A practice with a handful of good clients does not owe anyone a course, a membership or a software product. Each step up adds audience-building, support and maintenance work that some people enjoy and others find has cost them the work they liked. Know the progression exists mainly so you can stop, deliberately, at the rung that suits you.
What to build first
In order, and not much of it:
One sentence that names the problem, the person and the outcome. A short description of the small first offer, with a scope and a price. A short list of people who might plausibly have the problem or know someone who does. Then the conversations.
Not a logo. Not a content calendar. Not a course outline. Those come after someone has paid you to solve the problem once, because that first engagement will change your sentence — and it is cheaper to change a sentence than a website.
If your starting point is a subject you want to write about rather than a problem you want to solve, choosing a first digital business idea is the better place to begin. But if you are sitting on decades of work wondering what part is sellable, the answer is almost never all of it, and almost always the thing people kept coming to you for anyway.
You have been solving that problem for years. The only new work is naming it, putting a price on it, and saying it out loud to someone who needs it solved.
