Everyman Brand Archetype
Automotive
Expense Management Software
Soldo
Built a European spend-control position by making every employee and supplier payment programmable through cards, wallets, budgets, and ERP-ready data, despite fragmented European payment regulation and entrenched finance processes.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Soldo began in 2015 with prepaid Mastercard cards, wallets, spending rules, and real-time transaction visibility rather than a broad finance suite. It first proved that decentralized employees and contractors could spend within controlled limits, then added receipts, approvals, accounting integrations, supplier cards, and multi-entity governance as customers expanded.
Question this model answers
We need to decide what to build first.
BUSINESS MODEL
SaaS
HOW THEY BUILT IT
'- Soldo was founded in London in 2015 by Carlo Gualandri to give businesses control over decentralized spending. → It combined prepaid Mastercard cards, wallets, mobile receipt capture, and a management console. → Its first customer arrived in 2017.
- It made every card programmable: managers set budgets, merchant rules, user permissions, and funding controls. → This shifted spend control from after-the-fact reimbursement to pre-approval and real-time monitoring. → Customers include Mercedes-Benz, Sony, Toyota, and GetYourGuide.
- It built a full-stack payment and SaaS platform rather than relying entirely on third-party infrastructure. → This supported customization, ERP integration, and multi-country deployment. → Soldo serves more than 25,000 organizations across 31 countries.
- It expanded from employee cards into supplier-specific virtual cards, invoices, procurement controls, and accounting exports. → This moved Soldo from expense management into broader pay-and-spend automation. → Its platform supports advertising, software, travel, e-commerce, and operational purchases.
HOW TO ARCHITECT IT
1. Identify a spending decision that is distributed across employees, teams, or contractors but must remain accountable to finance; validate that the current process creates delays, policy breaches, or reconciliation work.
2. Build the payment instrument and control layer together, because a card without budgets and rules is merely a payment method.
3. Start with one high-friction spending category—travel, software, advertising, or field expenses—and prove that controls reduce leakage without slowing work.
4. Make transaction data ERP-ready before scaling enterprise sales; finance teams adopt systems that reduce reconciliation, not merely add dashboards.
5. Add supplier cards and procurement workflows only after employee spending controls are trusted.
6. Avoid promising unlimited flexibility before permissions, audit trails, and compliance are robust; the common mis-build is giving decentralized users freedom without giving finance a reliable system of control.
DISTRIBUTION MODEL
Direct Sales, Enterprise Sales, Inside Sales, Partnerships
HOW THEY OPERATIONALIZED
'- Soldo sold directly to mid-market and enterprise finance leaders who needed decentralized spending with centralized control.
- Inside sales converted smaller businesses through self-serve plans and card-based onboarding.
- ERP, accounting, and travel-system integrations created adoption paths through finance and procurement teams.
- Named enterprise customers such as Mercedes-Benz, Sony, and Toyota provided credibility for larger, multi-country deployments.
HOW TO REPLICATE WHAT WORKED
What Worked
Sell control and auditability to finance leaders while making the employee experience simple enough to avoid workarounds.
Trap if Copied Blindly
Enterprise sales fail if implementation and ERP integration remain bespoke; the cost is long cycles, heavy services drag, and weak gross margin.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — PROCUREMENT-NATIVE SPEND MANAGEMENT. Most tools begin with employee expenses; the larger opportunity is connecting purchase requests, supplier onboarding, approvals, payments, and reconciliation into one workflow.
GOLDMINE 2 — POLICY-AS-CODE SPENDING. Companies need rules that vary by team, geography, vendor, and cost center; a configurable policy engine can reduce manual finance review and improve compliance.
GOLDMINE 3 — SPEND INTELLIGENCE FOR CFOs. Transaction data can identify duplicate subscriptions, vendor concentration, budget drift, and savings opportunities; the gap is turning controls into proactive financial decisions.
THE TRAP TO WATCH
THE PIT — CARD ISSUING AS THE ENTIRE PRODUCT. A card solves payment access but not governance; without budgets, approvals, and reconciliation, it becomes commoditized quickly.
THE SECOND PIT — ENTERPRISE CUSTOMIZATION WITHOUT PRODUCTIZATION. Highly configurable controls can win large logos but destroy margins if every deployment requires bespoke implementation.
MOVE WITH CAUTION
Do not build a spend platform without a clear answer for reconciliation and auditability; finance leaders will not replace existing controls for a better mobile experience alone.
2
MARKET
MARKET TYPE
Mature Market
WHY THEY WON
Expense management was a mature category when Soldo scaled, with established travel-and-expense systems and accounting tools. Its opening was that many companies still managed decentralized spending through corporate cards, reimbursement forms, and manual controls. Soldo changed the comparison from “expense reporting” to “spend governance,” where budgets, permissions, and payment controls were built into the card itself. This mattered because finance leaders wanted real-time control, while employees and contractors needed autonomy. Incumbents could add cards, but legacy expense workflows and enterprise implementations made embedded controls harder to deliver quickly. The transferable lesson is that mature categories can be disrupted by moving control upstream—from reimbursement to authorization.
Soldo entered spend management against Concur, Expensify, Pleo, Spendesk, Ramp, and corporate-card providers. It differentiated by serving both decentralized employees and finance teams: cards had embedded budgets and rules, while the platform produced ERP-ready transaction data and multi-entity controls.
Question this model answers
We need to differentiate from established competitors.
ENTRY STRATEGY
Brownfield Entry
EXECUTION
Soldo entered by replacing corporate cards, reimbursement processes, and fragmented spend controls rather than creating a new spending category. It targeted companies already managing employee and contractor purchases, offering programmable cards, wallets, budgets, and accounting exports. The critical bet was that finance teams would adopt a system that gave employees autonomy without losing oversight. This required card issuing, payment infrastructure, mobile capture, and ERP integrations. The founder-level lesson is that brownfield entry succeeds when the new workflow reduces both employee friction and finance-team risk. It fails if controls are too rigid, implementation too complex, or reconciliation incomplete.
FOOTHOLD STRATEGY
Wedge Strategy
THE HOW
Soldo’s first wedge was European businesses with decentralized employees and contractors making frequent purchases. They were reachable through finance and operations networks, could pay because expense leakage and reconciliation were costly, and could start with a limited number of cards. The path outward extended into mid-market and enterprise accounts, supplier cards, procurement workflows, and multi-country governance.
MARKET TYPE PLAYBOOK
RULE 1 — MAKE CONTROL VISIBLE TO THE ECONOMIC BUYER. Show finance leaders where spend leaks, which approvals delay and how reconciliation cost falls.
RULE 2 — REPLACE THE WORKAROUNDS. Corporate cards, reimbursement forms and manual reconciliation are the incumbent; programmable cards and budgets give the buyer a measurable alternative.
RULE 3 — INTEGRATE WITH THE ACCOUNTING STACK. Controls only matter if spend data flows cleanly into the ERP and accounting tools finance already trusts.
RULE 4 — EXPECT A CROWDED CATEGORY. Mature expense systems can bundle cards and approvals, so the entrant must keep owning decentralized, employee-level spending.
In a mature market, the entrant must make a specific control improvement visible to the economic buyer.
The strongest wedge is usually a workflow where leakage, delay, or reconciliation cost is measurable.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Target workflows buyers already run. Companies managing employee and contractor purchases already have budget and urgency.
RULE 2 — Preserve auditability during migration. Every payment needs an approval trail and a clean export so finance can adopt without risk.
RULE 3 — Ship controls and integrations together. Programmable cards without accounting sync, or sync without controls, leaves reconciliation manual.
RULE 4 — Reject brownfield entry when the incumbent workflow is already trusted. If the buyer sees no leakage, delay or reconciliation pain, the switch is not worth the risk.
Use brownfield entry when the incumbent workflow is manual or fragmented and the replacement can preserve auditability.
Build payment controls and accounting integrations together.
Start with a spending category where decentralization creates measurable risk.
Expand into adjacent workflows only after controls and reconciliation are trusted.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Pick a category where decentralization creates measurable risk. Employee and contractor purchases leak budget when controls are weak.
RULE 2 — Prove the control loop before adding features. Budgets, receipts and approvals must work reliably before anything else is layered on.
RULE 3 — Expand through the same finance relationship. Once controls and reconciliation are trusted, add supplier payments and wallets.
RULE 4 — Avoid expanding before reconciliation is trusted. Breadth without accurate data erodes the finance buyer’s confidence.
Soldo’s wedge was European businesses with decentralized employees and contractors making frequent purchases; failure occurs when it expands into adjacent workflows before controls and reconciliation are trusted.
HOW TO APPLY MARKET ENTRY STRATEGY
Soldo replaced corporate cards, reimbursement processes and fragmented spend controls rather than creating a new category; failure occurs when auditability or accounting integration lags the payment controls.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN FINANCE-CONTROL SOFTWARE DISTRIBUTION:
1. FINANCE LEADERS BUY CONTROL; USERS ADOPT CONVENIENCE. The product must satisfy both sides or it creates workarounds.
2. INTEGRATIONS DE-RISK ENTERPRISE ADOPTION. ERP and accounting connections make the platform part of existing reporting systems.
3. ENTERPRISE REFERENCES ACCELERATE MID-MARKET SALES. Large logos reduce perceived implementation and security risk.
WEAKNESS
Customization creep. Complex enterprise requirements can turn a scalable SaaS product into a services business.
GROWTH CAMPAIGNS
Spend-management education and webinars; Spend Index research; supplier virtual-card campaigns; ERP and accounting-integration positioning; enterprise case studies with Mercedes-Benz, Sony, Toyota, and GetYourGuide; country expansion across Europe; card-and-wallet onboarding campaigns.
| So What
Soldo’s supplier-card concept reframed recurring vendor spend from an accounting line item into a controllable payment workflow.
| Key Learning
The strongest expansion wedge is often not the employee but the recurring vendor relationship behind repeated purchases.
| How to Use
Identify a recurring, fragmented spend category—software, ads, logistics, contractors—and create a dedicated payment-and-control object that makes every transaction traceable to a budget and owner.
3
MONEY
REVENUE MODEL
Subscription, Transaction Fee, Service Fee
Soldo prices by company plan and usage rather than relying solely on interchange. Its Standard plan starts at £27 per month with three users and three cards, while Unlimited includes unlimited users, wallets, cards, and transfers; card fees, foreign-exchange fees, and add-ons create additional revenue.
Question this model answers
We need to choose the right pricing metric.
PRICING STRATEGY
Tiered Pricing, Transaction Fee, Add-On Pricing
WHY THEY WON
Businesses pay recurring subscription fees for wallets, users, cards, controls, and integrations. Soldo also earns transaction-linked revenue from card usage and foreign exchange, plus fees for additional cards or services. The meter is organizations, users, cards, wallets, and spend volume; revenue expands as companies add teams, suppliers, countries, and controls. Margin depends on payment processing, compliance, support, and implementation costs.
TARGET AUDIENCE
Mid-market companies (Standard/Premium; want employee cards, budgets, and accounting sync); enterprises and multi-entity groups (Unlimited/custom; want global controls and ERP integration); finance teams (all tiers; want real-time visibility and reconciliation); operations and procurement teams (supplier cards; want vendor-level spend control).
Soldo uses tiered monthly plans: Standard from £27 per month and Unlimited with unlimited users, wallets, cards, and transfers. It charges a fixed 1.5% foreign-exchange fee and may charge for additional cards or services; enterprise pricing is customized around entities, integrations, and controls.
CUSTOMER BUYING BEHAVIOUR
A finance leader usually evaluates Soldo after expense leakage, reconciliation delays, or a decentralized-team control problem. They assess card controls, ERP compatibility, security, implementation effort, and pricing; adoption often begins with one team or spending category before expanding company-wide.
WILLINGNESS TO PAY
CORE INSIGHT
Customers are not buying cards; they are buying decentralized spending without losing financial control.
RULES OF ADOPTION
RULE 1 — PRICE THE CONTROL LAYER, NOT THE PAYMENT RAIL. Budgets, permissions, and audit trails create the durable value.
RULE 2 — USE CARDS TO CAPTURE STRUCTURED DATA. Payment instruments turn spending into real-time, actionable information.
RULE 3 — SELL ERP READINESS TO THE ECONOMIC BUYER. Finance teams pay for clean reconciliation and reporting, not mobile convenience alone.
RULE 4 — WATCH THE VENDOR COST TRAP. Card issuing, compliance, support, and enterprise implementation can consume subscription margin if not standardized.
The buyer is really buying governed spending autonomy, evidenced by the finance-operations and card-program budget.
REVENUE RISK
Implementation drag: enterprise deployments require ERP mapping, permissions, and change management, increasing cost-to-serve.
Interchange and FX pressure: payment economics vary by market and can be compressed by regulation or competition.
Enterprise concentration: large customers can dominate revenue, making renewals and expansion critical.
Accounting-platform competition: ERP and accounting vendors can add cards, approvals, or bill-pay functionality.
Compliance and fraud risk: card issuing, KYC, sanctions, and transaction monitoring create fixed operational overhead.
Control-versus-flexibility tension: overly rigid controls reduce employee adoption; overly loose controls reduce finance value.
Soldo is privately held; it raised $180 million in 2021, but public revenue and ARR are not disclosed.
4
MOTION
Soldo sold complex, multi-entity spend-control software to enterprises including Mercedes-Benz, Sony, and Toyota. Buying involved finance, procurement, IT, security, and ERP integration; its movement from SMB cards to enterprise governance confirms a structured enterprise sales motion.
Question this model answers
We need to build an enterprise sales motion.
GROWTH EXPANSION MODEL
Land & Expand, Product Line Expansion
HOW THEY EXPAND
Soldo began with employee and contractor cards, then expanded into supplier cards, invoices, procurement controls, accounting integrations, and multi-entity governance. It expanded within accounts by adding teams, countries, cards, and spend categories, while expanding across 31 countries.
COMPETITIVE STRATEGY
Sales-Led Growth
HOW THEY COMPETE
A finance leader identifies decentralized spending risk → Soldo launches cards, wallets, and controls for one team or category → transaction data improves visibility and reconciliation → additional departments, suppliers, and countries are added → ERP integration and governance deepen account dependence. The compounding trigger is control expansion: each new spending category creates more reason to centralize policy and reporting. The engine weakens if implementation remains bespoke, if employees bypass controls, or if finance teams cannot reconcile data cleanly. A founder can reproduce this by starting with one high-friction spend category and expanding only after the control model is proven.
GTM
Soldo uses a sales-led, finance-led GTM with product-led elements for smaller businesses.
$5–10M ARR
Direct and enterprise sales target CFOs, finance directors, procurement leaders, and operations teams; inside sales supports SMB onboarding. Accounting and ERP integrations reduce adoption risk, while customer references support larger deployments. The primary motion is sales-led, with product-led adoption at the team level. The founder-level implication is that governance software needs a credible implementation system; product-led adoption alone rarely converts into enterprise-wide contracts.
SUSTAINING MOATS
High Customer Lock-In
The moat is operational lock-in created by card programs, wallets, budgets, approval rules, transaction history, supplier mappings, and ERP integrations. Once finance and procurement workflows run through Soldo, migration requires reissuing cards, rebuilding controls, and remapping accounting data.
| Why This Moat Lasts
A lock-in moat lasts when payment instruments, controls, and financial records are embedded across teams and systems.
| Standard Rules
RULE 1 — CARD PROGRAMS CREATE OPERATIONAL DEPENDENCE. Employees, contractors, and suppliers rely on issued cards and wallets.
RULE 2 — CONTROL LOGIC CREATES INSTITUTIONAL MEMORY. Budgets, approvals, and policies encode how the company spends.
RULE 3 — ERP INTEGRATION CREATES DATA GRAVITY. Transaction mappings and reconciliation workflows make replacement costly.
| The Signal
Soldo serves more than 25,000 organizations across 31 countries, including large enterprises such as Mercedes-Benz, Sony, and Toyota. The moat does not protect against poor implementation, weak support, or a platform with stronger ERP-native controls.
ARR
JOURNEY
Pre-$1M ARR
PROVE PROGRAMMABLE CARDS. Founded in 2015, Soldo focused on prepaid Mastercard cards, wallets, and spending rules; its first customer arrived in 2017.
WATCH: whether finance teams would trust a new card program.
$1–5M ARR
WIN DECENTRALIZED TEAMS. Soldo targeted businesses with employees and contractors making frequent purchases, proving that controls could reduce leakage.
WATCH: onboarding and card-program operations.
$5–10M ARR
ADD ACCOUNTING AND ERP READINESS. The strategic move was to make transaction data exportable and integration-friendly, expanding beyond expense capture.
WATCH: implementation complexity.
$10–50M ARR
MOVE UP-MARKET. Soldo won mid-market and enterprise customers, including Mercedes-Benz, Sony, and Toyota, by emphasizing controls, integrations, and multi-country capability.
WATCH: customization and services drag.
$50–100M ARR
EXPAND INTO PROCUREMENT. Soldo added supplier cards, invoices, and procurement-oriented workflows, increasing account value beyond employee expenses.
WATCH: product breadth versus core spend-control focus.
$100M+ ARR
NOT REACHED based on available public evidence. The likely requirement is productizing enterprise configuration and scaling multi-country support without eroding margin.
BREAKDOWN
THE STANDARD
Build spend governance by making the payment instrument programmable, then expand from employee autonomy into supplier, procurement, and multi-entity control.
THE SEQUENCE
1. Identify a decentralized spending workflow with measurable leakage, delay, or reconciliation cost; prerequisite: access to finance and operations decision-makers.
2. Build cards, wallets, budgets, and permissions as one control system; decision gate: finance can enforce policy without slowing legitimate spending.
3. Add supplier cards, procurement, and ERP integrations only after the employee workflow is trusted; prerequisite: standardized configuration and reconciliation.
Soldo’s programmable cards and ERP-ready data helped it move from expense management into enterprise spend governance.