Solutions · Home & local services
Home services app: what to decide, build and test.
Planning one? Here's what to settle before you brief anyone, what goes in the first version, how the build runs week by week, how the beta is tested with real people, and the numbers that show it's working.
Employees, contractors or open marketplace: choose the pro model first
In a home services business the app follows the people model, not the other way round. The same booking screen hides very different operations behind it.
| Model | How it works | Gain | Cost |
|---|---|---|---|
| Salaried team | You employ and train the pros, and assign jobs | Quality and timing are in your hands | Payroll, idle hours and growth limited by hiring |
| Managed partners | Independent pros work only through you, with your training and prices | Scales with demand, brand stays yours | You still own quality, onboarding, payouts and, increasingly, social security duties |
| Open marketplace | Any verified pro lists and sets a price | Widest supply, least training | Quality varies, customers go direct to pros, hard to protect your brand |
Next, decide how you price: a fixed price per job (customer-friendly), per hour (simple for cleaning) or a quote after a visit (for repairs). TidyBee prices by time block; HomeCraft shows a package price and a locked quote for extras. The home services guide covers the market. Before you brief anyone, settle:
- Which two or three services you launch with, and in which neighbourhoods.
- Whether the pro is your employee, a managed partner or open on the platform.
- Price per job, per hour or by quote, and who approves extras.
- What you promise if the pro is late, does poor work or damages something.
Version 1: the modules that keep the promise at the door
| Module | First version | Add later | Why |
|---|---|---|---|
| Customer booking | Service, address, slot, price shown first, UPI or cash | Subscriptions, society plans, gifting | A clear price and slot is what converts. |
| Pro onboarding | Documents, photo, skills, languages, review status | Training modules with tests, skill badges | Onboarding is how you control quality. |
| Dispatch | Match by skill, area and availability; desk can reassign | Scoring with rating and fairness, auto-dispatch | A human-assisted desk is enough for the first hundreds of jobs. |
| Job flow | Accept, travel, start with OTP, finish with photos | Live location, route planning | Proof of work settles most disputes. |
| Payouts | Per-job earning shown, weekly payout to bank or UPI | Instant payout, incentives, advances | Pros judge you on payout day. |
| Ratings and issues | Rating after job, a one-tap issue, desk follow-up | Warranty claims and rework scheduling | Fix problems quickly before adding policy. |
| Pro app languages | Hindi and one regional language | More languages, voice prompts | Pros read less comfortably in English. |
| Website | Services, prices, a become-a-pro page | Society and corporate pages | The recruitment page feeds your supply. |
How the 8 to 12 weeks run, and what you bring
- Weeks 1–2: choose the services, price list and the areas you serve; prototype of customer and pro flows. You provide: price list with the time each job takes, a map of your launch areas, five or six real pros to react to the prototype.
- Weeks 3–5: customer app, pro app and onboarding. You provide: the documents you will ask pros for, service photos and descriptions, brand assets.
- Weeks 6–8: dispatch desk, job flow with OTP and photos, UPI and cash. You provide: payment gateway account, maps and SMS accounts in your name, a named dispatcher who will use the desk.
- Weeks 9–10: payouts, ratings, reminders and the website. You provide: payout rules in writing, cancellation and refund policy, privacy notice and terms checked by a lawyer.
- Weeks 11–12: a pilot in one neighbourhood with real pros, fixes, store release. You provide: cheap Android phones for testing, a support line, store accounts.
A single service with fixed slots can launch faster; a second or third service category adds rules and testing, so allow time for each.
How we work with you each week
The same rhythm runs from week 1 to launch, so you always know what's happening and what we need from you.
- Friday: a demo link and a 30-minute call. You open the latest build on your own phone and try it yourself, rather than watching our screen.
- Within 48 hours: your feedback, in writing. In one shared doc, next to the screen it's about. Written feedback is clear, dated and doesn't get lost between calls.
- Monday: triage. Every comment goes into fix now, next week or later. Anything that changes the agreed scope gets a written quote before we touch it.
- Each milestone: two revision rounds, then your sign-off. Sign-off is against the scope we agreed, so it's clear what done means.
- One decision-maker on your side. Most delays aren't build time. They're feedback waiting on several people who disagree.
The full version, including how the beta and user testing work across every kind of project, is on our process page.
The beta: one neighbourhood, real jobs, real pros
The pilot is weeks 11–12. It starts once a job can go from booking to dispatch to OTP start, finish photos and a payout line without the desk fixing it by hand. It covers one neighbourhood and the two or three services you launch with.
- What's in it. Booking with the price shown first, slots, UPI and cash, pro onboarding and review, the dispatch desk with reassign, the job flow with OTP and before-and-after photos, extras approved in the app, per-job earnings, ratings and the one-tap issue button.
- What stays out. Subscriptions and society plans, auto-dispatch, live location, instant payouts, warranty claims and extra service categories. They come once the basic job holds up.
- Who uses it. Six to ten of your pros, on their own Android phones; your named dispatcher; and 15–20 households in the neighbourhood who would book these services anyway, such as working couples who book a deep clean or a family with an AC that needs a service before summer. You recruit them. Friends who let a pro in as a favour won't complain about a late arrival or a surprise extra, and those are what the pilot needs to show.
- How they get it. Customers install through TestFlight or Google Play testing. Pros get the Android build, set to Hindi or their regional language. The dispatcher uses the desk on a staging link.
- How long. Two weeks of paid jobs at real prices, with enough bookings that each pro does several. The desk reviews every job each evening, and the feedback button sends a screenshot and a note to a shared sheet.
A new personal Google Play developer account has to run a closed test with at least 12 testers for 14 days before it can publish. Count the pilot pros and households towards that, or use an organisation account.
What we test with real people, and the tasks we set
A session is one realistic job, done on the person's own phone and in their own language, while we watch and keep quiet. Around five people per role brings out the problems that matter. We fix those first, then hand the same tasks to new testers.
| Who | The task | What we watch for |
|---|---|---|
| Customer | "Book a 2BHK deep clean for Saturday morning, and check what's included before you pay." | Do they see the full price and what it covers before choosing a slot? Do they understand what counts as an extra? |
| Customer | "The technician says your split AC needs a gas top-up. Approve or reject the extra charge in the app." | Is the extra shown with a price and a reason? Do they feel pushed, or able to say no? |
| Pro | "Finish your documents and skills, then accept tomorrow's 10 am job and find the flat." | Can they upload Aadhaar and a photo on weak data? Is the address shown only when it should be? Is the Hindi or regional text clear? |
| Pro | "Start the job with the customer's OTP, take before and after photos, and mark it done." | Is it easy with dusty or wet hands? Do the photos upload later if the flat has no signal? |
| Dispatcher | "The plumber for the 11 am leak job has cancelled. Find another pro with the right skill nearby and tell the customer." | How quickly do they find a match? Does the customer get a WhatsApp update without a manual call? |
The numbers that say it's working
In week 1 we pick two or three of these with you. If you take bookings on WhatsApp or by phone now, we note today's figure to compare against. Tracking goes in before the pilot, and we report at launch and again 30 days later. We can't promise the results, but we can make sure you see them clearly.
| Goal | What we measure | Where it comes from |
|---|---|---|
| Pros arrive on time | Arrival time versus booked slot, by pro and by service | Pro app OTP start times |
| The price at the door matches the app | Jobs with an extra, and how many extras were rejected | Job records |
| Jobs are done right the first time | Issues raised and rework visits per 100 jobs | Issue button and desk log |
| Pros keep taking jobs | Pros who did a job in the pilot and are still accepting a month later | Pro app and payout data |
| The desk isn't firefighting | Jobs reassigned by the desk, and why | Dispatch desk |
| Households book again | Customers who book a second job within 60 days | Booking data |
Cost: what pushes a home services app up or down
With customer app, pro app, dispatch desk, live tracking and payments, a home services product sits in the marketplace-with-live-maps-and-payments tier of our app development cost guide: a ballpark of ₹25–60 lakh at small-studio rates. A scheduled-slots business with your own staff and no live map moves closer to the two-user-types-plus-admin tier of ₹10–25 lakh. These are ballparks, not a quote.
- Pushes it up: instant matching with live location, versus booked slots your dispatcher confirms.
- Pushes it up: many service categories, each with its own pricing rules, tools and warranty terms.
- Pushes it up: warranty, damage cover and rework flows, which are small products inside the product.
- Pushes it down: one service in one area, with a human dispatcher and weekly manual payout review.
- Not in the build price: maps, SMS, WhatsApp, payment fees, insurance and hosting.
Rules and habits specific to work done at someone's home
- Social security for platform workers: the Code on Social Security 2020, in force since 21 November 2025, asks aggregators to contribute 1–2% of annual turnover, capped at 5% of what they pay gig and platform workers. Whether a home services platform counts, and from when, is a question for your lawyer.
- State gig-worker laws: Karnataka has its own gig-worker welfare law with a fee on platform payouts, and other states are moving. Keep the payout record clean enough to report per payment.
- Pro verification: customers let strangers into their homes. Decide what you check, how, and what you tell customers; check local police verification practice with your lawyer.
- GST and invoices: tax depends on service type and on whether you act as the supplier or as a platform. Fix this with your CA before you design invoices and payouts.
- Data: addresses, phone numbers, photos of homes and pet or family details are personal data. The DPDP Rules, notified in November 2025, phase in over 18 months, so limit who sees an address and when. See the DPDP checklist.
- Language and contact: pros prefer Hindi or a regional language, and customers expect WhatsApp updates. See regional language apps and WhatsApp for business apps.
This is general information, not legal or tax advice. Labour and platform rules are changing quickly; confirm with a lawyer and a chartered accountant before launch.
Mistakes that hurt home services apps, and what to do instead
- Recruiting customers before pros. Ten reliable pros in one area beat a hundred scattered ones. Start with supply and cover one neighbourhood well.
- Hiding extra charges. A price that rises at the door breaks trust. Show a starting price and require approval in the app for any extra.
- Letting the app decide dispatch alone. Early on a person catches mismatches. Give the desk an override from day one.
- Paying pros late or unclearly. Show each job's earning and the payout day inside the pro app.
- English-only pro app. If pros cannot read it they will phone you. Ship Hindi or a regional language at launch.
- No proof of work. Photos at the start and end settle disputes. Make them part of finishing a job.
- Going wide at launch. Each service adds training, tools and rules. Launch two or three and learn.
Cost and timeline
8–12 weeks for a first version.
Fixed quote within 48 hours of your brief: scope, timeline and price in writing before we start. These are what move the number.
- Number of service categories and pricing rules
- Instant matching versus scheduled slots
- Pro onboarding, training and verification
- Subscriptions, warranties or memberships
- Payout and incentive rules
Questions
About your home services app.
How much does a home services app cost in India?
It depends on the number of services, how jobs are matched and how much the pro app needs to do. We give a fixed quote within 48 hours of your brief. The app cost guide explains each driver. Extra categories can be added later.
Can the pro app work in Hindi and other languages?
Yes. Pros often prefer their own language, so we build the pro app in Hindi or a regional language with English as an option. Our regional language guide covers how we handle it. Job notes from customers can be shown with a translation.
How long does it take?
A customer app, pro app and dispatch desk usually take 8 to 12 weeks. A single-service business with fixed slots can launch faster, or start with a website that takes bookings. We show working screens from the first fortnight, so you can test them with a few pros early.
Will it run on the cheap phones our pros use?
Yes. We test the pro app on low-cost Android phones, keep it light on data and make sure job details stay available when the signal drops. Large buttons and clear icons help pros who read less comfortably on a small screen.
Who owns the app and the data?
You do. The source code, designs, brand system and customer data are yours, and are handed over in full. Pro records, ratings and payout history stay in your accounts, and any developer can carry the product forward after we hand over.
Read next
- ServicesHome services apps: booking, pros and quality control →How to build an Indian home services app: slot booking, upfront pricing, a pro app, dispatch, before-and-after proof, safety tools and ratings that stay fair.
- CostHow much does it cost to build an app in India? →Ballpark app development costs in India for 2026, from a simple app to a multi-sided marketplace — what moves the price, and how to get a quote you can trust.
- LanguagesBuilding apps in Hindi, Tamil, Kannada and other languages →How to build an app or website in Indian languages: scripts and fonts, longer text, voice input, transliteration, lakh and crore formats, and translation that sounds right.
- MessagingWhatsApp and your app: order updates, OTPs and support →How Indian businesses use the WhatsApp Business Platform with their app: approved templates, opt-in, the 24-hour window, OTPs, team inboxes and costs.
Start a project
Tell us how your business runs. We'll build what it runs on.
Four taps, about a minute. Fixed quote within 48 hours.


