The logic behind every screen
Every distributor gets one report built from four moving parts. Understanding the selection rules is what lets you approve the copy: each rule below decides which fixed block a respondent sees.
A report is always: one overall tier verdict, five dimension reads (one per dimension, chosen by that dimension's level), one primary-constraint recommendation (driven by the lowest dimension), and an unscored context readout that sizes the operation. Scale is never scored — it only sets how much each constraint costs.
Overall tier — by total score (0–100)
| Tier | Score range | What it signals |
|---|---|---|
| Orchestrated | 85–100 | Largely automated and proof-driven; scale is an advantage. |
| Scalable | 65–84 | Substantially systematized; a few constraints left before scaling. |
| Coordinated | 40–64 | Repeatable in places, but still leans on manual effort. |
| Manual | 0–39 | Runs on people and manual effort; each new program adds load. |
Dimension level — by that dimension's points (0–6)
| Level | Points | Bar |
|---|---|---|
| Constrained | 0–2 | The dimension is a bottleneck. |
| Developing | 3–4 | Workable, but strains at scale. |
| Strong | 5–6 | A scalable foundation. |
Two rules that override the simple average
| Rule | What it does |
|---|---|
| Floor rule (cap) | If any single dimension is essentially absent (0–1 of 6), the tier is capped at Coordinated no matter how high the average — because an operation isn't scale-ready with a core capability missing. Only bites when the raw tier would otherwise be Scalable or Orchestrated. |
| Primary constraint | The lowest-scoring dimension becomes the headline constraint and selects the recommendation. Ties break in fixed order: Speed → Personalization → Partner Adoption → Governance → Measurement. |
Two recommendations branch further
| Constraint | Branches on | Variants |
|---|---|---|
| Personalization | The tiers/types question (Q3) | 2 — "sends the same to all" (under-segments) vs. "rebuilds by hand" (hand-builds) |
| Partner Adoption | The barrier question | 5 — time · complexity · relevance · technical setup · unsure |
The headline verdict (5 states)
The top of every report. One of these four tiers, plus the capped variant that appears when the floor rule fires. Score shown is representative of the range.
What each dimension says at each level (15 reads)
Every report shows all five dimension rows. Each row prints one of three reads, chosen by that dimension's score. Bars are shown at a representative width for the level.
The headline constraint & recommended move (10 blocks)
The most important block for the respondent — and the one that leads into the demo. Whichever dimension scores lowest prints its block here. Personalization and Partner Adoption each branch, so all variants are shown.
How the pieces come together (one per tier state)
Five complete reports as a distributor would receive them — one for each tier state, exercising the floor rule and the branch logic. These are illustrative profiles, not the only reports possible; the blocks above are the exhaustive set.
Context readout & what sales receives
Two blocks that aren't part of the score. The context readout is parametric — it reads back the operation's size. The sales capture panel is never shown to the respondent; it's the lead record.