Bootstrapping a Developer Tool to $8K MRR While Working Full-Time

What is LogShift and where did the idea come from?

LogShift is a log management CLI that lets small engineering teams aggregate, search, and alert on logs without paying enterprise prices. The idea came from frustration at my day job — we were spending $1,200 a month on a logging platform for a team of four engineers. Most features we never used.

I started looking at alternatives. The open-source options required too much infrastructure overhead. The cheap SaaS options had confusing pricing that ballooned. I thought there had to be a middle path.

You kept your job for 18 months. Was that the plan from the start?

No, I thought I’d quit after three months if it got traction. That was naive. What actually happened was that keeping my day job removed the financial pressure that makes bad product decisions. I could say no to features I didn’t believe in. I could take six weeks to do something right instead of three weeks to do it fast.

At $3K MRR I wanted to quit. My partner talked me out of it. Good call. At $8K MRR I quit on my own terms, with savings, and with a clear sense of what the product needed to be.

How did you find your first customers?

I posted a “Show HN” on Hacker News. The product was rough. The post was honest about that. It said: “this is an early version, pricing is $20/month, I want to talk to people who are frustrated with log pricing.”

Eleven people replied. Six became paying customers. Two of them are still customers today.

After that I wrote a detailed guide on cheap log management for small teams and posted it to a Go subreddit. That drove 800 visits and 40 trial signups in one week. Content was my entire distribution strategy for the first year.

How do you handle support alone?

I have a 48-hour response SLA. I tell customers this upfront. Most are fine with it — they’re developers, they understand that a solo founder isn’t a support team.

I use a shared inbox with templated responses for common questions. Anything that comes up twice becomes a documentation page. The documentation quality is now the main thing that reduces support volume.

What’s something you got wrong early on?

Pricing. I launched at $20 a month because I was scared. That price attracted a lot of free-tier explorers who had no real logging pain. When I moved to $49 a month the conversion rate dropped but the quality of customers went way up — less churn, more engagement, better feedback.

The lesson: price for the customer you want, not for the widest possible funnel.

What does “bootstrapped and profitable” actually feel like day-to-day?

Slower than I expected. Revenue doesn’t just grow automatically. Every month I spend time on distribution, support, and talking to customers. It’s not passive. But it’s mine, and the decisions are mine. That’s worth something I couldn’t fully appreciate before.

What are you building next?

Alerting and anomaly detection. Right now LogShift just surfaces logs — customers want to know when something goes wrong without writing their own queries. That’s the next major feature, and I think it’s what gets teams to stick for years rather than months.