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 tested whether their growth could repeat, 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' go-to-market, pricing, buying behaviour and revenue risks, so you can judge whether your own growth repeats.
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
BILL (formerly Bill.com)
HireVue
Maze
PublishDrive
Ramp
Xero
PandaDoc
SocialPilot
Fly.io
Planful
Prezly
Trendemon
Databricks
✓ 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 is repeatable growth harder to confirm in RetailTech when merchants are small and fail often?
Because every merchant you win can disappear for reasons you don't control. Slice's research names high failure rates and limited technology budgets among independent pizzerias, and says closures remove transaction revenue directly. PourMyBeer adds capital-intensive sales cycles and installation cost. So the test of repeat is retention of merchants and their order volume, not the count you signed.
How do I tell RetailTech growth that repeats from growth that depends on a few merchants?
• Count active merchants by order volume, not by sign-up, since Slice needs dense repeat transactions before it expands geographies.
• Check that the merchant's economics improve. Slice's merchants see incremental orders and average-order-value gains after online ordering goes live.
• Look at cost to onboard. Field sales fail when merchant volume is too low to support onboarding and support costs.
• Check concentration. PourMyBeer warns that dependence on large hospitality or stadium accounts makes revenue sensitive to a few operators.
• Track whether new merchants come from referrals as well as outbound visits.
• Compare cohorts by region or venue type, to see whether the playbook travels.
How did Slice and PourMyBeer turn a first win into a repeatable RetailTech motion?
Both started with one proof point, then productised it.
• Slice converted pizzerias' existing phone-order business into direct digital orders, using field sales, local referrals and a low fixed per-order fee; it grew from more than 10,000 pizzerias in 2018 to more than 15,000 by 2021.
• PourMyBeer used founder-led venue sales and a real Baltimore tavern deployment to win its first paying customer in February 2009.
• By 2015 PourMyBeer had refined its beer-wall system and sold about 30 projects in its first commercial year, turning a founder-led pilot into a repeatable venue-sales motion.
• By 2024 it reported more than 540 active customers, over 12,000 connected taps and more than 403 million ounces processed (company-reported).
What did RetailTech companies show to prove their first merchants were not a fluke?
They showed the same economic result in a new setting. Slice showed a flat per-order fee beat percentage-based delivery commissions for independent pizzerias, then repeated it across thousands of shops. PourMyBeer showed in bars, then stadiums, hotels and grocery stores, that self-pour could cut waste and queues. In both cases, the merchant's own numbers did the selling.
What evidence should a RetailTech startup gather to show merchant results repeat?
• 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 did Slice and PourMyBeer charge, and what proof did they publish in RetailTech?
Their prices show how each linked its fee to the merchant's gain.
• Slice charges pizzerias a flat per-order fee, $2.25 per order by 2020, instead of a percentage of order value, and monetises payments, websites, marketing, loyalty, POS and supplier services on top.
• PourMyBeer prices custom systems by taps, screens and add-ons such as POS integration, SMS and mobile wallet; reported hardware and wall configurations range from roughly $1,300 to $18,000.
• PourMyBeer says its system can save venues up to $142 per keg (company estimate).
• Coca-Cola participated in a 2020 investment in PourMyBeer, though its current revenue is not publicly disclosed.
RetailTech examples: how did Slice, PourMyBeer and Rocket League decide how growth would repeat?
Slice chose to stay on independent pizzerias and add services only after ordering worked, positioning as a reverse franchise. PourMyBeer chose to validate in one venue, then standardise a beer wall before widening venue types. Rocket League, outside retail, kept its core loop and repeated growth through a free-to-play shift. The lesson I'd take is that both RetailTech names narrowed first and widened only when the playbook held.
Which RetailTech growth path should I use: stay narrow or expand to new merchant types?
• Stay in one merchant type until the sales and support playbook is repeatable.
• Start with one high-frequency transaction that has measurable revenue impact, such as the order.
• Design a fee that beats the incumbent's economics. Slice uses a capped, flat fee because percentage fees punish a merchant's most valuable orders.
• Add operating services only after transaction liquidity exists.
• Avoid expanding across categories before the vertical playbook, supply network and merchant support model are repeatable.
How did Slice and PourMyBeer win their first RetailTech merchants?
Both sold close to the merchant and priced to the merchant's gain.
• Slice sells to independent pizzerias, small chains and multi-shop owners, pizza suppliers and local consumers, and describes itself as a reverse franchise that gives independents shared scale without taking ownership of their brands.
• PourMyBeer sells to bars and taverns, stadiums, hotels and casinos, and grocery and food-hall operators, starting with a pilot or limited tap wall.
• Slice competed against Domino's, Pizza Hut, Papa John's, DoorDash, Uber Eats and Grubhub.
• LinkedIn made individual utility real before selling institutional access.
How to test whether your RetailTech growth is repeatable before you add more reps
Take the next ten merchants you sign without the founder in the room and see whether they activate and reorder like the first ten. Your first decision is whether your fee is capped, flat or percentage-based, and what the merchant keeps in each case. The condition that decides the path is whether the merchant's numbers improve within weeks. The caution from Slice's research is not to copy a low-fee model without attached services or enough order density.
Business Core shows each company's go-to-market, pricing, ARR journey and how-to-copy steps, so you can see how growth repeated at each stage.
Check the pits and revenue risks of each RetailTech company in Business Core, such as merchant churn and low fee ceilings, before you scale sales.
What makes RetailTech growth fall apart when independent merchants close or fees are capped?
Merchant failure, fee ceilings, consumer dependency, incumbent marketplaces and installation cost. Slice names high failure rates, a low fee ceiling, reliance on consumers reordering and DoorDash, Uber Eats and Grubhub. PourMyBeer adds upfront hardware cost, alcohol rules, venue concentration and rising service cost.
How many merchant closures can a RetailTech revenue plan take?
• Assume a share of your merchants close each year and see what happens to revenue.
• Calculate what a capped fee earns on your smallest orders, and what services must be attached.
• Check consumer repeat behaviour. If shoppers use you only occasionally, merchants see too few incremental orders and churn.
• Add the cost of hardware, installation and maintenance per location.
• Check licensing and compliance rules that could restrict deployment.
• Ask what happens if a large marketplace copies your offer.
Which risks did Slice and PourMyBeer say could cap RetailTech growth?
The risks decide how fast a repeat motion can grow safely.
• Slice: merchant churn and failure; a low fee ceiling that needs attached services; consumer-demand dependency; competition from delivery marketplaces with larger audiences; category concentration in pizza.
• PourMyBeer: a capital-intensive sales cycle; alcohol-service and age-verification rules; venue concentration; service-cost escalation with every installed location; consumer-experience risk if self-pour feels impersonal.
• Slice's pits are a low-fee model without attached services and consumer-marketplace dependence.
• PourMyBeer's pits are automation without experience design and custom hardware for every venue.
How do shop and venue owners test a RetailTech vendor before they commit?
They test on a small part of the business. A pizzeria facing high delivery-app fees evaluates Slice through a local rep or a referral, tests online ordering, sees incremental orders, then adopts POS, loyalty or supplier services. A venue owner reacting to queues, staffing shortages or keg waste evaluates PourMyBeer through demos, site assessments, ROI projections and reference venues, and starts with a limited tap wall.
What should a RetailTech founder watch between a merchant's first demo and a wider rollout?
• Find the trigger: high delivery-app fees, long queues, staffing shortages or keg waste.
