u/Leading_Yoghurt_5323

Maybe this is just me getting older, but I feel like software in general has become noticeably less dependable over the last few years.

Not necessarily worse looking.
Not less powerful.
Not lacking features.

Just... less predictable.

A lot of modern apps now depend on:

• cloud sync
• background services
• accounts/logins
• subscriptions
• web wrappers
• live APIs
• constant updates
• online-only functionality

And individually none of those things are bad.

But combined together, it feels like software breaks in stranger and harder-to-debug ways than it used to.

Things randomly desync.
Features disappear after updates.
Electron apps suddenly consume absurd RAM.
Notifications arrive hours late.
Desktop apps stop working because some remote service changed.
A “simple tool” now needs 6 background processes and an internet connection.

What’s interesting is that software is simultaneously more advanced and more fragile.

I miss when software felt more self-contained and deterministic.

Curious whether others here feel the same way, or if this is just nostalgia talking.

One thing I keep noticing across SaaS products I try:

The marketing is usually clear enough.
The signup flow is usually polished enough.
The product itself is often technically capable.

But the moment after signup is where things start falling apart.

A lot of products still assume users will:

• configure everything correctly
• understand the workflow immediately
• import/setup data properly
• figure out the “aha moment” themselves

And if they don’t reach value fast enough, they silently disappear before support even realizes they were serious users.

What surprised me is how often the actual issue isn’t pricing or features.

It’s that the product asks for too much confidence from a brand new user too early.

I’ve started paying way more attention to:

• how fast users reach a meaningful outcome
• how many decisions they must make upfront
• how much context the product assumes
• how recoverable mistakes are during setup

Curious how other SaaS founders/operators think about this now.

What onboarding change had the biggest impact for your retention?

I’ve been running a small business long enough to notice customer behavior changing pretty significantly lately, and I’m curious whether others are seeing the same thing.

It feels like people expect:

• responses much faster
• updates much more frequently
• issues resolved almost immediately
• and generally have a much lower tolerance for delays than they used to

Even when expectations were clearly communicated upfront.

I completely understand wanting good service, and we work hard to provide it. But sometimes it feels like the emotional temperature of customer interactions is much higher than it used to be.

A delay of a few hours can suddenly feel like a major issue to someone.

What I’m struggling with is finding the balance between:

• being responsive
• keeping customers happy
• and not creating an environment where staff feel permanently “on call”

For other small business owners:

• Have you noticed this shift too?
• Did you change how you communicate timelines/expectations?
• Any boundaries or systems that helped without hurting customer relationships?

Been using Claude Code heavily for months now and the biggest workflow improvement I’ve made recently wasn’t a better prompt, MCP setup, or model change.

It was changing the final artifact I ask Claude to produce.

For a long time I defaulted to:

• markdown reports
• csv exports
• text summaries
• logs/debug notes

Which worked fine internally, but the second the output had to leave my repo/workflow, I’d end up manually reformatting everything for humans anyway.

Lately I’ve switched to asking Claude to generate polished standalone HTML deliverables instead.

Not giant React apps. Just single-file HTML:

• clean styling
• executive summary at the top
• searchable/filterable sections when useful
• expandable detail blocks
• confidence tags
• lightweight interactivity where it actually helps

And honestly this is the first time AI-generated output has started feeling “delivery-ready” instead of “draft-ready.”

Example from this week:
Had Claude build a client health scoring analysis across ~60 accounts.

Instead of:
“generate markdown report”

I asked for:
“generate a polished standalone HTML report optimized for non-technical stakeholders”

The output included:

• summary insights
• account ranking table
• plain-English score explanations
• peer comparisons
• confidence indicators where data quality was weak
• expandable supporting evidence

The interesting realization:
Claude is surprisingly good at generating presentation layers when you treat the output itself as part of the task.

I think a lot of us still use these tools like:
“generate content/code”

instead of:
“generate the final usable artifact.”

Curious if anyone else has shifted away from markdown/text-first outputs for internal agent workflows.

What output formats have actually stuck for you long term?

I’m realizing the hardest part of running a small business isn’t the work itself.

It’s the constant mental load.

There’s always:

• one more email
• one more customer issue
• one more thing that “only takes 5 minutes”
• one more problem waiting tomorrow morning

I’ve gotten better at handling operations, but worse at mentally disconnecting from the business.

Even when I’m technically off work, my brain still feels “on.”

For those who’ve been running a business for years:

Did you eventually develop systems/boundaries that helped?

Or is this just part of owning a business forever?

YSK: If you’re overwhelmed by a task, making it “smaller” is usually more effective than trying to motivate yourself

A lot of people wait until they “feel ready” to start difficult tasks.

In reality, the biggest source of procrastination is often that the task feels too large or unclear in your brain.

Instead of:

• “clean the apartment”
• “fix my resume”
• “study for exams”

Reduce the task until it feels almost stupidly easy:

• pick up clothes from floor for 3 minutes
• rewrite only the first resume bullet point
• study one page

Usually the resistance drops after starting.

Why YSK:

People often treat procrastination like a motivation problem when it’s frequently a task-design problem. Breaking work into smaller, clearly defined actions reduces mental friction and makes it easier to build consistency in work, studying, cleaning, exercise, and other daily responsibilities.

One thing I noticed hiring for a small business:

A lot of applicants underestimate how much clarity matters in a resume.

Not “making it impressive.” Making it easy to understand.

The candidates who usually moved forward quickly were the ones who:

• explained what they actually did
• quantified results where possible
• kept formatting clean
• tailored the resume slightly to the role instead of blasting the same version everywhere

Example:

Bad:
“Responsible for customer support and operations.”

Better:
“Handled 40–60 customer support tickets daily while coordinating scheduling for a 12-person team.”

Most hiring managers are scanning resumes fast. Confusion kills more applications than lack of experience.

If you’re not getting interviews, simplify before you try to sound smarter.

I’m running a small business and hitting a problem I didn’t expect to be this hard.

There are always too many things that seem important at the same time:

• getting new customers
• improving the product/service
• fixing internal processes
• handling day-to-day operations

The issue isn’t knowing what to do—it’s deciding what to ignore.

If I focus too much on operations, growth slows.
If I focus too much on growth, things start breaking.

What I’ve tried so far:

• Making weekly priority lists
• Blocking time for “deep work” vs admin
• Trying to batch similar tasks

But in reality, urgent things keep taking over, and long-term priorities slip.

My question:
For those who’ve run a business for a while, how do you decide what not to work on?

• Do you follow any rules or systems for prioritization?
• How do you avoid constantly reacting instead of acting intentionally?
• At what point do you accept that some areas will stay “messy”?

Looking for practical approaches that have worked in real businesses, not general productivity advice.

Many people agree to things too quickly — extra work, favors, meetings, commitments — because it feels easier than saying no in the moment.

The problem is that each “yes” adds up:

• Your schedule fills with things you didn’t actively choose
• Important tasks get delayed
• You end up stressed, distracted, or rushing everything

A better approach is to pause before agreeing:

• Give yourself time to think instead of answering immediately
• Check if it actually fits your priorities
• Get comfortable saying “no” or “not now” when needed

Even a short delay like “let me get back to you” can prevent overcommitting.

Why YSK:
Overcommitting reduces focus, increases stress, and lowers the quality of your work. Learning to be selective with your time improves productivity, decision-making, and overall well-being by making sure your effort goes toward things that actually matter.