A broad service tells people the field you work in. A narrow offer tells them what problem you will address and what they will receive. Both can be useful, but they serve different stages. For a first paid engagement, a narrow offer is usually easier to explain because fewer assumptions remain hidden.
What “broad” and “narrow” mean
“Marketing support,” “operations consulting,” and “design services” are broad. They leave the buyer to determine which tasks, channels, limits, and outputs apply. “Review one landing page and return an annotated clarity report” is narrow. It identifies an object and deliverable without claiming that the page will convert at a particular rate.
The explanation test
Give each version twenty seconds. A listener should be able to answer four questions: Who is it for? What problem does it address? What will be delivered? What is outside the engagement? If the explanation requires a menu of unrelated services, the offer is probably too broad for a first transaction.
Where a broad service helps
- You are introducing your general professional category.
- The buyer already understands your capabilities from direct experience.
- The engagement genuinely requires diagnosis before scope can be defined.
- You maintain several mature offers and need an umbrella description.
Even in these cases, the paid work still needs a defined scope before it begins.
Where a narrow offer helps
- The buyer has never worked with you.
- You need to estimate effort with limited delivery history.
- The work can be reviewed through a visible artifact.
- You want to learn from one repeatable problem rather than many unrelated requests.
- You need a clean boundary between the offer and additional work.
Comparison through one example
Consider “website help” versus “content inventory for a site containing up to thirty public pages.” The narrow version can specify the crawl method, spreadsheet fields, exclusions, buyer-provided access, and review point. It should not promise traffic growth or rankings. The broad version may attract more kinds of questions, but it also creates more discovery work and a greater risk of mismatched expectations.
Narrow does not mean trivial
A narrow offer can solve an important problem. Narrowness refers to the boundary, not the value. A clearly structured executive presentation, a reconciled list, or an accessibility review of a defined asset may be highly useful. Avoid shrinking the offer so far that the deliverable no longer addresses a meaningful buyer need.
Watch for false precision
Adding an arbitrary page count or turnaround time does not automatically make an offer good. The limit should reflect capacity, inputs, and quality requirements. Do not advertise “24-hour delivery” unless you can support it under realistic conditions and state when the clock begins. Never use an artificial deadline or fake scarcity to force a decision.
Fit decision
Choose the narrow version when you can define a standard input, process, output, and review. Keep a broad description only as a category label. If every buyer requires a different process before you can name the deliverable, use a paid diagnostic or written scoping step rather than pretending the work is standardized.
Switching triggers
Broaden later when repeated delivery shows that buyers reliably need adjacent work and you can price and control it. Narrow further when explanations lead to different interpretations, estimates vary widely, revisions repeatedly add new outputs, or delivery depends on unstated access. A switching trigger should come from observed friction, not the hope that a broader label will attract everyone.
Final decision record
Write both versions side by side. Underline every noun that could mean different things to different buyers. Circle the deliverable, the buyer input, and the acceptance point. Select the version with fewer unresolved terms. Then record the event that would justify changing it, such as three completed engagements showing the same adjacent need. This keeps the decision evidence-based rather than permanent.
Conversation test for both versions
Test the descriptions without pitching. Ask a peer to restate each version and list the questions it creates. Broad descriptions usually produce category questions: “What kind of marketing?” or “Which operations?” Narrow descriptions should produce fit questions: “Does the page limit include the homepage?” Fit questions are useful because they reveal boundaries that can be clarified. Category confusion means the buyer still cannot picture the service.
Do not treat agreement from friends as demand validation. The test measures explanation, not willingness to pay. A real offer test requires an ethical buyer decision with the price, scope, and limitations visible.
Measure explanation quality, not enthusiasm
After each conversation, record what the listener thought the service included, which words required explanation, and whether they could name the deliverable. A positive reaction is pleasant but weak evidence. A precise restatement shows that the offer is understandable.
Use the same test sentence for several conversations before revising it. Changing the wording after every reaction makes patterns impossible to see. If listeners consistently understand the narrow version and misread the broad one, keep the narrow offer as the transactional unit and use the broad phrase only as a professional category.
Do not narrow through arbitrary buyer labels
A niche should connect to a real workflow or constraint. “For women,” “for veterans,” or “for local businesses” does not automatically improve the offer. Narrow by the object, situation, platform, stage, or required deliverable when those factors genuinely change the work. Avoid targeting based on protected or sensitive characteristics unless there is a lawful and necessary reason.