# Launching online ordering and delivery from scratch

_For groups with no online channel of their own_

Your app and ordering website, POS integrations, delivery and a back office, launched together for every brand. We build on top of the POS you already run, so your dining rooms keep working the way they do.

For restaurant groups with 30–250 locations that sell through dining rooms and delivery apps

**In short.** Launching online ordering and delivery from scratch means four pieces go live together: a branded app and ordering website, an integration that sends each order to the right location's POS, delivery through your own couriers or a courier network, and a back office for menus, prices and orders. For a group with several brands, all four run on one backend. The first step is a 2–3 week Assessment.

## Why groups stop relying on delivery apps alone

- Share of restaurant traffic that's off-premises: Nearly 75%. Source: National Restaurant Association, April 16, 2025, checked 2026-11-09
- Delivery app commission on a delivery order: 15–30% DoorDash, 20–30% Uber Eats. Source: merchants.doordash.com/en-us/pricing and merchants.ubereats.com/us/en/pricing, checked 2026-11-09
- Operators who say delivery app orders aren't profitable: 47% full-service, 43% limited-service. Source: National Restaurant Association comments to the FTC, May 18, 2026, checked 2026-11-09
- A courier for your own orders, with no commission: $6.99–$10.99 per delivery (DoorDash Drive); from $7.99 (Uber Direct). Source: DoorDash Drive On-Demand and Uber Direct pages, checked 2026-11-09

Checked November 9, 2026. Commissions depend on the plan and the market.

## What happens when you launch it piece by piece

Most groups start with one piece. Each piece creates the next problem.

- **Month 1**: An agency ships an app. Staff still type its orders into the POS by hand.
- **Month 3**: Delivery runs through three apps, with a tablet for each one at every location.
- **Month 6**: Each brand keeps its menu in four places, and prices drift apart.
- **Month 9**: Nobody can say what a delivery order earns after commission and courier costs.

## How to launch online ordering and delivery, step by step

Four steps. The app, the integrations, delivery and the back office go live together, one brand at a time.

- **Map brands, POS systems and delivery partners** (Weeks 1–3): List every brand, POS system, delivery partner and payment provider. Agree on a launch order and get a fixed estimate for Build. This is the Assessment.
- **Build one backend and connect every POS** (Weeks 4–10): Set up one backend for menus and orders, connect it to each location's POS, and add payments and a back office for menus, prices and orders.
- **Build the app and ordering website** (Weeks 6–14): Ship iOS and Android apps and an ordering website for each brand, all on the shared backend.
- **Set up delivery and roll out brand by brand** (Weeks 12–19): Choose in-house drivers, a courier network or both, and draw delivery zones. Launch one pilot brand, fix what breaks, then roll out the rest.

Timelines depend on the number of brands, POS systems and delivery partners. We fix them in the Assessment. Your own app and website start from $100,000.

## What goes into your own restaurant delivery platform

- **[Online ordering platform](https://dev.family/foodtech/online-ordering-platform)**: An app and an ordering website for every brand on one backend.
- **[Delivery operations](https://dev.family/foodtech/delivery-operations)**: Restaurant delivery software that sends each order to your own drivers, a courier network or both, with dispatch rules for each location.
- **[POS integration](https://dev.family/foodtech/pos-integration)**: Orders go straight into each location's POS. Staff stop retyping them from tablets.

## A 16-brand restaurant group in four countries

Saudi Arabia, Kuwait, the UK and the US. The group sold through dining rooms and delivery apps, with no ordering channel of its own. We're launching its app and ordering website, POS integrations, delivery logistics, payments and a back office for every brand at once. The Deliverect and Nash integrations are built, tested and running. The project is launching now, so there's no case study yet.

## Where it usually hurts

- Build the courier app around how your stations already work. At Sizl, bundling stayed manual, and couriers mark an order with one button.
- Proof-of-delivery photos have to save offline. Couriers lose signal inside buildings.
- Give the menu one owner before launch. If each brand edits prices in the POS, the app and every delivery app, they drift within weeks.
- Decide who dispatches before the app ships: your own drivers, a courier network, or both, with a fallback when no driver is found.

From the 16-brand group launch and Sizl Rider. Written by the PM, checked by the backend lead.

## Who this page is for

- **[Restaurant groups and franchises](https://dev.family/foodtech/multi-brand-franchise)**
- **[Who we serve](https://dev.family/foodtech)**

## Questions

### How do you launch online ordering and delivery for a restaurant group?

Start with one backend for menus and orders, connect it to each location's POS, then put the app, the ordering website and delivery on top. Launch one brand first, fix what breaks, then roll out the rest. The dining rooms keep their POS and their routine.

### Do we have to leave DoorDash and Uber Eats?

No. Most groups keep the delivery apps for reach and move regulars to their own channel, where there's no commission. Orders from both land in the same POS and the same report, through an aggregator such as Deliverect or through direct integrations.

### Should we run in-house delivery or use a courier network?

It depends on how dense your orders are. Courier networks such as DoorDash Drive and Uber Direct charge per delivery and need no fleet. Your own restaurant delivery drivers pay off where orders are dense. Many groups run both and let delivery management software such as Nash pick the courier for each order.

### Should we use a white label delivery app or build our own?

A white label delivery app gets one brand live fast on a vendor's template, and you pay a subscription for it. It gets harder when your brands run on different POS systems, or when you want your own loyalty rules and dispatch. Then your own app on one backend is usually the better fit. We compare both on your numbers in the Assessment.

### How much does it cost, and how long does it take?

Your own app and ordering website start from $100,000. The price and timeline depend on your brands, POS systems and delivery setup, and we fix both in the 2–3 week Assessment. A courier app alone took 2.5 weeks for Sizl.

### Which POS systems do you connect to?

Any POS that shares its menu and takes orders through an API. We check each of your POS systems in the Assessment, before Build starts.

### Do you work with chains in the US and the UK?

Sizl, a dark-kitchen chain in Chicago, is our US project. For a 16-brand restaurant group in Saudi Arabia, Kuwait, the UK and the US, we're launching its own ordering and delivery. Our Lisbon workday matches the UK and overlaps with US mornings.

## You talk to the people who will do the work

We don't have a sales team. On the call you get the founder and the PM who would run your launch.

- Max Bantsevich, Founder
- Andrey Maksimenko, Project Manager

- Headquartered in Lisbon, in the EU: contract and DPA under EU rules
- We sign an NDA before the first call if you need one
- Security pack and data-flow diagram on request
- Our workday matches the UK and overlaps with US mornings
- You own the code, the models and the data

## Launching your own online ordering and delivery?

A call to map your brands, POS systems and delivery setup, and what has to be ready on launch day.

---

Last updated: 2026-11-11
Page: https://dev.family/foodtech/launch-delivery
Contact: https://dev.family/project-evaluation