How to Build a Service Marketplace App in Nigeria

What a service marketplace app is, and the four business models

A service marketplace app is a two-sided platform where customers request services and independent providers fulfil them, with the platform handling discovery, booking, payment and quality. The business model determines how the platform earns and how much operational responsibility it takes on.

Many Nigerian platforms start productised in one vertical (cleaning, AC, generator servicing, laundry pickup) because fixed prices remove haggling and make the customer experience predictable, then add quote-based jobs (renovation, custom furniture, events) once the provider base is trusted.

The trust problem: vetting providers in Nigeria

Customers will let a stranger into their home only if the platform has done the checking they cannot. In Nigeria, vetting typically combines identity verification, a guarantor, skill evidence and a probation period. A practical vetting pipeline:

1. Identity. Government-issued ID and a live selfie match. NIN or BVN verification services exist through licensed providers; use them lawfully, store the minimum, and comply with the Nigeria Data Protection Act 2023.
2. Guarantor. A named guarantor with verifiable contact details is a widely understood norm and a strong deterrent.
3. Skill evidence. Photos of past work, trade certificates where they exist, and a short practical test or supervised first job for technical trades.
4. Address and area. Confirm where the provider is based; supply must be near demand.
5. Probation. First three to five jobs flagged for follow-up calls and mandatory ratings.
6. Ongoing signals. Rating trends, cancellation rate, response time and dispute history feed a visible trust score.

Vetting is also a cost line. Budget staff time for onboarding calls and physical checks; it is not something the app does on its own.

The leakage problem: keeping jobs on the platform

Leakage is when a customer and provider who met through the app agree to deal directly next time, so the platform loses the commission. Every Nigerian service marketplace faces it, because WhatsApp is one tap away. Leakage cannot be eliminated, but it can be reduced by making the platform more useful than a direct arrangement.

• Mask phone numbers until a job is booked and paid, and route early conversations through in-app chat.
• Protect the payment. Customers pay the platform; the provider is paid after completion. That protection is worth something to both sides.
• Offer a job guarantee (rework or refund on verified complaints) that a direct deal cannot match.
• Make rebooking effortless. One tap to book the same provider again, with the price and history already stored.
• Reward providers for platform volume with better visibility, faster payouts or lower commission tiers.
• Keep commission reasonable. A rate that feels punitive pushes both sides off-platform; model the economics with realistic job values before setting it.

Core features for customers, providers and admins

A service marketplace is three products sharing one backend. The table shows what each role needs in a first version.

Two mechanics deserve care. The completion code (an OTP the customer gives the provider when the job is done) is a simple, widely understood way to trigger payment release. And the job request with photos reduces wasted visits for quote-based work because the provider can see the problem before travelling through traffic.

How to build a service marketplace app: nine steps

The core steps are: choose one vertical and one area, recruit and vet a starting pool of providers, decide the pricing model, test manually, write requirements for three roles, build the backend and admin tools, build the provider and customer apps, launch in the chosen area and manage liquidity by hand until the numbers work.

1. Choose one vertical and one area. Home cleaning in Lekki–Ajah, AC servicing in Wuse and Maitama, or generator repair in GRA Port Harcourt. Density beats breadth.
2. Recruit and vet the first providers. Twenty to fifty vetted providers in the chosen area is a realistic starting pool for one vertical.
3. Decide the pricing model. Productised prices where the job is standard; quotes where it is not. Set commission after modelling typical job values.
4. Test the model manually. A WhatsApp number, a Google Form and a payment link can process the first jobs and reveal what customers and providers actually argue about. The guide to testing an app idea before spending millions describes this approach.
5. Write requirements for three roles. The provider app is usually the most neglected; it must be simple enough for a technician with a mid-range Android phone and limited data.
6. Build the backend and admin dashboard. Vetting, jobs, payments with holds and releases, disputes and reporting. Multi-role permissions are central; the guide to building a mobile app with multiple user roles is relevant.
7. Build the provider app, then the customer app. Supply tools first so providers are onboarded and trained before customers arrive.
8. Launch in the chosen area only. Advertise locally, fill provider calendars, and call every customer after the first job.
9. Manage liquidity manually. In the early months, staff will match jobs, chase providers and settle disputes by phone. That is normal; automate what repeats.

What changes for a Nigerian service marketplace

For a Nigerian service marketplace, the local factors that shape the product are guarantor-based trust, cash habits, area density and traffic, provider phone and data limits, haggling culture, safety for home visits, payment-holding rules and data protection.

• Guarantors and physical checks carry more weight than online badges. Build them into onboarding rather than treating vetting as a form.
• Cash still happens. Some customers will want to pay the provider directly on completion. Decide whether to allow it with a recorded commission owed, or to insist on in-app payment; mixed models create reconciliation problems.
• Area density and traffic define the service radius. A plumber in Ikorodu is not available to Victoria Island at short notice, whatever the map says. Model service areas by axis, not by city.
• Provider devices and data. The provider app must be light, work on older Android versions, and function with intermittent connectivity; consider SMS or WhatsApp notifications as a fallback for job alerts.
• Haggling and quotes. Where prices are negotiated by custom, let providers quote within the app with a clear breakdown, and let customers compare two or three quotes.
• Home-visit safety for both sides: verified identities, shared job details, arrival confirmation and an easy way to report problems.
• Holding customer money. Collecting payment and releasing it later touches payment regulation. Use a licensed payment provider's features (for example split payments or sub-accounts) rather than building your own escrow, and take advice on current Central Bank of Nigeria requirements before launch.
• Personal data. IDs, addresses, guarantor details and job photos are personal data under the NDPA 2023. Store the minimum, restrict staff access, and publish a privacy notice; verify obligations with the Nigeria Data Protection Commission.

