Case Study
Sales Operations Build
Rizq Rise · High-ticket sales organization · 4 closers, 5 setters
The Situation
The team was booking calls and closing deals. What they didn't have: any operational infrastructure underneath it.
Every booking field entered manually. Every call recording forwarded by hand. No leaderboards. No dashboards. Performance data lived in individual sheets no one was required to update on a schedule.
The setter manager had no way to see his team's numbers without messaging each person directly — which meant requesting information they should have been reporting automatically, every time he needed it.
This wasn't just friction. It was a slow erosion of operational authority.
What I Built
Six systems, built to interlock — each one removing a manual step or creating visibility that didn't exist.
Booking Capture
When a setter books a call, five fields now auto-populate in the tracking sheet: name, email, appointment date, booking date, and lead source. The setter claims their name from a dropdown — they aren't identified in the booking system directly — and the rest writes itself. A Slack notification fires on every booking, and the setter's live counter increments for the day, feeding daily competition.
Before: all five fields filled manually, 2–3 minutes each. Roughly 20 bookings a week across 5 setters.
Call Recording Router
The team generates roughly 15 recordings a week — team meetings, coaching calls, closer sales calls. Each one now routes automatically to the correct Slack channel based on meeting type. Before, someone had to manually forward each one after it came in.
Closer Leaderboards — Weekly & Monthly
An automated leaderboard pulls closer performance from the tracking sheet and posts to Slack — weekly on schedule, monthly on schedule.
Before, closers had no shared scoreboard. Now every Monday and the first of every month, the ranking is public to the whole team. That changes the culture of the floor — accountability without a manager having to manufacture it. This did not exist before I built it.
EOD & EOW Setter Reports
An end-of-day summary posts automatically to the setter reporting channel. An end-of-week leaderboard posts to the wins channel, sorted by priority: clients closed → bookings → dials. The system identifies each setter's individual sheet by naming pattern — call setter vs. DM setter — and computes their metrics without manual input.
These reports did not exist before.
Setter Performance Dashboard
Ten charts total — six for call setters (closed, booked, and dials across the current week and month), four for DM setters (no dials metric). Week-over-week and month-over-month comparison lines built in.
One consolidated weekly performance table holds all five setters in a single tab with color coding: green if on target, red if significantly under, yellow in between.
Before this, the setter manager was messaging each setter individually to ask for their numbers. Now he opens one tab.
Weekly Performance
| Setter | Dials | Pick ups | Convos | Bookings | Showed | Closes | Pick-uprate | Convo→booking | Showrate | Set-to-close | Show-to-close |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Ahmed | 510 | 62 | 31 | 17 | 11 | 2 | 12% | 55% | 65% | 12% | 18% |
| Neha | 480 | 28 | 9 | 4 | 6 | 0 | 6% | 44% | 150% | 0% | 0% |
| Adeeb | 560 | 55 | 24 | 9 | 4 | 0 | 10% | 38% | 44% | 0% | 0% |
| Team Total | 1,550 | 145 | 64 | 30 | 21 | 2 | 9% | 47% | 70% | 7% | 10% |
New Client Closed Capture
Same logic as booking capture, applied to closes. Triggered from the closer side. Closers fill in a few fields manually at their convenience, guided by an end-of-day SOP.
Infrastructure
Beyond the six systems: standardized and hardened the team's tracking spreadsheet. A silently miscategorized date field was corrupting monthly calculations — the numbers looked right until they didn't. Fixed it, and documented the template with clear instructions for year-on-year changes (month lengths, leap years) through 2027 and beyond. One canonical version the team can hand off without tribal knowledge.
Impact
A high-ticket sales organization now has the operational infrastructure it should have had from the start — and the manager running the setter floor no longer has to ask his own team what's happening.
The leaderboards, dashboards, and reports didn't exist before. That's not time saved — it's capability created. The closer floor now has a public scoreboard. The setter manager has a single screen. The team has a record of every booking, every close, every call, logged automatically.
Conservative estimates on time returned:
- ~3.5 hours/month from booking entry alone
- ~1.5 hours/month from call recording routing
What's Next
A deduplication layer for call recording routing is designed but not yet implemented. When multiple team members attend the same call, the summary will route once instead of once per attendee. Scoped and ready to build.