Give the Product Its Own Position

Task

Define product positioning separate from consulting.

Summary

Explain the product independently of the service wrapper that originally revealed the problem.

Position the Product So Buyers Do Not Mistake It for Consulting

Task ID: S3-03

A standalone product needs a market meaning that does not depend on the founder’s expertise or a custom project. This article explains how to choose the product’s category, define its customer promise, separate software value from implementation help, test message clarity, and produce a positioning brief that sales and product teams can use without overstating what the product can do.

When the product still sounds like a project

A company can build useful software and still sell it as though it were consulting. The demo begins with the founder’s experience. The proposal describes discovery workshops, analysis, recommendations, and custom configuration. Buyers ask who will do the work rather than what the product enables them to do. When the founder leaves the call, the offer becomes harder to explain.

That is a positioning problem before it is a copywriting problem.

Positioning is the deliberate choice of how a product should be understood relative to the alternatives a buyer already knows. The American Marketing Association describes brand positioning as defining an organization’s place in the market relative to competitors and using that choice to guide communication of value and benefits. For a company moving from custom work to software, the central question is more specific:

What can the customer buy, use, and benefit from without purchasing the company’s judgment by the hour?

The answer must be visible in the product’s category, promise, proof, price, demo, onboarding, contract, and support model. A polished tagline cannot compensate for an offer whose core result still depends on unbounded expert work.

The distinction is not that products are automatic and consulting is human. Many enterprise products require migration, configuration, training, or change management. The distinction is what creates the repeatable value.

These are operating distinctions, not moral judgments. A consulting business can be excellent. The problem arises when a company claims to have a standalone product while the product’s promised result is still delivered mainly by consultants.

The product needs its own market meaning

The operating principle is simple: position the product around a customer problem and repeatable product outcome; position consulting as bounded help that accelerates, adapts, or extends that outcome.

This work belongs after the company has learned from real customer projects but before it depends on software sales for repeatable growth. Earlier client work should have produced evidence about the customer, the problem, the trigger to buy, the repeated tasks, and the result customers value. Positioning turns that evidence into a market choice. It does not create evidence that is missing.

The separation should show up in five decisions:

1. Target customer: the specific buyer and user in a recognizable situation.
2. Category: the kind of product the buyer should compare it with.
3. Promise: the result the product itself enables.
4. Difference: why the product is a better choice than the buyer’s real alternatives.
5. Service boundary: the help available around the product, including what is required, optional, partner-delivered, or out of scope.

The service boundary is especially important in design-partner sales. Early customers often receive unusual access, custom configuration, and founder attention. Those arrangements are useful for learning, but they can make a weak product appear complete. The positioning brief must therefore distinguish what the product does today from what the team did manually to make the customer successful.

A useful internal statement is:

For [specific customer in a buying situation], [product] is a [recognized category] that helps them [achieve a concrete outcome]. Unlike [current alternative], it [meaningful difference], supported by [credible proof]. Consulting is [required, optional, or not offered] for [bounded activities]; it is not required for [the core product value].

This is an internal decision tool, not necessarily website copy. Its purpose is to force choices that can be tested.

Choose the category before writing the narrative

A buyer needs a frame of reference. The category tells the buyer what the product is, which budget it may come from, who should evaluate it, and which alternatives belong in the comparison set. Without a category, a sales conversation spends too much time explaining the concept and too little time establishing value.

Research on brand categorization supports a balance between familiarity and difference. In four studies, Mita Sujan and James Bettman found that a moderately discrepant brand tended to be perceived as differentiated within a category, while a strongly discrepant brand was more likely to be treated as a niche subtype. Research on new ventures also finds a recurring tension: fitting a recognized category can increase legitimacy, while spanning categories can create differentiation but may also produce an “illegitimacy discount” when audiences do not know how to evaluate the venture.

That leads to three practical category choices.

Creating a new category should be a business decision, not a desire to sound original. Research on the emergence of satellite radio found that early market actors first had to establish the legitimacy of the category before attention shifted toward differences among firms. A small company that invents a category therefore takes on two jobs: persuade buyers that the category matters and persuade them that its product is the best choice within it.

For most companies separating software from consulting, the safer starting point is a familiar product category with a precise customer and use case. The product can then be distinctive in the outcome, workflow, data, speed, control, or economic model without forcing the buyer to learn an entirely new market language.

The category decision should be followed by a short narrative that explains change without turning into a company biography:

• The customer is trying to accomplish a specific job.
• The current approach creates a costly or risky problem.
• A change in the customer’s environment makes the old approach less acceptable.
• The product provides a different way to complete the job.
• Evidence shows why the claim is believable.