Example (hypothetical): a home-repair marketplace on the Lekki–Ajah axis

Example (hypothetical): a founder plans a home-services marketplace for plumbing, electrical and AC work along the Lekki–Ajah corridor, where estates are dense and residents complain about unreliable artisans. Before development, she recruits 35 artisans through estate facility managers, vets each with ID, guarantor and a supervised first job, and processes 60 jobs over six weeks through a WhatsApp line and payment links. That manual phase shows that most requests are standard (tap replacement, socket faults, AC servicing) and can be productised, while about a fifth need quotes. Version one scope: a customer app with fixed-price menus and photo-based quote requests for the rest, a provider app with job feed, quotes, status updates and a completion code, in-app chat with masked numbers, payment held with the gateway and released on completion, a dispute flow and an admin dashboard for vetting, jobs and payouts. Excluded: wallets, provider insurance, iOS and any expansion beyond the corridor. Success metrics: jobs completed per week, share of customers rebooking within 60 days, dispute rate and an estimate of leakage from cancelled-then-completed patterns. This illustrates a sensible sequence; it is not a client outcome.

How much does a service marketplace app cost in Nigeria?

For a Nigerian service marketplace app, the main cost drivers are the three-role architecture, payment holds and payouts, in-app chat, location features, the dispute and vetting tools, and whether iOS is included at launch. The figures below are indicative 2026 ranges; actual quotes vary with scope, vendor and exchange rate. Compare two or three written quotations on identical scope.

Recurring costs:

• Cloud hosting: roughly ₦150,000–₦800,000+ per year, growing with usage.
• Payment gateway fees per transaction and any charges for split payments or payouts.
• Identity verification checks per provider, billed by the verification provider.
• Maps and location services, SMS and WhatsApp messages, typically in USD or per message.
• Operations staff for vetting, matching and disputes, which usually exceeds software costs in year one.
• Maintenance: typically 15–25% of the build cost per year.

Mistakes to avoid

• Launching nationwide. Sparse supply in many cities is worse than deep supply in one axis. Customers who cannot find a provider do not come back.
• Building both apps before recruiting providers. An empty marketplace cannot be fixed by features.
• Free-text jobs without pricing structure. "Describe your problem" leads to haggling, wasted visits and disputes. Productise what you can.
• Exposing phone numbers early. It turns the platform into a one-time introduction service.
• Skipping vetting to grow supply quickly. One theft or botched job in an estate WhatsApp group can end the platform's reputation in that area.
• No dispute process. Disputes will happen; without evidence rules and a decision process, staff improvise and both sides feel cheated.
• Ignoring the provider experience. Confusing job alerts, slow payouts and heavy apps drive good artisans back to word of mouth.
• Underestimating operations. The app is perhaps a third of the work; matching, quality and support are the rest.

Conclusion

A service marketplace app in Nigeria is an operations business with software attached. Choose one vertical and one area, recruit and vet providers before building, productise what can be priced, protect payments through a licensed provider, mask contacts to slow leakage and design the dispute process before the first complaint. Build the provider tools before the customer app, launch locally and expect staff to manage liquidity by hand for months. Budget indicatively ₦5,000,000–₦15,000,000 for a multi-role MVP and ₦15,000,000–₦50,000,000+ for a full platform, and judge success by repeat bookings and dispute rate. If you are planning a service marketplace and want a first version that reflects how artisans, customers and payments actually behave in Nigeria, Linestech can help you scope the three-role architecture, payment flows and admin tooling and give you an indicative budget for your vertical.

Frequently asked questions

Can we start a service marketplace with WhatsApp before building an app?

Yes, and it is usually wise. A WhatsApp line, a request form and payment links can process the first jobs, prove that customers will pay through you and show which services can be priced as fixed menus. The app is then built around real patterns rather than assumptions.

How do we stop customers and artisans dealing directly after the first job?

Mask phone numbers until a job is paid, hold payment until completion, offer a rework or refund guarantee, make rebooking a single tap, and keep commission at a level both sides accept. Leakage will still exist; the aim is to make the platform worth more than the saving.

Do we need a licence to hold customer payments until the job is done?

Holding money on behalf of others may fall within payment-service regulation. The usual approach is to use a licensed payment provider's hold, split-payment or sub-account features rather than operating your own escrow. Take advice on current Central Bank of Nigeria requirements before launch; this article is not legal advice.

Should providers or customers pay the platform fee?

Most Nigerian service marketplaces take a commission from the provider's side of each paid job, sometimes with a small customer booking fee. Charging providers subscriptions before they earn tends to drive good artisans away. Model the economics on realistic job values before deciding.

How do we verify artisans without slowing onboarding?

Automate the parts that can be automated (ID checks through a verification service, document uploads, address capture) and reserve human effort for guarantor calls and supervised first jobs. A clear checklist and a target onboarding time keep the queue moving.

How many providers do we need before launch?

Enough to fill demand in the chosen area with acceptable response times, typically twenty to fifty vetted providers for one vertical in one axis. Supply density matters more than the total count.

Do we need real-time provider location tracking?

Not at launch. Status updates ("on the way", "arrived") with a timestamp cover most needs. Live location tracking adds battery, data and privacy considerations and is best added when customers ask for it; the guide to building an app with GPS tracking explains what is involved.

Sources and further reading

Figures, platform rules and regulations change. These are the primary references behind this article and the places to check before you act on it.

• Nigeria Data Protection Commission (NDPC)
• Central Bank of Nigeria (CBN)
• Baymard Institute e-commerce UX research