Skip to content

Five days from phone orders to apps in review

What a launch actually involves, in the order it happens — including the parts that are slow, the parts that are outside anyone's control, and what the platform will not do for you.

This is an illustrative example, not a customer story. Hela Fresh is invented. We are a new product and have no launches to point at yet, and a case study about a company that does not exist would be worth less than saying so. Every capability, price and timeline below is real and verifiable elsewhere on this site — only the shop is made up.

The situation

Four shops, two vans, and a phone that never stops

Hela Fresh runs four grocery shops in and around Colombo. Delivery already works: customers call or message, someone writes the order on a pad, and one of two vans takes it out that afternoon.

It works until it does not. Nobody can tell a customer where their order is without phoning the driver. Stock is whatever the person answering the phone remembers. Two people taking orders at once sell the same last crate of mangoes twice. The busiest hours are the ones where the system is a notepad.

They do not want a marketplace that takes a cut of every order and owns the customer. They want their own app, with their own name on it.

Day by day

The order below is the order it happens in. Most of week one is decisions, not development — the software already exists.

  1. Day 1

    The call, and the catalogue

    We go through what Hela Fresh sells, where they deliver, what they charge for it and how they want it to look. Nothing is built yet. The point of this call is to find the things that will not fit — a tax rule, a delivery exception, an existing POS — while changing them is still free.

  2. Day 2

    Branding and backend

    Their colours, name and logo are applied across the apps and the web shop, and a cloud project is set up for Hela Fresh alone. We host it as part of the plan; the data in it is theirs.

  3. Day 3

    Catalogue, zones and slots

    Products, categories and prices go in. Delivery areas are drawn on a map rather than typed as postcodes, because their vans do not think in postcodes. Delivery windows are set per day, with capacity per window.

  4. Day 4

    A real order, on a real phone

    Someone at Hela Fresh places an order on the customer app, a driver picks it up in the driver app, and it moves through the admin panel in front of them. This is where the questions that matter actually get asked.

  5. Day 5

    Web shop live, apps submitted

    The web shop can go live straight away, since no store has to approve it. Builds go to Apple and Google under Hela Fresh's own developer accounts, so the listings belong to them. Review takes one to three days per store and is outside anyone's control, including ours.

One order, three places

The same order as the customer sees it, as the driver works it, and as the shop watches it. Real captures, with names and addresses blurred.

Your store in one app —

Step 1 of 3

The customer

Picks a delivery window, pins an address on a map, and pays cash on delivery. The total is worked out on the server, so a tampered app cannot talk itself into a discount.

1 / 3

5 days

Brand to submitted build

excluding store review

$119

Per month on Launch

billed annually, in USD

4 apps

Customer, web shop, driver, admin

one deployment

$0

Extra for hosting

included in the plan

Honestly

What this would not fix

If any of these is the thing standing between you and launching, we would rather say so on the call than after the invoice.

Card payments on day one

Cash on delivery works from the first order. The payment gateway included in the plan is integrated during setup, and which gateways exist depends on the market.

App store review

One to three days per store, and occasionally a rejection that needs answering. Neither of us controls it, and no plan makes it faster.

Customers who want to phone

An app does not stop anybody ringing. Hela Fresh would run both for a while, and the admin panel is where the phone orders get typed in.

Your cloud bill

It goes to your own account, not through us. We do not mark it up and we cannot cap it — it is yours, which is the same reason your data is.

Deciding what to sell

Catalogue, pricing, margins and delivery charges are yours. The software will do whatever you configure, including things that lose money.

Tell us about your shops

We will walk the same five days against your catalogue, your markets and your delivery model — and tell you where it does not fit.

We reply to every enquiry within one business day.