Most SaaS founders have a positioning statement. Few of them use it to make decisions. That is not a communication failure. It is an architecture failure: the statement was designed to be read, not applied.
A positioning statement written for the website and one written for the team are different documents. The first is marketing copy. The second is a decision filter. Most founders have the first and believe they have the second.
The difference shows up in practice. When the product team debates a new feature, does anyone pull up the positioning statement? When sales debates pricing, is the statement part of the conversation?
When a new hire asks what the company does, does the statement give them an answer they can use tomorrow? If the answer is no to any of these, the statement exists for external consumption, not internal use.
The Decision-Filter Positioning Framework produces a statement the team actually reaches for. This article is for the founder who has a positioning statement written for the website and hasn’t opened it since the last fundraise.
Why Most Positioning Statements Fail the Team Test
The obvious failure mode: the statement is vague. “We help teams work smarter” or “The AI-powered knowledge platform for modern businesses.” Both statements could describe dozens of companies. Neither helps anyone make a decision.
The less visible failure is specificity without applicability. A statement can be specific about the customer and the problem and still fail the decision-filter test.
“We help Series A SaaS companies reduce engineer onboarding time through an AI-assisted knowledge base” is specific. But it doesn’t tell the engineer whether to build the new import integration or the new search interface. It isn’t applied to decisions because it wasn’t written for that purpose.
The deepest failure is a statement that doesn’t travel. If the founder must be in the room for the statement to be applied, the statement isn’t working. The test is whether the team uses it when the founder isn’t present.
The Decision-Filter Positioning Framework
The framework builds a positioning statement in three layers. Each layer adds a constraint that makes the statement more useful as a decision filter.
Layer 1 anchors the statement to a specific customer with a specific problem
Generic positioning fails because it doesn’t say no. A statement that includes “teams,” “businesses,” or “organizations” without further specification is a statement that applies to everyone. It cannot be used to make decisions because it provides no criteria for exclusion.
Layer 1 specifies three things:
- The customer segment
- The specific workflow or context where the problem occurs
- The cost of the problem when left unresolved
Not aspirational cost. Actual, observable cost that the target customer recognizes immediately.
If a candidate reads Layer 1 and does not recognize their own situation in it, they are not the target customer. That exclusion is the test.
Layer 2 names the specific mechanism that makes the approach different
Generic differentiation fails for the same reason. “AI-powered,” “intuitive,” and “enterprise-grade” are categories, not differentiators. A true differentiator names the specific thing the product does that alternatives do not.
Layer 2 specifies three things:
- The mechanism of differentiation
- Why the mechanism matters to the customer from Layer 1
- Why alternatives cannot offer the same mechanism
This layer is where most positioning statements fail. It requires intellectual honesty about what is genuinely different.
Before: Differentiating on “AI-powered knowledge management.” This is a category, not a mechanism. After: Differentiating on “a maintained intelligence layer that produces updated outputs without manual compilation.” This is the specific mechanism competitors don’t offer.
Layer 3 tests whether the statement works without the founder in the room
Layer 3 is not written into the statement. It is a test applied after drafting.
Run three decisions through the completed statement. If it helps a product manager choose between two features, the statement is working. If it gives sales a reason to decline an outside-segment discount, the statement is working. If it answers a new hire’s question about why the company exists in a way they can act on, the statement is working.
If none of those decisions get easier with the statement in hand, the statement has not yet reached Layer 2 specificity.
How the Living Library Keeps Your Positioning Statement Current
The week before quarterly planning, the positioning statement is already updated. New competitive context from the past quarter has been incorporated. Customer language from recent interviews has been reviewed against Layer 1.
One phrase has been sharpened to match how customers currently describe their problem. This is not a task you scheduled. The Library did it.
Inside Kiluma, the Living Library does the active work of keeping the positioning statement current. Customer notes, competitive research, and ICP updates flow into the Positioning Collection as they accumulate. The Library reads them and maintains the statement. The team works from current evidence, not the version drafted at the last fundraise.
When a specific decision needs the statement checked against recent evidence, the Conductor surfaces the relevant data from your Library. Kiluma’s Conductor is context-aware AI. It knows what’s in your Library and what your team is working on. It uses that context to support or challenge the current draft, not to generate generic positioning advice.
Write Layer 1 Before You Do Anything Else
This week, before writing a full positioning statement, write only Layer 1. One paragraph. The specific customer, the specific context where the problem occurs, and the specific cost left unresolved.
Then run the exclusion test. Name three types of companies or roles that Layer 1 explicitly does not describe. If you can’t name three, the statement is still too broad. A statement that includes everyone has excluded no one.
The pivot work from Why Early-Stage SaaS Founders Change Direction Constantly, Article 01, connects here directly. A Layer 1 statement solid enough to exclude provides the customer-evidence foundation the Three-Question Pivot Audit’s Question 2 draws from. They are the same work, done from opposite directions.
The Positioning Statement That Works Is the One the Team Uses
A positioning statement written to be applied is different in kind from one written to be read. The team can tell the difference by whether they reach for it. Try Kiluma free for 14 days at kiluma.ai.