Discovery Brief — Dynamic Driver Commissions
Discovery Brief — Dynamic Driver Commissions
Status: NEW IDEA
Last Updated: October 15, 2025
Product Manager: @Christy Cocchia-Barbaree
Product Area: FBI – Driver Pay
Part I: The Opportunity Proposal
Problem Statement
Core Problem:
Dropoff’s operations team relies on manual intervention to adjust driver commissions in response to fluctuating supply and demand. This results in inconsistent margins, reactive dispatching, and excessive dispatcher effort during high-demand periods — particularly in healthcare and STAT delivery windows where timing and coverage are critical.
For the Customer:
-
Dispatchers currently manage driver pay adjustments manually, often escalating to get orders covered.
-
Adjustments are only made upward — there is no mechanism to optimize or throttle down when supply is abundant.
-
Real-time decisions rely on gut feel and Slack broadcasts, which drivers often mute, leading to slower response times.
-
Driver engagement during late-day surges, traffic peaks, or bad weather remains unpredictable, requiring manual bonuses or guarantees.
For the Business:
-
Margins erode when commissions rise reactively.
-
Dispatchers lose productivity managing pay instead of service-level compliance.
-
There is no visibility into which commission increases were necessary, effective, or excessive.
-
Dropoff leadership (Sean, Terri, Jeff) wants data-driven insight into when and why commission adjustments occur, and how to automate them intelligently.
Vision
To empower dispatchers and operations teams with real-time, data-driven commission recommendations that balance supply, demand, and service-level needs — reducing manual effort while improving on-time delivery and margin consistency.
Proposed Solution
We believe we can solve this problem by developing a Dynamic Driver Commissions Engine that evolves in three phases:
Phase 1 — Historical Assessment (Post-Event Analysis)
-
Analyze historical order, commission, and driver activity data to identify when bonuses or guarantees were used.
-
Surface patterns by market, time of day, client, and service level (STAT, ASAP, etc.).
-
Quantify missed opportunities and overpayments to establish a baseline model.
Phase 2 — Real-Time Monitoring & Recommendation
-
Introduce live monitoring that calculates a Supply-Demand Ratio (SDR) in real time.
-
Alert dispatchers when the ratio indicates a shortage or oversupply.
-
Provide a simple UI control (e.g., “+10%,” “+25%”) to throttle commissions across the market, replacing manual adjustments.
-
Integrate with Slack or SMS to automatically notify drivers of active commission boosts.
Phase 3 — Automation & Optimization
-
Automate commission changes via API based on validated thresholds.
-
Optionally use predictive analytics to forecast future driver shortages using signals such as order intake velocity, dwell times, and historical patterns.
-
Track impact via dashboards on acceptance rates, coverage time, and on-time performance.
Out of Scope for v1:
-
Real-time AI prediction and automatic pay reductions.
-
Individual driver pay adjustments or contract-specific pay models.
-
Deep integration into third-party broadcast/messaging systems beyond initial Slack/SMS proof-of-concept.
Initial Goals & Success Metrics
|
Goal |
Success Metric (KPI) |
|---|---|
|
Identify and codify top 5 recurring commission adjustment scenarios |
Patterns defined across 3 pilot markets (DFW, Houston, ARC) |
|
Reduce dispatcher manual adjustments |
-30% fewer manual pay edits after 90 days |
|
Increase on-time performance during shortage periods |
+10% on-time delivery in undersupplied time blocks |
|
Improve gross margin stability |
±5% variance between payout and target margin |
|
Validate SDR and time-of-day weighting logic |
80% correlation between recommended and manually successful adjustments |
Part II: Discovery & Validation
Deep Dive: Users & Context
Primary Persona:
-
Dispatcher / Operations Manager (Jeff’s Team)
-
Handles 30–60-minute SLA orders and STAT coverage.
-
Relies on Slack broadcasts and experience to determine pay bumps.
-
Operates under time pressure with little automation or predictive support.
-
Secondary Persona:
-
Independent Contractor (Driver)
-
Accepts or declines based on posted pay per job.
-
Engages more readily with clear, round-number bonuses (“$10 more”) vs. percentage multipliers.
-
Often operates multiple apps or delivery networks simultaneously.
-
Environment & Context:
-
Each market (e.g., DFW, Houston, LA) has different client mixes, payout structures, and supply conditions.
-
Most orders are paid as a percentage of revenue (typically 50–60%), with some fixed-rate clients.
-
Driver supply fluctuates sharply during traffic peaks, adverse weather, or end-of-day healthcare spikes.
-
Dispatchers currently use macros and SQL tools to analyze commissions but lack a unified view of adjustments or effectiveness.
Deep Dive: Problem Validation
Evidence from the Customer:
-
Jeff’s team “only adjusts up” and has no mechanism to dial down pay when supply is high.
-
Peak-hour coverage requires heavy manual “bonuses” that vary by market.
-
Data exists (via SQL and Tableau) but isn’t leveraged for real-time insights.
-
Slack broadcasts are muted by many drivers due to late-night noise, reducing engagement.
-
Drivers respond more positively to flat bonuses than percentage multipliers.
Internal Alignment:
-
Terri: Start with retrospective analysis and simple recommendations, then move toward automation.
-
Paul: Envisions a real-time SDR dashboard and dispatcher “throttle” button.
-
Jeff: Supports a pilot starting with historical analysis, followed by controlled testing.
-
Christy: Will coordinate with ongoing “Driver Availability & Scheduling” discovery to align datasets and avoid terminology conflicts (e.g., avoiding “schedule” for ICs).
Deep Dive: Hypotheses & Risks
Opportunity Hypothesis:
We believe that by analyzing historical commission adjustments and surfacing data-driven recommendations, Dropoff can reduce overpayments, improve driver coverage during surges, and build a foundation for full dynamic automation, leading to higher margins and reduced dispatcher workload.
Key Assumptions to Validate:
-
Historical data can be parsed to identify all manually adjusted commissions.
-
Commission behavior patterns (bonuses/guarantees) are consistent by time of day and market.
-
Dispatchers will trust and adopt suggested adjustments over manual decisions.
-
Drivers will respond positively to automated, transparent bonus messages.
-
Predictive models can forecast high-risk coverage windows accurately enough to preempt shortages.
Key Risks & Mitigations:
|
Risk |
Mitigation |
|---|---|
|
Driver backlash if perceived as “commission cuts” |
Begin with only bonus/guarantee logic; introduce reduction logic later |
|
Market variability (client-based pay rules) |
Model per-client, per-market data; start with single-client (ARC) pilot |
|
Dispatcher override culture |
Build trust with transparent logic and outcome tracking |
|
Data completeness |
Collaborate with Dropoff’s SQL/BI team to ensure clean, timestamped audit trails |
Validation Plan & Next Steps
|
Learning Goal |
Activity |
Success Signal |
Owner |
|---|---|---|---|
|
Identify when and why commissions are adjusted |
Query Dropoff audit trail / macros |
≥80% accuracy in identifying adjusted orders |
Dropoff Ops + CXT Data |
|
Map high-frequency adjustment patterns |
Analyze DFW, Houston, ARC data |
Top 5 “bonus scenarios” defined per market |
CXT Product |
|
Validate dispatcher usability needs |
Workshop dashboard mockups with Jeff’s team |
≥4/5 dispatchers approve design flow |
PM + UX |
|
Define equation weights (time of day, service type, driver count) |
Regression test on historical data |
R² ≥ 0.8 correlation to manual success |
CXT Data Science |
|
Prototype SDR alert logic |
Simulate alerts on 1-week live data feed |
Match ≥70% of manual intervention events |
CXT Engineering |
Discovery Partners & Interested Customers
|
Customer |
Contact |
Status |
|---|---|---|
|
Dropoff |
Paul North, Jeff Hackman, Terri Luke |
Primary pilot partners |
|
Dropoff Data Contact |
Viola (SQL Analyst) |
Supporting data extraction |
|
Dropoff ARC Market |
American Red Cross (DO NOT CONTACT) |
This is Dropoff’s customer they will be modeling |
|
Internal |
@Christy Cocchia-Barbaree |
PM alignment on Driver Availability project |
-
Dropoff Spec Presentation (reviewed Oct. 15, 2025)
-
Dynamic Driver Commissions 06.26.25.pptx
-