Appearance
Persona feature map: who logs in, what they see, where the data goes
This page and personas and access are deliberately different views. Do not restate one in the other
| Answers | |
|---|---|
| Personas and access | Identity. Authentication, RBAC scope, trust boundaries, login routing, must-never-see |
| This page | Navigation. What each login sees and does, which plan each feature belongs to, and where the data flows |
📘 Two pages describing one subject is how QRS-843 happened. Persona names here are taken verbatim from that page; if they ever disagree, that page wins on identity and this one on navigation.
⚠ Read this first: no persona differentiation exists today
🧮 Every login below renders the SAME screens right now, because RBAC is 0% built
No roles, no permissions, no role_assignments, no is_admin() (QRS-803). The merchant app has 17 feature directories and not one of them is role-aware.
So this page is the TARGET navigation, not a description of the product. It is a specification to build against and a map for onboarding — never evidence that a persona's view exists. RBAC is 📘 the largest single dependency in Wave 2.
Legend
Every node carries one commercial label. The label also tells you when it is buildable, because tier and wave are the same ladder (commercial model):
| Label | Meaning | Plan | Available |
|---|---|---|---|
[Inc] | Included by default | Foundation and above | Wave 1 · Dec 2026 |
[Growth] | Plan-dependent | Growth and above | Wave 2 · Apr 2027 |
[Complete] | Plan-dependent | Complete | Wave 3 · Aug 2027 |
[Group] | Plan-dependent | Group Intelligence, min 3 outlets | Wave 3 · Aug 2027 |
[Add-on] | Paid add-on, priced separately | any | per line |
[Usage] | Usage-based, prepaid drawdown | any | Wave 1 |
[Integr] | Optional integration, external approval needed | Growth+ | ❓ gated externally |
[Future] | Not committed to any wave | — | ❓ |
Access markers used in the persona tables: R read · C create · E edit · M manage · ⛔ must never see.
0 · Does this persona need a Setu Card?
⚠ CHALLENGED AND CHANGED 2026-08-23 — the Team Leader card is REMOVED from default scope
📘 The owner asked the right question: "what actual customer-facing activity would a Team Lead perform through their own Setu Card that cannot be handled through their normal login?"
I could not answer it well enough to keep the card, so it is out. QRS-854.
The eight proposed use cases, assessed one at a time
| Proposed Team Leader card use | Verdict |
|---|---|
| Direct customer acquisition | ⚠ Conditional. Real only if the TL carries a retail target — see the rule below |
| Handling high-value prospects | 🔎 The strongest case, and it is still weak. Escalation is real on a ₹10-45 lakh purchase, but the customer already holds the rep's card and the TL can join that QR Setu conversation. A card is not what escalation needs; a conversation is |
| Continuity when a rep leaves | 🔎 Genuinely real — 🌐 29.53% attrition means the customer's contact walks out. But 📘 cards are org_owned, so the outlet keeps the customer and reassigns them. The org card and the new rep's card both cover it |
| Receiving enquiries directly | Conditional, same as acquisition |
| Sharing their professional identity | ❌ Reject. That is a LinkedIn need, not a dealership workflow |
| Booking test drives | ❌ The login does this. No card involved |
| Sharing dealership / product information | ❌ The Organisation Setu Card already does this, better, and a standee puts it on every table |
| Building a personal professional network | ❌ Reject. Not a dealership workflow, and it is the use case most likely to produce a card nobody scans |
🔎 One conditional, one real-but-covered, six rejected. That is not enough to make a card default.
The rule that replaces the assumption
The card follows the TARGET, not the TITLE.
| Setu Card | A customer-facing acquisition channel. Justified when the person is measured on customer outcomes they personally create |
| Login | An internal operational role. Justified when the person's job is to see, direct and measure other people's work |
🔎 In an Indian dealership a "Team Leader" is often a senior consultant with a team and their own retail target — in which case they are a rep with extra duties and a card is correct. Where the TL is a pure manager, it is not. The title does not tell you which; the target does.
⚠ Applying the same test to every persona, which goes beyond what was asked
🔎 It would be inconsistent to challenge the Team Leader and leave the others, and the same test moves one more: Sales Manager.
| Persona | Carries a customer-facing target? | Card |
|---|---|---|
| Sales Representative | Yes, always | ✅ Mandatory |
| Service Advisor | Yes — service retention is their number | ✅ Mandatory |
| Team Leader | Sometimes | ⚠ Optional, not default |
| Sales Manager | Rarely at a large outlet, sometimes at a small one | ⚠ Optional, not default |
| General Manager | No | ⚠ Optional |
| Dealer Principal | No | ⚠ Optional |
| Receptionist | No — they route, they do not own outcomes | ❌ Never |
| Marketing | No | ❌ Never |
| Org Admin | No | ❌ Never |
| The outlet itself | n/a | ✅ Mandatory — 1 Organisation Setu Card |
⚠ Two consequences, and the second one changes the price book
1 · The tighter card ceilings now fit the standard outlet properly
🧮 A 30-staff outlet — 20 consultants, 5 advisors, 4 team leaders, 1 sales manager:
| Cards needed | Growth's 30 | |
|---|---|---|
| Card follows title | 1 org + 30 staff = 31 | ⚠ over by 1, needs an extra card |
| Card follows target | 1 org + 25 staff = 26 | ✅ fits with room |
🔎 So this decision and the ceiling tightening reinforce each other: the standard franchise outlet now lands inside Growth's allowance instead of one card over it.
2 · The management-login allowance was too tight the moment this changed, and keeping it would have been the wrong shape
🧮 The displaced managers need logins. At that same outlet: reception 2, 4 team leaders, 1 sales manager, GM 1, CRM head 1, marketing 1, accounts 1, org admin 1 = 12 management logins.
| Allowance | Outcome |
|---|---|
| Growth at 8 (as published this morning) | 4 overflow logins × ₹2,499 = ₹9,996 extra |
| Growth at 12 | ✅ within allowance, ₹0 |
⚠ Charging ₹9,996 for the seats we just told the dealer they need instead of cards is indefensible — it would read as moving a charge rather than removing one. The allowance rises to 5 / 12 / 25, caps 10 / 20 / 45 (commercial model).
🧮 Net revenue effect of the whole decision: minus ₹4,999 per outlet. Small, and the right call — 🔎 a card forced on someone who will not use it is a slot the dealer pays for and gets nothing from, it produces no interactions, and it makes "cards issued vs staff on roll" meaningless as a health metric.
1 · The ten logins, and why there are no new ones
📘 The six personas in the brief map onto the established taxonomy without inventing a role:
| In the brief | Established persona | Card? | Login class |
|---|---|---|---|
| Receptionist / Front Desk | Receptionist | No | Management login |
| Sales Representative | Sales Representative | Yes | Included with card |
| Admin | Org Admin | No | Management login |
| Team Lead | Team Leader | ⚠ Optional — see §0 | Management login by default |
| CRM / Sales Manager | Sales Manager | ⚠ Optional — see §0 | Management login by default |
| GM / Dealer Principal | General Manager and Dealer Principal — 📘 separate personas, different scopes | Optional | Management login |
| Other operational / management | Marketing · Service Advisor | Advisor yes, Marketing no | Advisor with card, Marketing management |
Two personas are outside this page, on purpose
- Customer / Prospect — 📘 anonymous-first, no account required. They scan; they do not log in. A signup wall in front of a scanned card destroys the growth mechanic.
- QR Setu Platform Admin — our staff, on
/admin. 📘 ADR-0028:/adminand/orgare different trust boundaries that must never share a route group. A dealership persona never appears on/admin(QRS-842).
🔎 Service Advisor earns its place on money, not tidiness: 🌐 20 vehicles serviced per 1 sold, at 41.2% after-sales gross margin, and the service-reminder engine is Wave 2's revenue capability. A dealership map without aftersales misses the fattest margin in the building.
text
Car Dealership (one organisation, one or more outlets)
│
├── CARD HOLDERS — public identity + login included
│ ├── Sales Representative mandatory card
│ └── Service Advisor mandatory card
│
├── MANAGEMENT LOGINS — no public card by default, counted against 5 / 12 / 25
│ ├── Team Leader ⚠ card OPTIONAL, only if target-carrying
│ ├── Sales Manager ⚠ card OPTIONAL, only if target-carrying
│ ├── Receptionist never a card
│ ├── General Manager card optional
│ ├── Dealer Principal card optional
│ ├── Marketing never a card
│ └── Org Admin never a card
│
├── THE OUTLET ITSELF
│ └── Organisation Setu Card (occupies 1 card slot, always active)
│
└── NO LOGIN
└── Customer / Prospect (anonymous-first)2 · Setu Card map
text
Organisation (the dealer group)
│
├── Group Setu Card [Group] ships with Group Intelligence, costs no outlet slot
│
└── Outlet (a showroom or a service centre with its own P&L)
│
├── Organisation Setu Card [Inc] 1 slot, always active
│ ├── Dealership profile + hours + contact
│ ├── Vehicle catalogue + images/video [Inc] ⚠ blocked: no public media URL (QRS-852)
│ ├── Offers + promotions [Inc]
│ ├── Team directory [Inc] links to each rep's card
│ ├── Test-drive booking [Growth]
│ ├── Enquiry + contact [Inc]
│ ├── Feedback capture [Growth]
│ ├── Google review prompt [Integr]
│ └── Marketplace listing [Inc] ⚠ visibility add-ons not sellable (QRS-849)
│
├── Employee Setu Cards [Inc] org_owned, never rep_owned
│ ├── Sales Representative cards mandatory
│ ├── Service Advisor cards mandatory
│ ├── Team Leader card ⚠ OPTIONAL — target-carrying only (§0)
│ └── Sales Manager card ⚠ OPTIONAL — target-carrying only (§0)
│
└── Physical QR standees [Add-on] ₹225 each + GST
├── Reception ─┐
├── Waiting area │ each standee carries its OWN code
├── Tables │ and a first-class PLACEMENT field,
├── Vehicle displays │ so scans are attributable per position
├── Sales desks │
└── Test-drive bay ─┘⚠ Two card-layer facts that change how this page should be read
- 📘 Cards are
org_owned. With 🌐 29.53% frontline attrition, a rep-owned card is a product that helps salespeople take customers to their next employer. - 🧮 Card images do not resolve today. No public media URL exists in the codebase, so every catalogue image on a public card is unresolvable (QRS-852). The card layer is the foundation of everything below and it has a live gap at the top of it.
3 · How a scan becomes managed work
The one node that decides whether any of this works
🔎 Assigned employee. Every management view above is a fold over that field. If a card is shared, a standee is untracked, or a walk-in is logged without an assignment, the chain breaks at that node and every box downstream shows a number nobody can act on. 📘 It is why cards are org_owned, why standees carry their own codes, and why no access seat is priced high enough to make sharing rational.
4 · Persona navigation trees
4.1 · Receptionist / Front desk
text
Receptionist no card · management login
│
├── Today [Inc]
│ ├── Visitor log — the day's list [Inc]
│ ├── Log a walk-in ← 2 fields + dropdown [Inc] ⚠ must be faster than a pen
│ ├── Who is available now [Inc]
│ └── Assign to a rep [Inc]
├── Catalogue — read only [Inc]
├── Offers — read only [Inc]
├── Appointments and test drives — today [Growth]
└── Notifications [Inc]| R | Today's visitors, rep availability, the catalogue, today's bookings |
| C | Visitor entries, assignment to a rep |
| E | Their own entries, same day only |
| M | Nothing |
| ⛔ | Lead values, any rep's performance, any financials, other outlets |
| Flows up → | Every walk-in becomes a lead with a named owner and a timestamp — the input the entire management ladder folds over |
🔎 Lowest behaviour-change persona and therefore the adoption wedge. Reception must log visitors anyway; we only have to beat a pen.
4.2 · Sales Representative
text
Sales Representative card + login included
│
├── Dashboard — my day [Inc]
├── My Setu Card [Inc]
│ ├── Share — WhatsApp / QR / link [Inc]
│ ├── Who viewed it, and what they viewed [Inc] ⚠ beacon broken (QRS-734)
│ └── Appearance — palette only [Inc]
├── My Leads [Growth]
│ ├── New / unattended [Growth]
│ ├── Follow-ups due today [Growth]
│ ├── Overdue ← SLA breach [Growth]
│ └── Converted / Lost with reason [Growth]
├── My Customers [Growth]
├── Test Drives [Growth]
│ ├── Requests · Scheduled · Completed [Growth]
├── Tasks [Growth]
├── My Performance — vs my target [Growth]
├── Feedback on my interactions [Growth]
├── Catalogue and offers [Inc]
├── Enquiries ← ANONYMOUS, no account needed [Inc] ⚠ the high-volume entry point
│ ├── New enquiries assigned to me [Inc]
│ └── Reply by WhatsApp or phone [Usage]
├── Conversations ← QR SETU NATIVE CHAT [Inc] ⚠ REGISTERED consumers only (D7)
│ ├── My threads, per customer [Inc]
│ ├── AI-drafted reply, I edit and send [Add-on]
│ └── Handover to a colleague [Growth]
└── WhatsApp ← reach and notification only
├── "You have a reply" notification [Usage] ₹0.115
├── Send a utility message [Usage]
└── Campaigns ⛔ not this persona| R | Own card analytics, own leads, own customers, own tasks, own targets, the outlet catalogue |
| C | Interactions, enquiries, follow-up outcomes, test-drive requests, notes |
| E | Own lead stages and notes, own card palette |
| M | Nothing beyond their own work |
| ⛔ | Another rep's leads or customers, team or outlet performance, discounts beyond their authority, financials, other outlets |
| Flows up → | Activity, conversion, overdue count and loss reasons — attributed to them by name |
⚠ The highest behaviour-change persona in the product. Everything here asks the lowest-paid, highest-churn staff (🌐 29.53% attrition) to change a habit so a manager can measure them. 📘 It ships in Wave 1 and does not lead the sale (why).
4.3 · Service Advisor
text
Service Advisor card + login included
│
├── Dashboard — today's bay [Inc]
├── My Setu Card [Inc]
├── Service due list ← per vehicle [Growth] 🌐 41.2% gross margin
│ ├── Due by date · Due by odometer [Growth]
│ └── Contacted / Booked / No response [Growth]
├── Bookings [Growth]
├── Vehicle history ← the asset record [Growth]
├── Insurance renewal due [Complete]
├── Feedback after service [Growth]
├── Reminders sent [Usage]
└── Customers — service side [Growth]| R | Service bookings, vehicle history, own assignments, the service-due list for their outlet |
| C | Bookings, service notes, reminder sends, feedback requests |
| E | Own bookings and vehicle notes |
| M | Nothing |
| ⛔ | Sales leads and pipeline, any performance data outside their own, financials, other outlets |
| Flows up → | Retention rate, reminder-to-booking conversion, per-advisor feedback scores |
🔎 The only persona whose module produces revenue with no staff behaviour change — the reminder runs on data the dealer already has. 📘 That is why it is Wave 2's commercial lead.
4.4 · Team Leader
text
Team Leader management login · ⚠ card OPTIONAL, not default (§0)
│
├── My Setu Card ⚠ only if target-carrying (§0)
├── Everything a Sales Representative has [as above, if card-holding]
│
├── My Team [Growth]
│ ├── Per rep — activity, leads, conversions [Growth]
│ ├── Overdue follow-ups across the team [Growth] ← the one list that matters
│ ├── Unattended leads [Growth]
│ └── Reassign a lead ← rep on leave [Growth]
├── Team targets vs actual [Growth]
├── Team test-drive throughput [Growth]
└── Team feedback and review scores [Integr]| R | Every rep in their team: activity, leads, overdue, conversions, targets |
| C | Team targets, reassignments, coaching notes |
| E | Lead ownership inside the team, team target allocation |
| M | Their team's queue and workload |
| ⛔ | Other teams, outlet-wide financials, other outlets, HR or payroll data |
| Flows up → | Team activity and performance, aggregated — never raw rep-by-rep to the group |
4.5 · Sales Manager / CRM Head
text
Sales Manager management login · ⚠ card OPTIONAL, not default (§0)
│
├── Everything a Team Leader has, across all their teams
│
├── Funnel [Growth]
│ ├── By stage · By source · By loss reason [Growth]
│ └── Ageing and stalled leads [Growth]
├── Teams — side by side [Growth]
├── Lead sources — which produced business [Growth]
│ ├── Standee scans by placement [Add-on]
│ ├── Employee card shares [Inc]
│ └── Marketplace and walk-in [Inc]
├── Targets — allocate down the tree [Growth]
├── SLA policy — set the follow-up clock [Growth]
├── Discount governance [Future] ⚠ dealer-owned, never OEM-visible
├── F&I attach workflow [Future] ⚠ workflow only, never commission
└── Reports [Growth]| R | All teams in their division and outlet, funnel by stage and loss reason, source attribution |
| C | Targets, SLA policy, campaigns requests, reports |
| E | Team structure inside their division, lead routing rules |
| M | The division: people, targets, pipeline hygiene |
| ⛔ | 📘 Provider fee and platform margin — a hard line. Other outlets unless granted. Payroll |
| Flows up → | Division funnel, conversion, source ROI, SLA compliance |
⚠ Discount governance carries a legal constraint, not a preference
🌐 The CCI penalised Maruti Suzuki over a Discount Control Policy enforced by mystery shoppers, with dealer penalties to ₹2,00,000 and supply threats. A tool helping a dealer govern their own team's discounting is on the right side of that order. An OEM-facing view of dealer discount data is on the wrong side of it and must never be built.
4.6 · General Manager
text
General Manager card optional · management login
│
├── Outlet overview — one screen [Growth]
│ ├── Walk-ins · leads · test drives · conversions [Growth]
│ ├── Overdue follow-ups, outlet-wide [Growth]
│ └── Sales AND service side by side [Growth]
├── People — per-person performance [Growth]
├── Setu Card health [Inc]
│ ├── Published / not published / needs attention [Inc]
│ └── Cards issued vs staff on roll [Inc]
├── Google Business — this outlet [Integr]
│ ├── Reviews and ratings [Integr]
│ ├── Respond [Integr]
│ └── Service-recovery queue ← unhappy feedback [Integr]
├── Standee performance by placement [Add-on]
├── Targets — outlet level [Growth]
├── Automation and workflows [Complete]
└── Reports and exports [Growth]| R | The whole outlet, both divisions, per-person performance, reviews, card health |
| C | Outlet targets, workflow rules, review responses |
| E | Outlet structure, teams, assignment policy |
| M | The outlet end to end |
| ⛔ | 📘 Provider fee and platform margin. Other outlets unless the group grants oversight. Another outlet's member_owned data |
| Flows up → | Outlet performance as one comparable row in the group view |
4.7 · Dealer Principal / Owner
text
Dealer Principal card optional · management login
│
├── Group overview [Group]
│ ├── Every outlet, every brand, side by side [Group] ← the moat
│ ├── One funnel across brands [Group]
│ ├── Personnel performance across outlets [Group]
│ └── Group targets [Group]
├── Drill down: group → outlet → team → rep → customer [Group]
├── Outlet comparison and ranking [Group]
├── Google Business — all locations [Group]
├── Campaigns published once, targeted at a subtree [Complete]
├── Subscription and billing [Inc] ⚠ web only, never in-app (ADR-0002)
└── Everything a General Manager has, per outlet [Growth]| R | Every outlet, every brand. All personnel performance. Consolidated funnel and service book |
| C | Group targets, group campaigns, outlet structure |
| E | Organisation tree, sharing flags, oversight grants |
| M | The group |
| ⛔ | 📘 Provider fee and platform margin. ⚠ An employee's member_owned personal business and consumer history — never, at any depth |
| Flows up → | Nothing. This is the top of the dealership tree |
Why this persona is the whole commercial argument
🔎 Each brand's mandated system reports upward to its own manufacturer, so consolidation today is a person with a spreadsheet at month end. 🌐 The strongest local incumbent structurally cannot sell this — its customer is the manufacturer, and a cross-brand view is the one thing a manufacturer does not want dealers to have.
4.8 · Marketing
text
Marketing no card · management login
│
├── Campaigns [Add-on]
│ ├── Build and schedule [Add-on]
│ ├── Target a subtree [Complete]
│ ├── Festival / seasonal [Add-on]
│ └── Managed service — we run it [Add-on] ⚠ labour, capped ~15 accounts
├── WhatsApp
│ ├── Templates and approval status [Inc]
│ ├── Opt-in ledger [Inc]
│ ├── Message balance and recharge [Usage]
│ └── Delivery and read reporting [Inc]
├── Google Business [Integr]
│ ├── Business information [Integr]
│ ├── Review responses [Integr]
│ ├── Review request workflows [Integr] ⚠ ask EVERYONE, never only the happy
│ └── Review analytics, per outlet and per rep [Integr]
├── Offers and promotions on the cards [Inc]
├── Marketplace listing [Inc]
│ └── Featured placement [Future] ⚠ not sellable (QRS-849)
├── Standee orders and placement map [Add-on]
└── Audience counts and campaign attribution [Growth]| R | Campaign performance, audience counts, aggregate funnel, review analytics |
| C | Campaigns, templates, offers, review requests, standee orders |
| E | Card offers, business information, campaign schedules |
| M | The messaging and reputation surface |
| ⛔ | Individual customer records beyond campaign membership. Per-rep pipeline detail. Financials |
| Flows up → | Source ROI and campaign attribution into the Sales Manager funnel |
⚠ Review requests must go to EVERYONE
🌐 Google prohibits review gating — soliciting selectively by expected sentiment. The internal feedback score routes a service-recovery task to a manager; it must not decide who is asked for a review. The asset at risk is the dealer's own profile (QRS-853).
4.9 · Org Admin
text
Org Admin no card · management login · lands on /org
│
├── Organisation
│ ├── Outlets — the tree [Group]
│ ├── Locations — addresses, free [Inc]
│ └── Sharing flags — default OFF [Group]
├── People
│ ├── Invite / deactivate [Inc]
│ ├── Roles and scopes [Growth]
│ └── ⚠ Deactivate → the card slot frees [Inc] (QRS-850)
├── Setu Cards
│ ├── Issued vs allowance [Inc]
│ └── Buy additional cards — ₹4,999/yr [Inc]
├── Access
│ ├── Management logins used vs 5 / 12 / 25 [Inc]
│ └── Buy additional login — ₹2,499/yr [Inc]
├── Subscription
│ ├── Plan and renewal [Inc]
│ ├── Invoices — all prices + 18% GST [Inc]
│ └── ⚠ Upgrade — WEB ONLY, no in-app CTA [Inc] (ADR-0002)
├── Storage — used vs 5 / 25 / 100 GB [Inc]
└── Audit log [Growth]| R | Organisation structure, seats, roles, subscription, usage against every allowance |
| C | Users, roles, outlets, locations |
| E | The tree, sharing flags, role scopes, plan |
| M | The tenant |
| ⛔ | ⚠ Operational customer data they have no role for. Anything outside their organisation. Any other tenant. Platform configuration |
| Flows up → | Nothing operational. Usage and billing flow to QR Setu, not to the dealer's own hierarchy |
⚠ Org Admin is a CUSTOMER's employee, not our staff
📘 Powerful inside one organisation, powerless outside it. Conflating this with Platform Admin is privilege escalation. ⚠ And note which surface is higher-consequence: a bug on /admin exposes our platform data to our own staff; a bug on /org exposes one customer to another (QRS-842).
5 · The upward-visibility ladder
| Level | What aggregates here | What it does NOT get |
|---|---|---|
| Rep / Advisor | Own activity and customers | Anyone else's |
| Team Leader | Team activity, overdue, conversion | Other teams |
| Sales Manager | Division funnel, source ROI, SLA compliance | Provider fee, platform margin |
| General Manager | Whole outlet, both divisions, per person | Other outlets unless granted |
| Dealer Principal | Every outlet and brand, drillable to one customer | ⚠ An employee's member_owned business |
⚠ Sharing flows DOWN; oversight flows UP. They are never symmetric
📘 Sharing is an explicit flag, default off — a child may use an ancestor's resources. Oversight is a subtree read scope — an ancestor may read, never write. ⚠ And oversight applies only to org_owned descendants: an employee's personal business and consumer history must never be visible to their employer.
6 · Feature → plan → persona
| Module | Plan | Receptionist | Rep | Advisor | TL | Sales Mgr | GM | DP | Marketing | Org Admin |
|---|---|---|---|---|---|---|---|---|---|---|
| Organisation Setu Card | [Inc] | R | R | R | R | R E | R E | R E | R E | M |
| Employee Setu Cards | [Inc] | — | R E own | R E own | R team ⚠ | R div ⚠ | R | R | — | M |
| Catalogue and offers | [Inc] | R | R | R | R | R E | R E | R E | R E | M |
| Visitor register | [Inc] | C E | R own | — | R team | R | R | R | — | — |
| Card view analytics | [Inc] | — | R own | R own | R team | R div | R | R | R | — |
| Marketplace listing | [Inc] | — | R | R | R | R | R | R | R E | M |
| Leads and follow-up SLA | [Growth] | C | C E own | — | E team | E div | R | R | — | — |
| Customers / parties | [Growth] | C | C E own | C E service | R team | R div | R | R | aggregate | — |
| Test drives | [Growth] | R today | C E | — | R team | R div | R | R | — | — |
| Service due + reminders | [Growth] | — | — | C E | — | R | R | R | — | — |
| Targets and performance | [Growth] | — | R own | R own | C E team | C E div | C E outlet | C E group | — | — |
| Team and funnel rollups | [Growth] | — | — | — | R team | R div | R outlet | R group | aggregate | — |
| Roles and scopes | [Growth] | — | — | — | — | E div | E outlet | E group | — | M |
| Audit log | [Growth] | — | — | — | — | — | R | R | — | R |
| Insurance renewal | [Complete] | — | — | R | — | R | R | R | — | — |
| Automation / workflows | [Complete] | — | — | — | — | E | C E | C E | E | — |
| Subtree campaign targeting | [Complete] | — | — | — | — | — | R | C E | C E | — |
| Cross-brand consolidation | [Group] | — | — | — | — | — | — | R | — | — |
| Group targets and ranking | [Group] | — | — | — | — | — | R | C E | — | — |
| WhatsApp utility messages | [Usage] | — | C | C | R | R | R | R | M | — |
| WhatsApp campaigns | [Add-on] | — | — | — | — | R | R | R | C E | — |
| Physical QR standees | [Add-on] | R | R | R | R | R | R E | R E | C E | M |
| Managed campaign service | [Add-on] | — | — | — | — | R | R | R | R | — |
| Google Business portal | [Integr] | — | — | — | R | R | R E | R E | M | — |
| Discount governance | [Future] | — | — | — | — | R | R | R | — | — |
| F&I attach workflow | [Future] | — | — | — | — | R | R | R | — | — |
| Featured marketplace placement | [Future] | — | — | — | — | — | — | R | R | — |
| Subscription and billing | [Inc] | — | — | — | — | — | — | R | — | M |
⚠ Three columns nobody gets, at any plan or persona
📘 provider_fee_minor and provider_fee_tax_minor — the gap between what the payment provider charges us and what we charge the merchant is the platform margin. A test pins this. The merchant sees their own contract: amount, commission, commission rate, net to merchant. A buyer sees less again.
7 · What each revenue line sells, and to whom
| Line | Persona who buys it | ⚠ Blocked by |
|---|---|---|
| 1 · Subscription | Dealer Principal signs; Org Admin administers | — |
| 2 · Additional cards | Org Admin | — |
| 3 · Additional logins and storage | Org Admin | — |
| 4 · Standees | GM or Marketing | ⚠ Card images do not resolve (QRS-852) |
| 5 · WhatsApp usage | Marketing | Per-workspace send cap must exist first |
| 6 · Google and managed services | Marketing, DP for group | API approval; review-gating design (QRS-853) |
8 · What is refused, so no persona ever gets a tab for it
text
NEVER BUILT — each refusal has a reason, so "no" stays cheap
│
├── DMS replacement — invoicing, allotment, warranty, parts OEM-mandated
├── OEM-facing view of dealer discount or margin ⚠ the CCI order
├── Insurance or finance commission licence-gated
├── Vahan market-intelligence dashboards 🌐 discontinued Aug 2026
├── Advertising or profiled placement no consumer base + DPDP profiling
├── Owning telephony integrate, never own
├── Accounting, GST filing, parts inventory Tally/Marg territory
├── Recruitment and training delivery a services business
└── A second card-product abstraction no second card product exists yet9 · Onboarding path for a new developer
| Question | Read |
|---|---|
| Who logs in and what may they see? | This page · personas and access |
| Why does the product exist in this shape? | product decisions |
| What does a scan actually record? | operating model |
| Which plan is a feature in? | commercial model |
| When is it buildable? | go to market |
| What exists today? | index — 🧮 measured, not asserted |
| Why is a persona view missing? | RBAC is 0% built (QRS-803) |
Related
- Personas and access — identity, RBAC scope, trust boundaries, login routing
- Product map — the eleven ecosystem and data-flow diagrams
- Commercial model — plans, caps, add-ons, the seven revenue lines
- Value proposition — why the rep's screens do not lead the sale