Not signups. not page views. not even MRR in the early days.
For us it was when users started coming back without us emailing them. no nudge, no reminder. They just returned because they wanted to.
Everything before that felt like we were pushing. That was the first time the product pulled.
What was yours?
Strong opinion. Hear me out.
I've seen founders with perfect dashboards make terrible calls because they already knew what they wanted to do and used the data to confirm it.
But I've also seen founders flying completely blind make confident decisions that were just wrong in ways that were totally avoidable.
Bad instincts you can coach. Bad data just accelerates the wrong direction.
How much are you actually trusting your data right now?
Sat with this question and the answer made me uncomfortable.
Intercom. Because it has everything. Every customer conversation, product feedback, billing complaints, things people say to support they'd never put in a form. Years of it.
Not just names and emails. Actual relationship history. the kind of data that doesn't show up in a breach notification but absolutely gets used.
And honestly I have no idea what their security posture looks like. I read the terms once, clicked accept and moved on like everyone does.
We spend a lot of time asking if tools are worth the price. Not enough time asking if they're worth the risk.
Which vendor would hurt you most? and has anyone actually audited what each tool is sitting on?
For us it was the third time the Hubspot sync broke in a month.
No alert. no error. Just silently wrong. we found out on a customer call. that was the moment.
We'd spent more time maintaining the integration than building it. every tool promised seamless sync. every tool had undocumented edge cases. every edge case became someone's problem at the worst time.
So we ripped it out and built something simple we actually understood. A few tables, basic logic, one place to look. Not pretty. But it hasn't broken once.
Fighting bad integrations is expensive. It's just harder to see on a spreadsheet than a subscription fee.
What was your breaking point?
Mine has 200 contacts, 11 deals marked in progress from 8 months ago, and a last activity date that I'd rather not look at.
I set it up properly. Spent a weekend importing everything, building pipelines, writing templates. Felt productive. Then actual work happened and it became the thing I'd catch up on later.
Now my real CRM is a pinned Slack message, a Notes app with initials I barely remember, and my sent folder.
Genuinely curious if anyone has cracked this. Because every CRM I've tried was built for a sales team of 10, not one person juggling product, support, and growth at the same time.
Do you actually keep yours updated? and if so, what made it stick?
Curious how far people have taken this.
We started using Supabase as our app database and at some point realized it could just... be more. Customer records, billing events piped in from Stripe, support history, internal notes. It's all just tables at the end of the day.
Now I'm wondering how many of the SaaS tools we're paying for are just a UI on top of something we could own ourselves.
Already thinking about replacing our CRM. Maybe our basic analytics. Possibly the janky Google Sheet we use for tracking renewals that nobody wants to admit is load-bearing.
What have you actually replaced with Supabase? and where did you hit the wall where a proper tool was genuinely worth it?
Would love to hear real setups, not theory.
Not talking about a full data warehouse. Not Segment with 47 integrations. Just the bare minimum you need to actually understand what your customers are doing and catch problems before they become cancellations.
Right now we're tracking signups in Supabase, payments in Stripe and support in Intercom. Three tools, no single view. Good enough for now but I can already see it falling apart as we grow.
So what's the floor here? what do you actually need before the duct tape stops working?
Is it just getting everything into one database? a simple events table? some kind of lightweight activation tracking? or does it not matter until you hit a certain number of customers?
Spent months running interviews, sending surveys, mapping drop-offs manually. People lie in interviews anyway, not on purpose, they just tell you what sounds right.
Tried Skene.AI on a whim. It scanned my codebase and Supabase schema and came back with three activation gaps I'd completely missed. Lifecycle holes, drop-off points, automation opportunities are all sitting in the code the whole time.
Didn't need to talk to a single user.
Interviews are still useful for the why. But if you want to find where your product is quietly bleeding users, your codebase already knows. You just need something that can read it.
Anyone else doing codebase-first growth analysis? feels underrated.
This should be a solved problem by now. It's not.
We run Hubspot, Stripe and Intercom. Three tools, three dashboards, three exports if you're lucky. Want to see which customers are churning, how much they've paid and how many support tickets they've filed in one place?
Good luck.
You're either paying for a data warehouse you don't have the eng resources to maintain, duct taping Zapier flows that break every month or manually cross-referencing spreadsheets like it's 2012.
The data exists. all of it. It's just siloed behind three different APIs that were never meant to talk to each other.
Can't be the only one hitting this wall. How are smaller teams actually solving it?
Are you using Retool, Metabase, a proper warehouse setup? or have you just accepted that a unified customer view is something enterprises have and everyone else improvises?
Nobody talks about the moment a tool becomes load-bearing. You stop questioning it. You build around it. Your team learns it instead of the problem it solves.
That's not lock-in from a contract. That's lock-in from forgetting what you actually needed in the first place.
So, which tool in your stack have you stopped questioning?