Navigation menu drawer

This is a navigation menu drawer that contains links to browse products, sign in, and sign out.

Back to Posts

How I Got My First Customers for BooklierAI: What Actually Worked

Building a SaaS is exciting.

Getting your first real customer is a completely different feeling.

When I started building BooklierAI.com , I had an idea I genuinely believed could help authors. The goal was simple: make the journey from a book idea to a finished book much easier with AI.

But there was always one question in my mind:

“What if I build it and nobody cares?”

That question changed how I approached the launch.

Instead of spending months building everything before showing it to anyone, I decided to put BooklierAI in front of real people as early as possible.

I didn't start with ads

I didn't have a huge marketing budget, and honestly, I didn't think ads were the right starting point.

I didn't even know exactly which features people would value most.

So I started with something much simpler:

I talked about what I was building.

I shared BooklierAI on X, posted product updates, showed improvements, shared screenshots, and asked people for feedback.

Sometimes the post was as simple as:

“I'm building this. Would you try it and tell me what you think?”

That started conversations.

And those conversations became extremely valuable.

My first customers came through conversations

I initially thought getting customers would look like:

Build → Launch → Traffic → Customers.

It wasn't.

My first users came from people who discovered what I was building, became curious, tested the product, and started conversations with me.

That taught me something important:

People don't buy because you built a product. They buy because they believe it can solve a problem they have.

As a builder, it's easy to focus on features.

Customers care about outcomes.

For BooklierAI, the outcome was much more important than the technology behind it.

Someone doesn't necessarily care which AI model is running behind the scenes.

They care about whether they can turn their idea into a useful book faster and with less frustration.

I asked for feedback before asking for money

One thing that worked surprisingly well was asking people to test BooklierAI.

Instead of immediately saying, “Buy my product,” I would ask:

“Can you test it and give me honest feedback?”

That made the conversation much more natural.

Some people loved certain features.

Others told me what was confusing.

Some suggested features I hadn't even considered.

That feedback directly influenced the product.

I kept improving things like the writing workflow, author-style controls, book covers, mockups, and the overall experience of creating a book.

The product became better because real people were using it.

X became my feedback loop

I also treated X as more than a place to promote BooklierAI.

It became my public feedback loop.

I shared progress.

I talked about what I was learning.

I posted small wins.

I asked questions.

I showed improvements.

I didn't want every post to feel like an advertisement.

I wanted people to follow the journey.

That made a difference because people could see the product evolving over time.

And some of the people who followed the journey eventually became users.

The growth loop

Looking back, my early growth process was pretty simple:

Build → Share → Get feedback → Improve → Share again → Start conversations → Get users

There was no magic growth hack.

It was repetition.

Every time someone gave me feedback, I had another reason to improve the product.

Every improvement gave me something new to share.

And every post created another opportunity to start a conversation.

What I learned

My biggest lesson was that builders can easily spend too much time building things nobody asked for.

It's tempting to keep adding features.

But instead of asking:

“What should I build next?”

I started asking:

“What is stopping the user from getting the result they want?”

That's a much better question.

If I started again, I'd talk to potential customers even earlier.

I'd ask authors what takes the most time, where they struggle, what tools they already use, and what they would actually pay to make easier.

Those conversations can save months of development.

The real lesson

Getting my first customers wasn't about finding a secret SaaS growth hack.

It was much more basic.

I built something, showed it to people, listened, improved it, and repeated the process.

Some people ignored me.

Some weren't interested.

Some feedback wasn't useful.

That's normal.

But every conversation helped me understand the customer better.

And eventually, the questions changed from:

“What are you building?”

to:

“Can I try it?”

and then:

“How much does it cost?”

That transition is one of the most rewarding parts of building a startup.

BooklierAI is still early, and there's a lot more I want to improve.

But if there's one thing I'd tell another indie hacker starting from zero, it's this:

Don't hide in the codebase.

Build something.

Put it in front of people.

Ask questions.

Listen.

Improve.

Repeat.

Your first customers might not be waiting for a perfect product.

They might simply be waiting for someone to solve a problem they already have.

– Mahmudul Rubel

Comments (0)

Trending on SaaSCurate