Sales Operations Platform for a Field and Phone Sales Brokerage
The full operational backend for a field and phone sales brokerage: GPS-qualified activity, a 38-rule payout engine, deal intake, and rep and admin portals.
- 98
- live api endpoints
- 38
- payout rules encoded
- 4
- background job queues
A high-volume field and phone sales brokerage runs its entire day on a platform we built: activity tracking for reps in the field, deal intake with duplicate checking, dialer and CRM integration, a commission engine, and portals for reps and admins alike.
The problem
The brokerage's operation had outgrown the patchwork of generic tools it started with. Activity reporting, deal flow, and pay calculations lived in different systems with different answers, and the operational logic that held it together lived in people's heads.
What we built
One coherent backend, 98 live API endpoints across 15 route modules, serving every part of the operation:
- GPS-qualified field activity. Rep check-ins are verified against a 250-yard geofence, with five qualification outcomes and explicit reason codes, so activity numbers reflect presence, not paperwork.
- A payout engine with the rules written down. 38 payout rules covering rates from 45 to 120 percent across four payout structures, with statement reconciliation resolving every line into one of eight explicit states.
- Deal intake that defends itself. Real-time duplicate checking runs read-only with a hard timeout, so bad entries are caught at the door without ever blocking the pipeline.
- Integrations without lock-in. A commercial CRM, a predictive dialer, spreadsheet exports, address verification, mapping, and a finance read-API, all behind clean internal interfaces.
- Four background job queues with separate worker processes handle syncing and heavy work off the request path.
How it works
The database is the enforcer: 48 purpose-built indexes, triggers and functions that make invariants impossible to violate, timezone-aware timestamps, and fixed-precision money everywhere pay is involved. Authentication uses short-lived tokens with rotating refresh, and every external integration is throttled to be a polite citizen of the client's other systems.
What it proves
This is what "production-grade" means in practice: not a demo that works when everyone behaves, but the system a business actually runs on, all day, with money on the line.