Does it need live location tracking?

Only if it truly helps your service. Tracking adds cost and complexity, so we include it where it builds trust and skip it where status updates are enough.

How are payments split between providers and us?

Through a payment provider that supports marketplace payouts. We agree commission and refund rules with you, then implement them within that provider's terms.

On-demand style apps

Apps built around bookings, orders, or service requests, scoped to what your specific business needs rather than a generic template.

In depth

What on-demand style apps really involves

On-demand apps connect someone who wants something with someone who can provide it, at a time that works for both. Home services, appointments, deliveries, rentals, consultations. Easy to describe, surprisingly fiddly to build, because every booking involves two or three parties whose needs have to be matched in real time.

There's usually more than one app inside it. A customer side for browsing, booking and paying. A provider side for accepting jobs and setting availability. And an admin side for pricing rules, disputes and reports. Underneath sit scheduling logic, status tracking, notifications and payment splitting. Skip any of these and your team ends up coordinating by phone, a job that grows with every booking.

We lean hard towards starting narrow: one city, one service type, a small group of providers. Matching quality and day-to-day operations matter more than feature count, and you'll learn which rules your marketplace actually needs by running real bookings. The foundation is built so more services and areas can be added later without a rewrite.

Why it matters

How this helps your business grow

Lets customers request or book what you offer without a phone call or WhatsApp message

Reduces missed bookings and back-and-forth scheduling

Gives you a record of requests and orders in one place instead of scattered across channels

What's included

What we set up for you

Scoping of the actual request/booking flow your business needs, no assumed niche template

Real-time status updates for requests, bookings, or orders

Notification flows so customers and staff both know what's happening

Admin tools to manage requests without needing a developer involved

How it goes

How we approach on-demand style apps

Map each role's journey

Customer, provider and admin are mapped separately, including cancellations, no-shows, reschedules and disputes. Those are the cases that make or break these products.

Define matching and scheduling rules

How bookings are assigned, how availability works, and what happens when nobody accepts. Clear rules prevent operational chaos.

Build the smallest working loop

Request, accept, perform, pay, review. Surge pricing and loyalty schemes wait until that loop works.

Pilot in a small area

A limited launch exposes real operational problems with few customers affected, so rules and screens get fixed before you expand.

Ideal for

Who this fits

Service businesses that currently take bookings by phone or WhatsApp

Businesses wanting to formalize an order or request process

Watch out for

Common mistakes, and how we avoid them

Building only the customer app

If providers and admins lack proper tools, your team ends up on the phone all day. We scope all three sides.

Launching wide with thin supply

Customers who can't get a booking rarely come back. We suggest starting where you can reliably serve demand.

Vague payment and payout rules

Commission, refunds and payout timing must be decided before code. We write them down first.

FAQ · 05