The launch that dragged on
You decide to try a new brand: loaded chicken tenders, using the chicken and fries you already have. The idea takes an afternoon. The launch takes much longer. You create the brand on each app, which involves separate applications and checks. You write a menu, adapt it to each app's structure, upload photos in the sizes each one wants, write descriptions, set hours, prep times and delivery settings, and then connect the new listings to the kitchen's tablets or aggregator.
Then you find the modifiers are set up differently on one app, a photo was rejected on another, and the new items do not print properly in the kitchen because nobody mapped them to stations. The brand goes live on two apps and a week later on the third.
Why every launch starts from scratch
Each brand is set up by hand on each app, and the knowledge of how to do it lives with whoever did the last one. There is no template: no standard list of what a listing needs, no reusable menu structure, no checklist. So each launch repeats the same mistakes.
The kitchen side is also forgotten until the end. A new brand is mostly existing kitchen products with new names, sauces and packaging, but unless those are mapped to stations and ingredients, the new brand's orders arrive as unfamiliar tickets and bypass stock tracking.
What a slow, manual launch costs
| Problem | Effect |
|---|---|
| Menus built by hand per app | Inconsistent items, prices and modifiers |
| No launch checklist | Missing photos, hours or settings found after going live |
| Kitchen mapping left late | Confusing tickets and stock not tracked |
| Staggered go-live across apps | Early data from one app misleads the decision |
| No baseline to judge success | A brand kept or dropped on feel |
Virtual brands are meant to be cheap to test. When each launch takes weeks of admin, you test fewer ideas and hang on to weak ones longer because relaunching feels expensive.
A repeatable brand launch
- New brands are built in your master menu as a template: brand name, logo, description, hours, prep times and delivery settings in one place.
- Menu items are created by choosing existing kitchen products and adding the brand's name, sauce, build and price, so station mapping and ingredient use are inherited automatically.
- The tool checks each item against each app's requirements, such as photo sizes, description lengths and modifier rules, before publishing.
- Once the brand's listings are approved on each app, the menu is published to all of them through their menu interfaces or an aggregation service.
- A launch checklist tracks each step per app, from account approval to first live order, with owners and dates, so nothing is left to memory.
- From launch day, the brand's orders, ratings and margin appear on the same reports as your existing brands, with a view that compares its first weeks against how your other brands started.
Account creation and approval on each app still follow the app's own process, which we cannot speed up. We make everything on your side ready and consistent.
The next launch
You build the tenders brand in an afternoon, reusing the chicken, fries and sauces already in the system. The tool flags that two photos are too small for one app. You fix them. When the listings are approved, you publish to all three apps on the same day. The first order prints on the fryer station with the new brand name and the right packaging note.
- New brands built from existing kitchen products
- Menus checked against each app's rules before publishing
- A launch checklist nobody has to remember
- Every new brand measured from its first day
Does a new brand take you weeks?
- Each new virtual brand is set up by hand on every app.
- Brands go live on different apps at different times.
- New items print badly in the kitchen at first.
- Only one person knows how to set up a brand.
- You judge new brands on feel rather than numbers.