u/Cautious-Nature-9052

MeetMatch is sitting at 6,320 total meetings handled and 199 active users right now.

That sounds decent when I type it out, but the actual day-to-day still feels pretty messy. Like this week I fixed a CRM contacts hooks order issue and a lead source column rendering bug. Very glamorous founder work. Nothing makes you feel like you're building the future quite like staring at a table column that refuses to render correctly for like 3 hours on a Tuesday morning.

The good number is the meetings one. People are actually using the thing for real calls, not just creating accounts and poking around.

The less-good number is 199 active users, because it has not moved in some dramatic hockey-stick way. It moves, then stalls, then moves again. Very annoying. Very normal, probably.

I also added call snippet annotations so managers can tag specific moments in recordings for training. That one feels like it might actually matter, because sales managers dont want "AI coaching" in the abstract. They want "show the new rep the 47 seconds where this objection got handled well."

On the ugly side, the overbooking confirmation window logic needed more rework. There was an edge case where both slots got claimed, which is exactly the type of bug that makes a scheduling product look stupid. Fixed the logic, but I hate that it existed.

Also shipped a team utilization grid perf fix and team filter fix, because apparently once you add team features, every page eventually becomes a spreadsheet with opinions.

For other B2B SaaS folks around 100 to 500 active users, what does "healthy" look like for you week to week? Are you still spending 30%+ of your time on bug fixes and weird edge cases, or is that a sign I'm carrying too much product surface area too early? Honestly feels like my code is held together with duct tape sometimes.

This week was one of those weeks where the product felt like it was actively trying to embarrass me. Been nursing way too much coffee trying to figure this out.

MeetMatch has handled around 6,300 meetings now, and there are 199 active users kicking the tires or actually using it. Which is cool, except the more meetings run through it, the more every weird scheduling edge case stops being theoretical and starts becoming a person emailing me with screenshots.

The one that almost broke me was in the overbooking confirmation window logic. The feature is supposed to let a backup prospect grab a risky slot if the first person doesnt reconfirm. Simple enough.

Except there was an edge case where both slots could basically get claimed. Not common, but common doesnt matter when the thing you are building is trusted to not make sales reps look incompetent.

I stared at that flow for way too long thinking, maybe this whole feature is too clever. Maybe I should just copy the normal scheduling tools and stop trying to build the weird no-show protection system I wanted when I was doing sales myself. Honestly started questioning everything around 2am Saturday.

The annoying part is I also shipped good stuff this week. Training library is live now, with courses, chapters, snippet annotations from calls, and progress tracking. Fixed the event follow-up tab and some onboarding junk. Also changed HubSpot outbound sync to default off for new orgs because auto-syncing too early is a great way to make people nervous.

But none of that feels like progress when one scheduling edge case can eat the whole day and make you wonder if users are quietly losing trust.

For people building workflow software where mistakes are very visible, how do you decide when a powerful feature is worth the support burden versus when its just product complexity wearing a fake mustache?