Sep 29, 2020 · 20m · top-founders
OnFleet Flirting With $10m ARR Processing 3m Deliveries Per Month for 900 Customers
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, host Nathan Latka speaks with Onfleet CEO and co-founder Khaled Naim about scaling the last-mile delivery SaaS platform to $800,000 in monthly recurring revenue and three million monthly deliveries. Naim details Onfleet's Stanford origins, enterprise customer adoption, capital-efficient growth, and upcoming fundraising plans.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Nathan holds 35.9% of the talking time here. How this is scored →
speaking balance: gold is Nathan, purple is the guest (3 minute bins)
Khaled directly clarifies that the host's recorded 72% gross churn figure was incorrect, affirming their actual gross retention sits around 85%.
Hardest push from Nathan ▶ 8:20 Pressing for exact software cut on a sample orderNathan cuts through general labor expense explanations to demand the exact software fee extracted from a theoretical $100 restaurant order.
Biggest teaching moment ▶ 8:24 Explaining the SaaS per-task model over sales take-ratesKhaled explains why Onfleet does not take a percentage commission of retail basket size, distinguishing software infrastructure pricing from marketplace aggregator models.
Nathan holds their own ▶ 10:16 Instant mental math on task volume and daily unit velocityNathan instantly calculates that $900 per month at 20 cents per task translates to roughly 4,500 monthly tasks and 150 daily deliveries per client.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Nathan as informed peer | Guest teaching | Guest disagreement | Nathan pushing back | Why |
|---|---|---|---|---|---|---|
| Onfleet's Mission and Delivery Software Operations | 5 | 3 | 1 | 1 | Nathan frames the macro environment around COVID-driven delivery demand and inquires about driver employment structures. Khaled cooperatively explains how retailers use Onfleet to manage both in-house and third-party fleets. | |
| The Origins of Onfleet at Stanford | 6 | 5 | 1 | 2 | Nathan tracks historical customer growth metrics and challenges the use case of large enterprise clients like Gap and Sweetgreen versus delivery aggregators. Khaled explains the margin and omnichannel advantages of running dedicated internal fleets. | |
| Transparent SaaS Pricing vs Aggregator Take Rates | 7 | 6 | 1 | 3 | Nathan asks for a specific order P&L breakdown to understand Onfleet's take-rate. Khaled clarifies that Onfleet operates as pure SaaS charged per task rather than taking a percentage commission on merchandise value. | |
| Scaling to Three Million Deliveries and Breakeven Operations | 7 | 3 | 1 | 2 | Nathan conducts quick mental math on unit economics, breaking down average customer spend into daily delivery volume, and probes into breakeven status and acquisition interest. Khaled confirms the math and discusses pacing growth efficiently. | |
| Mid-Roll HostGator Website Builder Advertisement | 5 | 2 | 1 | 1 | Following a sponsor ad read, Nathan investigates Onfleet's balance sheet, debt financing with Lighter Capital, and target round sizing. Khaled shares their plan to raise a targeted $10M to $15M while remaining capital efficient. | |
| Team Composition and Sales Team Scaling | 7 | 5 | 2 | 3 | Nathan drills down into sales team ratios and SaaS churn dynamics, pointing out a discrepancy in previously recorded gross churn figures. Khaled clarifies that annual gross retention is 85% with net retention exceeding 115%. | |
| Founder Transparency and the Famous Five | 3 | 1 | 1 | 1 | Nathan asks why Khaled is willing to be transparent on public metrics before running through the standard rapid-fire Famous Five questionnaire. | |
| Episode Conclusion and Onfleet Financial Summary | 0 | 0 | 0 | 0 | Nathan delivers a rapid solo recap of Onfleet's core metrics and valuation positioning at the close of the episode. |