I've been building SaaS products for the past few years.
Like many indie hackers, I started with excitement, convinced that if I built something useful, people would come.
They didn't.
My first product failed.
It was a platform where I provided small loans to people so they could sell digital products. The idea felt meaningful—I believed I was helping people start something for themselves.
But reality hit hard.
Many borrowers defaulted on their payments.
That experience taught me a difficult lesson: even when your intentions are good and genuinely beneficial to others, people don’t always respect those intentions.
I had built something with purpose, but I hadn’t fully accounted for human behavior.
So I started over.
The second product also failed.
This time, the mistake was different.
I built the product without ever speaking to my target customers. I assumed I understood their needs, spent time building, and then tried to market it.
There was no response.
No traction. No engagement. Nothing.
Eventually, I had to accept the truth—I had built something nobody asked for.
So I shut it down and moved on.
Instead of giving up, I decided to try one more time.
This time I made myself a promise.
I would spend another five months building and marketing one last product. If I still couldn't find users who genuinely needed it, I'd stop chasing SaaS ideas and try something completely different.
That promise led me to Incentise.
The idea came from something I noticed almost every day on social media.
Brands, creators, and businesses post amazing content, but actually getting to the product or website behind the post is surprisingly difficult.
Instagram doesn't allow clickable links in captions.
TikTok keeps most links in the bio.
Many platforms discourage outbound links because they want users to stay on the platform.
As a result, I've often found myself wondering:
"Where's the actual product?"
So I built Incentise.
Instead of relying on clickable links inside every post, Incentise lets publishers map each social media post to one or more destination URLs.
Someone who discovers a post can simply copy the post URL, paste it into Incentise, and instantly discover the destination behind it—whether that's a product page, online store, marketplace listing, blog article, website, or something else.
The goal is simple:
Help people discover the destination URLs behind social media posts.
I'm still validating whether this is a real problem worth solving.
I don't know if this will become a business.
I don't know if anyone will pay for it.
But I do know this is the most focused I've been on solving a single problem instead of trying to build dozens of features.
Over the next five months I'll keep building, talking to users, and sharing what I learn—whether it's good or bad.
If it succeeds, great.
If it doesn't, at least I'll know I gave it one honest final shot instead of wondering "what if?"
I'd genuinely love your feedback.
Is this a problem you've experienced?
Would you ever use something like Incentise?
What's the biggest flaw you see in this idea?
The key insight here is that you learned to talk to users before building — not after. That's the actual win, regardless of whether Incentise works out.
One thing to stress-test though: you're solving a friction point that creators experience, but Incentise requires them to actively do the mapping. Most people default to link shorteners or their bio because no additional work is needed from their side. The question isn't "is finding products behind posts hard?" (it is). The question is "will creators adopt a tool that adds a step to their workflow to make it slightly easier for followers?"
That's a different problem. Worth talking to 10 creators who post regularly and ask them specifically: would you spend 2 minutes mapping each post to its destination for us, if it meant your audience had an easier way to find what you're promoting?
Their answer to that question matters more than whether the problem feels real to you.
Hi Omri,
Thanks for your feedback! I really appreciate you taking the time to read my post.