Verticals — start here

One industry at a time. A vertical enters a release only through the G-D discovery gate: a scope item carrying vertical: "<slug>" needs verticals/<slug>/discovery.md to exist at scoped and to be approved at scope_frozen (check:release, QRS-475).

Read before changing or designing a vertical

1. This page · 2. verticals/_template/discovery.md · 3. the vertical's own discovery page — and its first line: real_estate/discovery.md says of itself "THIS IS NOT A COMPLETED DISCOVERY" · 4. Festival stall — the R1 launch vertical and the first brief completed under the process · 5. Platform model: a new vertical is configuration, never code. Your plan must answer: which archetype, which primitive composition, and which grants are sparse deviations.

Pages

• Vertical discovery brief — template
• The admin control plane: what exists, what does not, and the three decisions before screens
• AI strategy: what to build, what is not AI at all, and what it costs
• Architecture and backend validation: every capability against the real schema
• Annual pricing, packaging, cost to serve, and the ₹2 crore question
• Employees are replaceable, dealership data is not
• Data isolation and deployment models: what we can honestly offer
• Digital layer, not dealership OS: the brownfield entry question
• car_sales — vertical discovery brief
• Go to market, positioning, roadmap and risks
• car_sales — the dealership operating layer
• Market landscape, competitors and pricing
• Operating model: how the card becomes the operational spine
• Dealer economics, operational pain, and the gap the OEM leaves
• Persona feature map: who logs in, what they see, where the data goes
• Personas, authentication, RBAC and operational capability
• Podium teardown: what it sells, why dealers pay, and what QR Setu should take
• Product decisions: build, must-have, never build, own, moat
• Visual product map
• Product scope: baseline, differentiators, modules, and what to refuse
• Screen blueprint: the validated design input, persona by persona
• Why QR Setu? The dealer's case, and the case against
• Vertical discovery brief — Direct seller / independent distributor
• Direct seller — the engagement layer
• Festival Stall — discovery brief
• Festival Stall — journey map & implementation readiness
• Intercity Bus — architecture fit
• Real Estate — discovery brief