On-demand app development for service businesses and marketplaces
On-demand app development is the build of a service platform where a customer asks for help now or at a chosen time, and the right provider is matched, sent and paid. We build the customer app, the provider app and the operations console behind them, with split payments and the EU platform rules designed in from the first version. If you are comparing on demand app development companies, the difference to look for is simple: the rules of your business in the code, not a generic clone script, and the code in your company's own account.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
Who we build on-demand apps for
On-demand is a pattern, not a single industry. We build for three kinds of owner. The first is a service company with its own staff, such as a cleaning, repair, care or installation business, that wants customers to book and track visits in an app instead of by email. The second is a marketplace that connects customers with independent providers, such as tradespeople, beauty professionals, tutors or dog walkers. The third is a business-to-business platform where companies order staff, equipment or services on short notice. Each model has different rules about who sets the price, who is responsible for the work and which laws apply, so the first workshop settles the model before any screen is drawn.
| Model | Who does the work | Who sets the price | What it changes in the build |
|---|---|---|---|
| Own staff, booked in an app | Your employees | You | Scheduling and routes matter most; payments are simple |
| Marketplace of independent providers | Independent businesses or individuals | The provider, or you within rules | Provider onboarding, split payouts, trader and tax reporting duties |
| Managed marketplace | Individuals whose work the platform organises | The platform | Platform Work Directive rules on automated decisions and human review |
| Business to business on demand | Suppliers or agencies | Contract prices | Approvals, purchase orders, invoicing instead of card payments |
What we build
- Customer app. Browse services, see availability and a clear price before booking, book now or later, track the provider, pay, rate and rebook in two taps.
- Provider app. Accept or decline jobs, see the address, the tasks and the customer's notes, navigate, mark arrival and completion, add photos, and see earnings and payouts.
- Operations console. Every job, provider and payment in one view, with manual reassignment, refunds, dispute handling, provider approval and service area settings.
- Matching engine. Your rules for who gets which job: distance, skills, certificates, availability, rating, fairness of job distribution and travel time.
- Messaging and notifications. In-app chat between customer and provider without sharing private numbers, and push notifications for every status change.
- Admin and reporting. Bookings, completion rates, cancellation reasons, provider supply by area and hour, and payouts, exportable to your accounting.
Matching, time slots and live status
The core of every on-demand platform is the moment a request meets a provider. Instant services, like a ride or an urgent repair, need fast matching on distance and availability, with a fallback when nobody accepts. Scheduled services, like a weekly cleaning, need a calendar of slots that only shows times a qualified provider can actually reach. Most platforms need both. We write the matching rules down with you: how far a provider may travel, how long an offer stays open, who is offered the job next, how repeat customers keep their favourite provider, and when a person in your team steps in.
After matching, the customer sees live status: accepted, on the way with an arrival estimate, arrived, finished. Cancellations and no-shows have written rules on both sides, shown before booking, so a fee never comes as a surprise. Location is collected from the provider only while a job is active, which keeps both the store review and the data protection work simple.
Payments, commissions and payouts
A marketplace handles money that belongs to someone else, which is why we build payments on a provider designed for platforms, such as Stripe Connect, Adyen for Platforms or Mangopay, rather than routing funds through your own bank account. The customer's card is authorised at booking and charged on completion, tips and extras are added before capture, the provider's share is paid to their verified account on a schedule, and your commission and any fees are recorded per job. Refunds and disputes run through the console with a reason code, so the numbers match your accounting at month end.
The app stores have clear rules here. Apple's App Review Guidelines state in 3.1.3(e): "If your app enables people to purchase physical goods or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase to collect those payments, such as Apple Pay or traditional credit card entry." Google Play applies the same principle to physical services. Digital extras sold inside the app, such as a premium subscription, follow the in-app purchase rules instead (App Review Guidelines, read 11 November 2026).
EU rules that shape an on-demand platform
Three pieces of EU law decide much of the design. We do not give legal advice; we build what your legal adviser confirms, and the list below is where that conversation starts.
- Digital Services Act, trader traceability. Article 30 of Regulation (EU) 2022/2065 requires online platforms that let consumers conclude distance contracts with traders to collect, before a trader may offer services, the trader's name, address, telephone number and email address, an identification document, payment account details, trade register details where registered, and a self-certification that the trader only offers services that comply with EU law. Article 29 excludes platforms that qualify as micro or small enterprises. Provider onboarding in the app collects and checks exactly this list.
- DAC7 tax reporting. Under Council Directive (EU) 2021/514, in force since 1 January 2023, platform operators report information on sellers of four activities: rental of immovable property, personal services, sale of goods and rental of any mode of transport. The European Commission states that reports are due no later than 31 January of the year following the calendar year of the activity. The platform keeps per-seller totals and identifiers ready for that report.
- Platform Work Directive. Directive (EU) 2024/2831 must be applied by Member States from 2 December 2026. It presumes an employment relationship where the platform directs and controls the work, forbids processing data such as a worker's emotional state or private conversations (Article 7), and requires that decisions to restrict, suspend or terminate a worker's account are taken by a human being (Article 10). Workers can ask for a review and must get a substantiated written reply within two weeks (Article 11). Matching and rating logic is therefore logged and explainable, and account actions go through a person in the console.
(All three sources read on 11 November 2026.) Outside the EU, the same design choices, such as human review of account actions and clear seller records, make the platform easier to adapt to local rules.
Trust and safety
An on-demand service sends a stranger to a customer's home or a customer to a stranger's door, so trust is a feature, not a policy page. Providers are verified before their first job, with identity checks through the payment provider and certificates or licences where the service needs them. Ratings go both ways and are collected only after a completed job. Customers and providers message inside the app, private contact details stay hidden, and an incident button reaches your team with the job details attached. The console shows patterns that need a person's attention, such as repeated cancellations or complaints, and a person decides what happens next.
Start narrow: one service, one area
Most marketplaces fail on supply, not software: customers open the app, see no provider nearby and do not come back. The build follows the launch plan. The first version covers one service in one area, with enough providers signed up before launch that customers get a fast answer. The operations console makes manual work possible at the start, such as assigning jobs by hand, so you learn the real rules before automating them. Each later phase adds a service, an area or an automation, once the numbers from the previous phase are in. For the wider product approach, see software development for startups.
Clone script or your own platform?
Ready-made on-demand scripts, often sold as an "Uber for X" clone, promise a marketplace in days. For a quick test of demand they can be enough. The cost shows up later.
| Question | Clone script | Your own platform |
|---|---|---|
| Matching and pricing rules | The script's defaults, changed by settings | Your rules, written and tested |
| Payouts and commissions | The payment flow the script supports | Built on a marketplace payment provider you choose |
| EU duties: DSA, DAC7, platform work | Rarely covered, added by hand | Designed into onboarding, records and the console |
| Store review | Template apps are a known rejection risk | Apps built and submitted for your brand |
| Code ownership and changes | A licence, often with limited source access | Your repository, your accounts |
How we build it
- Model workshop. Who does the work, who sets the price, how matching and payouts work, which rules apply. Written down for your approval.
- Scope and fixed price in writing. The first service, area and apps, what is manual at launch and what this phase leaves out.
- Design and clickable prototype. Customer, provider and console flows, tested with real providers before code.
- Build in short rounds. You install each test build on your own phone through TestFlight and the Android test track.
- Launch with real supply. Store submission under your company's accounts, providers onboarded, the console in use from day one.
- Measure and extend. Time to match, completion and cancellation rates, and repeat bookings decide the next phase.
You own it
As a standard term, the source code sits in a repository in your company's own account, and the apps, database, hosting and payment provider accounts are in your company's name. Hosting runs in an EU data region, and personal data is processed under a written data processing agreement. You can keep us for maintenance, run it yourself or hand it to another team.
For a single vertical, see taxi app development and our guide to food delivery app development. If the platform sells physical goods, see e-commerce app development; for wallets and money movement, fintech app development. For booking and visit planning behind a service business, see field service management software. For the build approach, see mobile app development and cross-platform app development. See prices.
Questions we get
What is an on-demand app?
An app where a customer asks for a service, such as cleaning, repairs, beauty, laundry, delivery or a ride, and a provider is matched to it now or at a chosen time. It usually has three parts: a customer app, a provider app and an operations console where your team sees every job, provider and payment.
Do we need our own app or is a white-label script enough?
A white-label script can be a quick way to test demand in one city. It becomes a problem when your matching rules, prices, payouts or legal duties differ from what the script assumes, or when you need to own the code. We build your own platform, starting with the smallest version that proves the model.
Can customers pay in the app without Apple or Google taking a commission?
For services used outside the app, yes. Apple's guideline 3.1.3(e) says purchases of physical goods or services consumed outside the app must use payment methods other than in-app purchase, such as Apple Pay or card entry, and Google Play has a similar rule. Digital extras sold inside the app are different and follow the in-app purchase rules.
How do provider payouts work?
Through a payment provider built for marketplaces, such as Stripe Connect, Adyen for Platforms or Mangopay. The customer pays once, the provider's share is paid out to their verified account, and your commission stays with you. The payment provider handles the licensed part, including identity checks on providers.
Which EU rules apply to an on-demand platform?
It depends on the model. A marketplace where independent traders sell to consumers has trader traceability duties under the Digital Services Act, platforms with sellers report their income under DAC7, and platforms that organise work done by individuals fall under the Platform Work Directive, which Member States apply from 2 December 2026. We design for the rules your legal adviser confirms.
Who owns the platform?
Your company. The source code sits in a repository in your own account, and the apps, database, hosting and payment provider accounts are in your company's name. You can keep us for maintenance, run it yourself or hand it to another team.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.