Build or Replaced
Today: Claude for Small Business | Scorched Earth 2000 – Web | Linux gaming is faster because Windows APIs are becoming Linux kernel features Episode date: 2026-05-14.
Download MP3 →JOSH: It's Thursday, May 14. This is Build or Be Replaced — powered by ScanBrief.dev. I'm Josh, here with Erik Anderson. ERIK: AI isn't a tool anymore. It's staff. If you don't wire it into real work, somebody else will. [beat] JOSH: Stick around — Erik's got an AI pro tip at the end about building a model router that saves money without slowing down. [pause] JOSH: Three quick ones first. Anthropic rolled out Claude for Small Business. Is that actually a big shift, or just a nicer landing page? ERIK: Big shift. When the model ships with connectors and ready-made workflows, it stops being a demo and starts acting like a junior operator inside finance, sales, and support. [beat] JOSH: YellowKey hit BitLocker with a zero-day and the proof of concept is already public. How bad is that? ERIK: Bad enough that every admin should care today. Encryption is great until the boot chain hands the keys over too easily. [beat] JOSH: Cisco posted record quarterly revenue, then said it's cutting fewer than four thousand jobs to push harder on AI. What's the read? ERIK: Same story across tech. Revenue up does not protect repetitive work. Budget is moving toward AI infra, security, and the people who can actually build with it. [pause] JOSH: Start with Anthropic. Why does this one matter more than the usual product launch noise? ERIK: Because it changes where the battle is. For a while, AI was a tab. You opened Claude or ChatGPT, typed in a box, got some text, maybe pasted it into another system. That's useful, but it's not operational. Claude for Small Business moves it into QuickBooks, HubSpot, Google Workspace, Microsoft 365, PayPal, DocuSign. That's not "help me think." That's "help me do work where the records already live." [beat] JOSH: What's the difference for a normal business owner? ERIK: Blank box versus installed worker. That's the whole thing. Most owners don't wake up wanting to prompt engineer. They want the lead email answered, the CRM updated, the invoice checked, the calendar sorted, the overdue stuff surfaced. Early AI products dumped people into a text field and acted surprised when adoption stalled. A bakery owner or a small MSP doesn't want a research project. They want a lane. JOSH: So the lane is the product. ERIK: Exactly. Not the model. The lane. Prebuilt workflow, limited permissions, clear finish line. That's what sells. [beat] JOSH: People have been pitching integrations forever, though. ERIK: Yeah, and most of them were duct tape with nice branding. What's different now is the packaging got opinionated. Anthropic isn't saying "connect whatever you want and hope for the best." They're saying, here's finance, here's customer service, here's sales, here's ops. That's important because trust matters more than IQ once AI can touch money and records. JOSH: Less freestyle. ERIK: Way less. Freestyle is fun in a demo. Freestyle in accounting is how you buy the same software license twelve times. [beat] JOSH: Where does this land for people building custom systems? ERIK: It squeezes the shallow wrappers. Hard. If your startup is "we connected a model to Gmail and HubSpot," the platform vendors are already eating that category. You survive by owning the ugly edges. Approvals. weird data. audit trails. domain rules. all the stuff demos skip because it isn't sexy. JOSH: That's where your stuff lives. ERIK: Exactly. PrimeRouter exists because one model is not the answer to every task. A cheap extraction job doesn't need the same brain as a change plan touching production network configs. Routing matters. Permissions matter. Logging matters. If a model is drafting a reply, that's one thing. If it's updating a CRM record tied to revenue, that's another. If it's writing an NSO service change, now we're in a completely different risk class. [beat] JOSH: What do you mean by routing, in plain English? ERIK: Match the job to the brain. Small model for classification. Bigger model for synthesis. Local model for private low-risk stuff if you can get away with it. Human checkpoint before any action that can cost money or break trust. That's what PrimeRouter does in my world. It sends the right job to the right provider with failover and telemetry, instead of pretending every prompt deserves the expensive path. JOSH: And that saves real money? ERIK: Yep. People burn money because they treat all tokens like they're sacred. They're not. Most work is boring. Sort this. extract that. tag this. compare those fields. My Hermes box on the Mac M3 pushes around 70 tokens a second locally. That's great for certain classes of work. Then when I need a stronger model, PrimeRouter bumps it up. That is a systems problem, not a prompt problem. [beat] JOSH: Where do small teams mess this up? ERIK: Permissions first. They get excited and hand the model broad access because the first run looked clean. That's reckless. Give it read access before write access. Make it stop before send. Make it stop before payment. Make it stop before merge. PrimeBus taught me that one fast. A guardrail that blocks a bad action is not friction. That's the product working. JOSH: People hate hearing "add a checkpoint." ERIK: They hate it right until the wrong invoice gets approved or the wrong customer gets emailed. Then suddenly checkpoints look pretty smart. [beat] JOSH: If somebody listening runs a twenty-person company, what's the first use case? ERIK: Pick one ugly workflow with a boring finish line. New lead comes in, enrich it, score it, draft the response, create the CRM entry, stop. Or incoming invoice lands, extract fields, compare against PO, flag mismatches, stop. Don't start with "AI for the business." That's how you get a slideshow and no outcome. JOSH: Narrow lane. Clear stop sign. ERIK: Yep. Then review exceptions every day for two weeks. You want the mistakes. The mistakes show you the rails you forgot to build. [pause] JOSH: YellowKey. This one sounds like security people arguing over boot sequences while everyone else zones out. ERIK: They shouldn't zone out. This one matters because BitLocker is one of those things teams assume is handled. Check the box, move on, sleep better. YellowKey is a reminder that disk encryption is only as strong as the path that unlocks the disk. [beat] JOSH: The public summary made it sound like somebody can crack a protected drive with files on a USB stick. Is that real? ERIK: Real enough to change behavior. The details matter, though. It's not magic. It doesn't mean every stolen drive on earth is instantly open. Reports around the proof of concept say it relies on the target machine's TPM flow, and it doesn't work the same way if TPM plus PIN is enabled. That detail matters because lazy summaries make people either panic too much or ignore it completely. JOSH: So what's the practical lesson? ERIK: Convenience has a cost. TPM-only boot is convenient. User never types anything. Fleet rolls easy. But if the pre-boot trust chain gets abused, convenience becomes your weak point. If the laptop leaves the building, your threat model changes. Full stop. [beat] JOSH: What should infra teams do right now? ERIK: First, find out where you're using TPM-only BitLocker. Not next quarter. Today. Second, decide which devices deserve TPM plus PIN. Exec laptops. field laptops. anything that travels. Third, test recovery procedures before you roll a policy and brick your help desk with lockouts. Security changes that don't account for operations turn into their own outage. JOSH: That last part gets skipped a lot. ERIK: Constantly. People love saying "turn on the secure thing." Cool. Did you test escrow? Did you test remote recovery? Did you test what happens when Susan in accounting forgets the PIN in an airport lounge. Security without runbooks is theater. [beat] JOSH: How does this connect to AI? On the surface it doesn't. ERIK: It does, because we're about to hand more machines more authority. If your foundations are loose, adding agents on top is insane. Everybody wants the flashy part. Nobody wants to inventory pre-boot settings or map identity paths. But that's the work. In my setup, the event bus sees problems first. ScanBrief catches the external signal. PrimeBus distributes the event. Then a workflow can decide whether it's advisory, whether it's a ticket, whether it needs a human. The point is not "AI fixes security." The point is you need systems that react fast without guessing. JOSH: So security news becomes an event, not a memo. ERIK: Exactly. Memo culture is slow. Event culture moves. [beat] JOSH: Is this one of those stories where the fix is old-school discipline, not a new product? ERIK: Mostly, yeah. Better boot policy. better segmentation. better handling for traveling endpoints. better runbooks. Dry answer. Correct answer. The industry keeps wanting a magic box. Half the time the fix is "stop taking convenience discounts on security." [pause] JOSH: Cisco. This one hit close to your world. Record quarter. AI demand up. Jobs cut anyway. ERIK: Yep. And nobody in networking should pretend this is surprising. Cisco reported record quarterly revenue, up 12 percent year over year, then said it's cutting fewer than four thousand jobs while shifting investment toward AI, security, silicon, optics. That's not a contradiction. That's the map. [beat] JOSH: Explain that. ERIK: Companies are buying different value now. They still need networking. Probably more than ever. But they don't want armies of people doing repeatable manual work around that networking. If a task can be turned into a system, the system wins. Humans move up to architecture, policy, exception handling, and weird troubleshooting. Or they get cut out. That's the blunt version. JOSH: That's rough. ERIK: Rough, yeah. Also true. [beat] JOSH: What kind of work is most exposed? ERIK: Anything repetitive with clear inputs and expected outputs. Ticket triage. config audits. standard change generation. dashboard summaries. first-pass incident correlation. A lot of NOC work is sitting right in that lane. Same for a bunch of help desk flows. The teams that survive are the ones building the automations, not waiting to be assigned the old steps. JOSH: That's basically the show's title. ERIK: It is not a metaphor. [beat] JOSH: Does AI actually help that much in infra, or are people forcing it? ERIK: Helps a lot when you treat it like part of a system. Hurts when you treat it like a lucky rabbit's foot. In my home lab, everything automated means 229 cron jobs are already doing background work before I touch the keyboard. ScanBrief scores 396 items daily across 56 sources and lands at 6:30 AM. PrimeTrader watches 109 tickers in three batches an hour during market hours. That's the mindset. You build the rails first. Then AI slots into the spots where judgment or language is the bottleneck. JOSH: Not "ask a chatbot to run the company." ERIK: Right. That's comedy. Useful comedy, sometimes, but still comedy. [beat] JOSH: What does Cisco's move say about the market for engineers? ERIK: It says being good at one tool is not enough anymore. If all you know is the manual path, you're exposed. If you know Terraform, NSO, Python, APIs, event systems, model routing, maybe some Kubernetes, now you're useful in the new stack. The demand is shifting from operators who click to builders who wire. JOSH: That's a different career path. ERIK: Very different. And people need to stop waiting for permission. Nobody handed me a perfect environment and said, go build your bus. I built PrimeBus because I was sick of isolated tools. Everything needed to talk. Events in. actions out. agents subscribing. humans only where they add value. That's where the work is going. [beat] JOSH: Does that make the human less important? ERIK: No. It makes lazy human labor less important. Big difference. The human who designs the rails, defines the stop points, reviews the exceptions, and understands the blast radius? That person matters more, not less. JOSH: Wait, really? ERIK: Yeah. Somebody has to know when the machine is confidently wrong. That's high-value work. [beat] JOSH: And the people who don't move? ERIK: They're gonna have a rough couple of years. [pause] ERIK: This episode is sponsored by Prime Automation Solutions. If you're still doing it manually, we automate it. Also, special on a website — $250. primeautomationsolutions.com [pause] JOSH: Alright, what's the AI pro tip today? ERIK: Build a model router before you build a giant prompt library. Most teams do that backward. They spend weeks polishing prompts, then send every task to the same expensive model. Bad move. Start by labeling your work. Extraction. classification. summarization. planning. code review. long-context analysis. Then define a default model per class, a fallback model, and a hard rule for when a human has to approve output. [beat] ERIK: Keep the first version stupid simple. One YAML file is enough. Task type, primary model, fallback model, max cost, timeout, approval flag. Then log every call. Latency, cost, success, retry, who touched it. After a week, you'll know which jobs are overpowered and which ones are underpowered. [beat] ERIK: That's how PrimeRouter should be built in any environment. Not as "pick my favorite model." As traffic control. Cheap fast brain for cheap fast work. Bigger brain for high-risk synthesis. Local model where privacy and speed make sense. If one provider gets weird, fail over without drama. That's your tip. Use it. [pause] JOSH: Track your freedom score and net worth with the Freedom Blueprint app — free download, link in the show notes. [pause] JOSH: One more thing — we started a Discord for builders. If you're shipping AI, automation, or anything that makes a human obsolete — come hang out. Link at buildorbereplaced.dev. ERIK: Post what you built. We'll post what we're building. Real wins, real builds, no fluff. [pause] ERIK: Build or be replaced. JOSH: If you want these signals in your inbox every morning, scanbrief.dev. See you tomorrow.