Appearance
Target end users & use cases
RETIRED 2026-08-08 — superseded by two pages, and it CONTRADICTED one of them
This page has been reduced to a pointer. Its 273 lines of segment curation were superseded twice over, and keeping them was actively harmful rather than merely stale:
- Audience taxonomy → User Ecosystem. This page modelled "two audiences" (business users + individuals). QRSETU has three user categories plus its own staff, and the enterprise category was absent from this page entirely — not a variant of the others, a category whose org admin governs the employee's archetype and subscription.
- Industry / use-case mapping → Industry Scope. That page does the same job correctly against the archetype × primitive model, with a five-question fit test and explicit exclusions.
⚠ Why it was retired rather than patched. Two problems that a banner cannot fix:
- It mapped segments onto "live capabilities" that do not exist. Every segment listed a "Live QRSetu fit" drawn from BioLink · Website · Digital Menu · Polls · Lead Forms · vCard. BioLink was retired in favour of the Setu Card (QRS-172) and its tables dropped; the Studio website builder is out of R1; Digital Menu is
legacy/and R1-excluded. One segment was headed "Creators & Influencers — BioLink-primary, strong today", recommending a product that no longer exists as the strongest current fit. - It contradicted Industry Scope on scope itself. This page made "Restaurants & Cafés" the flagship Wave 1 segment. The approved industry scope excludes cafés and restaurants, with a reason: they are aggregator-fed (Zomato/Swiggy) or footfall-fed, so they will not do the promotional work that seeds the platform's growth mechanic. Two overview pages disagreeing about the flagship vertical means neither is usable, and the newer, reasoned one wins.
Keeping a second industry list in sync is the duplicate-source-of-truth defect this repo has hit at QRS-249/284/287. So there is now exactly one.
Where each question is answered now
| If you came here for… | Read |
|---|---|
| Who the users are — the six user types, their onboarding, permissions, dashboards and billing subjects | User Ecosystem |
| How each user type maps to real tables — memberships, workspaces, cards, grants | User Ecosystem §1–§3 |
| Which industries QRSETU is built for, by archetype, with the primitives each needs | Industry Scope §4 |
| Whether a new industry is a fit — the five-question test | Industry Scope §2 |
| Which industries to refuse, and the reason to give | Industry Scope §5 |
| What a merchant can actually do today vs what is designed | Current Architecture State §2 |
| Whether a specific business type is supportable, with the blockers named | Business-Domain Coverage |
The one idea worth carrying forward from this page
Its most useful instinct was to curate against real capability rather than list every market a platform could theoretically serve — the original 40+ segment list was cut down deliberately. That discipline is preserved and strengthened in Industry Scope, where the test is no longer "does a feature exist" but the sharper structural one:
Does this industry's way of operating decompose into primitives we already have? A "yes" makes it configuration. A "no" makes it a new primitive, which needs a written justification that it serves ≥3 industries — the governing gate of the whole architecture.
That reframing is why the platform's cost is O(primitives), not O(industries), and it is what makes the 20th vertical cheap instead of the 20th rewrite.