The narrative should begin with the customer’s situation, not with the consultancy’s history. Official user-research guidance from the UK government makes the same underlying point for service design: teams should understand who users are, what they are trying to do, how they currently do it, and the problems they experience, while treating non-user opinions as assumptions to be tested.

Build a positioning brief that forces real choices

A credible positioning brief is short enough to use and detailed enough to prevent the old consulting offer from reappearing under product language. The brief should contain decisions, supporting evidence, and unresolved assumptions.

The customer side and the product side should be kept separate during the analysis. Strategyzer’s guidance on its Value Proposition Canvas warns against mixing several customer segments, starting with the solution rather than the customer, and trying to address every pain and gain. It recommends focusing on the highest-priority customer jobs, pains, and gains rather than claiming universal relevance.

The same discipline applies here. A product positioning brief should not merge the economic buyer, administrator, daily user, and consulting sponsor into one fictional persona. Their needs may overlap, but their reasons to care, objections, proof requirements, and language can differ. Choose the primary audience for the first message, then document secondary messages separately.

The following flow shows the order of decisions. In text: begin with evidence from customer work, choose one buying situation, select a category, state the product outcome, define the alternatives and difference, draw the service boundary, and test whether buyers can explain the product correctly.

flowchart TD
    A[Evidence from customer work] --> B[Choose one buying situation]
    B --> C[Select the product category]
    C --> D[State the product outcome]
    D --> E[Define alternatives and difference]
    E --> F[Set the consulting boundary]
    F --> G[Test with target buyers]
    G --> H{Can buyers explain the product without consulting?}
    H -->|Yes| I[Approve and use the positioning]
    H -->|No| B

The brief should also include a “not this” statement. For example: “This is not a custom analytics project,” “This is not outsourced operations,” or “This is not a strategy assessment.” Negative boundaries are useful when the company’s history makes the old interpretation likely.

Test message clarity as a business measure

Message clarity is not the same as internal agreement. Sales and product approval is a useful governance gate because it confirms that the message is sellable and technically true. It is not a universal benchmark, and it is not market validation.

Clarity should be tested with target buyers before the company depends on the positioning. Digital.gov recommends testing content as soon as there is enough material to evaluate and using methods such as paraphrase testing, usability testing, and comparative studies. Its usability guidance suggests beginning with a small number of intended readers for a round of testing, then testing again after revisions; that is a practical starting point for directional learning, not a statistical rule for every market.

A message test should reveal whether the buyer can answer four questions without coaching:

• What is this?
• Who is it for?
• What result does it help produce?
• Why would I choose it instead of the way I handle the problem now?

Add a fifth question for this task: What work do you think the vendor’s consultants must do for you to receive the result? If buyers assume a custom project is necessary when it is not, the product is still positioned as consulting. If buyers assume the product is self-contained when substantial services are required, the message is misleading.

Technical language deserves particular attention. A 2024 consumer-behaviour study found that unfamiliar technical language lowered purchase intention through reduced processing fluency, although the effect weakened when consumers had relevant knowledge or when the product was a typical technology product. The lesson is not to remove every technical term. It is to use the language the target buyer understands and to explain necessary terms in plain business language.

A practical clarity scorecard can combine comprehension, relevance, and commercial behaviour.

Do not declare success because a headline receives a high preference score. Buyers often choose language that sounds attractive without understanding what they would be buying. Paraphrase, comparison, and boundary questions reveal more than asking, “Do you like this message?”

The company can set an internal target for correct, unprompted comprehension, but the appropriate threshold will depend on market maturity, price, sales complexity, buyer expertise, and the consequences of misunderstanding. The most important practice is to define the scoring method in advance, record actual responses, and improve the message across rounds rather than changing the standard after seeing the result.

Keep services in their proper role

Separating product positioning from consulting does not require eliminating services. It requires making their role explicit and economically visible.

Salesforce provides a useful large-company example. In its fiscal year ended January 31, 2026, subscription and support represented about 95% of revenue, while professional services and other revenue represented about 5%. The company states that professional services help adoption, support larger subscription contracts, and contribute to customer success. It also reports that professional services are generally distinct from its cloud services and that the cost of professional services may exceed the related revenue. The lesson is not that every software company should copy Salesforce’s revenue mix. It is that services can support adoption while the product remains separately defined, sold, accounted for, and valued.

