Demand is easy. Supply is the product.
Anyone can take a booking. The platform earns its margin in matching, travel time, no-shows and payouts — the parts customers never see and professionals feel every day.
- Experienced engineers
- NDA before day one
- You own the code
- Customer + pro apps
Match
Skills, distance, history
Travel
Buffered, not guessed
Payout
Statement a pro can read
Four categories, four different dispatch problems
A 20-minute salon booking and a four-hour AMC call need the same app in different shapes.
A plumber, a two-hour window and a flat nobody can find.
Repairs, cleaning and installations where the job length varies wildly and the address is half the problem.
- Job types with realistic durations
- Address notes and access instructions
- Parts and materials on the invoice
- Reschedule without losing the pro
Six systems behind one booking
Three face customers, three face the people doing the work — and the second three decide whether the first three have anyone to send.
Booking and scheduling
Slots that reflect real job durations, travel time and the professional's own calendar — not an optimistic grid.
- Duration per job type
- Travel buffers between jobs
- Reschedule and cancellation rules
Matching and dispatch
Rules that decide who gets the job: skills, distance, rating, continuity with the customer, and who actually accepted.
- Skill and radius matching
- Broadcast or direct assignment
- Fallback when nobody accepts
The professional's app
A one-handed app for people working between jobs: today's list, navigation, job notes, photos and payment collection.
- Offline job capture
- Navigation handoff
- Before / after photos
Pricing and payments
Base rates, surge or time-of-day rules, materials, discounts and the split between platform and professional.
- Dynamic and package pricing
- Materials and add-ons
- Commission and payout splits
Trust and safety
Verification before the first job and signals afterwards — background checks, document expiry, ratings and complaint handling.
- Document and licence expiry
- Background check workflow
- Complaint and refund flow
Supply operations
The console your ops team lives in: onboarding queues, utilisation, no-shows, zones and the levers to fix a bad morning.
- Onboarding pipeline
- Utilisation and no-show views
- Zone and capacity controls
From a tap to a paid professional
Five stages, each one a status the customer can see and a record your ops team can act on.
Who does what, stage by stage
Professionals leave quietly, and never come back
Marketplaces rarely die of weak demand. They die when the good professionals stop opening the app, and the four things below are usually why.
Onboarding is a funnel, not a form
Documents, verification, training and a first-job checklist, with the drop-off at each step visible to your ops team.
Utilisation decides earnings
Idle time between jobs is what pushes good professionals off a platform, so zoning and slot design matter more than incentives.
Payouts have to be boring
Clear statements, predictable cycles and a dispute path — the fastest way to lose supply is an unexplained deduction.
Ratings need a human
A single bad rating shouldn't end a livelihood; reviews route to a queue with context before any action is taken.
What we instrument
- Onboarding drop-off at each step
- Idle time between accepted jobs
- No-shows by professional and by zone
- Payout disputes and their causes
The services a marketplace leans on
Payments, verification, maps and the channels customers already answer.
Payments
- UPI
- Cards
- Wallets
- Cash on completion
- Payout APIs
Verification
- ID and address checks
- Background screening
- Licence registries
- Liveness
Comms
- SMS
- Push
- Masked calling
Maps
- Google Maps
- Mapbox
- Travel-time estimates
- Geofenced zones
Business
- Invoicing
- GST fields
- Accounting export
- CRM sync
Insight
- Funnel analytics
- Cohorts
- Ops dashboards
- Raw exports
The same four steps, every time
So you always know what happens next, what it costs and when you'll see it working.
Operations review
A free 30-minute call with a senior engineer. We walk a real booking, a real no-show and a real payout.
Fixed-scope proposal
Modules, timeline and cost in writing within 5 business days, including what we would leave out of version one.
Build in the open
Short cycles with a demo every week. You book a job, dispatch it and pay a professional in the real system.
Launch and look after it
We ship, then stay on as the team that already knows your platform — new cities, new services, new rules.
Pick what fits where you are
Fixed-scope build
RecommendedA defined platform with a written scope, timeline and price.
- Best when
- Services, pricing and the payout model are settled.
- You get
- Scope, milestones and a fixed price before work starts.
Dedicated team
Senior engineers as an extension of your team, month to month.
- Best when
- The category and the unit economics are still moving.
- You get
- A named team, weekly demos, re-planning each sprint.
Take over a live marketplace
An existing app reviewed honestly — matching, payouts, app store state — then fixed, extended or rebuilt.
- Best when
- Growth is limited by the software, not demand.
- You get
- A code and data review, a risk list, then fixes in order.
Real clients. Work you can check.
Verified client testimonials will be published after approval from our clients. Until then, here's what we built — and where you can see it live.
No invented reviews or ratings — only clients you can verify.
Questions about service marketplaces
Still unsure? Ask us directly — a senior engineer replies within one business day.
Do we need separate apps for customers and professionals?
Yes, and they should feel different. Customers book occasionally and want choice; professionals use the app all day and want fewer taps, offline capture and clarity about earnings. One codebase, two products.
How does matching actually work?
Rules you control: skills required for the job type, distance and travel time, rating thresholds, continuity with a customer who has booked before, and acceptance behaviour. Jobs can be broadcast to a pool or assigned directly, with a fallback path when nobody accepts.
Can you support both instant and scheduled bookings?
Yes. Instant requests dispatch against who is free now, scheduled bookings hold a slot in a professional's calendar with travel buffers, and both share the same job, pricing and payout logic.
How are payouts and commissions handled?
Commission rules per service, city or professional tier, with statements the professional can read, scheduled payout cycles and a dispute path. Cash-collected jobs reconcile against what was deposited.
What happens when a professional doesn't turn up?
A no-show is a first-class event: the customer is told and offered a reassignment, the job is re-dispatched, and the pattern is recorded against the professional for your ops team to act on.
Can one platform run in several cities with different pricing?
Yes. Cities, zones, service catalogues, pricing and commission are configuration rather than code, so launching the next city is an ops task.
Tell us where your bookings fall apart.
A free 30-minute operations review with a senior engineer — honest advice on build, fix or scale, with no sales pitch.
