Part of an aggressive fast-response sales campaign, the team needed tooling that didn't exist field reps were losing leads from blind spots in availability and follow-up. The tool I built became the campaign's enabler.
Context
Stone was running an aggressive fast-response sales campaign. Field reps had to respond to leads quickly, across multiple channels, with limited tooling the campaign needed an enabler that didn't exist yet.
Problem
Reps were losing leads from blind spots in availability and follow-up who needed callback, when, on which channel. Everything lived in each person's head; nothing was shared, nothing was timed.
Design
Competitive reassignment as the core mechanic: every lead carries a SLA timer; if a rep doesn't respond, the next eligible rep picks it up. Visibility everywhere who's working what, since when, on which channel. Squad of 5 devs + PO + Scrum Master.
Engineering
100% TDD + Clean Architecture from day one. Backend sustaining 10k+ req/s at peak with zero downtime through high-traffic periods. Pattern that the team kept long after I left.
Impact
+20% in sales attributed directly to the tool, 250k+ interactions per month orchestrated through the system. Became Stone's primary engagement and retention tooling and the team's internal quality benchmark.
- Why competitive reassignment instead of round-robin?SLA timer + competitive pickupRound-robin is fair on paper but brutal on revenue: a slow rep blocks the lead. Competitive reassignment makes responsiveness the currency fairness becomes self-policing without a manager intervening.
- Why 100% TDD on a brand-new system?Test-first from day oneRevenue-critical system + small squad + fast iteration = a single regression is expensive. Tests give us the confidence to refactor aggressively without a QA bottleneck.
- Why Clean Architecture for a 1-year project?Use-case + boundary separationRecently-formed squad: layered separation flattens onboarding. Use-case classes read like requirements documents new devs ship features in the first week instead of the third.
+20% measured revenue. Became the #1 engagement tool and an internal quality benchmark that the team kept after I left.