GitLab shows the operating boundary more directly. It describes itself as an intelligent orchestration platform for DevSecOps, while its professional-services pages separately offer training and implementation help. Its public handbook distinguishes standard professional-services stock-keeping units from custom statements of work and says consulting services become standard offerings only after repeated delivery has clarified price, scope, timeline, and product-market fit. That separation helps a buyer understand which value comes from the platform and which work is a service.

A high-touch product can still be a product. Palantir’s 2025 annual report describes four software platforms while also acknowledging that deployment, training, ongoing technical services, and configuration for customer environments can be important to successful use. This is a useful counterexample to simplistic advice. In complex, regulated, or operationally critical markets, the right boundary may be “product plus required implementation,” not “product with no people.” The positioning must still identify the durable software capability and avoid presenting every customer engagement as a new invention.

The service boundary can take four forms:

The danger is hidden service. Hidden service appears as free founder work, manual data preparation, custom reports, bespoke workflows, or ongoing interpretation that is necessary for the customer to perceive value but is absent from the product price and promise. It distorts product economics and makes positioning claims difficult to defend.

The company should therefore review every design-partner engagement and label each activity as product capability, standard onboarding, support, temporary manual bridge, or custom consulting. Temporary bridges need an owner and an expiry decision: automate them, standardize them as a paid service, transfer them to the customer or a partner, or remove the promise they support.

Evidence that the positioning is ready to use

The task is complete when the company has more than a sentence. It should have a small set of connected artifacts that guide sales, product, marketing, onboarding, and service decisions.

A credible evidence package includes:

• A product positioning brief with the target customer, buying situation, category, alternatives, product promise, points of parity, point of difference, proof, and service boundary.
• A category decision record explaining why the company chose an existing, modified, or new category and what evidence would cause it to revisit that choice.
• A customer-first narrative that describes the buyer’s situation, the limits of the current approach, the product’s different way of solving the problem, and the proof.
• A product-and-services boundary showing what is included in the subscription or licence, what onboarding is required, what services are optional, and what remains custom.
• A proof register separating verified facts, customer evidence, product demonstrations, assumptions, and future claims.
• A message-test record containing the audience, stimulus, questions, unprompted responses, scoring method, revisions, and unresolved confusion.
• A sales and product approval record confirming that sales can use the message in real conversations and product leaders agree that the claims are currently true.

Approval by sales and product is a sensible working target because both teams must live with the result. Sales can identify whether buyers recognize the category and care about the difference. Product can identify whether the promise overstates capability or commits the roadmap to custom work. Neither team should have unilateral control. A message that is easy to sell but false is dangerous; a message that is technically precise but incomprehensible is unusable.

Before the company relies on the positioning, the following should be true:

• A target buyer can explain the product, its outcome, and its category without hearing the consultancy’s history.
• The product can be demonstrated as a repeatable capability rather than as a consultant-led method.
• Product price and service price are visible separately, even when they are purchased together.
• Required implementation has a bounded scope and a clear end state.
• The proof supports the product promise, not merely the quality of the consultants.
• Sales and product use the same core language and record exceptions instead of improvising a new offer for each account.
• Design partners can be asked whether they would buy the product without recreating the original custom engagement.

The final decision is not whether the wording sounds polished. It is whether the company has defined a product that buyers can recognize, compare, purchase, and use as a product. When that answer is clear, consulting can remain valuable without carrying the identity and economics of the software business.

Sources

Primary and official sources

• American Marketing Association, “Branding,” including its definition of brand positioning.
• Salesforce, fiscal 2026 Form 10-K, including revenue mix, professional-services economics, and the distinction between cloud services and professional services.
• GitLab, company positioning, professional-services materials, and handbook guidance on standard service offerings.
• Palantir, 2025 Form 10-K, including platform positioning and the role of deployment and services.
• GOV.UK Service Manual, guidance on learning about users and their needs.
• Digital.gov, guidance on testing content for understanding and usability.
• Strategyzer, guidance on common mistakes in applying the Value Proposition Canvas.

Open research

• Mita Sujan and James R. Bettman, “The Effects of Brand Positioning Strategies on Consumers’ Brand and Category Perceptions.”
• Jan Goldenstein, Michael Hunoldt, and Simon Oertel, “How Market Conditions Affect New Ventures’ Propensity to Engage in Category Spanning.”
• Chad Navis and Mary Ann Glynn, “How New Market Categories Emerge.”
• Jiayao Liu, Xinyue Hong, Zhixing Zheng, and Jianan Zhong, “When Consumers Have Difficulty Understanding Ads: How Technical Language Lowers Purchase Intention.”