Axle Logistics
All customers
Axle Logistics logo

Case study · Logistics

How Axle Logistics scaled retainers across new markets with Subby

Axle Logistics sells recurring capacity retainers to shippers. Subby became the billing backbone for expansion into new cities.

5

New markets entered

3.5x

Retainer revenue growth

99%

Billing uptime

Location

Ibadan, Nigeria

Industry

Third-party logistics

Scale

Multi-city shipper retainers

The recurring payment problem

Different businesses. Same recurring payment problem.

Before Subby, Axle Logistics ran into the same problems as every business that collects payments on a schedule:

  • Payments fail
  • Collections live across spreadsheets, bank alerts, phone calls, and payment links
  • Finance can’t tell what was collected, what failed, what is outstanding, and what has actually settled

Their workflow

Capacity retainers and lane packages across cities

The infrastructure is shared. The workflow is not.

Problem

Expansion stalled on billing complexity

Every new city meant new contracts, new invoice habits, and new collections spread across spreadsheets, bank alerts, and payment links.

Failed payments went unnoticed until month end, and finance could not say what had been collected, what was outstanding, and what had settled in each market.

Finance feared growth because each market added another messy process.

Solution

Retainers standardized on Subby

Capacity retainers and recurring lane packages were set up as Subby plans with clear tenure and pricing.

Collections, reminders, retries, and settlements work the same whether the client is in Ibadan, Lagos, or a new market. Axle’s booking tools connect to Subby through the API, tested first in the sandbox.

Settlements and payouts give leadership a multi-market view of recurring revenue without waiting on month-end spreadsheets.

Subby features used

  • Recurring payment plans
  • Business-type workflows
  • SMS, email, in-app, Telegram & WhatsApp reminders
  • Failed payment retries
  • Settlements & payouts
  • API & sandbox

How it works

From signup to settlement on Subby

  1. 1

    Shipper buys a retainer plan

    Recurring capacity is billed on a schedule both sides can see.

  2. 2

    Same playbook in every city

    New markets inherit the same Subby workflow instead of inventing local invoice chaos.

  3. 3

    Failed payments are recovered

    Retries and reminders protect retainer revenue automatically.

  4. 4

    Built into Axle’s own tools

    Axle integrates with Subby’s API and sandbox, so billing runs alongside bookings.

Results

Expansion without billing chaos

Axle entered five new markets with stable collections from day one. Retainer revenue grew 3.5×.

Finance stopped being the bottleneck on go-to-market decisions.

Axle spends less time chasing payments and more time moving freight for the shippers who pay for it.

5

New markets entered

3.5x

Retainer revenue growth

99%

Billing uptime

“We don’t open a market until billing is ready. Subby made “ready” the default.”

Yemi Balogun

Yemi Balogun

CEO, Axle Logistics