Number of Seats/Users: Sherpa offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Sherpa that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Sherpa. Sherpa reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Sherpa offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Sherpa. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Sherpa often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Sherpa tends to be chosen for its price and operating hours, but many Spendbase clients end up concerned about reliability, support, and overall delivery control.

Key positives our clients highlight:
– Competitive per-delivery pricing, especially for:
– High-volume days (e.g., campaigns, holidays)
– Businesses wanting no monthly subscription or lock-in
– Wide operating window (7am–9pm) in most major Australian cities
– Attractive as a backup or overflow option when in-house fleets are at capacity

However, there are recurring themes on the downside:

1) Operational reliability and timeliness
Many clients rely on Sherpa for time-sensitive drops, but our data shows:
– Drivers starting shifts late, in some cases by hours
– Missed or delayed business deliveries that directly impact customer satisfaction
– Constraints such as:
– Needing to upload bulk jobs 24 hours before the run
– Inability to add new jobs once the run starts
This undermines Sherpa’s positioning as an “on‑demand” solution.

2) Customer support and dispute handling
Spendbase clients often mention:
– Rigid cut-off rules for disputes and issue escalation
– Limited willingness to take responsibility when service failures occur
– Frustration over fees (e.g., returns) applied without clear pre-approval

3) Platform and tracking experience
From a product and CX standpoint, internal feedback shows:
– A clunky, unintuitive interface for assigning and monitoring jobs
– Lack of clear visibility into which driver is handling which delivery
– No easy public tracking links to share with end customers
– No dedicated section for delivery notes or special instructions

How we position Sherpa in Spendbase savings strategies:
– Sherpa can make sense as a low-cost option for:
– Non-critical, flexible deliveries
– Bulk drops where timing windows are wide
– For high-value or time-sensitive orders, we usually advise:
– Pairing Sherpa with more premium couriers
– Negotiating clear SLAs and dispute policies
– Closely monitoring hidden costs such as return fees and failed-delivery charges

In short, Sherpa is a cost-efficient tool in the stack, but only when used with clear boundaries and backed up by more reliable partners for mission-critical deliveries.