A positioning template asks for your category, and that is where the writing stops. Your company uses software but also does the work for customers. Calling it software leaves out the people; calling it consulting leaves out the technology. The website, sales deck and spoken pitch begin to describe different offers.
The familiar parts of a statement are useful: a target buyer, a need, a category, a benefit and an alternative. Crossing the Chasm describes those parts. The question for a company between categories is which part to write first and how to keep the finished statement connected to what buyers want.
A business positioning statement names the buyer's need first
Write the problem the buyer wants solved before deciding what to call the company that solves it. The category then does one job: it helps the buyer recognise where to look for help.
Someone searching for soda to quench their thirst could also buy water. Start the statement with the thirst: it explains why the person is looking and how another offer could help. The category in the request is useful information about the buyer, but the need leaves room to explain a different answer.
The same reasoning applies when a business searches for help. The buyer may know a category of provider without knowing your kind of company exists. Explain how your work answers their request. Otherwise, an unfamiliar label forces them to work out why they should consider you before they have understood the offer.
Name the buyer alongside the problem they want solved. Read those two parts together: would that person recognise the problem as their own? Then describe what they gain when it is solved. This keeps the explanation tied to a change the buyer wants, before it introduces the company's preferred terminology.
Include the alternative the buyer uses now. That alternative helps explain the choice the statement is asking them to make. For a company combining software with service, the comparison should account for both parts of the work. A buyer needs to understand what changes when they choose the offer.
Write the category last, using words the buyer already recognises or searches for. This is the order for developing the statement; the finished sentence can follow the order that reads most naturally. All the parts should still agree about the person, problem and benefit being described.
Name the buyer. Identify whose need the statement addresses so the offer has a clear audience.
Describe the wanted change. Use the buyer's words for the problem and benefit so they recognise their situation.
Choose a familiar category. Select a name that helps buyers find and understand the work after the need is clear.
The draft now has something to test. A buyer can respond to the need, the benefit and the comparison. Their reply gives more useful information than an internal debate about which label sounds different.
Leading with your own category name leaves buyers guessing
A category can describe your business accurately while missing the words a buyer types when looking for help. Compare the label with those searches before building the whole statement around it.
Keyword research for a recruiting-research firm found 210 monthly searches for its category term. The phrases its buyers used accounted for about 34,000 monthly searches. The keyword plan measured monthly search demand, with a much wider set of searches in buyer language. Using only the category term would leave those other ways of asking for help outside the statement.
A startup looking for candidates might search for "hire engineers", "engineering headhunter" or "software engineer contractors". Each phrase expresses a way the buyer currently understands the task. A firm able to help needs to explain that connection, even if its own description uses a different category.
Keep the description accurate about what the company does. The statement can use the buyer's problem as the opening, then explain how the company addresses it. That gives a familiar request an accurate answer. The buyer can judge the offer without first learning the company's internal classification.
The distinction is especially useful for businesses selling expertise through software. The software may perform part of the work while people interpret, review or deliver it. Buyers need language that explains what they receive. A category argument among founders can consume attention without making that answer easier to understand.
Read the draft as someone who has only the problem in mind. Can that person see why this company is relevant? If the sentence depends on knowing a new category already, add the connection between the problem and the work. The category then helps organise an offer the buyer has begun to understand.
Search language is one input to that reading. Calls and emails show how people describe the task when they can explain more than a short query allows. Put those sources together. The statement should sound familiar to the intended buyer while remaining precise about what the company does.
The recruiting example shows why naming starts with buyer language. Its useful lesson is that the category term can leave much of the buyer's language outside the statement. Read that language before choosing the label, and the draft starts from what buyers actually say.
Back what sets you apart with proof buyers can check
A buyer considering software sold with a service needs to judge both the technology and the people delivering the work. Give the difference in the statement something they can inspect.
A claim about technology becomes easier to assess when the buyer can open a demonstration or try the relevant function. The demonstration connects the statement with something the product does. Published code can serve that purpose for a technical buyer too (including an open-source system where the code itself is available to inspect).
Show the part of the technology that supports the difference you claim. If the statement says the software helps with a particular job, the demonstration should show that job. Explain what the buyer is looking at and how it relates to the work they would receive.
People need evidence of their own. Relevant backgrounds help a buyer understand who will take responsibility for the service. A company can show where its team worked or studied and let readers check those details. Those backgrounds support a claim about experience without requiring a famous public name to stand in for the whole team.
The company's thinking provides another way to judge it. Essays and white papers in a founder's name can explain how the work is approached and why decisions are made. A buyer who rarely purchases directly from a website may use that writing to decide whether a conversation is worth having.
The statement can stay short when the supporting material is easy to inspect. Link the technology claim to a relevant demonstration. Support the service claim with the team's backgrounds and writing about its work. A buyer then has somewhere to take each question the statement raises about the software, the people or their judgment.
Keep numbers in that material tied to their sources. A precise figure can sound persuasive while leaving the reader unable to tell what was measured. The source and circumstances make it usable evidence. If the company cannot support the number, it should not become the reason a buyer is asked to believe the statement.
The buyer can now ask about the difference and receive a concrete answer. When the buyer asks what makes the company suitable, the answer can lead to a demonstration, a relevant background or a piece of thinking. Each gives the conversation somewhere concrete to go.
Rewrite the statement when buyers' replies show who buys
Put the statement where a buyer can answer it, then use the answer to decide what needs rewriting. A headline, a post and an outreach message expose different parts of the same claim.
Early sales conversations can change a founder's view of who needs the offer. Keep that possibility open when writing the first statement, then compare it with the people who respond. A sentence that reads well in a document may name a need buyers do not recognise, or attract people who want a different part of the offer.
A page headline tests whether the offer is understandable at the point of discovery. A post lets readers respond to the problem and the company's thinking about it. An outreach message gives a particular buyer a direct opportunity to answer. Each placement makes the statement available to someone outside the group that wrote it.
Read the replies for what they clarify. Buyers may ask about work the statement barely mentions. They may describe a different alternative from the one assumed in the draft. Those answers point to specific parts to change: the need, the benefit, the comparison or the category. The rewrite should follow the answer it is intended to address.
A useful record keeps the statement beside the reply that prompted the change. That makes it easier to distinguish a revision based on buyer language from a revision based on taste. It also keeps the site, deck and spoken pitch connected as the wording changes.
A branding workshop can help a company agree on a statement and deliver a document people can use. A positioning consultant's framework can help organise the buyer, alternatives and difference. Both can provide structure when the founders have been describing the company in conflicting ways.
The ongoing option is people who put that statement into pages, posts and outreach, then rewrite it from the replies. The comparison turns on who tests the wording against buyers after the document exists. For a company still learning who buys, that responsibility belongs in the work from the beginning.
Revision does not mean abandoning every part whenever someone asks a question. Keep the parts that explain the offer well and change the part the replies put in doubt. The aim is a statement that becomes more accurate as the company hears from buyers, with the reasoning behind each change still visible.
Write a separate statement for each new market you enter
A move into another market can change the problem words and alternatives your statement needs to address. Write for those buyers when their starting point differs from the market you already know.
A European company entering the US may understand its product and its existing customers very well. It can still struggle to explain the offer to American buyers. The reverse move presents the same kind of question: what language will the new buyer recognise, and what do they already use to address the problem?
Read calls and searches from the market you are entering. Look at how those buyers describe the job and what they expect a provider to do. The words may look similar to the ones in the existing statement while implying a different scope of work.
Alternatives deserve the same attention. The statement asks someone to choose the company over what they use or consider now. If that comparison changes in the new market, the difference needs to be explained against the new alternative. Reusing the old comparison can answer a question the new buyer is not asking.
A separate statement is useful when those inputs differ. It can retain the company's actual capabilities while changing which need and comparison it explains first. That keeps the offer accurate and lets the new buyer recognise why it applies to them.
Where buyers in both markets use the same words and consider the same alternatives, one statement can serve both. A geographic move alone does not require a different claim. The reason to separate the statements is a meaningful difference in what the buyer needs to understand.
Repeated questions are particularly useful when making that judgment. A question that appears across conversations points to something the wording has not settled. Compare it with the questions from the established market. If the new group consistently needs another explanation, write that explanation into the statement for those buyers.
Keep the two statements traceable to those buyer differences. The team can then explain why one headline leads with a particular need and another uses a different comparison. That makes market-specific writing easier to maintain without allowing the website and sales deck to drift into unrelated descriptions of the company.
Example: rewriting a positioning statement once founders wanted help
In November 2026, we changed our own statement to reflect what founders were asking us to do.
| Part | Earlier statement | Current statement |
|---|---|---|
| Buyer | Builders who use coding agents | B2B startups whose founders have clients and no experienced marketing lead |
| Need | Do marketing with a coding agent without writing the system from scratch | Find profitable growth channels |
| Category | Open-source marketing system | Growth experiments for B2B startups |
| Difference | Open source and runs in the coding agent | Founder and engineering experience applied to the growth work |
Founders who discovered the system wanted help doing the work, so the need in the statement changed. Earlier descriptions, including "outsourced growth team", were replaced; this comparison records the wording change without attributing a later sales result to it.
Fill each part of the statement from buyers' own words
Gather buyer language
Collect phrases from calls, emails and searches, keeping the questions that recur beside the situations that prompted them.
Write the need
Describe what the buyer wants to change in familiar words before choosing the category that will describe your company.
Select the category
Use a name buyers already search for, then check that the statement accurately explains how your work meets their need.
Support the difference
Connect the reason to choose you with a demonstration, relevant background or piece of thinking a buyer can examine.
Test the statement
Put the wording into one headline and one outreach message, then revise the parts buyers' replies show need attention.
Sources
Source for the statement's parts: target customer, need, category, benefit and alternative.