A working lead-management prototype, built for a luxury-automotive dealer group's pitch in Puerto Rico. A lead comes in, gets routed to the right branch by municipio, and the dealer's phone lights up in seconds — with a clock running that the branch can't quietly ignore.
One endpoint. Web form, social, chat — every lead lands in the same place.
Auto-assigned to the right dealer by the buyer's municipio.
The branch is pinged in seconds — not swept up hours later.
A countdown to first response. Breach it and it escalates.
The brand sees the funnel and who's answering fastest.
↑ no product screenshots here — this is the actual flow, drawn the way it was pitched
A luxury-automotive dealer group in Puerto Rico — several franchise rooftops across the island — was spending real money to generate leads, then losing them in the handoff. Enquiries arrived from the website and social, dropped into a shared inbox, and waited. We can't name them: the engagement never closed. So this is a lab piece, told honestly as one.
Speed-to-lead is a brutal arithmetic. Roughly 78% of buyers purchase from whoever answers first; respond inside five minutes and a lead is about 21× more likely to qualify; yet the average dealer takes around 47 hours. On an island, "answer first" also means answering from the right rooftop — routing by municipio isn't a nicety, it's the whole game.
We didn't pitch a deck. We built the thing — a working prototype in weeks, on the same production pattern as psi-inbox, the operations software we'd already shipped. Lead capture, municipio routing, second-count notifications, an SLA clock with escalation, and a brand dashboard with a per-dealer response leaderboard. Then we put it in front of the room.
Every source — web form, social lead ad, chat — normalized into a single tracked record the moment it arrives. No lead enters through a side door and disappears.
Puerto Rico's 78 municipios mapped to the dealer network, so a lead in Caguas reaches the Caguas rooftop, automatically. Geography does the triage.
The assigned branch is alerted the instant a lead lands — the five-minute window is the target, not an aspiration.
Every lead starts a clock. If first response doesn't happen in time, it escalates up the chain — a manager sees the breach before the customer feels it.
The group sees the whole funnel — leads in, first-response times, conversion — plus a per-dealer leaderboard that turns "answer faster" into a number nobody can argue with.
Not a throwaway mock: the same React, serverless and managed-Postgres pattern behind the PSI inbox platform we run in production today.
Any source, one record, timestamped on arrival.
Assigned to a rooftop by municipio, instantly.
The branch is pinged before the lead cools.
SLA clock runs; breaches climb the chain.
Every response time rolls up to the brand.
| Rooftop | Leads (30d) | Median first response | Within SLA |
|---|---|---|---|
| Rooftop A · Metro | 142 | 2m 40s | 96% |
| Rooftop B · Norte | 118 | 4m 12s | 89% |
| Rooftop C · Sur | 97 | 11m 05s | 71% |
| Rooftop D · Oeste | 86 | 38m 20s | 44% |
Rooftop names, counts and times above are illustrative placeholders drawn to show the shape of the report — not data from any real dealer group.
A Mutiny Labs lab prototype. Concept & write-up © 2026 Mutiny Labs · mutiny-labs.com.
Built speculatively for a pitch that did not proceed; the dealer group is deliberately unnamed. This is an independent lab exploration by Mutiny Labs — not affiliated with, authorized, or endorsed by any automotive manufacturer, dealer group, or their brands. Figures shown are widely cited industry benchmarks or illustrative concept data, never client results. All trademarks and names remain the property of their respective owners.
under the hood: Built on the same production pattern as psi-inbox — React front end, serverless API layer, managed Postgres, role-based access, and an event pipeline driving notifications and SLA escalation.
We reply personally. A senior partner, not a sales pod. We'll tell you straight whether we can help.
