Building SaaS was easy. Talking to users? Hell no.

ctrjunkie

i thought building a SaaS would be the hard part. Turns out, having real conversations with users is the actual nightmare. I'm working on a small Library Management project, and every institution handles books differently. Some use registers, some Excel, others just remember everything manually. Half of them don't even realise they have a problem until you dig deeper.

As a beginner founder, I used to believe 'good product = people will use it'. Now I realise understanding user behaviour and communication is probably ten times harder than coding.

Building feels controllable. User conversations force you to hear uncomfortable truths fast. Most founders spend way too long polishing features nobody asked for.

Anyone else feel like coding is the easy bit? What changed your understanding of users completely?

funnelhacker

Talking to users is where the real ROI hides. spent years buying programmatic and thought I knew audiences, turns out watching real workflows-especially niche ones like libraries-floors all the demographic data. The best leads come from the noise they complain about on forums and social. Setting up keyword alerts (there's solid tools for that now) surfaces authentic pain points without manual scrolling. That's how you validate a product before burning dev budget

wordweaver

oh, absolutely. Building feels safe because you're the one in control - you can hide behind code and pretend everything's fine. user conversations? That's where you discover your beautiful baby is actually a bit ugly. Too many founders spend months polishing features they think are genius, only to find out nobody even knew they existed. It's like building a swimming pool in the desert and wondering why nobody's diving in.

tagmanager

Honestly, that's the part that rewires everything.

So many founders assume the hard bit is the build. But the real challenge is whether you properly understood the problem in the first place. What caught me off guard was how wildly different "users" can be from the personas you sketch in a pitch deck. A customer support agent, a store manager, and a returns handler can all say "we need to automate order updates," but their workflows, pain points, and priorities are often worlds apart.

A few things shifted my perspective fast:

asking "what's your current workaround?" rather than "what features do you want?"
sitting in on their actual process, not just listening to them explain it
looking for patterns of recurring frustration, not just loud complaints
noticing what they lean on - spreadsheets, sticky notes, WhatsApp, email chains - that's where the real product specs live

For a DTC brand especially, the manual customer communication is where you uncover the real gaps. If someone is still copy-pasting order confirmations or relying on memory for follow-ups, there's usually a reason - habit, trust in the old way, tight budgets, or just a workflow that's "good enough."

So yeah, coding can test your patience, but user conversations are where you find out if you're solving something real or just polishing the wrong solution

adcraft

Building the product? Yeah, that's been commoditised. Marketing automation tools like Claude and GPT churn out content, sure. But talking to actual users? That's where most SaaS founders fall apart. Automation masks the real problem: you haven't validated a single pain point. i'd rather spend an hour on a user call than let another bot write "engaging" copy I'll never read.

marketingmule

Biggest shift for me was realising clients rarely want a "better campaign structure" - they want something that slots into the chaotic workflow they already have. Most of the learning came from sitting in on their internal calls and watching what people actually do, not what they say they do when we're in a briefing.

maya-b2b

That realisation hit me hard too. Building the product? That's the easy bit these days. The real grind is getting someone to stop scrolling long enough to hear your story. Marketing isn't just key-it's the entire lock. Still working out how to cut through the noise without sounding like everyone else

jamesaso

what shifted things for me was realising i couldn't tell if users were confused or just uninterested. Solved that gap by focusing on PMF clarity, or running more discovery calls.

pixelperfect

You'd think listening to users would be the easy bit, wouldn't you? What finally clicked for me was realising most people describe the solution they want, not the actual problem they're stuck with. You have to sit beside them while they work through a messy process, step by painful step, and keep asking "why" until you hit the fifth layer. Otherwise you're building what they say, not what they actually do.