Appearance
Why QR Setu? The dealer's case, and the case against
Part of
car_sales— the dealership operating layer. This page is deliberately adversarial. The product case is argued against the dealer's real alternatives, not against a strawman.
The verdict, before the argument
🔎 The feature set as currently sequenced is not compelling enough, and the reason is structural rather than a missing feature.
The product's strongest claim today — "you will know which rep caused which enquiry" — is a management-side benefit that costs frontline effort and carries no revenue. It asks the lowest-paid, highest-churn people in the building to change what they hand a customer, so that their manager can measure them better. That is the hardest category of software to land anywhere, and it is being sold into a business with negative profit before tax.
The fix is not more features. It is a different order. Lead with the two capabilities that require zero behaviour change and produce value in week one, and let attribution accumulate underneath while the dealer is already paying. Argued in §6, and it revises the roadmap.
1 · Why a dealer would choose QR Setu
Ranked by how quickly the dealer feels it, not by how much we like it.
| # | Reason | Evidence it is real |
|---|---|---|
| 1 | Walk-ins are invisible today, and they are the majority of showroom traffic. Reception writes them in a notebook nobody reads again | 🌐 The notebook is documented practice. Nothing in the OEM system records a visitor who did not become an enquiry |
| 2 | Nobody can prove who followed up and who did not. Follow-up is handled by memory and headcount | 🌐 One listed group runs 262 customer-service staff across 6 call centres against 11 application-IT employees. The alternative to software here is people |
| 3 | Per-rep performance is anecdotal. Reviews run on assertion, not record | 🌐 Frontline attrition 29.53%, so the institutional memory of who was good leaves with them |
| 4 | Cross-brand comparison takes a person and a spreadsheet at month end | 🔎 Each brand's mandated system reports upward to its own manufacturer. They structurally cannot be joined |
| 5 | Service and renewal revenue leaks quietly | 🌐 20 vehicles serviced per 1 sold, at 41.2% after-sales gross margin. The listed dealers name service retention as their own strategy |
| 6 | The OEM system was never built for them. Their own association says so | 🌐 FADA/NRI, Jan 2025: "Priority given to manufacturer reporting requirements over dealership operational efficiency" |
2 · Why a dealer would NOT choose QR Setu
🔎 This is the more useful list, and none of these is answered by adding a feature.
| # | Objection | How real | Our honest answer today |
|---|---|---|---|
| O1 | "This needs my reps to change what they hand a customer." Attribution only works if the rep shares a card instead of a phone number | Severe. The lowest-paid, highest-churn staff must change habit, permanently, and 25% of them are replaced each year | None yet. This is the central adoption risk and §6 restructures around it rather than answering it |
| O2 | "Why am I entering things twice?" The OEM DMS is mandated; QR Setu sits beside it | Severe | Partly honest: the data QR Setu captures (walk-ins, card interactions, follow-up) is data the DMS never held, so it is not double entry. But a booking is entered twice, and we should say so rather than deny it |
| O3 | "Who else uses this?" | Severe | Nobody. Zero reference customers, zero case studies, zero measured numbers from any Indian dealer |
| O4 | "You are two people." Continuity, support SLA, what happens if you stop | Real and legitimate | No answer that a dealer should find convincing. Mitigations in §5 |
| O5 | "WhatsApp is free and already has my customers." | Real | True, and we should ride it rather than argue with it. What WhatsApp cannot do is attribute, roll up, or enforce an SLA |
| O6 | "My margins are gone." | Real | 🌐 PBT of minus ₹13.30 Cr at a ₹6,381 Cr group. Price against the ₹14 lakh per outlet advertising line, never against profit |
| O7 | "What happens to my data if I leave?" | Real, and it is the fear behind every moat we design | Needs an explicit export promise. A moat the customer experiences as a trap does not get bought in the first place |
| O8 | "My OEM might not like it." | Moderate | 🌐 The CCI record shows manufacturers policing dealer conduct with fines and supply threats. Our answer is that dealer data never goes to an OEM — which is also the strongest trust position available |
| O9 | "₹1.5 lakh a outlet, and you want three years?" | Real, and we CREATED it on 2026-08-23 | 🔎 The repricing was correct on unit economics and it made this objection worse. Answer with the dealer's own arithmetic — 18 additional retained service jobs a year (break-even) — and with the comparison that survives scrutiny: 🌐 10.7% of the ₹14 lakh per outlet they already spend on advertising. Never with a discount (§8) |
3 · What they will keep using regardless
🔎 Assume every one of these stays. A product that assumes displacement will be wrong.
| Tool | Why it survives |
|---|---|
| The OEM's mandated DMS | Contractual. Not a competitive choice, and not ours to win |
| Free, universal, and already holds the customer relationship. 🌐 48% of new buyers contact dealerships there | |
| Excel | For anything month-end, financial, or shaped differently this month than last |
| Their existing back-office DMS | 🌐 INFOMAN, Orbitsys, AutoBooom and peers run invoicing, parts and stock. We do not touch it |
| The physical visitor register | Until reception is given something genuinely faster than a pen, not merely better |
| Phone calls | The follow-up itself stays a call. We record and enforce it; we do not replace it |
4 · What we do genuinely better
🔎 Three claims, and only three. Each is a thing no incumbent can produce, not merely one they do badly.
| Claim | Why nobody else has it |
|---|---|
| Attribution from a named employee to a named customer outcome | The OEM DMS records transactions and has no concept of which rep caused this. A CRM starts at "a lead exists" and cannot see the interaction that created one. A visiting card is unmeasurable by construction |
| The population that opened and left | Every other system starts at the enquiry. A customer who viewed a vehicle on a rep's card and did nothing is invisible everywhere else, and it is the cheapest re-engagement list in the building |
| Cross-brand, cross-outlet operational rollup | Structurally impossible for a single-brand system. And 🌐 the strongest local incumbent cannot sell it — its customer is the manufacturer, and a cross-brand view is the one thing a manufacturer does not want dealers to have |
What is NOT differentiated, and should never be pitched as though it were
Lead lists, task reminders, dashboards, mobile apps, WhatsApp templates, review requests. All of it exists, cheaply, from several vendors. 🌐 Per-seat CRM overlays start at ₹800/user/month. Leading a demo with any of it invites a feature comparison we lose on price.
5 · What would make a dealer actually bet on this
🔎 Ordered by how much each one moves a signature.
- One measured number from one comparable Pune dealer. "Reception logged 340 walk-ins last month; 96 had no follow-up recorded." That single sentence does more than every feature on the roadmap. It is also the cheapest thing on this list and does not exist yet.
- The group view, demoed live. The one screen their DMS provably cannot produce. This is the moment the conversation stops being about software and starts being about their business.
- A first deal below the committee threshold — which is now a SEQUENCING requirement, not a price one. 🔎 A single outlet at ₹1,49,999/yr is still a Dealer Principal's discretionary signature. A three-outlet group at ₹6,90,000 is not — that is a procurement conversation with a finance review attached, and at two people we cannot absorb a six-month cycle. ⚠ So land one outlet, then expand. Group Intelligence becomes an upsell to a paying customer who has already seen it work, rather than a line item in a first close. That is a real cost of the repricing and the mitigation is structural, not a discount.
- Done-for-you setup. Issue every employee card, populate the catalogue, load the templates. 🌐 The dealer's own alternative is ~50 hours of somebody's time, and charging for this is honest revenue (commercial model).
- A written data-export promise. Answers O7 directly. Counter-intuitively it makes the moat easier to sell, because the dealer stops reading accumulation as capture.
- Two named humans and a stated response time. O4 cannot be argued away, only made concrete.
6 · The sequencing change this analysis forces
The adoption asymmetry, stated plainly
The person who benefits is not the person who must change. The GM and Dealer Principal get the visibility; the rep and the receptionist do the work. Software with that shape fails on adoption, not on features — and every roadmap in this section until now led with the capability that has the worst ratio of benefit-to-behaviour-change.
🔎 So rank the first release by behaviour change required, not by product elegance:
| Capability | Behaviour change asked of frontline | Value visible in | Verdict |
|---|---|---|---|
| Visitor register | None. Reception must log visitors anyway. We only have to be faster than a pen | Week 1 | Lead with this |
| Service and renewal reminders | None. Runs on data the dealer already has, sent by the system | Week 2-4, as revenue | Second |
| Overdue follow-up list | None for the rep; the TL simply sees it | Week 1, management-side | Third |
| Employee cards + attribution | High. Every rep, permanently | Month 2-3 | Ship it, do not lead with it |
| Group Intelligence | None, but needs the whole stack beneath it | Month 6+ | The moat. Sell it, build it last |
This partly vindicates the roadmap the reframe replaced, and that is worth saying out loud
The pre-reframe plan led with service annuity on the argument that the recurrence engine already existed and after-sales carries the fattest margin. The reframe replaced it with attribution, on the argument that attribution is the product. Both were right about different things, and the conflict was never real: they share a dependency (parties), and the honest resolution is that attribution is the product thesis while zero-behaviour-change capabilities are the adoption path.
Build the spine, lead the sale with the surface. The single roadmap in go to market now reflects this; the two competing versions have been removed.
7 · Adoption barriers to fix now, not later
| Barrier | Fix | When |
|---|---|---|
| No reference number from any dealer | The Pune census plus a paid pilot. Zero engineering | Now — E1-E3 |
| Rep behaviour change | Make the card the easiest thing to send: one tap from the phone they already hold, pre-filled. If it is slower than typing a number, it loses | Design, before Wave 1 ships |
| Reception must be faster than a pen | Two fields and a dropdown, offline-tolerant, on a shared tablet. Not a full CRM form | Wave 1 |
| Double-entry objection (O2) | Say the true thing: we capture what the DMS never held. Do not claim to replace it | Sales script |
| Lock-in fear (O7) | A written export commitment | Before the first contract |
| Two-person continuity (O4) | Named contacts, stated response time, and an escrow or export clause if a dealer asks | Before the first contract |
| Card view tracking is broken | 📘 QRS-734. Until it is fixed, "every scan is measurable" is false | 1-2 days, first |
8 · The one-line positioning, and what it must never become
TIP
Not another CRM or DMS. A digital operational layer connecting dealership employees, Setu Cards, customer interactions, leads, follow-ups, test drives, communication, team performance and management visibility — across every outlet and every brand the group carries — sitting alongside the OEM systems the dealer is obliged to use.
⚠ What it must never become in a pitch: "a cheaper CRM", "a lead generator", or "a replacement for your DMS". The first loses on features, the second sets a measurement the product cannot meet, and the third is a promise about systems the dealer cannot switch off.
Related
- Product decisions — what to build and what to refuse
- Personas and access — who uses it and what they may see
- Go to market — the single roadmap this page revises
- Operational gaps — the evidence behind §1