We keep tweaking our signup steps to make it frictionless, but I'm starting to think a smoother form doesn't solve the core issue. People breeze through the steps and then never touch the core feature.
It feels like we're optimizing for the wrong metric if they aren't reaching that first "aha!" moment quickly enough.
For other builders: where did your biggest drop-off happen, and what specific change finally got them past it?
I ve been thinking about where the line actually is with Kubernetes. When you re a small team, something like Render, Railway, Fly, or a managed cloud setup can take you pretty far. You push code, it runs, and nobody has to become the accidental infrastructure person. Then the product grows. You have more services, workers, cron jobs, environments, traffic that doesn t behave nicely, maybe different scaling requirements. At some point someone says, We should probably move to Kubernetes before this becomes a mess. But moving early can create a completely different mess.
Now someone needs to understand the cluster, networking, autoscaling, deployments, observability, upgrades, Helm/YAML, and what happens when something breaks at 2 AM. On a five-person engineering team, that can very quickly become one person s unofficial full-time job. Waiting too long doesn t sound great either. If you eventually need Kubernetes, migrating when the existing infrastructure is already struggling is probably the worst possible time to do it.
So I m curious what the actual trigger has been for teams here.
Was it traffic? Number of services? Cloud cost? Needing more control over deployments? Hiring a platform/DevOps person? Or did you get quite far without Kubernetes and realise you never actually needed it?
Today, I read a TechCrunch article about what investors are no longer looking for in SaaS, or rather, what to avoid if you don't want to lose their interest.
The red flags were:
Too easy to replicate light AI wrappers, generic horizontal tools, basic CRM clones, generic productivity or project management tools.
No real depth products where differentiation is mostly UI and automation, anything without proprietary data, surface-level analytics.
Becoming obsolete workflow automation tools that coordinate human work (agents are taking over), integrations as a moat (MCP is making connectors a commodity), and "workflow stickiness" products trying to keep humans inside their software.
I have tried several ways to promote my product, but distribution has been much hareder than building it.
product hunt is the only channel where I've found meaningful visibility so far. Reddit has been difficult because self promotional posts are often removed, and I don't want to spam communities where the product isn't genuinely relevant.
My co-founder and I love how fast we can ship using OpenAI endpoints, but the unpredictable monthly bill is forcing us to cap feature usage. It feels terrible having to limit user experiments just to keep costs under control.
We're tempted to switch to self-hosted open-source models for predictable hardware costs but taking on server maintenance and potential drops in output quality gives us pause.
I emailed someone who cancelled and asked why. Not a survey a real question, from me, personally.
They told me. Honestly and in detail. It was the most useful feedback I've gotten in a year, and it arrived from someone who had absolutely no reason to be nice to me.
I ve been thinking about how much company knowledge never makes it into the docs. Someone leaves and all the files are still there. Slack is still searchable. But the reasoning behind decisions and all those you had to be there details leave with them. How are you handling this at your company?