top of page

Can Trial Pricing work in Logistics & Supply Chain Technology with operational risk?

Logistics software gets purchased after a costly failure, so a trial should resolve an actual shipment, inventory or hiring workflow rather than show a feature list. Veeqo gives sellers free core shipping functionality and sells additional inventory capability; Tenstreet uses tailored enterprise pricing based on fleet and recruiting scope. Neither proves a fixed-duration Trial Pricing offer here. A warehouse that connects one channel may still suffer overselling elsewhere; a carrier cannot assess driver compliance from a fabricated application.

See how top RetailTech companies balanced subscriptions and payments in their revenue, in Business Core.

✓ Skip the success story. Get the decisions behind it  ✓ Not a case study. A teardown you can copy from.

Business Core breaks down top RetailTech companies' revenue models, pricing, buyers and revenue risks, so you can see how software fees and payment revenue work together.

40 Foundational Decisions

34 Model Frameworks

80 Strategy Patterns

4 Pillars of any Business

Backed by evidence
On which a company is built on
Of proven growth & expansion 
Model · Market · Money · Motion

✓ Find relevant precedents in under 2 minutes   ✓ Updated every 6 months    ✓ 6 ARR stages, from pre-$1M to $100M+

Pick a decision or a strategy.
Go deep on companies that made it

Your exact comparables, one filter away.

The companies you study didn't build by instinct alone.
Neither should you.

Stop studying companies that never faced your call.
Famous case studies won’t fit your decision. These will.

​

With a Situation or Strategy you need insight on

​

Open results to see exactly how they did it - and how you can do the same.​

​

The framework walks you through every layer of how the company was built, grown & sustained big

Product & Business Model Decision
Business Model

Tulip

Brainshark

Prowly / Semrush

Klaviyo

Dagster

TrueLayer

Heroku

Nestio

Rocket League

Red Hat OpenShift

Amber Road

SAP

WebStarts

✓ Get the Full list of companies under each   ✓ Unlock in-depth intel on each company
From “what should we do?” to a written plan in one sitting

DISTRIBUTION MODEL

Why do payments make predictable revenue both easier and harder in RetailTech?

Easier, because payment revenue grows automatically with merchant sales and can become the largest line. Harder, because it falls when merchants' sales fall, and rival processors compress the take rate. Independent merchants are also fragile, so closures remove revenue directly. The design question is which line pays your fixed costs. I'd show investors the subscription number first and the payments number second, because the first is what you can defend in a downturn.

How should a RetailTech company split revenue between subscriptions and payments?

• Set subscriptions to cover your support and software cost, as Toast's $1.061 billion subscription ARR does.

• Treat payments as the growth engine and plan for compression. Toast names competition from Square and Clover as pressure on payment economics.

• Keep hardware as a cost, not as a profit line, because installation and support are expensive.

• Consider capped fees to attract larger orders, as Slice did at $2.25 per order by 2020, but add services to build account value.

• Avoid a commission model if your pitch is that you are not a marketplace, as BentoBox did by charging a monthly fee.

• Show merchants the effective total cost per month, combining software, hardware and payment fees in one number.

Which RetailTech companies published pricing that shows the subscription and payments mix?

Toast is the direct example and the others are same-industry precedents.

• Toast charges monthly SaaS fees for software modules, transaction-based fees on payment processing and hardware costs for terminals and peripherals.

• Lightspeed (precedent): monthly SaaS tiers with Retail commonly around $99 a month, Restaurant around $69 and e-commerce around $59 in earlier references, plus payments as a percentage of volume.

• Slice (precedent): a flat $2.25 per order by 2020, plus payments, websites, marketing, loyalty, POS and supplier services.

• BentoBox (precedent): historical plans from about $100 to $500 a month, with Presence at $198, Storefront at $345 and Concierge at $426.

• Notice how each company's first price is easy to explain, which is why merchants adopted it before the more complex lines were added.

What did Toast and Lightspeed report to prove their RetailTech revenue was recurring?

