From Designing Houses to Debugging Code
I spent years as an architect, designing homes for people — thinking about how light falls in a room, how a hallway makes you feel when you walk through it.
Today I’m a self-taught SaaS founder with zero coding background. Here’s how that happened — and a question I’d love this community’s take on.
The problem I couldn’t unsee
After architecture, I started creating digital products for designers and architects — templates, guides, small tools to make their work easier. To sell them, I did what everyone does: I ran ads.
And I watched the same thing happen, over and over. Visitors would land on the sales page, read everything, hover over the price… and leave. Not because the offer was bad. Because of one small moment of doubt nobody was there to answer.
So I did what most of us do — I spent more on ads to “fix” it. More traffic, same leak. It took me a while to realize the problem was never traffic. It was the silence at the exact moment someone almost said yes.
So I built the thing I wished existed
I taught myself Lovable, wired up Supabase for the backend, and used Claude’s API to build FlowEra — an AI that detects that exact hesitation moment on a sales page (price hover, exit intent, scrolling to the bottom) and starts a warm, real conversation right then, in the creator’s own voice, to bring the visitor back.
No dev team, no co-founder, no CTO. Just me, a lot of trial and error, and a problem I’d watched too many creators — including myself — quietly lose money to.
Where I am right now
A recent Reel about this got close to 14,000 views, and a free quiz I built to show creators their own leak point has been quietly building a list of warm, engaged leads.
Right now I’m figuring out the best way to turn that warm interest into paying customers — especially without a short free trial. For this kind of tool, a few days just isn’t enough time to actually see results, so a trial would set people up to cancel before the product even proves itself. I’m leaning on other ways to build trust instead.
None of this is really about hitting a number for me. What actually excites me is knowing that somewhere, a creator is spending less on ads this month — not because they cut their budget, but because the leads they already paid for stopped quietly slipping away. That’s the entire reason I built this in the first place.
Teaching yourself Lovable and Supabase to ship this is a serious hustle, huge congrats on getting the product out there. Your logic on trials is spot on—time-bound free trials are a death sentence for tools that require data to accumulate. If you want to protect your time and build trust without a trial, a solid "30-day money-back guarantee if it doesn't bring back a visitor" works way better. It filters out the tire-kickers who just want to play with the tech, and ensures you're only onboarding creators who have real traffic and an urgent leak to fix.
That's a really interesting perspective. I hadn't thought about replacing a free trial with a results-based guarantee, but it actually aligns much better with the problem Flow Era is solving. Thanks for the idea!:)
Glad it helped! The coolest thing about a results-based guarantee for an early-stage tool is that it sets up a super valuable feedback loop. If a paying customer does end up reaching out for a refund because it didn't rescue a visitor, you instantly get a perfect excuse to look at their setup. You can dig straight into their page layout to see exactly why the exit-intent logic missed or what copy failed to bring the buyer back. It's basically high-quality debugging data from highly motivated users. Rooting for you!
That's a really smart point. Turning refund requests into learning opportunities could actually help improve the product much faster. Thanks again for the thoughtful feedback! If you ever launch or sell a digital product yourself, I'd be happy to let you try the beta and hear your thoughts :)
Catching exit intent and price hovering before someone silently disappears is a real problem most sales pages just don't address at all. The trial question is tricky though, too short and it undercuts the tool before it proves anything, too long and you're giving away the value for free. Have you considered gating it by outcome instead of time, like a free trial that ends after it recovers its first saved lead rather than after X days?
I really like the idea of tying the trial to an outcome instead of a timeline. That's a much more meaningful way to demonstrate value. Definitely something I'll explore—thanks!:)
Glad that reframe was useful. The tricky part once you build it will be defining "outcome" precisely enough that it's not gameable, like making sure a recovered lead is a real save and not just someone who was going to convert anyway. Worth watching closely once you ship it.
The attention to detail you probably developed drafting blueprints is a huge asset in debugging—you're already trained to spot the one thing that's breaking the whole system. That architectural thinking translates way more than people expect.
I love this analogy. You're right The goal isn't to add more information everywhere, it's to answer the right question at the exact moment doubt appears. Thanks for putting it that way.
the architect background isnt a footnote here, its the actual skill. a hallway works because it answers "where next" exactly when you ask — not with a sign at the front door. your page leaks because the answer to that doubt already exists, its just not AT the price, where the doubt actually happens. so id not stack more proof up top — id move the one objection-killer down to the exact moment someone hovers and hesitates.
That's a great point. One of the things I'm hoping Flow Era can do is surface those recurring objections so creators can improve not only their conversions, but also their product and messaging over time .
The line about silence right when someone almost says yes is sharp. A lot of founders respond to that by chasing more traffic, when the better move is usually to pin down the exact objection and build around it. I learned that the same way building DictaFlow, the most useful copy came from the oddly specific sentences users sent when something almost worked for them. If you keep hearing the same hesitation, I'd turn each one into onboarding, proof, or a small product fix before spending more on clicks.
That's really helpful, especially coming from someone who's faced a similar challenge. I agree that demonstrating outcomes is much more powerful than offering a short trial. Appreciate you sharing your experience
This trust-without-a-trial problem is so real, we've hit the same wall with hiring products, you can't prove that kind of outcome in a few days. What's worked for us is leaning on specific outcomes from similar customers instead of just trial access, and maybe a hands-on pilot with a few warm leads so they actually see the leak close before committing.
I love how you phrased that. "Intervening when uncertainty appears" captures exactly what I'm trying to build. Thank you—that's a really insightful way to describe it.
What stood out to me is that you're not trying to increase conversions—you’re trying to intervene at the moment uncertainty appears.
That's a subtle but important distinction. If you consistently solve hesitation instead of simply adding another chat widget, you're defining the product around a decision rather than a feature.
I really appreciate this perspective. That's exactly the problem I'm trying to solve—understanding hesitation and helping visitors move forward before they leave. I love the way you framed it. Thank you!
I'm glad it resonated.
Reading your reply, I found myself thinking about one implication of that product direction. I'd rather explain it in the context of FlowEra than give you a generic answer because I think the context changes the conclusion.
If you're open to it, what's the best email to reach you on?
Thanks, I’d definitely be interested to hear your thoughts. I really appreciate you taking the time to think about FlowEra beyond just the surface level.
You can reach me here: [email protected]
Looking forward to hearing your perspective!
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.
Could you please send it again? I didn’t receive it.
Thank you!
Thanks for the heads up!
I've just resent it, so it should be in your inbox now. If you don't see it in the next few minutes, could you also check your Spam and Promotions folders? Sometimes first emails end up there.
Looking forward to hearing your thoughts once you've had a chance to read it.