An example, in full
The Brief
The argument, start to finish.
Every page below is the real output of one run. Names and figures belong to an example engagement; each sheet is stamped as such.
The Premis™ Brief
The Decision
Whether to commit the product, GTM resources, and success model to the enterprise segment or the SMB segment — and retire the other as a primary growth bet.
Prepared for
Example — Not a Client Engagement© 2026 The Premis™ Brief · ID c91c704a
01 · THE DECISION
The call
This is the only path that forces the decision the company keeps deferring
IT STANDS ON ONE ASSUMPTION — AND ONE THING WOULD END IT
IF IT HOLDS
Departing SMB customers gave specific enough reasons that complexity can be cleanly separated from price. The 90-day plan proceeds — 16 tasks, day 0 to 90.
THE TRIPWIRE
If the exit reasons come back mixed or mostly about price rather than a clear complexity majority, the ambiguity isn't resolved.
TEST IT BEFORE YOU COMMIT — 48 HOURS, NO NEW DATA
Ask the heads of product, sales, and customer success in separate conversations to name the primary target customer and the metric that defines success for that customer.
THE OPTIONS, IN ONE LINE EACH
A · TAKENForce the Segment Decision — This option explicitly defers feature adoption mapping, enterprise pipeline assessment.8 · 2 · 4
BContained SMB Simplification Pilot — This option does not resolve leadership's strategic ambiguity or establish segment governance7 · 4 · 3
CEnterprise Bet Validation First — This option delays the fastest path to SMB churn diagnosis7 · 3 · 5
R · REFRAMESplit the Product — Splitting the product doubles the roadmap while the diagnosis is untested9 · 8 · 8
WHERE THIS READING CAME FROM
1/3
Key drivers quoted from your own material
2/3
Inferred by the engine — verify before acting
4
Evidence gaps named up front, not papered over
THE TWO TO CHECK
Segment decision-rights clarity · Enterprise deal velocity trend — neither appears in the material you supplied.
IN CIRCULATION FORM
The Decision Memo carries this page and the ninety days in three pages — for whoever has to act on the call without reading the argument behind it.
The Premis™ BriefEXAMPLE · c91c704a · 01 / 12
PROBLEM TYPE
Strategic ambiguity
CONFIDENCE
Medium
TESTS
3
EVIDENCE GAPS
4
TASKS
16
NOT MEASURED
TODAY
TODAY
3/4
THE BRIEF AT A GLANCE
The organization has never formally chosen its primary segment
so sales optimizes for enterprise, CS absorbs SMB churn, and product ships features that serve neither cohesively — producing two quarters of flat growth despite investment.
THE RECOMMENDATION
Force the Segment Decision
This is the only path that forces the decision the company keeps deferring
IMPACT
8/10
EFFORT
2/10
RISK
4/10
T-T-VALUE
0-30D
THE NEXT NINETY DAYS, IN ONE LINE EACH
DAYS 0-30D · 7
Retrieve, code, and validate SMB churn signal
DAYS 30-60D · 5
Translate the leadership segment decision into a written feature triage framework and kill criteria, align sales and CS teams to the new strategy
DAYS 60-90D · 4
Measure whether the strategy is working, lock in structural governance before the next feature planning cycle.
THE FOUR NUMBERS THAT SAY IT WORKED
SMB exit interview reason-code concentration
More than 60% of departing SMBs citing complexity within 7 days
SMB monthly churn rate by cohort
Churn rate for pre-feature cohort stabilizes or declines within 90 days
Feature adoption rate for the three new enterprise features
Adoption rate mapped and baselined within 30 days
Days to leadership segment decision
Formal segment decision
The Premis™ BriefEXAMPLE · c91c704a · 02 / 12
CONTENTS
Twelve pages, in the order a decision actually gets made.
READ THIS FIRST · 3 PAGES
The decision
01
Executive summary
02
Contents
03
THE PLAN · 4 PAGES
Options & What would change it — opener
08
Strategy
09
What would change this answer
10
The 90-day plan
11
THE ARGUMENT · 4 PAGES
Diagnosis & Evidence — opener
04
The diagnosis
05
The evidence
06
The tests
07
WHAT WE WON’T DECIDE · 1 PAGE
What we won’t decide
12
TWO COMPANION DOCUMENTS
The Decision Memo is this brief in three pages, for whoever has to act on it without reading the argument. The Appendix carries the full reasoning — every hypothesis, test protocol and adjudication in longhand.
THREE WAYS TO READ IT
Ten minutes before the meeting — the decision, the glance, and the pressure track.
01 · 02 · 11
Defending the call — the argument in full, and what would change it.
04 – 07
Acting on it — the option space, the plan, and the calls held for you.
08 – 12
The Premis™ BriefEXAMPLE · c91c704a · 03 / 12
PART TWO · THE ARGUMENT
02
What is actually wrong, and how do we know?
Competing reads were argued separately before one was taken forward.
Diagnosis
The read, and its strongest alternative
Evidence
The branches built to confirm or break it
Tests
What confirms it, what abandons it
The Premis™ BriefEXAMPLE · c91c704a · 04 / 12
05 · THE DIAGNOSIS
The structural-frame and strategic-ambiguity diagnosis is most supported by the evidence
THREE READS, ARGUED SEPARATELY, THEN ADJUDICATED
CONVICTION
Structure & Operating Model
PREVAILED
72%
Demand & Market
72%
Execution & Capability
75%
WHAT DECIDED IT
Leadership is debating a binary strategic choice in real time — 'simplify or double down on enterprise' — without resolved data.
THE READ
The organization has never formally chosen its primary segment, so sales optimizes for enterprise, CS absorbs SMB churn, and product ships features that serve neither cohesively — producing two quarters of flat growth despite investment.
IF THIS IS WRONG
The execution frame's hypothesis — that features are shipping without sales enablement or CS integration, making the strategic debate premature because the organization lacks the diagnostic data to choose well.
RECONSIDER IF
Cohort churn analysis showed that SMB customers who were actively onboarded onto new features retained at prior-cohort rates, and that sales conversion is declining specifically on deals where new features are introduced.
STILL STANDING
When decision rights over segment focus and GTM strategy are ambiguous across functions, each optimizes locally (sales closes enterprise deals; CS tries to retain SMB; product builds without clear target buyer clarity).
THE FRAGILITY OF THIS READ, COMPUTED
Three of the four assumptions carrying this diagnosis would change the call if they broke — and each has an observable signal that arrives first. The full table is on page 10.
The Premis™ BriefEXAMPLE · c91c704a · 05 / 12
06 · THE EVIDENCE
How we know — the issue tree, and the branch built to break it.
01 · SUPPORTS
Segment strategy ownership
No owner exists or accountability is split across functions with conflicting metrics
02 · SUPPORTS
Feature-to-revenue linkage
Features show low adoption across both segments and are absent from closed-won deals
03 · SUPPORTS
Enterprise pipeline health
Enterprise pipeline is healthy and growing but not converting to revenue at the same rate
04 · CHALLENGES
SMB churn root cause
SMB churn clusters at onboarding or early activation
DRAWN FROM THE ISSUE TREE IN THIS BRIEF — EACH BRANCH STATES WHAT ITS FINDING WOULD MEAN, IN BOTH DIRECTIONS.
WHAT ACTUALLY DETERMINES THE OUTCOME
1
Segment decision-rights clarity — whether a formal owner with aligned incentives exists for the enterprise vs. SMB choice
NOT IN THE MATERIAL YOU SUPPLIED · ENGINE INFERENCE
2
Feature adoption rate by segment cohort vs. churn correlation
QUOTED FROM YOUR OWN MATERIAL
3
Enterprise deal velocity trend over the two flat-revenue quarters
NOT IN THE MATERIAL YOU SUPPLIED · ENGINE INFERENCE
WHAT DETERMINES THE OUTCOME
Segment decision-rights clarity — whether a formal owner with aligned incentives exists for the enterprise vs.
Feature adoption rate by segment cohort vs. churn.
Enterprise deal velocity trend over the two flat-revenue.
WHY THE LAST BRANCH EXISTS
The branch that can break this read: Segment strategy ownership. If a clear segment owner exists and has made a call, the diagnosis shifts toward execution failure in delivering that stated strategy. A tree with no branch against you is decoration.
The Premis™ BriefEXAMPLE · c91c704a · 06 / 12
SECTION
07
TESTS
3
FASTEST
48 HRS
NEW DATA
REQUIRED
REQUIRED
SOME
PLATE
04
07 · THE TESTS
How you would find out for yourself — and what would make us drop the whole read.
T1
Does any function own the segment strategy decision
CONFIRMED IF
Divergent answers from three functional leaders and misaligned incentives confirm the strategic ambiguity hypothesis
ABANDONED IF
If all three leaders name the same segment and their metrics align, the ambiguity frame collapses and the diagnosis
T2
Are the three new features present in closed-won deals, adopted by retained customers.
CONFIRMED IF
Low adoption and zero appearance in closed-won deals across both segments confirms features were built without a segment anchor
ABANDONED IF
High enterprise adoption with strong retention but near-zero SMB adoption shifts the diagnosis: the product has already de facto chosen a segment and the real.
T3
Is SMB churn concentrated at a specific lifecycle stage
CONFIRMED IF
Churn concentrated at renewal among customers who completed onboarding and used the product
ABANDONED IF
Churn concentrated in the first 30-60 days among customers with incomplete onboarding
The Premis™ BriefEXAMPLE · c91c704a · 07 / 12
PART THREE · THE PLAN
03
What should you do about it?
Force the Segment Decision — one of four paths argued independently, one of which questioned the premise itself.
Options
Where the paths actually sit
What would change it
The assumptions, the flips, the signals
The plan
The ninety days, and the two-week track
The Premis™ BriefEXAMPLE · c91c704a · 08 / 12
09 · THE OPTION SPACESTRATEGY
Force the Segment Decision — and what the other three paths cost.
Big swing · light lift
Big swing · heavy lift
Contained · light lift
Contained · heavy lift
↑ Impact
Effort →
A
B
C
R
A
Force the Segment Decision
IMPACT 8 · EFFORT 2 · RISK 4
B
Contained SMB Simplification Pilot
IMPACT 7 · EFFORT 4 · RISK 3
Why not: This option does not resolve leadership's strategic ambiguity or establish segment governance
C
Enterprise Bet Validation First
IMPACT 7 · EFFORT 3 · RISK 5
Why not: This option delays the fastest path to SMB churn diagnosis
R
Split the Product
IMPACT 9 · EFFORT 8 · RISK 8
Argued against, on the record: Splitting the product doubles the roadmap while the diagnosis is untested
A · TIME TO VALUE 0-30D
Retrieve and audit all SMB exit interview records from the past 6 months
B · TIME TO VALUE 30-90D
Run a two-week exit interview analysis correlated with product usage logs to isolate which of the three enterprise features appear in churn patterns.
C · TIME TO VALUE 30-90D
Conduct a two-week diagnostic on enterprise pipeline health
HOW TO READ IT Position is impact against effort on the engine’s 10-point scale. The filled mark is the recommendation. The dashed square is the reframe — it questions the problem as posed; its case-against is on the record, with the condition that reopens it.
The Premis™ BriefEXAMPLE · c91c704a · 09 / 12
10 · WHAT WOULD CHANGE THIS ANSWER
Three of the four ways this could be wrong would change the call — and every one announces itself first.
THE LOAD-BEARING ASSUMPTIONS · RANKED BY FRAGILITY
HIGHDeparting SMB customers gave reasons specific enough that complexity separates cleanly from price.Watch for: Coded exits come back mixed — price and complexity both near 40%, or a third of records land in “other”.→ FLIPS TO C
MEDIUMLeadership will treat the churn data as binding once it is delivered.Watch for: The decision meeting ends without a documented commitment and is rescheduled.→ FLIPS TO B
MEDIUMAt least 20 usable exit-interview records exist from the past six months.Watch for: The first-week retrieval returns fewer than 20 codable records.→ FLIPS TO B
LOWEnterprise pipeline health is knowable from existing CRM data within two weeks.Watch for: The two-week diagnostic slips because win-rate and velocity have to be reconstructed by hand.CALL SURVIVES
THE SCENARIO TABLE
Every assumption holdsA
Departing SMB customers gave reasons specific enough.C
Leadership will treat the churn data as binding once it is.B
At least 20 usable exit-interview records exist from.B
Enterprise pipeline health is knowable from existing CRM.A
THE MARGIN
+2
The recommendation’s lead over its nearest rival on the engine’s own scores (impact − effort − risk).
BASIS: THE 10-POINT SCORES. COMPUTED, NOT PROMPTED.
THE VERDICT
2/5
Scenarios in which the call stands unchanged.
RIGHT UNDER EVERY SCENARIO — START THESE REGARDLESS
Retrieve and code the last six months of SMB exit interviews
Name a single accountable owner for the segment decision
Baseline adoption for the three new enterprise features
The Premis™ BriefEXAMPLE · c91c704a · 10 / 12
11 · THE 90-DAY PLAN
Seven of sixteen tasks land before day 30 — the diagnosis is tested before you spend.
90-Day Objective
Convert churned SMB exit interview data into a binding leadership decision on target segment strategy, formalize kill criteria before the next feature planning cycle, and validate the enterprise pipeline's viability — all within 90 days.
Sixteen tasks across 90 days, front-loaded — seven land in the first window.
Days 0–30
Retrieve, code, and validate SMB churn signal; run parallel enterprise and feature-adoption audits.
7 tasks
Days 30–60
Translate the leadership segment decision into a written feature triage framework and kill criteria.
5 tasks
Days 60–90
Measure whether the strategy is working, lock in structural governance before the next feature planning cycle.
4 tasks
0306090
T1–T2
Retrieve and audit all SMB exit interview records from the past 6 months
T3–T4
Audit SMB-tier adoption of the three new enterprise features to quantify friction exposure
T5–T6
Synthesize churn findings into a binding decision brief and present to leadership
T7
Define the plan-invalidation rule: document what churn signal outcome triggers fallback to enterprise-first path
T8–T9
Document feature-to-segment mapping matrix and formal kill criteria
T10–T11
Audit current feature backlog against kill criteria and produce disposition table
T12
Conduct a governance checkpoint: confirm segment decision is holding and no backlog drift has occurred
T13–T14
Produce a 60-day outcome report comparing SMB churn rate, enterprise win rate, and backlog compliance versus pre-intervention baselines
T15
Embed kill criteria review as a standing agenda item in the recurring product planning process
T16
Conduct day-75 leadership review: determine whether 90-day plan achieved its forcing-function objective or requires a follow-on phase
Drawn from the 90-day plan in this brief — the complete task-level plan lives in your workspace.
IF YOU HAVE TWO WEEKS AND THREE FIRES
Start regardless: Retrieve and code the last six months of SMB exit interviews; Name a single accountable owner for the segment decision; Baseline adoption for the three new enterprise features. Right under every scenario the stability table maps.
The rule under dirty data: If the exit reasons come back mixed or mostly about price rather than a clear complexity majority, the ambiguity isn't resolved.
The Premis™ BriefEXAMPLE · c91c704a · 11 / 12
12 · WHAT WE WON’T DECIDE
Five calls stay with you — and how the rest was built.
THESE ARE YOURS TO DECIDE — THE ENGINE WILL NOT
01
Whether to treat the churn data as truly binding or to allow leadership to reopen the debate if the signal is uncomfortable
Even with a pre-agreed 60% threshold documented in T7, leadership may experience political pressure from enterprise-oriented board members or major enterprise.
02
Which of the four non-primary segment treatment options to choose — abandon, partner, simplified track, or dual UI
This decision involves customer relationship commitments, partner economics, engineering capacity.
03
Whether to adjust sales rep commission structures and quota assignments to align with the new segment priority
Commission restructuring involves legal constraints, retention risk for high performers.
04
Whether the exit-interview data is solid enough to act on, or whether the gaps found early mean it can't be trusted to force the decision
If fewer than 20 usable records exist or if a large proportion are coded 'other,' the statistical basis for the 60% threshold collapses.
05
How to disposition in-flight enterprise feature work that has already been staffed and partially built when the backlog audit in T10 flags it as out-of-segment
Stopping in-flight work affects team morale, vendor commitments, and sales promises already made to enterprise prospects.
HOW THIS BRIEF WAS BUILT
Competing reads, argued separately
Independent frames build rival diagnoses; an adjudicator commits and records why the others lost.
Every figure resolved
Each number is traced to your words, derived with the working shown, or flagged as the engine’s own — arithmetic, no model call.
Nothing invented to fill a gap
Evidence gaps are named up front rather than papered over.
The reasoning is kept
Every hypothesis, protocol and adjudication in longhand — the Appendix, and your workspace at premisbrief.com.
The Premis™ BriefEXAMPLE · c91c704a · 12 / 12
The Premis™ Brief
This report is produced for the named decision-maker and is confidential. It is not a substitute for legal, financial, or regulated professional advice. All judgements and decisions remain with the reader.
© 2026 The Premis™ Brief