How easyLife Started: From a Random Instagram Ad to Building a Local Services Marketplace

Every company has a beginning. Some begin with a business plan. Some begin with funding. Some begin with a problem that founders have spent years trying to solve. easyLife started much more simply.

It started with an Instagram advertisement, a casual conversation with a friend, and one question:

"Why don't you build something like this?"

At the time, I had no idea that this small conversation would eventually turn into a product, a team, a company and a journey that I would become deeply invested in.

This is the story of how easyLife started.

The conversation that started everything

It was November 2025.

A friend of mine was casually scrolling through Instagram when she came across an advertisement for an application that promised to provide a maid within minutes.

She looked at me and said something along the lines of:

"Everyone is creating applications for maids and cleaning. You're a software engineer. Why don't you build something like this?"

I wasn't planning to start a company. I wasn't looking for investors. I wasn't researching startup ideas. I was simply a software engineer who enjoyed building applications.

So I thought:

Why not? Let's build something and see what happens.

My initial mindset was actually quite simple. If the idea worked, maybe it could become a real business. If it didn't, at least I would have built an interesting project that I could put on my resume and learn from.

I didn't realize at the time that this small experiment would become easyLife.

Looking for the gap

The first thing I did was research.

I looked at existing platforms and tried to understand how companies such as Urban Company and Justdial had approached the market.

I wasn't trying to copy them. I wanted to understand what they were doing well and whether there was a gap between their models.

One thing stood out to me.

Urban Company's model focuses heavily on connecting customers with professionals through a managed service experience. Justdial, on the other hand, has historically been strong in business discovery and online visibility.

I started thinking:

What if we could take some of the strongest ideas from both models and build something different?

The idea behind easyLife

The first concept was simple.

Instead of controlling the professional's entire service experience, what if we created an open platform where professionals could register themselves?

A professional could potentially:

• Create their own profile
• List their services
• Set their own pricing
• Describe their experience
• Build an online presence
• Become discoverable by local customers
• Manage their business through the platform

The idea wasn't just to create another service-booking application.

I wanted to build something that could help an independent professional become more visible online.

A photographer shouldn't necessarily need a large marketing budget to be discovered. A repair professional shouldn't need to understand SEO or build their own website just to have an online presence. A salon professional shouldn't have to depend entirely on a large platform to find customers.

That became one of the early principles behind easyLife:

Help local professionals build visibility and connect with customers.

Buying the domain and starting from zero

Once I had the idea, I bought a domain and started working.

Then reality hit.

There were many things I had never done before.

I created an AWS account for the project and started setting up the infrastructure. This was my first serious experience working with AWS from scratch.

For me, that part was actually fun.

I wasn't just writing application code anymore. I was figuring out:

• Infrastructure
• Hosting
• Databases
• Redis
• Domain configuration
• Email
• Deployment
• Security
• Application architecture
• And all the small things that come with running an actual product

The next challenge was cost.

Since easyLife was only an idea at that stage, I didn't want to spend a lot of money before knowing whether the product would even go anywhere.

So I started looking for free or inexpensive options for things like databases, Redis and other infrastructure components. That process itself became a learning experience.

I also created a proper working email for the company. It sounds like a small thing, but when you're building your first product, every small piece feels like progress.

You slowly stop thinking about it as a project and start thinking:

"Maybe this can actually become something."

Designing easyLife with ChatGPT

Another interesting part of the journey was the design process.

At that point, I had the idea in my head, but I didn't have a clear visual identity.

So I started using ChatGPT as a brainstorming partner.

I'd describe what I was thinking and ask questions like:

• What should the homepage look like?
• What colors should we use?
• How should the service cards look?
• What should the navigation look like?
• What kind of layout would make sense?
• What should the user experience feel like?

I generated many ideas. Most of them didn't feel right. Eventually, I found a direction that looked decent enough to start building.

Then came the name.

I explored many names and suggestions. Eventually, one name felt simple, familiar and aligned with what I wanted the product to represent:

easyLife.

The idea was straightforward:

Life made easier by helping people find the right services and professionals.

The logo that became part of the story

For the logo, I wanted something that represented the fundamental idea behind the platform: a professional and a customer connecting with each other.

That's why the original concept included a handshake.

Later, some of my friends suggested changing the logo. But I decided to keep it.

Not because I thought it was perfect. Because for me, the logo represented the original idea behind easyLife.

A connection between two people. A professional offering a service. A customer looking for that service.

That connection is still at the heart of the product.

"This looks like a cheap copy of Urban Company."

Then came one of the first reality checks.

I shared the easyLife idea and the website with some friends. I was expecting feedback like: "This looks great."

Instead, someone told me:

"This is just a cheap copy of Urban Company."

That hurt. But it was also useful.

