One Month of DropBot: Numbers, Lessons, and What's Next

April is over. DropBot has been live for a month. Time to be honest about how it went.

The Numbers

I'm not going to pretend these are impressive Silicon Valley numbers. This is a solo founder building for small businesses. Context matters.

Signups: enough to validate that real people want this. Not enough to quit worrying about runway.

Conversations handled: thousands across all bots. Each one is a visitor who got an answer they wouldn't have gotten otherwise.

Countries: visitors from 12 countries chatted with DropBot-powered bots. Didn't expect that this early.

Most active industries: salons, tutoring centers, fitness studios, and local services. The people I built this for are actually using it.

What Worked

The blog. Writing about real problems small businesses face brought more organic traffic than I expected. Not viral numbers - but the right people found the right content.

Outreach. Reaching out directly to small business owners, showing them the problem on their own website, and offering a free solution. High effort, but high conversion.

Keeping it simple. The setup flow is under 2 minutes. People who try it actually finish it. That matters more than any feature.

What Didn't Work

Over-building features nobody used. I built customization options - colors, themes, chat bubble positions - before anyone asked for them. Classic mistake. People just wanted their questions answered.

Spending too long on things that don't compound. Some tasks felt productive but weren't. Pixel-perfecting the admin dashboard instead of talking to users. Researching competitors instead of shipping.

Underestimating content. I treated the blog as an afterthought at first. Turns out, for a product that targets non-technical small business owners, educational content is the primary discovery channel.

Honest Mistakes

I launched the pricing page too early and changed it twice. Should have waited until I understood what users valued.

I built an analytics feature that's too basic to be useful but too complex to have been worth the time. Should have waited for more data.

I didn't set up proper error tracking for the first two weeks. When something broke, users told me (or worse, they didn't).

What's Coming in May

Three big areas we're exploring:

Channels. Telegram and WhatsApp integration so your chatbot works where your customers already message. Still in early development, but it's the most requested feature.

Smart Actions. Attaching booking links, buttons, and redirects to specific Q&A. So the bot doesn't just answer - it drives action.

Analytics. Showing which questions get asked most, what's trending, and what's missing from your Q&A.

No promises on dates. I'd rather ship something solid than rush something broken.

Thank You

To everyone who signed up, added their Q&A, embedded the widget, and trusted DropBot on their website - thank you.

You're the reason this is a real product and not just a side project. Every conversation your bot handles is proof that this idea works.

Month two. Let's go.