Before TrukingsI, I built TRUPERS, a project that got me to $100K in profit. What actually got me there wasn't luck, it was never making a decision without information. I was obsessed with onboarding: where visitors actually came from, exactly where they dropped off, whether a page was genuinely hard to use or just slow and bleeding people. Every change came from real data, not gut feeling. If something worked, I doubled down. If it didn't, I tried something else. If it was borderline, I kept tuning it. Never decide blind.
The biggest blind spot I had back then, and the one I see in almost every SaaS founder now, isn't traffic or conversion. It's not knowing what their own users actually think of the product. Is it easy to use. Is support good. Is it worth the price. Does it deliver on what it promises. Without that, you're deciding blind, guessing at what actually needs to change instead of knowing.
That's what I built TrukingsI to fix. It's simple: you list your SaaS and share the link TrukingsI gives you with your own users. They rate you on ease of use, support, value and reliability, and you see it broken down in a dashboard. That's real input you can act on, the kind of strategic decisions that actually improve the product. Free: https://trukingsi.web.app
Thanks for sharing the numbers, that makes it much easier to follow.
Nice work shipping it. What has been the biggest challenge since launch?
Curious how long it took before you saw the first real results?
Interesting. How are you measuring whether it is working?
Thanks for sharing the numbers, that makes it much easier to follow.
Nice progress. What is the next thing you are focusing on?
Great breakdown. What feedback have you had from early users?
Great breakdown. What feedback have you had from early users?
Great breakdown. What feedback have you had from early users?
What behavior would validate TrukingsI beyond collecting ratings—founders changing a product decision from the feedback, or users repeatedly returning to track improvements?
Good point. Did you test that with users before committing to it?
What made you pick this stack over the alternatives?
Nice progress. What is the next thing you are focusing on?
Thanks for writing this up. Bookmarking it for later.
Interesting approach. What was the hardest part to get right?
Curious how long it took before you saw the first real results?
Love this angle, honestly. What made you look into it in the first place?
Interesting approach. What was the hardest part to get right?
Interesting approach. What was the hardest part to get right?