Why the SaaS Boom Is Exposing a Care Gap

A Pattern I Can’t Unsee Anymore

Over the last few days, I’ve had the same quiet reaction scrolling through product forums and founder threads: everything is starting to look the same.

Another habit tracker. Another AI résumé reviewer. Another "we’ll fix hiring" pitch with slightly different screenshots. The volume is staggering—not just the number of products, but how interchangeable they feel. It reminds me of walking through a newly built apartment complex where every door opens into the same floor plan, just mirrored.

This isn’t a critique of ambition. If anything, it’s a sign of how many people want to build. The barriers are lower than they’ve ever been. Tools are faster, cheaper, and more forgiving. In many ways, that’s a win.

But watching these conversations pile up—How do I get my first users? Why didn’t my 50k views convert? Do I really need to be obsessed?—I keep coming back to a deeper tension. We’re not just seeing more software. We’re seeing a widening gap between shipping and caring.

And that gap is showing up everywhere: in bloated SaaS directories, in founders exhausted by distribution, in users who can’t tell one product from another—because, functionally, they can’t.

When Lower Barriers Don’t Lower the Work

There’s a popular narrative right now that AI is the reason everything feels sloppy. I think that’s only half true.

The real shift is that making something that works is no longer the hard part.

According to GitHub’s 2024 Octoverse report, over 92% of developers are already using AI-assisted coding tools in some capacity. Time-to-first-prototype has collapsed. A reasonably competent builder can spin up a functional SaaS in a weekend.

But speed has a cost. When effort is cheap, discernment becomes the scarce skill.

What I’m seeing across these threads is not laziness—it’s compression. The work that used to be spread across weeks of reflection, research, and iteration is now squeezed into days. Decisions that once required conviction are deferred or automated.

That’s how we end up with products that technically function but don’t land.

From a design perspective, this shows up in familiar ways:

Interfaces that solve the problem on paper but not in practice
Onboarding flows that explain features but never acknowledge anxiety
Marketing pages that describe what a tool does without clarifying who it’s for

Velocity without intention doesn’t compound. It blurs.

The Shopify analogy came up in one thread, and it’s useful—but incomplete. Shopify didn’t just enable e‑commerce. It invested heavily in education, patterns, and opinionated defaults. The ecosystem flourished because care was baked into the scaffolding.

What we’re seeing now is the scaffolding without the care.

Distribution Is Where Indifference Gets Exposed

One of the most common refrains in these discussions is some version of: “Building was easy. Distribution is the real work.”

That’s true—but not for the reason people think.

Distribution is painful because it’s the first moment your product has to survive outside your intent.

I was struck by a founder who shared that they received 50,000 views and zero sales—then converted two users through manual replies. That’s not a funnel problem. That’s a signal.

Those manual replies worked because they did something the product didn’t yet do:

They acknowledged context
They adapted to nuance
They showed care

From a research lens, this aligns with what we see repeatedly. Nielsen Norman Group reports that users form a first impression in under 50 milliseconds, and that impression is driven less by aesthetics than by clarity and perceived relevance.

When distribution fails, it’s often because the product hasn’t made a clear, specific promise to a real person. Not a persona. A person.

Practical insight I keep returning to:

If you can’t convince one person in a direct conversation, scale will only amplify that gap
Marketing doesn’t fix ambiguity; it makes it louder
Early traction isn’t about channels—it’s about resonance

This is where many founders get stuck lurking in communities, afraid to post. Not because they’ll get roasted—but because deep down, they sense the product isn’t finished emotionally, even if it’s finished technically.

Obsession Isn’t the Point—Attention Is

One thread that stayed with me involved a founder being told they weren’t “obsessed enough” for the VC game. Getting married. Living between countries. Not all‑in, apparently.

We romanticize obsession in tech, but obsession is a blunt instrument. Attention is the finer tool.

I’ve worked with teams who were obsessed with shipping—and missed the quiet signals of confusion in usability sessions. I’ve also worked with teams who had limited hours but extraordinary attentiveness. They noticed the pause before a click. The email that never got replied to. The feature request that was actually a complaint in disguise.

There’s solid data behind this. A 2023 Productboard study found that teams who regularly synthesized qualitative feedback alongside metrics were 2.4× more likely to report strong product-market fit than teams focused primarily on velocity metrics.

Attention looks like:

Revisiting copy because it felt slightly off in user interviews
Saying no to features that dilute the core promise
Designing for edge cases because that’s where trust is built

Care scales better than obsession ever will.

From a design systems perspective, this is why coherence matters. Not because it’s tidy—but because it communicates that someone was paying attention across time.

Enterprise, Consumer, and the Same Old Mistake

Another interesting contrast in these conversations is between early consumer apps scrambling for users and enterprise builders asking, “What features make this enterprise-ready?”

Despite the surface differences, the underlying mistake is often the same: confusing checklists for confidence.

Enterprise teams ask about SSO, audit logs, permissions. Consumer founders ask about channels, influencers, SEO hacks. All valid—but none sufficient.

What actually differentiates mature products is whether they reduce organizational or personal risk.

Enterprise buyers want to know: Will this make me look careless?
Consumers want to know: Will this waste my time or make me feel stupid?

Accessibility research underscores this. The WHO estimates that over 1 billion people live with some form of disability, yet most early-stage products still treat accessibility as a later concern. That’s not just exclusion—it’s risk transfer.

Designing with care means:

Making constraints visible instead of hiding them
Designing defaults that protect users from themselves
Being honest about what the product is not

These choices don’t show up in launch tweets. They show up in retention, referrals, and the quiet way people talk about your product when you’re not in the room.

What the Slop Conversation Is Really About

The fear of “slop SaaS” isn’t about bad software. It’s about indifference at scale.

When everything is easy to make, the differentiator isn’t intelligence or effort—it’s care. Care in how problems are framed. Care in how language is chosen. Care in how edge cases are handled.

As designers and researchers, this is familiar territory. We’ve always known that the smallest details often carry the most meaning. A loading state. An error message. A moment of reassurance.

The opportunity right now isn’t to out-ship everyone. It’s to out-care them.

That means fewer products, more considered ones. Fewer features, clearer intent. Less noise, more listening.

And maybe—just maybe—that’s how we turn this flood into something worth swimming in.

Because people don’t remember how fast you shipped.

They remember how it felt to use what you made.