Appearance
Right-sizing
What the Right-sizing and Tiers screens manage — and why steering buyers to the cheapest sufficient system is the product's differentiator.
What it is
Two admin surfaces configure the recommendation engine's cost behavior:
- Right-sizing rules — admin-editable data (not code) that map buyer requirements to the systems satisfying them. The matcher evaluates these rules and returns ranked candidates, each carrying the rationale of the rules that recommended it.
- The tier ladder — the ordered list of relative cost tiers (Budget → Mid-range → Premium → Ultra Premium). Ladder order is the cost model: right-sizing is a pure cost ordering over already-sufficient candidates, so no absolute pricing ever enters the engine.
Together they encode the "NW Acoustical 645 → NW Aluminum 640 → SL45" insight: when a cheaper system genuinely meets the requirement, surface it.
Why it exists
Over-specification is the failure mode with the largest downstream cost: an over-spec'd system is the one that gets value-engineered out at bid — sometimes to a competitor. A sales-led path naturally anchors high; NanaSelect deliberately anchors to sufficiency. Because the matcher only returns systems that already satisfy the requirement, a lower-tier candidate is by construction sufficient-and-cheaper — recommending it builds the trust that makes the recommendation persuasive ("right-size, don't up-sell" — see why it works).
Rules and the ladder live as admin-editable data so product experts can tune selection behavior without a deploy.
In the admin
| Screen | How-to |
|---|---|
| Right-sizing | Managing rules |
| Tiers | Managing cost tiers |
Learn more
- Right-sizing rule representation — the rule fields and semantics.
- Cost-tier right-sizing — the engine's API and behavior.
- Recommendation matching and recommendation API.