Toast reported 2025 ARR of $2.047 billion, with $986 million from payments and $1.061 billion from subscriptions, and GPV of $195.1 billion. Lightspeed, a precedent, processed $98.1 billion in GTV in fiscal 2026 across roughly 146,000 locations. Both report payment volume alongside software, because investors want to see how much of the revenue is the sticky kind.

What numbers should a RetailTech founder track to prove recurring revenue?

• Shipments completed with correct inventory deduction.


• Verification time for a qualified driver application.


• Use a contained operational lane: one channel-to-shipment flow or one verified driver application, with a rollback path and signed success criteria.

What ARR and volume figures did Toast and Lightspeed publish in RetailTech?

Both are public companies.

• Toast: 2025 ARR of $2.047 billion, payments ARR of $986 million, subscription ARR of $1.061 billion and GPV of $195.1 billion, up 23% year over year.

• Lightspeed (precedent): $98.1 billion in GTV in fiscal 2026 across roughly 146,000 locations.

• Slice (precedent): $2.25 per order by 2020.

Subscription, take rate or per-order fee: which RetailTech income line did each company lead with?

Toast led with software and payments together, BentoBox led with a subscription to avoid commissions and Slice led with a per-order fee. Each started with the line merchants understood best. The subscription is the most predictable and the per-order fee the most exposed to merchant failure. The per-order fee is attractive because merchants see it as fair, but it only works if you add services that raise revenue per merchant.

Which RetailTech pricing line is the easiest to defend to a merchant?

• A subscription is the easiest because the merchant knows the bill.

• A per-order fee is easy to understand and aligns with sales.

• A payments percentage is easy to hide and easy to compare.

• Combine lines and make the total clear.

• Show merchants what they save, not just what they pay.

• Test your price against a restaurant owner's monthly sales, and make sure the fee looks small as a percentage of what they earn.

Which RetailTech companies avoided commissions or capped them?

Two clear examples.

• BentoBox positioned Bento Ordering as zero-commission and charged a monthly subscription.

• Slice charged a flat per-order fee rather than a percentage of order value.

• Toast charges a mix of monthly SaaS, payment rates and hardware.

How to build a predictable revenue model in RetailTech

Use a subscription to cover your fixed costs and add payments as growth. The first decision is whether your merchants are independent or chains, because independents fail more often. The condition that decides the path is how much onboarding and hardware costs per location. If it's high, the lifetime value must be high too.

Business Core shows each company's revenue model, pricing, buyers and how-to-copy steps, so you can see how subscription and payment lines are combined.

Check the revenue risks and cautions behind each model in Business Core, such as take-rate compression and merchant failure, before you set your mix.

1-model (6).png

Which RetailTech risks can make payment-heavy revenue less predictable?

Take-rate compression, merchant fragility, hardware and implementation cost and bundling by Square, Clover and Shopify. Each can lower revenue without losing the customer. Take-rate compression is the one I'd read first, since it can shrink revenue with no merchant leaving.

How do RetailTech vendors protect revenue from fee compression and merchant failure?

• Don't depend too heavily on payment take rates.

• Build a software reason to stay beyond payments.

• Control field-sales cost.

• Add payroll, ordering and marketing modules for expansion.

• Plan for merchants' sensitivity to inflation and labour costs.

• Build annual contracts for software even if payments stay month to month, so the floor is protected.

What revenue risks did Toast, Lightspeed and Slice name in RetailTech?

Payments and merchants dominate.

• Toast: payment take-rate compression, SMB sensitivity to inflation and labour costs, hardware and implementation cost and competitive bundling.

• Lightspeed: payment commoditization, platform competition from Square, Shopify, Toast and Clover, acquisition integration risk and merchant concentration.

• Slice: merchant churn and failure, a low fee ceiling and consumer-demand dependency.

• Together these lists say the same thing: payments are powerful and fragile, so the software line is what protects you.

How do RetailTech buyers decide to switch their point-of-sale software?

