top of page
Transportation & Logistics
TravelTech
CRM
Masabi
Modernized public-transit fare collection by replacing bespoke hardware-heavy ticketing systems with a cloud-based Fare Payments-as-a-Service platform, despite procurement complexity, legacy infrastructure and public-agency risk aversion.
1
MODEL
BUSINESS MODEL
SaaS
- Founding positioning: make fare collection a configurable cloud service rather than a bespoke hardware project.
- Product architecture: Justride combines mobile ticketing, account-based ticketing, open payments, inspection, reporting and APIs.
- Operating model: agencies subscribe to Fare Payments-as-a-Service rather than fund large custom builds.
- Infrastructure: cloud fare engine, mobile apps, validators/readers where needed, payment integrations and SDK distribution.
- Build sequence: prove mobile ticketing first, then expand into account-based fares, open payments and multimodal SDKs.
1. Identify a regulated or infrastructure-heavy industry where the customer’s existing system is bespoke and expensive.
2. Build the smallest deployment that delivers visible rider value without requiring full infrastructure replacement.
3. Make the system configurable rather than custom-built.
4. Price it as a recurring service tied to deployment scope and transaction activity.
5. Add adjacent payment and mobility functions only after the core fare workflow is trusted.
The common mis-build is selling a full infrastructure replacement before proving a low-risk, incremental deployment.
DISTRIBUTION MODEL
Masabi prioritized mobile ticketing before asking agencies to replace vehicles, gates or smart-card infrastructure. Its first deployments let riders buy and display tickets on phones while agencies avoided upfront hardware replacement; this created a lower-risk path into account-based ticketing and open payments.
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Enterprise Sales, Partnerships, Direct Sales, Product Integrations
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Direct enterprise sales targeted transit agencies, authorities and operators.
- Partnerships with Uber, Moovit and mobility apps embedded Justride ticketing into rider-facing applications.
- The Justride SDK enabled ride-hailing, journey-planning and Mobility-as-a-Service platforms to distribute transit tickets.
- Reference agencies such as MBTA, MTA, Denver RTD and LA Metrolink reduced perceived procurement risk.
What worked: use a low-risk mobile-first wedge to enter an agency, then expand into account-based and open-payment infrastructure.
Trap if copied blindly: partnership distribution fails when the partner controls the rider relationship and can replace the underlying provider; the cost is dependency without durable account control.
| PATTERNS OF THIS MODEL
PATTERNS IN PUBLIC-INFRASTRUCTURE FAAS:
1. Incremental deployment lowers procurement risk. Mobile-first ticketing lets agencies demonstrate value before replacing physical infrastructure.
2. Configurable platforms beat bespoke builds. A shared fare engine reduces cost, implementation time and upgrade risk.
3. Long public contracts create revenue durability. Masabi’s MTA relationship included an up to 12-year, $97 million extension in 2024.
THE WEAKNESS: Public-sector sales can be slow, political and concentrated; a few agency losses can materially affect growth.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — MULTIMODAL FARE ORCHESTRATION. Riders use buses, rail, bikes and micro-mobility separately; a platform that prices and settles across modes can become the mobility wallet.
GOLDMINE 2 — CONCESSIONS AND SUBSIDY AUTOMATION. Fare capping, discounts, social tariffs and employer programs are administratively complex; automated eligibility and fare rules can expand value beyond ticketing.
GOLDMINE 3 — AI RIDER SUPPORT AND FARE OPTIMIZATION. AI can resolve fare disputes, recommend passes and detect fraud or revenue leakage.
THE PIT — HARDWARE-DEPENDENT DEPLOYMENTS. Once a project requires validators, gates and field installation, it becomes a capital project rather than scalable SaaS.
THE SECOND PIT — PARTNER DISINTERMEDIATION. Distribution through Uber or journey-planning apps can create reach but may weaken the agency’s direct rider relationship.
MOVE WITH CAUTION — Do not promise open payments or account-based ticketing without robust settlement, dispute and privacy controls; payment errors in public transit create immediate rider and political risk.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Transit fare collection relied on ticket machines, smart cards, paper tickets, bespoke vendor projects and long hardware cycles. Masabi entered by digitizing fare payments through mobile and cloud technology, where adoption barriers were procurement rules, integration with legacy systems and public accountability rather than rider demand.
MARKET TYPE
Fragmented Market
ENTRY STRATEGY
Brownfield Entry
WHY THEY WON
Public transit is fragmented across cities, agencies and operators, each with different fare rules, legacy systems and procurement processes. The structural opening was that many agencies wanted modern fare payments without the cost and risk of a full hardware replacement. Masabi exploited this by offering a configurable SaaS platform that could begin with mobile ticketing and expand into account-based and open payments.
EXECUTION
Masabi modernized existing fare-collection systems rather than creating a new transport mode. Its initial bet was that agencies would adopt mobile ticketing if it improved rider experience and avoided major hardware spend. This required secure ticket validation, integration with agency rules and credible support for public-sector operations. The approach was viable because it delivered value without forcing a disruptive replacement project.
FOOTHOLD STRATEGY
Wedge Strategy
The wedge was mobile ticketing for transit agencies that wanted to modernize without replacing on-vehicle hardware. These agencies were reachable through procurement and industry networks, could justify spend through rider convenience and reduced ticketing cost, and had a path into account-based ticketing, open payments and multimodal SDKs.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: The commercial mechanism is to enter through a low-risk rider-facing feature, then expand into the agency’s full fare-payment infrastructure.
KEY LEARNING: In public infrastructure, the first deployment must reduce political and operational risk, not merely showcase technology.
HOW TO USE: If selling into government or infrastructure, design an incremental deployment that produces visible public value before requesting a full-system replacement.
KEY LEARNING
THE STANDARD: Fragmented public-sector markets reward vendors that standardize a costly workflow while accommodating local rules.
RULE 1 — SELL OUTCOME AND RISK REDUCTION. Agencies care about rider experience, cost, equity and procurement defensibility.
RULE 2 — MAKE THE FIRST DEPLOYMENT SMALL. A mobile-ticketing pilot is easier to approve than a full fare-system replacement.
RULE 3 — USE REFERENCE AGENCIES. Public buyers rely heavily on peer deployments and proven contracts.
RULE 4 — FAILURE MODE: treating every agency as a bespoke project destroys SaaS economics; entry remains rational only with configurable deployment.
MARKET TYPE: Fragmented Market (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN PARTNER-EMBEDDED PUBLIC-SECTOR DISTRIBUTION:
1. Reference deployments drive procurement confidence. Agencies prefer vendors with comparable public-sector implementations.
2. Mobility partners create rider reach. Uber and journey-planning integrations put transit ticketing inside apps riders already use.
3. SDK distribution creates ecosystem leverage. A single integration can connect many agencies to many mobility apps.
4. THE WEAKNESS: Partner-led distribution can make the vendor dependent on another company’s rider relationship and product roadmap.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Brownfield entry fits when an existing public or industrial process can be modernized incrementally.
RULE 1 — Choose a workflow where the customer can adopt a new layer without replacing core infrastructure.
RULE 2 — Build interoperability with legacy systems before promising full replacement.
RULE 3 — Use a visible rider or operator benefit to create political support.
RULE 4 — Reject the approach when the customer requires a full replacement but lacks funding or governance capacity.
Example: OpenGov modernized government budgeting and reporting through cloud software; failure occurs when procurement and integration complexity exceed the vendor’s delivery capacity.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A wedge is a narrow deployment that creates visible value and opens a path to broader infrastructure.
RULE 1 — Select a use case with immediate rider or operator value.
RULE 2 — Avoid requiring full hardware replacement in the first deployment.
RULE 3 — Expand through the same fare, rider and payment data.
RULE 4 — Failure occurs when the wedge cannot demonstrate enough value to justify the next procurement phase.
Example: Toast entered restaurants through a point-of-sale wedge before expanding into payments and back-office software.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Masabi moved transit fare collection from large bespoke projects toward recurring Fare Payments-as-a-Service contracts. Its SaaS model provides predictable subscription revenue, while transaction-linked ticketing and payment activity scale with ridership; long contracts such as the MTA’s up to 12-year, $97 million extension reinforce revenue visibility.
REVENUE MODEL
Subscription, Transaction Fee, Service Fee
PRICING MODEL
Flat Rate Pricing, Transaction Fee, Custom Enterprise Pricing
WHY THEY WON
Agencies pay recurring subscription fees for the Justride platform and selected modules; ticket sales and payment processing can create transaction-linked revenue; implementation, support and integration services add fees. Revenue expands with ridership, fare-media adoption and additional agencies or mobility partners.
Masabi prices Justride as a predictable subscription rather than a large upfront capital project, with scope varying by mobile ticketing, account-based ticketing, open payments and SDK deployment. Transaction-linked economics can follow ticketing and payment volume, while enterprise contracts reflect agency size and service requirements.
TARGET AUDIENCE
Large transit authorities (enterprise; want account-based ticketing and open payments); regional and local agencies (subscription; want mobile-first modernization without hardware replacement); mobility and journey-planning platforms (SDK; want embedded transit ticketing); multi-agency alliances (platform; want interoperable fare payments).
CUSTOMER BUYING BEHAVIOUR
The trigger is aging ticketing infrastructure, rider-experience pressure, fare-policy complexity or a mobility-integration initiative. Agencies evaluate through RFPs, references, security reviews and pilot deployments; procurement is formal and political. Adoption begins with mobile ticketing and expands toward account-based or open payments.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Transit agencies pay to reduce capital risk and improve rider experience, not merely to digitize tickets.
RULE 1 — PRICE AGAINST THE LEGACY PROJECT. The comparison is a multi-year bespoke hardware contract, not another software subscription.
RULE 2 — MAKE THE METER FOLLOW RIDERSHIP. Transaction-linked revenue grows when the service is used.
RULE 3 — SELL CONFIGURABILITY. Fare rules, caps, concessions and multimodal integration change frequently.
RULE 4 — WATCH THE VENDOR COST TRAP. Payment disputes, field hardware and public-sector support can undermine SaaS margins.
The buyer is really buying lower-risk fare modernization, proven by the capital and operations budget.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Public-sector concentration: revenue can depend on a small number of large agencies and long procurement cycles.
Political risk: leadership changes, budget pressure and public scrutiny can delay renewals or expansions.
Payment risk: fraud, disputes, settlement errors and privacy issues can damage trust.
Partner dependency: Uber, Moovit and mobility-app channels may change strategy or build competing capabilities.
Competitive pressure: global ticketing vendors and payment networks can bundle fare collection into broader transit platforms.
Masabi is privately held; current ARR and detailed revenue are not publicly disclosed.
Where the model can break
4
MOTION
motion ge cs
Masabi used partnerships with Uber, Moovit and other mobility platforms to distribute transit ticketing through rider-facing apps. Its Justride SDK allowed ride-hailing and journey-planning platforms to sell transit tickets, giving agencies access to riders beyond their own apps.
GROWTH EXPANSION MODEL
Platform Expansion, Geographic Expansion
HOW THEY EXPAND
Masabi expanded from mobile ticketing into account-based ticketing, open payments and Mobility-as-a-Service SDK distribution. Geographic expansion followed deployments across North America, Europe and Asia-Pacific, while platform expansion connected agencies, riders and third-party mobility apps through Justride.
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Against legacy fare-collection vendors and bespoke smart-card projects, Masabi offered a lower-cost, cloud-based, mobile-first alternative. Its advantage was faster deployment and reduced hardware dependence; its constraint is that large agencies may still require validators, gates and deep integration.
GROWTH ENGINE
GTM
Content Flywheel
Agency sales create the fare platform deployment. Mobile ticketing activates riders and demonstrates value. Partnerships with mobility apps expand ticket distribution, while account-based and open-payment adoption deepens the agency relationship. The engine depends on agency references, reliable payments and partner incentives; it weakens if partners control the rider relationship or if procurement stalls.
Masabi uses an enterprise-led, partnership-amplified GTM. Direct sales wins transit agencies; pilots and mobile-first deployments reduce adoption risk; partner SDKs extend ticket distribution through mobility apps. Once deployed, Masabi expands into account-based ticketing, open payments and multimodal services. The primary motion is enterprise sales, with partnerships creating distribution leverage.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is high customer lock-in: Justride becomes embedded in fare rules, rider accounts, payment flows, inspection workflows and reporting. Replacing it requires a public agency to re-procure, migrate rider data and potentially replace or reconfigure fare infrastructure.
| MOAT INTELLIGENCE
THE STANDARD: Lock-in lasts when the platform controls mission-critical transactions and public-facing rider experience.
RULE 1 — FARE-RULE COMPLEXITY. Caps, concessions, transfers and multimodal rules accumulate in the platform.
RULE 2 — PAYMENT AND IDENTITY DEPENDENCE. Rider accounts, cards and settlement flows create switching friction.
RULE 3 — LONG PUBLIC CONTRACTS. Multi-year agreements create revenue durability and procurement inertia.
THE SIGNAL: Masabi’s MTA extension of up to 12 years and $97 million in 2024 indicates deep operational dependence; the moat does not protect against a major payment network or system integrator offering a bundled alternative.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — PROVE MOBILE TICKETING: Validate that riders will use phones and agencies will adopt a cloud-based fare service.
$1–5M ARR — WIN REFERENCE AGENCIES: Deploy with MBTA and other agencies to establish public-sector credibility.
$5–10M ARR — BUILD THE PLATFORM: Expand Justride from mobile ticketing into a configurable fare-payments platform.
$10–50M ARR — ADD ACCOUNT-BASED AND OPEN PAYMENTS: Move beyond tickets into tap-to-pay and fare capping.
$50–100M ARR — SCALE THROUGH PARTNERS: Use Uber, Moovit and SDK distribution to extend reach; Masabi reported more than 140 customers across nine countries in 2022.
$100M+ ARR — NOT PUBLICLY EVIDENCED: Standalone ARR at this scale is not publicly disclosed.
Rule: Enter with a low-risk rider-facing wedge, then expand into the agency’s full fare-payment infrastructure.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Modernize a hardware-heavy public system by starting with a low-risk digital layer, then expanding into the full transaction infrastructure.
SEQUENCE:
1. Identify a public or regulated workflow burdened by bespoke systems and capital cost.
2. Build a configurable cloud service that delivers value without full infrastructure replacement.
3. Add payments, identity and multimodal functions only after the first deployment is trusted.
WORKED: Masabi’s mobile-first approach reduced deployment risk and led to long-term agency relationships, including the MTA’s up to 12-year, $97 million extension.
CAUTION: Do not rely on partner distribution without retaining a direct agency relationship; also avoid hardware-heavy deployments that turn SaaS into a low-margin systems-integration business. Masabi’s private-company ARR is not publicly disclosed.
bottom of page