Run 100 locations on a typical ordering-and-delivery SaaS stack at $300 per location per month and you spend $360,000 a year on software rent. Next year the bill is $360,000 again. The product barely changes; the invoice never stops. A custom platform you own works the other way around: a fixed build plus maintenance, with the per-location cost dropping every time you open a store. Somewhere between those two cost curves the lines cross, and most chains sail past that point years before anyone sits down to do the arithmetic.
Per-location pricing is a tax on your growth
SaaS pricing for restaurant chains almost always scales per location: online ordering at $100–200, delivery management at $50–150, loyalty at $50–100, and on many plans a 1–3% fee on every order. A realistic mid-range stack lands around $300 per location per month before those transaction fees. The number is built to feel small, and at a single location it genuinely is.
Add a 2% transaction fee on digital orders and it gets worse. A location doing $40,000 a month in digital sales hands over another $800 a month, which is $960,000 a year across 100 locations. The 'cheap' SaaS stack has become a seven-figure line item that grows at exactly the speed of your success.
The crossover sits around 30–50 locations
A custom platform on our model costs a fixed setup plus a flat maintenance retainer, with no per-location meter ticking away in the background. For a mid-size chain, total cost of ownership usually runs $100,000–150,000 in year one and less after that, whether you operate 40 stores or 400. Put that against the SaaS curve. At 30 locations ($108,000/yr) the two lines meet. At 50, ownership is clearly cheaper. Past 100 the comparison barely holds your attention: you are weighing $360,000+ of permanent rent against a flat cost that each of your next 50 openings dilutes further.
The other side deserves a fair hearing. Under roughly 20 locations, SaaS usually wins. The fixed cost of ownership spreads over too few stores, and a small chain rarely needs a custom roadmap. This is an argument about scale, and it flips hard once you have the scale.
Bring your location count and current software bill. We'll build the comparison live on a 30-minute call.
Money is the smaller half of the argument
There are three things per-location SaaS can't sell you at any price, and they matter more than the invoice.
Start with your data. A 100-location chain generates millions of order records a year. On rented software that history lives in the vendor's schema, exportable as CSVs if you're lucky. Own the platform and it becomes a queryable asset: the raw material for pricing, site selection, and the customer segments your marketing runs on. We went into why that matters in what losing customer data costs.
Then there's the roadmap. When 100 locations need a regional pricing rule, a franchise-specific report, or an integration with the ERP your CFO already bought, a SaaS vendor drops it into a backlog behind 4,000 other customers. On a platform you own, the same request is a work order, and integrations get built for your stack instead of the average customer's.
And there's control. Nobody runs 100 stores from 100 browser tabs and honestly calls it management. A chain needs every location's orders, couriers, and kitchen load on one monitoring panel, plus reports that stack stores against each other without a week of spreadsheet work. Chains on our platform report 2–3× back-office efficiency from that consolidation alone.
"Custom" no longer means a two-year IT project
The old objection to owning your platform was the build itself: 18 months, a hiring spree, and maybe a 50% chance of shipping. That is the model we replaced. Dots deploys a proven core (branded apps, an ordering site, logistics, marketing, analytics, all already tested on 3M+ orders) and then customizes it to how you actually operate. A typical launch takes about two weeks rather than two years. You get the economics of ownership without the greenfield risk: the platform carries your brand, holds your data, and moves on your priorities.
The conversion upside rides along for free. Branded chain apps convert up to 35% of visitors into buyers and well-built ordering sites reach 15%, against roughly 3% for a marketplace listing. So the platform that cuts your software rent is also the one growing the direct channel it runs on.
The switching-cost objection, answered with sequencing
The usual reason chains stay on expensive SaaS is fear of the cutover: 100 locations can't hold their breath while IT replatforms. They don't have to. Migration runs in waves, one city or region at a time, with old and new systems live in parallel and POS and payment integrations connected before the first store flips. A 100-location chain usually finishes the move in a quarter, and the numbers from the first wave take most of the risk out of the rest. Set that one-time effort against $360,000 a year, every year: you pay the switching cost once instead of paying rent forever. The one genuinely bad window is a mid-expansion crunch, so pick a quiet quarter and sequence it.
Do this next
Open your software budget and work out one ratio: all your per-location software and transaction fees, divided by annual digital revenue. If it clears 2%, it's worth pricing the alternative. For the full decision framework, including the cases where SaaS still wins, see custom platform vs. SaaS subscription.
One owned platform for ordering, delivery, and management — launched in about two weeks.