I built a service marketplace while being the developer, product manager, marketer and salesperson.

I started this project as a developer.

But somewhere along the way, I realized that building the product was only one small part of the job.

I ended up doing development, product management, marketing, sales, customer discovery, operations and even figuring out the business model myself.

I'm sharing the journey through the product I've built because there has been a lot to learn , especially from failures.

It started with a client asking for an app

A client asked me to build an app for a service marketplace.

I delivered the app.

But then came the obvious problem:

How do you get people to actually use it?

The client had almost no marketing budget, so I started running Meta Ads myself.

I already had some knowledge and experience with Meta Ads, but the first results weren't particularly good.

I was spending money and learning the hard way that knowing how to run an ad isn't the same as knowing who exactly should see it and why they should respond.

Instead of treating those failures as someone else's problem, I included them in my own learning budget.

Eventually, I started getting clients for the platform with roughly ₹5,000 in Meta Ads spend, including the money spent learning what didn't work.

Then I moved to a metro city

The client didn't have an office.

I realized that trust and accessibility were becoming a problem, particularly when dealing with businesses.

So I moved to a metro city myself.

Being physically closer to potential customers made meetings easier, and conversions improved.

But then another problem appeared.

Clients started delaying payments.

And at the same time, there was pressure to offer services cheaper.

So now I had:

Lower prices + delayed payments + inconsistent conversion.

The software wasn't necessarily the biggest problem anymore.

The business workflow was.

So I changed the product

I introduced a proper agreement system & Termination notice system and started redesigning the way the marketplace handled transactions.

But another realization came from looking at the actual users.

The app wasn't necessarily the best B2B entry point.

Businesses were often more comfortable working through websites and desktops.

So instead of forcing everything through the mobile application:

We launched the website.

That immediately made the platform more practical for B2B usage.

Then we changed how people connect

Originally, the basic marketplace model was:

Find service → book service.

But that doesn't always work for professional services.

Businesses often want to:

Discuss → negotiate → understand scope → then book.

So I introduced a negotiation system before booking.

The idea was similar to:

Enter your phone number to unlock contact access.

Once unlocked, the client could connect with the service provider and negotiate before committing to the service.

It solved a surprisingly important problem:

People weren't necessarily refusing to buy. They wanted to talk first.

Then inbound leads changed the equation

We also started looking at inbound leads differently.

If a potential customer comes through the platform and multiple relevant service partners are connected to that opportunity, the platform naturally becomes the place where the transaction happens.

So instead of constantly asking:

"How do I get every partner to find their own customer?"

the platform could create the opportunity centrally.

That made the marketplace more valuable to the partners.

But then came the chicken-and-egg problem

The platform still had difficulty onboarding service partners.

The typical response was:

"Why should I join if there aren't any leads?"

And honestly, that's a fair question.

A marketplace needs both sides.

Customers want providers.

Providers want customers.

So I experimented with another model:

Franchise Partners

Instead of requiring every franchise partner to personally specialize in every service, the partner can act as a sales/negotiation representative across the service categories available on the platform.

They can start from their own specialization and potentially earn commission across other services as well.

That creates an interesting equation:

Fewer active partners → broader service coverage → more opportunities per partner.

It also reduces the pressure on the platform to continuously recruit hundreds of specialists before the marketplace can function properly.

Now I'm going back to marketing — but differently

I'm preparing to run Meta Ads again.

But this time, the product and the strategy are completely different.

Legal services

I've designed a package containing a substantial set of free/low-cost business services, including a free website component, to make the initial proposition easier to understand.

Software services

The approach is different again:

Free demo

Free proposal

Portfolio/case studies

Metro-city presence for easier meetings

Direct consultation

More emphasis on understanding the business before selling development

The objective isn't simply:

"Buy software."

It's:

"Let's understand what you actually need, show you something relevant, and then decide whether development makes sense."

Looking back

The funny thing is that I started this project thinking:

"I'm going to build an app."

What I actually ended up building was a lesson in:

Development → Product → Marketing → Sales → Operations → Trust → Payments → Marketplace economics → Customer behaviour.

Every problem forced another product decision.

And almost every failed experiment taught me more than the successful ones.

I'm still building it.

I'm still changing things.

And I'm still learning.

So I'm sharing the journey through the product itself rather than pretending I had everything figured out from the beginning.

For developers who have started building products themselves:

What's one business/product lesson you learned only after something you built failed in the real world?