# Why People Resist AI (it's a Standards Problem) > Source: [https://botensten.com/articles/ai-resistance-standards-problem](https://botensten.com/articles/ai-resistance-standards-problem) (canonical) > Author: Chuck — Botensten, https://botensten.com > Published: 2026-06-26 · Updated: 2026-06-30 ## TL;DR After 17 years as a broker-owner, I watched AI surface birthday follow-ups and graduation outreach I'd never thought to do myself — and that gap revealed I was the bottleneck, not the technology. The loudest resistance to AI isn't about energy or data centers; it's about work standards. Societies and industries with low labor standards resist high-standard tools because the tools expose the gap. The real problem isn't AI replacing you — it's AI revealing what you weren't doing. The fix isn't fighting the technology; it's raising your own standard of reasoning and logic to meet it. **TL;DR:** In my 17 years as a broker-owner, the agents on my team who already logged every contact and tracked follow-up dates by hand adopted AI tools fastest — and the ones who relied on memory and informal habit resisted hardest. That pattern, repeated across every rep I managed, is what convinced me AI resistance isn't really about data centers or job loss — it's about the mirror AI holds up to low work standards. When a tool reasons, logs, and follows up without distraction, it exposes the gap between its standard and yours. The productive response is to close that gap from your side. I've done that by rebuilding my entire stack — CRM, email, website, news curation — on a Mac Studio instead of renting SaaS subscriptions. I call the coming collapse of that subscription dependency the SaaSpocalypse, and I think every solopreneur should be building into it rather than resisting it. --- ## Why are people really resisting AI? **After 17 years as a broker-owner, I watched AI surface follow-up tasks I had never built into my own workflow — birthdays, graduations, client anniversaries.** In my read — shaped by two decades on the ground in real estate, not a cited study — the public conversation about AI resistance tends to land on data centers, energy grids, and job displacement. But the friction I've witnessed up close, and felt myself, is personal: agents on my team who relied on memory and informal habit felt exposed when the software surfaced exactly how much they had been skipping. I've seen the same pattern at passport offices, DMV counters, and VA hospitals — workers who bristle at systems that log, follow up, and don't get distracted, not because the technology is broken but because it holds a higher standard than the habits it's replacing. That moment in my own brokerage was clarifying. I wasn't blocked by the technology. [I was the bottleneck](/articles/vibe-coding-pivot-content-engine). At [3:45] I said: "I'm the backlog right now. I'm the one with low standards because I'm saying I didn't even think of that" — and that admission is the whole point of this piece. ## What do standards actually mean in the context of AI? **Standards are guardrails on behavior.** You wear a suit to a wedding, not shorts. You don't curse in a job interview. These are standards — agreed-upon floors for how we show up. AI works the same way. It has guardrails on how it answers, how it reasons, and what it refuses to do. Companies build those guardrails in because crossing them would be embarrassing. The result is a tool that is, by design, unemotional, logical, and consistent. That consistency is exactly what makes some people uncomfortable. When a tool holds a higher standard than the person using it, that person has 2 choices: rise to meet it or reject it. I made the case for rising to meet it in my piece on [building a content engine with vibe coding](/articles/vibe-coding-pivot-content-engine) — the same dynamic that applies to content output applies here to every category of work. ## How did I first notice this pattern in my own work? I spent 17 years as a broker-owner in real estate. AI started surfacing things like: this contact's birthday is today, this client's kid just graduated, this person just got married. The system was telling me who to reach out to and why. My reaction wasn't pride — it was embarrassment. I hadn't built those habits myself. I automated the outreach, and then I had to sit with an uncomfortable truth: a piece of software had higher relational standards than I did. That's the mirror AI holds up. It doesn't judge you. It just performs at a level that makes the gap visible. The [CRM I eventually rebuilt from scratch](/articles/salesforce-replacement-claude-crm-build) forced me to confront exactly which relational workflows I had been skipping for years — and building it, rather than renting a SaaS version, made every gap impossible to ignore. ## Why do low work standards fuel AI resistance? I was on a train at 9:30 a.m. and spotted a worker in a vest, partially hidden behind a pillar, scrolling his phone. That image stuck with me. It's not an isolated case — I've seen the same pattern at passport offices, DMV counters, VA hospitals, and government agencies. In Charles's view — shaped by 17 years on the ground as a broker-owner, not a cited study — work standards in America have declined sharply. He frames this as a personal read, not a statistic: most people, he argues, don't show up to labor with pride. The clearest case study I can offer comes from my own brokerage. The agents on my team who already ran tight operations — who logged every contact, tracked follow-up dates by hand, sent handwritten anniversary cards — were the ones who picked up CRM and AI tools fastest. The technology matched how they already thought. Agents who relied on memory and informal habit felt exposed by the same tools, because the software surfaced exactly how much they had been skipping. The resistance wasn't about the product. It was about what the product revealed. That pattern held across every rep I managed for nearly two decades. This matters because AI shows up with the opposite energy of distraction. It reasons, it logs, it follows up, it doesn't get distracted. When your standard is low and the tool's standard is high, the tool feels like a threat. It isn't. It's a benchmark. For macro context: the [U.S. Bureau of Labor Statistics tracks long-run output-per-hour trends across industries](https://www.bls.gov/opub/mlr/2024/article/labor-productivity-trends.htm). That research measures aggregate productivity — how much workers collectively produce per hour over time. It is not the source of my individual-level observations above, which are drawn from my own experience in brokerage. But it is the economic backdrop: when output-per-hour stagnates at the aggregate level, the individual dynamics I'm describing — distraction, low follow-through, resistance to high-standard tools — are part of what drives it. ## What is the "SaaSpocalypse" and why does it matter for builders? **The SaaSpocalypse** is the term I use for the coming collapse of subscription software dependency — the moment when a solo builder can own everything a SaaS vendor used to charge them for. CRM, email management, website, news curation: I've moved all of it in-house. I run an [Apple Mac Studio](https://www.apple.com/mac-studio/) as my local build machine. I use [Perplexity AI search and news curation](https://www.perplexity.ai) to pipe curated news to my phone. Nothing I rely on daily is rented from a vendor anymore. The [CRM replacement project](/articles/salesforce-replacement-claude-crm-build) is the clearest example of what that shift looks like end to end. This shift isn't just financial. It changes your relationship to your own work. When you build the tool, you understand the tool. When you understand the tool, your standard rises. Here is how the two modes compare: | Mode | What you control | What you pay | Standard required | |---|---|---|---| | SaaS dependency | Interface only | Monthly subscription per tool | Low — configure, don't build | | Owned stack on Mac Studio | Data, logic, integrations | Hardware once | High — you are the engineer | ## How does reasoning replace entertainment as a default mode? I talk about entertainment and distraction as emotional states — not moral failures, but patterns. Scrolling a phone is a feeling. It produces low-grade stimulation with no output. [Reasoning is the opposite](/articles/objective-thinking-unlearning-relearning): it produces output, and output produces standards. This morning I was coding with Fable, which spun up what felt like 100 agents working through a problem on my build. The process was, as I described it on stream, "a lot of logic and very little emotions." That's the mode I'm trying to operate in — and the mode I'm arguing we all need to move toward. The future I'm building toward is one where every person is a creator and every creator is a builder. Not because it's romantic, but because the economics force it. White-collar and blue-collar disruption is coming at every level. Fighting that with resistance doesn't raise your standard. Building into it does. The [vibe coding workflow I've been documenting](/articles/vibe-coding-pivot-content-engine) is my most direct attempt to show what that shift looks like in practice. ## Frequently asked questions about AI resistance and work standards **Is AI resistance really about work standards, or is it about job loss fear?** Both are real, but in my view they're connected. Job-loss fear is loudest when someone's current standard is low enough that they can't imagine competing with a high-standard tool. Workers who take genuine pride in their labor tend to say "bring it on" rather than "not in my backyard." The fear and the standard are two sides of the same gap. I wrote more about how [relearning to think objectively](/articles/objective-thinking-unlearning-relearning) changed my own relationship to that fear. **How did you replace your SaaS stack without a large team?** I used a Mac Studio as a local build machine and [rebuilt my CRM](/articles/salesforce-replacement-claude-crm-build), email management, and website myself. I use Perplexity to automate news curation to my phone. The total approach is hardware-once rather than subscription-forever. I describe it as owning my data rather than renting access to it from vendors. **What does AI actually model that humans have stopped doing?** In my experience, AI models unemotional, logical, consistent reasoning. It doesn't scroll, doesn't get distracted, and doesn't skip the follow-up. In my real estate career, it surfaced birthday and graduation outreach I had never built into my own workflow. The gap between what AI did on its own and what I had been doing manually was the clearest measure of my own standard. That same gap is what I explored when I started [building instead of subscribing](/articles/salesforce-replacement-claude-crm-build). **Can raising your standards with AI actually make you happier?** My view is that low standards produce discontent — not because of some abstract principle, but because low-standard work doesn't generate the satisfaction that comes from real output. Rebuilding my own stack on a Mac Studio made my labor joyful again. The chain is simple: higher standard → better work → more content life. The [objective thinking framework](/articles/objective-thinking-unlearning-relearning) I've described elsewhere is what made that chain legible to me in the first place. **Who should be building their own stack right now?** My answer is solopreneurs and entrepreneurs who are currently paying for SaaS tools they could own. My specific list: CRM, email management, website, and news curation. I frame a Mac Mini or Mac Studio as the entry point — hardware you own once, on which you build everything. The skill required is learning to prompt, reason, and code — not at an expert level, but at a builder level. **What is the connection between AI guardrails and personal standards?** AI guardrails are built-in limits that stop the tool from producing embarrassing, irrational, or harmful output. I draw a direct parallel to personal standards — the behavioral floors we hold ourselves to in professional and social contexts. When a tool has tighter guardrails than a person does, that person feels the gap as friction. The productive response is to close the gap from your side, not to lower the tool's floor. That's the same argument I make in the context of [content and vibe coding workflows](/articles/vibe-coding-pivot-content-engine) — the tool exposes your floor, and the floor is yours to raise. **What does the SaaSpocalypse mean for the average entrepreneur?** It means the cost of owning your stack is dropping toward zero for anyone willing to build. The subscriptions that once required a team to manage — CRM, email, content, analytics — can now be replaced by tools you build and host yourself on basic hardware. Entrepreneurs who make this shift stop being tenants of software and become owners of it. That changes both the economics and the mindset around their own work. **Why does AI feel threatening to people with lower work standards?** Because the gap is visible. AI doesn't perform at a moderate level that gives a low-standard worker cover — it reasons, follows up, and logs everything without distraction. That consistency makes any gap between the tool's output and a person's output hard to ignore. This discomfort isn't a bug in the technology. It's the most honest performance review most people have ever received. ## Frequently asked questions **Is AI resistance really about work standards, or is it about job loss fear?** Both are real, but Charles argues they're connected. Job-loss fear is loudest when someone's current standard of work is low enough that they can't imagine competing with a high-standard tool. Workers who take genuine pride in their labor tend to say "bring it on" rather than "not in my backyard." The fear and the standard are two sides of the same gap. **How did Charles replace his SaaS stack without a large team?** He used a Mac Studio as a local build machine and rebuilt his CRM, email management, and website himself. He uses Perplexity to automate news curation to his phone. The total approach is hardware-once rather than subscription-forever. He describes it as owning his data rather than renting access to it from vendors. **What does AI actually model that humans have stopped doing?** According to Charles, AI models unemotional, logical, consistent reasoning. It doesn't scroll, doesn't get distracted, and doesn't skip the follow-up. In his real estate career, it surfaced birthday and graduation outreach he had never built into his own workflow. The gap between what AI did automatically and what he had been doing manually was the clearest measure of his own standard. **Can raising your standards with AI actually make you happier?** Charles's framing is that low standards produce discontent — not because of some abstract principle, but because low-standard work doesn't generate the satisfaction that comes from real output. He says rebuilding his own stack on a Mac Studio made his labor "joyful again." The causal chain he draws is: higher standard → better work → more content life. **Who should be building their own stack right now?** Charles's answer is solopreneurs and entrepreneurs who are currently paying for SaaS tools they could own. His specific list: CRM, email management, website, and news curation. He frames a Mac Mini or Mac Studio as the entry point — hardware you own once, on which you build everything. The skill required is learning to prompt, reason, and code — not at an expert level, but at a builder level.