An example, in full
The Appendix
The working behind every page, in four parts.
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 Appendix
The working behind every page of the brief
Prepared for
Example — Not a Client Engagement© 2026 The Premis™ Brief · ID c91c704a
01 · APPENDIXAPPENDIX A
Appendix A — the diagnosis
Analysis operating without — the gaps in full
Cohort-level churn data for SMB: which customers are churning, when in the lifecycle, and whether they adopted new features — this single dataset separates a demand mismatch from an onboarding/execution failure.
Enterprise pipeline health metrics (deal velocity, conversion rate, ACV trend over the two flat quarters) — without this, it is impossible to know whether enterprise is holding or also quietly softening.
Feature adoption rates by segment: are the three new features being used by anyone, and by which segment — this reveals whether the features are demand-misaligned or simply undelivered by sales and CS.
Who formally owns segment strategy and with what decision authority — whether there is a segment P&L or cross-functional owner whose incentives are tied to a single segment outcome.
Why this diagnosis prevailed over the alternatives
(1) The most decisive evidence is that leadership is actively debating 'simplify vs. double down on enterprise' — this is not a debate about execution tactics or market conditions; it is an unresolved strategic choice about who the product is for, which is the defining signal of strategic ambiguity rather than execution failure or demand erosion.(2) The execution frame is less supported because execution failures produce variance across reps and teams, but here both sales and CS are reporting the same directional problem from their respective vantage points — the issue is not that some reps sell complexity well and others don't, but that the entire go-to-market is pulling in two directions simultaneously; the demand frame is also less supported because there is no evidence that enterprise demand itself has eroded or that a specific alternative is winning those deals.(3) The adjudication would flip to the execution frame if cohort churn data showed SMB customers who completed structured onboarding retained at the same rate as prior cohorts — that would mean the product-segment fit is acceptable and the gap is purely in delivery; it would flip to the demand frame if enterprise pipeline velocity has also declined, indicating the product has lost relevance across both segments.
The Premis™ BriefEXAMPLE · c91c704a · 01 / 09
02 · APPENDIX
Appendix A — the diagnosis, continued
Branch: Segment strategy ownership
Examines whether any individual, team, or P&L structure has formal decision rights over which segment is primary and is held accountable for the revenue outcome of that choice.
Branch: Feature-to-revenue linkage
Examines whether the three new features are present in sales pipelines, adopted by retained customers, and correlated with closed or churned accounts.
Branch: Enterprise pipeline health
Examines deal velocity, conversion rate, and ACV trend in the enterprise segment over the two flat quarters.
Branch: SMB churn root cause
Examines when in the customer lifecycle SMB accounts churn, what their feature adoption looked like, and what exit interviews or CS data identify as the stated reason.
What determines the outcome
1
Segment decision-rights clarity: whether a formal owner with aligned incentives exists for the enterprise vs. SMB choice
2
Feature adoption rate by segment cohort vs. churn correlation
3
Enterprise deal velocity trend over the two flat-revenue quarters
BThe testsWhat sits behind each test, and where the analysis stops.
The fastest test of the diagnosis
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 — divergent answers confirm the ambiguity diagnosis within 48 hours without any new data collection.
The Premis™ BriefEXAMPLE · c91c704a · 02 / 09
03 · APPENDIX
Appendix B — the tests, continued
Test: Does any function own the segment strategy decision
Interview the heads of product, sales, and customer success separately; ask each to name the primary target customer and the single metric that defines success for that customer — then compare answers. Map incentive structures (quotas, OKRs, comp) to see whether they converge on one segment or pull in opposite directions.
RACI mapping of segment strategy decisions; incentive-to-segment alignment audit
Test: Are the three new features present in closed-won deals, adopted by retained customers, or correlated with churn in either segment?
Pull CRM and product usage data to build a 2x2: segment (SMB vs. enterprise) by feature adoption (adopted vs. not adopted), then overlay churn and close rates. This takes 1-2 weeks with existing data if instrumentation is in place.
Cohort retention analysis; feature adoption funnel by segment
Test: Is SMB churn concentrated at a specific lifecycle stage
Segment churn by time-to-churn cohort (first 90 days vs. post-renewal) and overlay with onboarding completion data and any exit survey responses. Run 8-10 rapid exit interviews with recently churned SMB accounts if structured data is thin.
Customer exit interviews; lifecycle-stage churn waterfall
Where the analysis runs out
The analysis can establish whether strategic ambiguity is the root cause and which segment the data points toward, but it cannot make the commitment to exit or de-prioritize SMB — that requires a board-level judgment call about revenue concentration risk, the cost of a managed SMB wind-down versus the opportunity cost of continued resource split, and whether the enterprise bet carries enough pipeline to justify the transition. There is also a relational judgment: the sales team's 'too complex' diagnosis may reflect capability gaps in enterprise selling that no segment decision resolves on its own — leadership must separately assess whether the sales team can execute an enterprise-only motion before committing to it.
The Premis™ BriefEXAMPLE · c91c704a · 03 / 09
04 · APPENDIXAPPENDIX C
Appendix C — Strategy
Measure: Days to leadership segment decision from exit interview delivery
No decision made — the leadership debate is active and unresolved
Formal segment decision (SMB-first, enterprise-first, or documented dual-segment with kill criteria) made within 14 days of exit interview findings delivery
How the problem was interpreted
The product has been pulled toward enterprise complexity by three new features built without SMB-friendly configuration paths, but leadership has not formally decided whether enterprise is the target — meaning the company is neither defending its SMB base nor executing a deliberate enterprise pivot, just drifting. The core failure is that a segment strategy decision is being made by default through the product roadmap rather than by leadership intent.
The clearest driver here isn't a product problem — it's a leadership accountability gap: no one has set the rule for when an out-of-segment feature request gets turned down. Until that call is owned, even a successful SMB simplification will quietly undo itself.
The primary leverage point
Forcing leadership to a segment decision by making the churn reason code non-negotiable input — not advisory input — to the next feature planning cycle, because the mechanism of failure is unresolved strategic ambiguity being expressed through product drift, and that ambiguity is what makes every downstream fix temporary.
Option A — Force the Segment Decision
HOW IT WORKS
Immediately code the last 20-30 churned SMB exit interviews by primary reason (complexity, price, feature fit, support, competitive loss) and present the result to leadership within one week as the binding — not advisory — input to the segment strategy decision, treating the churn reason data as the kill signal that resolves the simplify-vs-enterprise debate before the next planning cycle.
The Premis™ BriefEXAMPLE · c91c704a · 04 / 09
05 · APPENDIX
Appendix C — Strategy, continued
Option A
WHAT IT GIVES UP
This option explicitly defers feature adoption mapping, enterprise pipeline assessment, and product simplification execution until the churn reason is confirmed — accepting that additional SMB exits may occur during the one-week diagnostic window.
Option B — Contained SMB Simplification Pilot
HOW IT WORKS
Run a two-week exit interview analysis correlated with product usage logs to isolate which of the three enterprise features appear in churn patterns, then immediately offer a simplified UI configuration path to at-risk SMBs (those using fewer than two of the three new features) as a 60-day reversible pilot — monitoring retention lift before committing any roadmap resources to a full SMB product track.
WHAT IT GIVES UP
This option does not resolve leadership's strategic ambiguity or establish segment governance — it treats the symptom (SMB friction) without forcing the organizational decision on segment prioritization, meaning the drift mechanism that caused the problem remains intact.
Option C — Enterprise Bet Validation First
HOW IT WORKS
Conduct a two-week diagnostic on enterprise pipeline health — win rates, deal velocity, competitive win/loss reasons, and average contract value trend — since the three new enterprise features shipped, to determine whether the product complexity that is driving SMB churn is actually generating commensurate enterprise revenue or is a strategic bet that has not paid off.
WHAT IT GIVES UP
This option delays the fastest path to SMB churn diagnosis — trading immediate validation of the complexity hypothesis for evidence of whether the enterprise motion is working, which means SMB attrition continues to compound during the diagnostic window with no concurrent retention action.
Option R — Split the Product
HOW IT WORKS
Spin the simple SMB core into a self-serve product line and refocus the flagship on enterprise — stop forcing one roadmap to serve two masters.
The Premis™ BriefEXAMPLE · c91c704a · 05 / 09
06 · APPENDIX
Appendix C — Strategy, continued
Option R
WHAT IT GIVES UP
A single unified roadmap, and roughly a quarter of engineering capacity during the split.
SMB exit interview reason code concentration
WHY THIS MEASURE
This is the single leading indicator that either confirms the primary hypothesis and unlocks the strategic decision or falsifies it and forces a pricing or enterprise-health pivot — it is the decision gate, not a lagging outcome.
SMB monthly churn rate by cohort
WHY THIS MEASURE
Cohort segmentation isolates whether churn is driven by the feature additions specifically or by a broader trend predating them, which is the confound that could invalidate the entire primary hypothesis.
Feature adoption rate for the three new enterprise features among active SMB accounts
WHY THIS MEASURE
If SMBs are not adopting the enterprise features at all, the complexity problem is UI exposure and navigation, not feature depth — this distinction determines whether the fix is a simplified onboarding path or a full feature-gating architecture.
WHY THIS RECOMMENDATION
This is the only path that forces the decision the company keeps deferring — commit to SMB or to enterprise — instead of feeding the debate with more analysis. Making the real reasons customers leave a binding input to the next planning cycle puts the segment question on the table with a deadline; the two alternatives produce useful evidence but leave that gap open. It is also the lowest-effort, highest-return move of the three, so commit to it rather than run another parallel experiment.
DExecutionThe registers: what would break the plan, and the calls held for you.
The Premis™ BriefEXAMPLE · c91c704a · 06 / 09
07 · APPENDIX
Appendix D — Execution, continued
WHAT TELLS YOU TO STOP OR PIVOT
1
Exit interview data is too thin or too dominated by 'other' codes to produce a clean signal, leaving leadership without the binding input the strategy depends on and extending the strategy debate into the next feature planning cycle
Early signalT1 returns fewer than 20 usable records, or more than 30% of coded records land in the 'other' category after T2 coding — either outcome means the 60% threshold cannot be meaningfully tested and the fallback diagnostic must be triggered immediately
2
Leadership accepts the churn data in the T5 meeting but then allows individual product or sales leaders to quietly re-admit out-of-segment features into the backlog, making the kill criteria framework a document rather than a practice
Early signalThe T12 governance checkpoint at day 45 finds one or more in-flight features that entered the backlog after T8 sign-off without a documented kill-criteria override — any single instance signals that the framework is not being enforced and structural accountability is missing
3
The churn signal is genuinely mixed — complexity and price both score near 40-50% — and leadership uses the ambiguity to defer the segment decision past the next feature planning cycle, precisely the outcome the strategy was designed to prevent
Early signalT2 frequency table shows no single reason category above 45%; leadership meeting in T5 ends without a documented commitment and is rescheduled — the absence of a written decision by day 14 is the earliest sign that the plan has failed to force the decision
The Premis™ BriefEXAMPLE · c91c704a · 07 / 09
08 · APPENDIX
Appendix D — Execution, continued
HELD FOR HUMAN JUDGMENT
1
Whether to treat the churn data as truly binding or to allow leadership to reopen the debate if the signal is uncomfortable
CEO’s callEven with a pre-agreed 60% threshold documented in T7, leadership may experience political pressure from enterprise-oriented board members or major enterprise customers to override a complexity-dominant churn signal. No analysis can prevent this override — it requires the CEO to hold the room to the pre-committed rule.
2
Which of the four non-primary segment treatment options to choose — abandon, partner, simplified track, or dual UI
CEO and Head of Product Management’s callThis decision involves customer relationship commitments, partner economics, engineering capacity, and brand positioning tradeoffs that cannot be resolved by data alone. The right answer depends on relationships with specific enterprise accounts, partnership terms, and the organization's appetite for technical complexity.
3
Whether to adjust sales rep commission structures and quota assignments to align with the new segment priority
VP Sales and Chief Revenue Officer’s callCommission restructuring involves legal constraints, retention risk for high performers, and mid-cycle morale impacts that require human judgment about individual rep circumstances and organizational trust. A data model cannot predict whether a given rep will exit or adapt.
The Premis™ BriefEXAMPLE · c91c704a · 08 / 09
09 · APPENDIX
Appendix D — Execution, continued
HELD FOR HUMAN JUDGMENT, continued
4
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
VP of Product and Head of Customer Success’s callIf fewer than 20 usable records exist or if a large proportion are coded 'other,' the statistical basis for the 60% threshold collapses. A human must judge whether to proceed on thinner data, commission new exit calls, or immediately trigger the fallback enterprise diagnostic — no rule can make this call without understanding the political cost of delay.
5
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
Head of Product Management and VP Sales’s callStopping in-flight work affects team morale, vendor commitments, and sales promises already made to enterprise prospects. The descope decision requires understanding which specific customers or deals were promised the feature and whether canceling it costs more than completing it.
The Premis™ BriefEXAMPLE · c91c704a · 09 / 09
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