lazarkap

Thanks for the words of encouragement, as you said to me, DON'T stop, and good luck.

If I can help somehow, hit me up on linkedin, Il be glad. https://www.linkedin.com/in/lazarbogosavljevic/

No, that was one of the products I slowly did let die, and kinda modified the product to be open-sourced, cli first tool.

Thanks for the words of support. I will definitely try to be more active on youtube and leverage that.

"The idea is the easy part" is something I knew deep down but was too afraid to admit to myself. It's easier to keep building than to confront that everything after it is the actual work. Took me years and a few dead products to really accept that.

I feel like Im in the process of swallowing that pill.

Most of them are down honestly, which kind of proves the point of my post.

Ourbit (ourbitapp.com) is still a work in progress (wrapping up the demo/assetes/characters).

BuzzBench is down but the repo is open and there's a demo video if you want to see what it did: github.com/LazarKap/buzzbench / https://www.youtube.com/watch?v=yAnbZMoQvmQ.

Building something new right now that's directly about this problem, will share when it's live.

Next to this, I have like 3 more failed projects.

This is exactly the problem I've been sitting with for some time now. Every platform I tried to find a marketing partner on was either dead, full of bots, or just a generic co-founder matching app with no real skin in the game.

I'm actually building something about this, would love to stay in touch and share it with you when it's live. Might be exactly what you've been looking for.

In case you are interested to stay in touch, shoot me a message. (https://www.linkedin.com/in/lazarbogosavljevic/)

None taken, I agree with you, and it is a fair point. I need to rethink my approach.

Fair point.

The 90% is relatable, I physically cannot stop building even when I know I should be doing something else. The mode switching is the hardest part, not the marketing itself.

Good reminder that ads can show results fast while SEO compounds slowly, running both makes sense.

The SEO + free tools as a funnel is something I hadn't thought about before.

Not universal for every product but for the right one it's a really clean distribution channel that compounds over time. The "make calls with users" part is universal though, that's the one I keep avoiding and probably shouldn't.

How long before the SEO started moving for you?

I'd love to take you up on that. Sending you a message, do you have an email/linkedin or preferred way to connect?

Platform where technical founders post their live products and marketers pitch to join as co-founders or paid partners. Built it because I kept running into the exact problem in my post. Not live yet but close.

I think I am definitely gonna try the direct sales approach, to try and fill out the platform once its ready.

I've definitely been guilty of building first and hoping customers appear. Funny timing on this post though, because right now I'm actually in the middle of doing exactly what you're describing.

100K MRR solo is insane, congrats.

I think the "Make contact with every customer" hits hard here. I think a bunch of people forget they you talk to people more.

Nothing to say, great advice.

I plan to add ability to deploy additional agent to the env that is being tested, and that one would just grab resource metrics and send back to me while its being tested. :D So you can see your resource usage while tests are running and you can predict how much traffic/usage your platfroms/services can handle

Thanks for this comment, here is something fast I pulled around:

Distributed Testing: BuzzBench runs agents directly in your environments, while Gatling/k6 typically run from a single location

Coding Required: BuzzBench uses UI configuration, while Gatling needs Scala and k6 needs JavaScript

Dashboard: BuzzBench includes a built-in dashboard, Gatling/k6 require separate setups

Environments: BuzzBench tests multiple environments simultaneously, harder to coordinate with Gatling/k6

Setup: BuzzBench has a simpler install with lightweight agents vs. more complex configuration for others

Learning Curve: BuzzBench is designed for quick adoption, Gatling/k6 have steeper learning curves

So BuzzBench can basically be a health check for your web app, it hammers your endpoints with requests to see if they hold up under pressure.

You can definitely use it for both quick "will this break under load" tests before deploying, and to track performance over time so you can catch when things start getting sluggish.

The cool part is you can run tests from pretty much anywhere, your laptop, your CI pipeline, different regions - so you get realistic results rather than some theoretical benchmark.

I agree, my initial plan was to get users to actually use it for free, and when I think I offer enough value, put a price on it, but of course, I would not be like "from tmrw, you pay this amount", it would be months in advance.

There is an open source Im working on, that will be able to achieve all this just without dashboard https://github.com/LazarKap/buzzbench.io. How did you analyze resource consumption with your tool??

Hey, imo, its much easier to setup, and its running tests FROM different environments, I think gatling is standalone tool and it is running test from their environment?