90 days ago, PostDrop had zero users.
Today, more than 350 people have used it.
350 isn't a huge number compared to the massive SaaS companies we see every day, but for me, it represents something much more meaningful: 350+ people discovered something I built and decided it was useful enough to use.
Why I Built PostDrop
PostDrop started with a simple problem. I noticed how unnecessarily complicated it can be to add a form backend to a website. You can build a beautiful website with HTML, React, Next.js, or any other frontend stack, but the moment you need to handle a contact form, you suddenly need backend logic, email delivery, spam protection, domain validation, and infrastructure.
I wanted to make that simpler.
So I built PostDrop, a headless form backend that lets developers handle website form submissions without building the backend themselves.
The first version was small. I built the backend, dashboard, form integration, spam protection and everything else I needed to get the product working. At that point, I was mostly focused on code.
Then I Launched It
Nobody knew it existed.
That's when I realized that building a product and getting people to use it are two completely different things.
I started working on SEO and documentation, writing content, sharing the product with developer communities, experimenting with Product Hunt and Indie Hackers, and reaching out to people directly.
A lot of it didn't work.
Some posts got almost no attention. Messages went unanswered. There were days when I would check the analytics and see almost no movement.
Honestly, that was harder than debugging code.
When your code breaks, you can usually find the problem. When nobody uses your product, you don't always know why.
Is the product not useful? Is the website unclear? Am I reaching the wrong people? Is the problem too small?
You just have to keep experimenting.
## Building a SaaS Is More Than Writing Code
There were technical problems too. Email delivery, deployment, DNS, authentication, payments and all the other things that become your responsibility when you're running a real SaaS. Things that seem simple from the outside can take hours to get right.
But slowly, people started using it.
The first few users felt incredibly different from simply seeing the product work locally. These were people I didn't know, finding something I had built and trusting it enough to use it.
Then came 50 users , then 100 , eventually 350+ users .
The biggest lesson I've learned isn't really about getting users. It's that building a SaaS teaches you much more than programming. You learn that users don't care how elegant your code is. They care whether the product solves their problem.
You learn that marketing isn't something you do after building. Distribution is part of building.
And you learn to keep working even when nobody is paying attention.
## What's Next?
I'm still far from where I want PostDrop to be. There are plenty of things I want to improve, and I know the next 350 users will probably be harder to get than the first 350.
But that's what makes it exciting.
90 days ago, PostDrop was just an idea with zero users.
Today, 350+ people have used it.
And now I'm curious to see what happens with the next 350.
If you're building something right now and you're stuck at zero users, don't assume that zero means you're failing.
Every product starts there.
Build it. Put it in front of people. Listen. Improve. Repeat.
That's what I'm doing with PostDrop, and this is only the beginning.
Top comments (0)