A trigger forces the decision: a restaurant opening, a POS contract expiring, a payment-fee increase, a staffing problem or a delivery expansion. Owners compare hardware reliability, payment rates, ease of use, support and total cost, and expand later into payroll and online ordering. Switching a point-of-sale system is disruptive, so owners prefer to change during a slow period or at contract end.

What do RetailTech buyers check before replacing their payment and POS system?

• Hardware reliability.

• Payment rates and the total monthly cost.

• Ease of use for staff.

• Support response when service is down.

• A path to add ordering, payroll and marketing.

• Offer a menu import and a staff training session, since a smooth first week decides the first year.

How did buyers of Toast, Slice and BentoBox purchase in RetailTech?

Each trigger is operational.

• Toast: a restaurant opening, POS contract expiration, payment-fee increase or staffing problem triggers evaluation, and owners assess hardware, rates, ease of use and cost.

• Slice (precedent): independent pizzerias adopt a per-order fee platform and expand into POS, rewards and marketing.

• BentoBox (precedent): restaurants buy a website and ordering presence for a monthly fee instead of paying marketplace commissions.

What did RetailTech companies get wrong when relying on transaction revenue?

They copied field sales without enough customer lifetime value, relied too heavily on take rates or monetised the wrong side of the market. Each of these made the model look cheaper to run than it was, and the support bill arrived with the first thousand locations.

How can a RetailTech business avoid leaning too hard on payment take rates?

• Don't copy field sales without high customer lifetime value.

• Don't depend too heavily on payment take rates.

• Don't plan without fee compression or regulatory change.

• Don't underestimate hardware and onboarding costs.

• Don't add products faster than merchants adopt them.

• Don't discount payment rates to win a merchant unless the software contract is signed alongside.

Which cautions did Toast, Lightspeed and Slice carry in their RetailTech playbooks?

The cautions follow the payment dependence.

• Toast's caution: do not copy field sales without high customer lifetime value, and avoid depending too heavily on payment take rates without a plan for fee compression.

• Lightspeed's precedent warns that payment costs, support and hardware expenses must be managed as volume grows.

• Slice's precedent warns that a capped per-order fee needs attached services to build account value.

Enter business core

Does Business Core show how companies priced their products?

Yes. The Monetization pillar covers each company's revenue model, pricing, who pays, how they buy and the revenue risks.

Does Business Core show which risks put revenue in danger?

Reliable recruiting or verification under the carrier’s real operating requirements.

Does Business Core explain who pays and how they buy?

Yes. The Monetization pillar covers who pays, how they buy and the pricing logic behind each company's revenue model.

Can I filter companies by revenue model or pricing strategy?

Yes. You can filter by revenue model and by pricing strategy, among other filters, and each matching company opens on its own page.

Business Core
Everything You Need To Build a Winning Business

Own the
playbook of companies 

that won

One-time payment · No subscription · No seat fees

Lifetime Access

Business Core

$180

180

​

​

Valid until canceled

SSL Secure Checkout. Instant access.

Companies broken down on the same 56 fields 

Filter by 40 decisions carried out by SAAS Cos.

114 model & strategy labels executed by Top Cos.

See what worked, failed and why

Leave with an ARR-stage replication blueprint

Turn proven patterns into your own strategy

​​​​

Your Business Core access is automatically added to your account on purchase.

The strategic intelligence gap closes the moment you open it.

Walk in with the decision; Walk out with companies that already made it - Here's what's INCLUDED :

MODEL

• Business Models  • Distribution Model  • Model Insights  • How to Apply it  • Opportunities & Risks

MARKET

• Market Type  • Market Entry & Foothold Strategy  • Growth Model  • Market Intelligence  • Playbook

​

MONETIZATION

• Revenue & Pricing Model  • Target Audience  • Customer Buying Behaviour  • Patterns  • Pricing Intel

MOTION

• Competitive Strategy  • Growth & Expansion Strategy • GTM Summary  • Growth Engine  • Sustaining Moats

​

bottom of page