Positioning Statement
beta · Family strategy-docs · Phase undefined · Sizes lean · ~4,400 tokens
The internal, present-tense record of how this product stands against a named alternative, for a specific target customer, now. Not the vision (future-facing), not messaging (built on top of this once it is settled), and not a battlecard or a positioning map.
An operator card. Read it before you fill the template and again before you agree the statement with
the team. The reasoning behind every rule here lives in
positioning-statement_companion.md.
When to use this document
Section titled “When to use this document”Write it once three things are true: a product strategy already names the target segment this statement is written for, the team can say what that target does today without the product, and the positioning has already been worked out through analysis rather than guessed at on the page. The document is then the dated, internal record of that analysis, written down for two reasons April Dunford gives: “Once you have all the pieces together, you will want to write it down.” Her two reasons: a shared record of what the team agreed, and “The document is dated so you can track when the positioning was last reviewed.”
This library places positioning after the product strategy has already chosen a segment, because the statement depends on that choice being made, not on which document gets written first in principle. That placement is this library’s own position, argued rather than sourced; see the companion’s Debates section before treating it as settled.
Is this the right document at all?
Section titled “Is this the right document at all?”| If the real question is | Write this instead |
|---|---|
| Where are we trying to get to, over years, and why is it worth it? | product-vision |
| Which problems will we solve to get there, and which will we not? | product-strategy |
| What exact words will sales and marketing use with customers? | a messaging framework. This library has not yet admitted one; see the companion’s Relationships section |
| What does a rep say when a named competitor comes up in a live deal? | a battlecard. Not yet admitted either, and downstream of this document, not an input to it |
| Which single measure of customer value shows the strategy is working? | north-star-metrics |
| In what order will we work on those problems? | product-roadmap |
| What measurable change do we expect this period, and did we get it? | okrs |
When NOT to use this document
Section titled “When NOT to use this document”- The reader might be external. Every source that names a reader names an internal one. HubSpot is direct about it: “your positioning statement isn’t public-facing.” If the audience is a customer, the press, or an investor, this is not that document, and April Dunford’s own methodology is explicit that it is scoped to one kind of reader: “The methodology in Obviously Awesome is designed specifically for customer positioning-not investor positioning, not employee positioning, not partner positioning.”
- The analysis has not happened yet. If nobody has worked out the target, the real alternative, and the differentiation, do not open this template to find out. Do that work first; this document records the result.
- The question is where the product is headed, not how it wins today. That is
product-vision’s job. This document is present tense only. - The content is customer-facing language. Talking points, a tag line, a sales script: that is messaging, built on top of this record once it exists, never a substitute for it.
- The product strategy has not yet named a segment. Positioning restates a segment the strategy has already chosen; writing it first would mean guessing at the segment instead of inheriting it.
Picking a variant
Section titled “Picking a variant”There is nothing to pick. This bundle ships one size, lean, and every admitting source agrees on why.
MIT: a positioning statement “forces you to use a one page format to summarize everything that matters
for your product.” HubSpot: “Aim for no more than three to five sentences, if possible.” Yesware gives
the same three-to-five-sentence ceiling. April Dunford’s own material is genuinely longer, a workbook she
gives her newsletter subscribers, but this library reads that workbook as a facilitation process for
reaching the one-page statement, not a second, heavier version of the statement document itself. Do not
invent a full-size version by copying her workbook’s steps into this template; that content belongs in a
facilitation process, not in the standing record. See the companion’s Variants and sizing section.
Who owns this document
Section titled “Who owns this document”Two camps answer this question differently, and neither is this library’s invention. Blackblot, Young
Urban Project, and Douglas Karr’s account of the Pragmatic Framework all name product marketing as the
owner. Aha!’s own guide and blog, and Devika Nair’s account of a product-management and product-marketing
split, instead describe the work as joint or shared rather than owned by one function alone. Which camp
fits your own company is, in this library’s own reading, an organization-dependent question rather than a
settled one. No source states this library’s own suggested default, that product management owns the
statement as product direction while product marketing drafts or co-writes it, and where the sources do
lean, they lean toward product marketing instead. The default is offered anyway, as this library’s own
reasoning rather than a finding: this bundle is scoped to product direction, and the other strategy-docs
examples are owned by product leadership. What matters more than which default you pick is that the
document names one owner.
The rubric
Section titled “The rubric”Score each row 0, 1 or 2. Below 10 out of 14, do not let this stand as the team’s record yet: at least one section still reflects a guess rather than analysis, or the document cannot tell a future reader what to check or when to come back to it.
| # | Criterion | 0 | 1 | 2 |
|---|---|---|---|---|
| 1 | Boundary names neighbors | The Purpose and Boundary section lists the four exclusions in the template’s own generic wording, with nothing about this product added | The exclusions are restated in product-specific terms, but a reader could not yet tell, from this section alone, which existing document already carries the content being excluded | Each exclusion names the artifact that actually carries that content for this product, so a reader who starts writing the wrong kind of sentence here can be pointed to where it belongs |
| 2 | Statement follows components | At least one word in the sentence, a benefit, a category, a claim, does not appear anywhere in the Components below it | Every word in the sentence traces to the Components below it, but the Components section still reads as justification written after the sentence rather than analysis that produced it | Every clause in the sentence traces to specific wording in a Component below it, and deleting the sentence would cost the reader nothing the Components did not already say |
| 3 | Real rival, not phantom | The named alternative is a category of competitor rather than one specific thing a customer would actually do, or it is a named competitor nobody on the team can point to a real, lost deal against | The alternative is specific, but the document does not say whether the team has actually lost to it or is guessing that customers would choose it | The alternative is specific, and the document states why the team believes it is the real rival: a named deal lost to it, or a stated reason the status quo is the default choice |
| 4 | Differentiation survives substitution | Swapping the named alternative’s name in place of the product’s name in the differentiation sentence would still sound credible; nothing in the wording is specific to this product | The differentiation names something specific to this product, but Why This Positioning offers no proof beyond the claim restated in different words | The differentiation fails the swap test, and Why This Positioning names a specific proof point, a measured result or a documented customer reaction, not the claim restated |
| 5 | Target defined by need | The target is a demographic or firmographic label with no stated need, or the need is a restatement of the product’s own feature list | A need is named, but it is generic enough to describe almost any product in the category | The need is specific enough that a reader could recognize a real customer conversation from it, and the target is defined by having that need rather than by a label alone |
| 6 | Revisit has an owner | The section states only a calendar interval, with no named event that would call for an earlier look and nobody named to notice one | A trigger event is named, but nobody is named as responsible for noticing it, or the check-in interval is missing | A dated last review, a stated check-in interval, and a named trigger appear together, with somebody named to notice that trigger |
| 7 | Separate from messaging | The document states talking points, a tag line, or sales language directly, instead of the competitive analysis such language would be built on | The document avoids messaging language, but nothing in it says that messaging comes next or points to where that work happens | A reader can tell from the document alone that messaging, a battlecard, or a sales pitch is the next, separate piece of work built on top of it |
Anti-patterns
Section titled “Anti-patterns”- Filling the sentence in from assumption instead of from the six components’ own analysis. This is April Dunford’s central, repeated critique of the fill-in-the-blank exercise, not a minor stylistic complaint: “The only valuable thing we can learn from the statement is that there are multiple components of positioning.” Writing the sentence first and reverse-engineering the Components to match it is the same failure in reverse.
- Positioning against a phantom competitor. April Dunford warns that a rival the team has never actually lost a real deal to “should not be considered when working on your positioning.” Naming one anyway invites the team to defend against a threat that is not actually costing it business.
- Treating the status quo as an afterthought. Dunford’s own account puts it first, not last: “the first competitive alternative we need to beat is the status quo.” A document that jumps straight to a named competitor and never asks what the customer does today without the product has skipped the harder, more common case.
- Importing a messaging cadence or trigger list into this record. A messaging framework may carry its own quarterly review cycle; this document does not inherit it. The Starr Conspiracy states which document to settle first: “Lock the positioning statement first.”
- Writing it once and never referring to it again. April Dunford names the specific failure a dated record exists to prevent: a document that is “completed and never, ever referred to again” has lost the only two things writing it down was supposed to buy the team.
- Rewriting it every quarter. A near-constant rewrite is a symptom, not a positioning problem, in CLIMB’s own diagnosis: “If you find yourself rewriting your positioning statement every quarter, the problem likely isn’t the statement. It’s that the underlying strategic choices haven’t been made firmly enough.”
- A differentiation claim that passes the substitution test. If swapping the named alternative’s name into the sentence in place of the product’s own name would still sound credible, the claim is not yet specific enough. Lumen Learning’s own desk test: “If you can substitute any competitor’s name for your own in the positioning statement-and it still sounds credible-then you need some additional work on your differentiators and competitive advantages.”
- Crediting the formula to Geoffrey Moore. No source this library’s research read firsthand attributes the fill-in-the-blank form to him. Treat the attribution, if it comes up, as unverified, never as a fact to put in this document or its guidance.
Before you share it
Section titled “Before you share it”- You can point at the Components section and show every word of The Statement came from it.
- The named alternative is something specific, and you can say whether the team has actually lost a deal to it.
- The differentiation fails the substitution test: swap in the alternative’s name and it stops sounding credible.
- Why This Positioning names a proof point, not just a restated claim.
- The revisit section has a date, an interval, and at least one named trigger with an owner.
- Nothing here is messaging, a battlecard, or a positioning map wearing this document’s heading.
- You have deleted every HTML comment before sharing it.
The artifacts
Section titled “The artifacts”positioning-statement_template-lean.md · ~4,400 tokens
---title: "{{product_name}} Positioning Statement"product: "{{product_name}}"owner: "{{who_owns_this_statement}}"target_customer: "{{target_customer_short_name}}"status: "{{draft_or_agreed}}"last_updated: "{{date}}"doc_type: positioning-statementsize: leansource_template: positioning-statementsource_template_version: 0.1.0---
<!--LEAN POSITIONING STATEMENT. This bundle ships one size, deliberately. Seepositioning-statement_guide.md, "Picking a variant," for why; that reasoning is not repeatedhere.
WHAT THIS DOCUMENT IS, AND IS NOT. A positioning statement is a short, internal, present-tenserecord of how this product stands against a named alternative, for a specific target customer,now. It is reached by analysis, not filled in from assumption: April Dunford's own five-postcritique of the bare fill-in-the-blank sentence is a critique of writing it from assumption andtreating it as finished work, not a ban on writing positioning down once the analysis behind it issettled. "Once you have all the pieces together, you will want to write it down," she says, fortwo reasons: a shared record of what the team agreed, and a dated record of when it was lastreviewed. This document is that record. It is NOT product-vision (that is long-term, aspirationaland future-facing; this is present-day and competitive). It is NOT messaging (the externallanguage built on top of this positioning, after it is settled; this library has not yet admitteda messaging-framework bundle). It is NOT a battlecard (downstream and reinforcing, not an input).It is NOT a positioning map (a two-axis competitive chart, a different artifact, out of thislibrary's scope on form grounds). See positioning-statement_companion.md section 1 and section 8for the fuller set of boundaries, and section 2 before crediting this formula to Geoffrey Moore: nosource this research read firsthand attributes it to him, and this template names him only as anunverified attribution, never as a sourced fact.
WHO FILLS THIS IN. No source read states this library's own default, that product management holdsthe statement as product direction while product marketing drafts or co-writes it. Where thesources lean, three name product marketing as the owner. This template's owner fieldcarries whichever answer your own organization gives; do not read a single correct owner into it.See positioning-statement_companion.md section 6 (Who owns the statement) before filling in theowner field.
WHERE THIS SITS IN THE CHAIN. This library places positioning third among its strategy-docsfamily, between the product strategy and the North Star metric, and names that placement its ownPOSITION rather than a sourced finding. A considered alternative places it second, between thevision and the strategy, on one practitioner's framing of positioning as part of the vision anddecision making. Nothing in this template depends on which place is correct; it depends only onpositioning following a strategy that has already named a target segment. Seepositioning-statement_companion.md section 6 (Debates).
HOW TO FILL THIS IN1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into positioning-statement_companion.md for the deep reasoning), guiding questions to ASK, a GOOD and a WEAK example, and the TRAP to avoid.2. Replace each {{placeholder}} with your content. Write The Statement last, after The Components below it are settled from analysis, not first and not from assumption.3. If a section does not apply, write "N/A" and one line of why, rather than deleting it.4. This is a standing record, revisited on the schedule and the triggers named in When We Revisit It below, not written once and filed away. Before you first share it: self-grade against positioning-statement_guide.md, then DELETE every HTML comment. They are guidance, not content.-->
# {{product_name}} Positioning Statement
## Purpose and Boundary
<!-- WHAT A short statement of what this document states, the present-tense competitive stance for a named target, and what it deliberately rules out by name. WHY Every source that names a reader names an internal one: HubSpot states "your positioning statement isn't public-facing," and eCornell calls it "an internal tool." Every source that draws a boundary with a neighbouring artifact draws it the same direction: positioning precedes and feeds messaging, never the reverse, and a battlecard is downstream and reinforcing, not an input. This library has not yet admitted a messaging-framework bundle, and a positioning map, a two-axis competitive chart, is a different artifact, out of this library's templating scope on form grounds, not a content overlap. Deep dive: positioning-statement_companion.md section 3 (Purpose and Boundary) and section 8 (Relationships to other artifacts). ASK Who reads this document, and is every reader internal? What present-tense competitive claim is this document making, as the market exists today, not where the product is headed? What three neighbouring documents could someone confuse this with, and what does each of them do that this one deliberately does not? GOOD "This document states how Orbital stands against the paper schedule and the group chat, for shift-work managers at single-site retail and food-service businesses, as of this review date. It is internal. It is not the Orbital product vision, not messaging, and not a battlecard." (names the alternative, the target, the audience, and the three things it is not) WEAK "This describes what makes Orbital special." (no named alternative, no named target, no stated audience, no boundary) TRAP Writing this section in future tense, or letting it describe where the product is headed rather than how it wins business today. That is product-vision's job, not this document's. -->
{{product_name}}'s positioning statement states how this product stands against{{named_alternative_short}}, for {{target_customer_short_name}}, as of {{date}}. It isinternal, written for the people who make product, marketing and sales decisions about{{product_name}}, not for customers or the press.
This document deliberately does not state:
- **Messaging**: the external language and talking points a team builds on top of this positioning, once it is settled.- **A battlecard**: sales-facing competitive responses, downstream of and reinforcing this positioning, never an input to it.- **A positioning map**: a two-axis competitive chart, a different artifact.- **{{product_name}}'s product vision**: the long-term, aspirational, future-facing destination this product is working toward. This document is present-day and competitive, not aspirational.
## The Statement
<!-- WHAT The fill-in-the-blank sentence itself, the one-line summary of the six components below it. WHY Every admitting source ships some version of this sentence: MIT, HubSpot, eCornell and Yesware each publish a slot-based formula, no two identical. The field labels below are this library's own wording, not any one source's exact phrasing, since HubSpot's and Yesware's own bracketed text is their own copyrighted formula. Deep dive: positioning-statement_companion.md section 3 (The Statement) and section 2 (Origins and evolution). ASK Have the six components below already been settled through analysis, or is this sentence being written first, from assumption? Could someone outside the room who reads only this sentence still understand why each word is there? GOOD "For shift-work managers at single-site retail and food-service businesses who need to clear a last-minute call-out without working the phones themselves, Orbital is the scheduling product that clears a shift swap in one tap, unlike the paper schedule and the group chat, because the schedule and the swap approval live in the same place." (every clause traces to a component below it, and the reason to believe sits right after "because") WEAK "For businesses that need to schedule shifts, Orbital is scheduling software that beats other scheduling tools, because it is easier to use." (a vague target and category, a phantom competitor named only as "other scheduling tools," and a differentiation claim with nothing behind it) TRAP Write this sentence last, from the finished Components below, not first as a guess to be reverse-engineered into analysis later. April Dunford's own critique names exactly this failure: the exercise "assumes great positioning is magically locked inside your head." Once written, do not treat it as the finished work either; it is a summary of analysis that lives in The Components below, not a substitute for that analysis. -->
For {{target_customer}}, who {{customer_need}}, {{product_name}} is the {{category}} that{{benefit}}, unlike {{named_alternative}}, because {{differentiation}}.
## The Components
<!-- WHAT Each named component expanded to a sentence or two: the named alternative, the target, the need, the category, the benefit, and the differentiation. Listed in this order, alternative first, because the rest of the analysis depends on it. WHY Dunford's own dependency argument is explicit: "I had the realization that the starting point had to be competitive alternatives," because "your differentiated features are only 'differentiated' when you compare them to competitive alternatives." Her working question for that first component is "What would a customer do if your offering didn't exist?" and her own answer puts the status quo first: "the first competitive alternative we need to beat is the status quo." MIT's six-field template and the classic form's five-field template both confirm the same shape under different labels. Deep dive: positioning-statement_companion.md section 3 (The Components). ASK What would this target customer do today if {{product_name}} did not exist? Is the named alternative a competitor the team has actually lost real deals to, or a phantom competitor nobody has really lost to yet? Who specifically is the target, by what they need rather than by a demographic label? What market category gives this target the right frame of reference? What benefit does this target get that the alternative does not? What makes that benefit genuinely different, not just differently worded? GOOD "Named alternative: the paper schedule taped to the stockroom wall, plus the group chat managers use to cover last-minute call-outs. It is free, already in place, and good enough for most weeks." (names a real, specific status quo rather than a vague competitor) WEAK "Named alternative: other scheduling software." (no specific rival named, and the status quo, the far more common real rival, is skipped) TRAP Naming a competitor the team has never actually lost a real deal to. Dunford is direct about this: a phantom competitor "should not be considered when working on your positioning." Adjust only once such a competitor starts showing up in real deals. -->
**Named alternative.** What this target customer does today without {{product_name}}, namedspecifically rather than as a category of competitor: {{named_alternative}}.
**Target.** Who this statement is written for, named by what they need rather than by ademographic label alone: {{target_customer}}.
**Need.** The specific problem or job this target has that sends them looking for a solution atall: {{customer_need}}.
**Category.** The frame of reference this target customer will use to understand what kind ofthing {{product_name}} is: {{category}}.
**Benefit.** What this target customer gets from {{product_name}} that matters to the needabove: {{benefit}}.
**Differentiation.** What makes that benefit genuinely different from what the named alternativedelivers, not just differently described: {{differentiation}}.
## Why This Positioning
<!-- WHAT The evidence behind the differentiation claim: what the named alternative actually does, and why this target should believe the stated benefit over it. WHY HubSpot's formula closes on exactly this question, a "reason why target market should believe your differentiation statement." A dated, written record is also the reason April Dunford gives for writing positioning down at all: once it is written down and dated, someone who was not in the room can later check it, which an unrecorded reason does not allow. Deep dive: positioning-statement_companion.md section 3 (Why This Positioning). ASK What proof, not just claim, shows this target that the stated benefit is real? If you swapped the named alternative's name into this statement in place of {{product_name}}, would it still sound credible? If so, the differentiation above needs more work. GOOD "Shift swaps that used to take three phone calls and a manager's evening now clear in one tap, because the schedule and the swap approval live in the same place. Three pilot sites cut manager overtime by four hours a week within a month of switching off the paper schedule." (states the proof, not just the claim, and names a measured result) WEAK "We're just better and easier to use." (a claim with no proof point behind it) TRAP A differentiation claim that fails Lumen Learning's desk test: "If you can substitute any competitor's name for your own in the positioning statement, and it still sounds credible, then you need some additional work on your differentiators." Run that substitution test on your own draft before treating this section as done. -->
{{reason_to_believe}}
## When We Revisit It
<!-- WHAT The date of the last review, the interval your team checks in on, and the named events that call for an earlier look, not a calendar entry standing alone. WHY Three sources state a cadence for positioning, one by name for the statement itself: Dunford describes "a positioning checkin every six months" at one company and, elsewhere, "a regular (a couple of times a year) check-in"; Lawson Abinanti recommends auditing the positioning statement "every 12 months." Dunford's own reason to date the record at all is so the team "can track when the positioning was last reviewed." She separately names triggers on both sides: an acquisition, a funding round or a senior hire can prompt a revisit, as can a bad quarter, lost deals, an outage, or an unplanned change in the CEO or other senior leaders. CLIMB adds a market or competitive shift, and a mismatch surfaced by customer research. Deep dive: positioning-statement_companion.md section 3 (When We Revisit It) and section 6 (Debates). ASK When was this positioning last reviewed, and when is the next check-in due, somewhere between six and twelve months out? Who notices a named trigger event first, and are they the person who brings the team back to this document? Has a check-in actually changed anything yet, or has it so far confirmed that nothing needs to? If nothing has changed, say so: April Dunford frames the check-in itself as existing "to determine whether or not you need to make a positioning adjustment," not to assume the answer is no. GOOD "Last reviewed 2026-04-01. Next check-in due by 2026-10-01. Revisit early if a direct competitor to the paper-schedule status quo launches, if we are acquired or acquire another scheduling tool, or if a new VP of Operations joins and wants to re-examine the sales pitch." (a dated last review, a stated interval, and named triggers on both sides) WEAK "We'll review this every quarter." (a bare calendar entry with no named trigger and no owner; it also imports a cadence this library's own sources scope to messaging, not to positioning itself) TRAP Confirming that a quiet quarter is itself evidence nothing needs to change, without naming who checked and against what. CLIMB holds the record to the same test: "A positioning statement isn't permanent, but it shouldn't change often." The record should still show that a check happened and what it was checked against, not just assume it. -->
- Last reviewed: {{last_reviewed_date}}- Check-in interval: {{checkin_interval}}- Who notices a trigger event and brings the team back to this document: {{revisit_owner}}- Named triggers that call for an earlier look, beyond the scheduled check-in: {{revisit_triggers}}positioning-statement_example.md
---title: "Acme Analytics Positioning Statement"product: "Acme Analytics"owner: "Dana Okoro, VP Product"target_customer: "the Recurring Analyst"status: "agreed"last_updated: "2026-01-30"doc_type: positioning-statementsize: leansource_template: positioning-statementsource_template_version: 0.1.0---
> **Worked example.** A filled `positioning-statement`, lean variant, for the same Acme Analytics product> used throughout this library's examples. Per [ADR 0076](../../docs/internal/decisions/0076-positioning-statement-joins-strategy-docs-as-a-sixth-member.md),> this type sits third in the `strategy-docs` chain: it is dated 2026-01-30, two days after the> [FY26 product strategy](../product-strategy/product-strategy_example.md) (2026-01-28) whose target> segment it carries forward, and it will sit just ahead of the North Star metric still to come. Dana> Okoro, VP Product, owns the vision, the strategy, and this document, which is why the three speak in one> voice. Nothing below is messaging, a battlecard, or a competitive map; those are a different document and> this library has not yet admitted the first of them.>> All figures are illustrative. They are internally consistent with the other examples in this library and> are not drawn from a real company. The 31 percent figure below repeats the FY26 product strategy> example's own baseline exactly, because both documents describe the same account behavior.
# Acme Analytics Positioning Statement
## Purpose and Boundary
This document states how Acme Analytics stands against the spreadsheet-and-a-favour status quo and againstgeneral-purpose BI tools, for the Recurring Analyst, as of 2026-01-30. It is internal, written for thepeople who make product, marketing and sales decisions about Acme Analytics, not for customers or thepress.
This document deliberately does not state:
- **Messaging**: the external language and talking points a team builds on top of this positioning, once it is settled. This library has not yet admitted a messaging-framework bundle.- **A battlecard**: sales-facing competitive responses, downstream of and reinforcing this positioning, never an input to it.- **A positioning map**: a two-axis competitive chart. A different artifact, out of this library's scope.- **Acme Analytics's product vision**: the long-term, aspirational, future-facing destination this product is working toward. That document already names the spreadsheet and the favour as the real incumbent; this one is present-day and competitive, not aspirational, and does not repeat the vision's horizon or its leaps of faith.
## The Statement
For the Recurring Analyst, who needs an answer to an operational question inside the same working sessionin which it came up, Acme Analytics is the in-context analytics product that answers a question withoutcopying the data anywhere else first, unlike the spreadsheet and the favour or a general-purpose BI tool,because Acme already sits inside the operational systems where the work happens.
## The Components
**Named alternative.** What the Recurring Analyst does today without Acme Analytics, named specificallyrather than as a category of competitor: the question goes to a shared analytics inbox, or into aspreadsheet that gets copied and then diverges, or to whichever colleague currently knows how to build theview, as a favour. A second, named alternative exists for the same target: general-purpose BI tools, whichcan answer the harder questions but require a modeling step the Recurring Analyst cannot perform alone, soadoption stalls at the same point, now behind a purchase order instead of a favour.
**Target.** Who this statement is written for, named by what they need rather than by a demographic labelalone: the Recurring Analyst, someone at a mid-market company who owns a number, answers questions about itweekly, and has no data team behind them.
**Need.** The specific problem or job this target has that sends them looking for a solution at all: ananswer to a question about their own operating number, inside the working session in which the questioncame up, without filing a request, waiting for a sprint, or learning a query language first.
**Category.** The frame of reference this target customer will use to understand what kind of thing AcmeAnalytics is: an analytics product that lives inside the operational systems where the work alreadyhappens, not a destination the Recurring Analyst travels to with a question.
**Benefit.** What this target customer gets from Acme Analytics that matters to the need above: a questionasked in plain language returns an answer inside the same operational system where it came up, withoutcopying the data anywhere else first and without a favour owed to anyone.
**Differentiation.** What makes that benefit genuinely different from what the named alternative delivers,not just differently described: Acme already sits inside the operational systems where the work happens,because that is where the product began and where its integrations already live, an arrangement thatstarted as an accident of history rather than a deliberate strategy. A general-purpose BI tool and thespreadsheet both require the data to be copied out to a separate place before anyone can ask it aquestion, and a BI tool then requires a modeling step this target customer cannot perform alone.
## Why This Positioning
Only 31 percent of new accounts today build a second view within 14 days of signing up, and the sessionrecordings behind that number put the drop at the dataset picker, the step where a user who does notalready know the schema has to construct one before asking anything. Acme's own self-serve path stillbegins there today; the differentiation above is about the step before that one. A general-purpose BI toolcannot reach that screen at all until someone has copied the account's data in and modeled it, a step thistarget customer cannot perform alone, while Acme's integrations already read the data where it lives, sothe account starts inside the operational system on day one instead of waiting on a modeling project. If ageneral-purpose BI tool's name were substituted for Acme Analytics in the statement above, the claim wouldstop being credible at the word "unlike": a BI tool has nothing to read until an account tells it what tomodel, which is the exact gap this positioning is built on.
## When We Revisit It
- Last reviewed: 2026-01-30- Check-in interval: alongside the annual strategy review each October, the same cadence the product vision already keeps, not on a shorter calendar of its own- Who notices a trigger event and brings the team back to this document: Dana Okoro, VP Product- Named triggers that call for an earlier look, beyond the scheduled check-in: a general-purpose BI vendor ships a modeling layer that a non-analyst can complete alone; the strategy's planned per-vertical modeling defaults ship and the second-view rate still does not move, which would say the dataset picker was never the gap this positioning's because-clause assumes; a lost-deal pattern starts naming the same alternative repeatedly, where today no single alternative recurs often enough to name by brand; or a senior sales or product leadership change, the same trigger the vision already watches for itself.Provenance
Section titled “Provenance”The reasoning, the history and every source, in the repository:
- Companion - the long-form argument: why these sections, where the sources disagree, and what the bundle refuses to claim
- History - what changed in this bundle, and when
- Research log - every source consulted, with what each one actually supports
- Catalog metadata - the machine-readable record this page is generated from
Catalog record: 5 sections across 1 format(s), methodology methodology-agnostic, typically owned by PMM / PM.