Because I realized something important. Having a good idea isn't enough. The product needs to communicate its own identity. The design needs to feel unique.

And most importantly, I needed to make it clear why easyLife should exist separately from the platforms that already existed.

That feedback pushed me to take the product more seriously.

Building the first real design team

I created a profile on Internshala and started looking for a UI/UX designer.

That's where I found Jugraj.

We started discussing the product almost every morning. I'd explain what I wanted. He would come back with design ideas. We would discuss them, change them, remove things, add things and repeat the process.

After roughly a month, the design started becoming something I was genuinely happy with.

Now I had something much more valuable than a few AI-generated screens. I had a product design that was being shaped by another person who understood design better than I did.

From one person to a team

Once the design was ready, I needed help building the product.

I went back to Internshala and brought in interns to work on the project.

Shreyansh, Neeraj and Apeksha joined during this phase.

They were hardworking and helped turn many of the ideas in my head into actual product functionality.

The product started taking shape. What had initially been a personal project was slowly becoming a real team effort.

Over time, other people joined as well. Eventually, Shreyansh remained with me through an important part of the journey and continued helping shape the product.

We started adding more than just service discovery. The product began evolving into something that could also provide business-management capabilities for professionals.

That was an important shift. We weren't just building a directory. We were trying to build a platform that could become useful to the professionals themselves.

The moment I realized this could become a company

The biggest change happened when I started discussing easyLife more seriously with a colleague.

I shared what I had built and explained where I wanted to take it. Then I asked him if he would consider joining me as a co-founder.

He agreed.

That changed the way I looked at easyLife. It was no longer simply: "Let's see if this project works."

We started thinking about:

• Team
• Product
• Business model
• Customer acquisition
• Professional onboarding
• Growth
• Operations
• Long-term strategy

We built a new team and decided that it was time to take easyLife into the market.

Our first attempt didn't go the way we expected

We initially thought salons would be a good category to target.

So we went out and spoke to several salons. We expected that if we demonstrated the product and explained the benefits, businesses would be interested.

But the response wasn't what we expected.

And that was one of the hardest lessons of the entire journey.

The problem wasn't necessarily that the product was bad. The problem was trust and marketplace liquidity.

Businesses asked a very reasonable question:

"Why should I join your platform if there are no customers here?"

And suddenly we understood the problem.

Building the platform was one challenge. Getting people to use the platform was another.

The marketplace chicken-and-egg problem

A marketplace has a difficult problem.

Professionals want customers. Customers want professionals.

But customers don't necessarily come to a platform with very few professionals. And professionals don't necessarily join a platform that doesn't have customers.

It's a classic chicken-and-egg problem.

At that point, we had two choices. We could decide that the idea wasn't working. Or we could change our approach.

We chose the second.

Changing our approach

We still believed the underlying idea was strong.

But we realized that we needed to earn trust first.

Instead of expecting businesses to immediately join because of business-management tools, we started thinking more seriously about individual professionals and visibility.

The goal became:

Bring professionals onto the platform → create useful profiles → build service and local content → attract traffic → create customer demand → give professionals a reason to stay.

It was a different approach. And we're still working on it.

easyLife today

easyLife is still early. We don't have everything figured out. There are still many things we need to improve.

There have been plenty of mistakes. There have been decisions that we changed later. There have been ideas that looked great on paper but didn't work in reality.

But that's what building a company actually looks like.

You build. You launch. You listen. You get rejected. You learn. You change. And you build again.

What started as a casual conversation in November 2025 has now become a real product, a real team and a real company journey.

What I've learned so far

If there is one thing this journey has taught me, it is that building the product is only the beginning.

As a software engineer, writing code was the part I was most comfortable with.

But building easyLife forced me to learn things outside pure engineering:

• Product design
• Branding
• Marketing
• SEO
• Customer acquisition
• Hiring
• Team building
• Sales
• Business models
• Infrastructure
• User research
• And most importantly, listening to people

I also learned that criticism can be valuable.

When someone told me easyLife looked like a copy, it initially hurt. But that feedback pushed me to think harder about our identity.

When salons asked why they should join without customers, it initially felt like rejection. But that rejection helped us understand the real marketplace problem.

Every difficult moment gave us another piece of information.

This is only Chapter One

I don't want to present easyLife as a finished success story. It isn't.

We're still building. We're still testing ideas. We're still trying to understand what works best for local professionals and customers. We're still growing.

And that's exactly why I wanted to document this journey.

Maybe one day, we'll look back at this first chapter and remember how small everything was.

The first domain. The first AWS account. The first design. The first logo. The first intern. The first customer conversation. The first rejection. The first co-founder conversation. The first time someone actually used what we built.

All of those small moments are part of the story.

easyLife started with one simple question:

"Why don't you build something?"

So I did. And we're still building.

This is only the beginning of easyLife.