Tag: The Signal

  • I Built My Business on Google Cloud. Here’s What Happens If I Rebuild It Entirely on Amazon.

    The Thought Experiment

    Last week I published a piece on Amazon’s vertical sovereignty play in logistics. The thesis was simple: Amazon is building a stack so complete that once you’re in, leaving becomes structurally expensive. Several people reached out and asked the obvious next question — so what would it actually look like to go all-in?

    Fair question. I run my own infrastructure on Google Cloud. I chose that path deliberately, and I’ve written about why. But intellectual honesty requires stress-testing your own decisions. So here’s the exercise: take a real-shaped business and rebuild it entirely on Amazon’s stack. Not as a hypothetical. As a genuine evaluation of where Amazon is genuinely impressive and where the walls start closing in.

    Meet Ridgeline Services

    To make this concrete, let’s build a company. Ridgeline Services is a 22-person regional facilities management company operating across three metro areas. They handle commercial building maintenance — HVAC, plumbing, electrical, janitorial coordination — for property management firms. They have a small warehouse for equipment and supplies, a fleet of service vehicles, and a growing need for both cloud infrastructure and physical logistics.

    Ridgeline is the kind of mid-market services company that exists in every region of the country. They’re past startup chaos but not yet at enterprise scale. They have real operational complexity — scheduling, procurement, fleet management, customer communication, compliance documentation — and they’re growing fast enough that their current patchwork of tools is starting to crack.

    The question: what happens if Ridgeline rebuilds everything on Amazon?

    Layer 1: Cloud Infrastructure (AWS)

    This is where Amazon’s case is strongest, and it’s not particularly close.

    AWS remains the largest cloud provider by market share. For Ridgeline, the relevant services are straightforward: EC2 or ECS for hosting their job management platform, RDS for their PostgreSQL database, S3 for document storage (inspection reports, photos, compliance records), and CloudFront for their customer-facing portal.

    The honest assessment: AWS is excellent here. The breadth of services is unmatched. If Ridgeline’s CTO wants managed Kubernetes, it’s there. If they need a simple managed database, it’s there. If they want serverless functions for automated notifications, Lambda handles it cleanly.

    Where it gets interesting is AI. Amazon Bedrock gives Ridgeline access to foundation models from Anthropic, Meta, Mistral, and Amazon’s own Nova family through a single API. They could build an AI assistant that reads inspection reports, flags compliance issues, and drafts customer communications — all within their existing AWS environment. Bedrock’s Intelligent Prompt Routing can reduce costs by routing simpler queries to cheaper models automatically.

    Verdict: Genuine strength. AWS for compute and AI infrastructure is a defensible choice for a company like Ridgeline. The lock-in exists at the service level (good luck migrating a complex Lambda architecture to another cloud), but the value proposition is real.

    Layer 2: Procurement (Amazon Business)

    Here’s where the stack starts getting interesting. Ridgeline buys a lot of stuff — HVAC filters, plumbing fittings, electrical components, cleaning supplies, safety equipment, uniforms. Their current process is probably a mess of distributor accounts, local hardware store runs, and someone’s personal Amazon account with a company card.

    Amazon Business replaces all of that with a single procurement platform. Approval workflows so the warehouse manager can’t order without the ops director signing off on purchases above a threshold. Integration with accounting systems through connections to platforms like Coupa and SAP Ariba. Business Prime for free two-day shipping on eligible items. Guided Buying to surface preferred suppliers and products that meet organizational standards. Spend Visibility dashboards that show exactly where money is going across all three metro locations.

    For a 22-person company managing multiple locations, this is genuinely useful. The approval workflows alone solve a real problem — Ridgeline’s ops director currently has no visibility into what each location is ordering until the credit card statement arrives.

    Verdict: Genuinely useful, with a catch. Amazon Business solves real procurement pain for mid-market companies. The catch is that once your approval workflows, supplier preferences, and spend history live inside Amazon’s system, switching costs are high. Not because of a contract — because of accumulated organizational knowledge embedded in a proprietary platform.

    Layer 3: Logistics (Amazon Freight and Supply Chain Services)

    This is the layer that prompted the original sovereignty article, and it’s the one that changed most recently.

    In June 2026, Amazon opened its LTL freight service to all domestic destinations — not just inbound to Amazon facilities. Ridgeline can now use Amazon Freight to move equipment between their three locations, ship palletized supplies from distributors to their warehouse, and deliver materials to job sites. The service includes next-day live pickup for orders placed by 5 p.m., real-time GPS tracking from pickup through delivery, automated appointment scheduling at receiving facilities, and electronic proof of delivery.

    Amazon Supply Chain Services (ASCS), launched in May 2026, goes further. Ridgeline gets access to Amazon’s fleet of more than 80,000 trailers, 24,000 intermodal containers, and 100 aircraft. For a facilities management company that occasionally needs to move heavy equipment between metros or receive bulk supply shipments, this is infrastructure they could never build themselves.

    Companies like Procter & Gamble, 3M, and American Eagle Outfitters have already signed on to ASCS. Peter Larsen, VP of Amazon Supply Chain Services, explicitly compared the play to what AWS did for cloud computing — taking Amazon’s internal infrastructure and selling it to everyone.

    Verdict: Impressive infrastructure, sovereignty risk intensifying. The logistics layer is where the vertical stack thesis becomes most visible. Amazon is now your cloud provider, your procurement platform, and your freight carrier. Each layer is individually competitive. Together, they create an integrated dependency that would be extremely painful to unwind.

    Layer 4: Customer Communication (Amazon Connect)

    Ridgeline’s customer communication is probably a disaster. Property managers call a main office number, someone writes the request on a sticky note, and it may or may not make it to the right technician. For a growing company, this breaks fast.

    Amazon Connect — recently rebranded to Amazon Connect Customer — is AWS’s cloud contact center service. It handles inbound and outbound calls, chat, email, and task routing. In April 2026, AWS expanded the portfolio to include Amazon Connect Decisions for supply chain workflows and announced 29 agentic AI features including pre-built autonomous AI agents that can handle routine customer interactions without human intervention.

    For Ridgeline, this means a property manager calls in, an AI agent captures the issue details, checks technician availability against the scheduling system, and either books the appointment directly or routes to a human dispatcher for complex situations. The system integrates natively with other AWS services — the call transcript goes to S3, the AI processing runs on Bedrock, the customer record updates in their RDS database.

    Verdict: Powerful, and deeply entangling. Connect is a genuinely good contact center product. It’s also the layer where Amazon’s vertical integration becomes most seamless — and most difficult to extract. Your call recordings, AI training data, workflow automations, and customer interaction history all live in the AWS ecosystem. Moving to Twilio or a competing platform means rebuilding every automation from scratch.

    Layer 5: Payments (Amazon Pay and Business Credit)

    This is where the stack gets thinner. Amazon Pay is primarily designed for e-commerce checkout — letting customers pay on third-party websites using their Amazon credentials. It’s supported by more than 720,000 merchants, but it’s fundamentally a consumer checkout tool.

    For Ridgeline, which invoices property management companies for services rendered, Amazon Pay doesn’t solve the core problem. They need accounts receivable, net-30 invoicing, and integration with their accounting system. Amazon’s recent rebrand of “Pay by Invoice” to “Business Credit Account” shows they’re moving in this direction, but the offering is still oriented around purchasing from Amazon, not general B2B invoicing.

    Verdict: Gap in the stack. This is where the Amazon-only thought experiment breaks down for a services business. Ridgeline still needs Stripe or a traditional payment processor for customer invoicing, and QuickBooks or similar for accounting. Amazon hasn’t built the B2B financial layer that would complete the sovereignty loop for a company like this.

    Layer 6: The Integration Tax

    Here’s what you don’t see in any individual product evaluation: the integration tax paid by companies that don’t go all-in on one stack.

    If Ridgeline uses AWS for infrastructure, Amazon Business for procurement, Amazon Freight for logistics, and Amazon Connect for customer communication — those four systems talk to each other with minimal friction. Procurement data flows into spend dashboards that inform logistics decisions. Customer calls trigger workflows that check inventory levels sourced from procurement data. AI models trained on call transcripts improve the automated responses that run on the same cloud infrastructure.

    The moment Ridgeline picks a non-Amazon tool for any layer — say, Twilio for communications or a traditional freight broker for logistics — they inherit an integration burden. APIs to maintain, data to sync, authentication to manage, and failure modes that multiply with each connection point.

    This is the actual mechanism of sovereignty capture. It’s not that any single Amazon service is irreplaceable. It’s that the integrated stack creates compound convenience that makes piecemeal alternatives feel expensive and fragile by comparison.

    Where I Actually Landed

    After walking through this exercise honestly, here’s what I think:

    Amazon wins on logistics and procurement for a company shaped like Ridgeline. The combination of Amazon Business and Amazon Supply Chain Services solves real operational pain that mid-market companies currently address with duct tape and spreadsheets. No other single vendor offers this combination.

    AWS wins on breadth but not uniquely on depth. Google Cloud and Azure are legitimate alternatives for compute and AI. The choice between them is real, not a formality. I chose Google Cloud for my own stack because of Vertex AI’s model garden and the integration with Google’s broader ecosystem. Ridgeline could make a credible case for any of the three.

    The sovereignty risk is real but not uniform. Logistics and procurement lock-in happens through accumulated operational data and workflow dependencies. Cloud lock-in happens through service-specific architectures. Payments is the one layer where Amazon hasn’t closed the loop, which means Ridgeline still needs external financial infrastructure regardless.

    The honest conclusion: building entirely on Amazon is more viable in 2026 than it was even six months ago. The ASCS launch and LTL expansion filled the biggest gaps. But “more viable” isn’t the same as “advisable.” The same operational convenience that makes the stack attractive is the mechanism that makes leaving expensive. You’re not buying services — you’re joining an ecosystem. And ecosystems have gravity.

    That’s not a reason to avoid Amazon’s services categorically. Some of them — particularly ASCS for logistics — are genuinely best-in-class. The discipline is in choosing deliberately: use the layers where Amazon demonstrably wins, maintain alternatives where the switching costs are highest, and never mistake integration convenience for strategic advantage.

    The companies that thrive in this environment won’t be the ones that went all-in on any single stack. They’ll be the ones that understood which layers to rent and which ones to own.



  • The Signal: AI Just Split Into Two Lanes — Field Notes From June 10, 2026

    The Signal: AI Just Split Into Two Lanes — Field Notes From June 10, 2026

    The Signal is a daily AI intelligence briefing from Tygart Media — field notes from someone who builds with these tools 12 hours a day, not someone who reads press releases about them. Each edition distills the day’s most consequential AI and search developments into what they actually mean for agencies, small business operators, and builders shipping real infrastructure.

    June 10, 2026: The Day the Lanes Forked

    Today was the kind of day where you can feel the road forking under your tires. Not because one thing happened — because eight things happened simultaneously, and if you squint at the pattern, they all point the same direction: AI just stopped being a product category and started being infrastructure. The plumbing layer. The thing you build on top of, not the thing you buy.

    I’ve been building with Claude since the Haiku days. I run it 12 hours a day across 20+ WordPress sites, a five-site knowledge cluster on Google Cloud, and a custom schema engine I shipped yesterday. When the landscape shifts, I don’t read about it on TechCrunch — I feel it in the tooling. And today, the tooling lurched forward in a way that matters.

    Here’s the daily signal.

    Claude Fable 5: Mythos-Class AI Goes Public

    Anthropic launched Claude Fable 5 yesterday — the first publicly available Mythos-class model, a tier above Opus. Pricing is $10 per million input tokens and $50 per million output tokens. It’s the most capable model Anthropic has ever released to the general public, state-of-the-art on nearly every benchmark, and it comes with a fascinating constraint: queries on certain topics automatically route to Opus 4.8 instead, triggering in less than 5% of sessions. Anthropic is essentially saying: here’s the most powerful thing we’ve ever built, and we’ve installed guard rails at the edge cases where power becomes risk.

    For agencies and small business operators, the practical read is this: Fable 5 is included on Pro, Max, Team, and Enterprise plans through June 22 at no extra cost. After that, it comes off the subscription tiers. If you’re building workflows that depend on Mythos-class reasoning, you have 12 days to test whether the capability justifies the API cost — or whether Opus and Sonnet handle your actual use cases just fine.

    The real signal isn’t the model itself. It’s that Anthropic also doubled Cowork limits at no charge and shipped Claude Managed Agents in public beta. They’re not just selling you a smarter model — they’re selling you an operating system for delegating work to AI. That’s a fundamentally different product than a chatbot.

    Meanwhile, I Was Building the Infrastructure Layer — Not Reading About It

    While the tech press was writing headlines about Fable 5, I was elbow-deep in the kind of work that actually turns these models into business value. Yesterday, across a 14-hour session, my team — which at this point is me and a fleet of Claude instances — shipped three things that matter more to my clients than any benchmark score:

    1. bcesg-knowledge-api v1.5.0 — a custom WordPress plugin I built and deployed across BCESG.org that outputs a JSON-LD @graph array containing Article, FAQPage, Organization, WebPage, BreadcrumbList, Person (author), and speakable schema — all generated from 13 custom meta fields. This isn’t a schema plugin you install from the WordPress directory. It’s a purpose-built schema engine designed for one thing: making every page on the site machine-readable enough that AI systems cite it as an authoritative source. That’s Generative Engine Optimization at the infrastructure level, not the content level.

    2. WordPress 7.0 across the entire knowledge cluster. All five sites — bcesg.org, restorationintel.com, riskcoveragehub.com, continuityhub.org, and healthcarefacilityhub.org — upgraded from WP 6.9.4 to 7.0. Why does this matter? Because WordPress 7.0 ships the Abilities API: agent-to-agent communication endpoints. That means my Claude-powered content pipelines can now negotiate directly with WordPress about what they’re allowed to do, without me acting as the middleware. The cluster just became AI-native infrastructure.

    3. The stack around it. RankMath SEO installed with the schema module deliberately disabled — because the custom plugin handles schema, and two schema systems fighting each other is worse than none at all. IndexNow for instant search engine notification on every publish and update. Microsoft Clarity for behavioral analytics so I can see what humans actually do when they land on AI-optimized content.

    And here’s the detail that would have been impossible to explain six months ago: the peer review on the bcesg-knowledge-api plugin was done by Claude Fable 5 reviewing the code that Claude Opus wrote. AI reviewing AI’s code. In production. On a live WordPress cluster. That’s not a demo — that’s Tuesday.

    OpenAI’s S-1 and the $965 Billion Elephant

    OpenAI filed a confidential S-1 with the SEC. They’re going public. Meanwhile, Anthropic hit a $965 billion valuation. These two facts, side by side, tell you everything about where the money thinks AI is going: it’s going to be the most valuable infrastructure layer since cloud computing, and the market is pricing it that way before most businesses have figured out how to use it.

    For small business owners and agency operators, this isn’t abstract finance news. It means the tools you’re using today — Claude, GPT, Gemini — are backed by companies with enough capital to keep shipping improvements for years. The platform risk isn’t that these companies disappear. The platform risk is that you don’t build on them fast enough and your competitors do.

    AI Passed the Turing Test. Now What?

    A UC San Diego study published in PNAS confirmed that OpenAI’s GPT-4.5 and Meta’s Llama-3.1-405B both passed a standard three-party Turing test — with GPT-4.5 being identified as human 73% of the time when given a persona prompt, significantly more often than actual human participants. This has been treated as a milestone headline, and it is one, but the practical implication is more subtle than “AI can fool humans.”

    What it actually means: the content quality bar just moved permanently. If AI can produce text that’s indistinguishable from a human expert, then the only content that wins is content with something AI can’t fake — lived experience, proprietary data, operational specifics, the kind of “I shipped this yesterday and here’s what happened” detail that no model can generate from training data. This is why I write The Signal as field notes, not as analysis. Analysis can be generated. Field notes from the arena cannot.

    Chrome WebMCP: The Browser Becomes an AI Endpoint

    Google shipped the Chrome WebMCP API in Origin Trial for Chrome 149 through 156. The Model Context Protocol — the same protocol that lets Claude connect to external tools, databases, and APIs — is now a browser-native capability. Web applications can expose structured tool interfaces that AI models call directly.

    This is a bigger deal than it sounds. Right now, when Claude interacts with a web application, it’s either through a dedicated MCP server or through browser automation (clicking pixels on a screen like a human would). WebMCP means any web app can define a structured API surface that AI agents consume natively. For agencies building client tools, this is the moment your internal dashboards and client portals become AI-ready without a full backend rewrite.

    If you’re running WordPress sites — and 43% of the web is — this has direct implications for how AI agents interact with your content management layer. The gap between “website” and “AI-accessible knowledge base” just narrowed dramatically.

    The GPU Infrastructure Play: xAI Becomes an AI REIT

    Elon Musk’s xAI, home of Grok, is increasingly looking less like an AI model company and more like a GPU real estate investment trust. They’re partnering with both Anthropic and Google to provide compute infrastructure. This is the clearest sign yet that the AI industry is stratifying into two distinct layers: model companies (who build the brains) and infrastructure companies (who build the data centers those brains run in).

    For builders, this is good news. More compute supply means more pricing competition means lower API costs over time. The $10/$50 per million tokens for Fable 5 today will look expensive in 18 months.

    The Security Layer Nobody’s Talking About

    HashiCorp announced Boundary for agentic AI — access security specifically designed for AI agents that need to authenticate across multiple systems. And MemPalace shipped a local-first AI memory system with 96.6% recall accuracy and 29 MCP tools for Claude Code.

    These aren’t headline products. They’re infrastructure connective tissue. When AI agents can securely authenticate across your entire tool stack (HashiCorp Boundary) and maintain persistent memory across sessions (MemPalace), you stop using AI for one-off tasks and start using it as a persistent operational layer. That’s the transition my agency is making right now — from “Claude helps me write articles” to “Claude runs the content pipeline while I focus on strategy.”

    What This All Means: The Two-Lane Highway

    Here’s the pattern I see when I lay these signals side by side:

    Lane 1: The AI product lane. This is where most people are. They use ChatGPT to draft emails. They ask Claude to summarize documents. They treat AI as a productivity tool, like a faster Google or a better autocomplete. This lane is getting crowded, commoditized, and — with the Turing test results — increasingly indistinguishable from one provider to the next.

    Lane 2: The AI infrastructure lane. This is where the alpha is. Custom schema engines. Agent-to-agent communication via the WordPress Abilities API. Browser-native MCP endpoints. Persistent AI memory. Secure multi-system authentication for autonomous agents. This lane is where you stop using AI and start building on AI — where it becomes the foundation layer of your operations, not an add-on.

    The gap between these two lanes is widening every day. Today’s eight signals all point the same direction: toward a world where the businesses that win aren’t the ones that use AI tools the best, but the ones that build AI infrastructure the fastest.

    I’m building in Lane 2. Yesterday it was a custom schema engine and a WordPress 7.0 cluster upgrade. Today it’s field-testing Fable 5 as a code reviewer. Tomorrow it’ll be whatever the next signal demands.

    The question isn’t whether AI is going to transform your industry. That’s settled. The question is whether you’re in the arena building the infrastructure, or on the sidelines reading about people who are.

    — Will Tygart, Tygart Media

    Frequently Asked Questions

    What is Claude Fable 5 and how does it differ from Claude Opus?

    Claude Fable 5 is Anthropic’s first publicly available Mythos-class AI model, released June 9, 2026. It sits a tier above Claude Opus in capability, priced at $10 per million input tokens and $50 per million output tokens. Fable 5 is state-of-the-art on nearly all tested benchmarks and includes built-in safeguards that route certain queries to Opus 4.8, triggering in less than 5% of sessions. It’s available free on subscription plans through June 22, 2026.

    What is the Chrome WebMCP API and why does it matter for businesses?

    The Chrome WebMCP API, now in Origin Trial for Chrome versions 149 through 156, brings the Model Context Protocol natively into the browser. This allows web applications to expose structured tool interfaces that AI models can call directly — eliminating the need for dedicated backend integrations or browser automation. For businesses running web-based tools, dashboards, or WordPress sites, this means your existing applications can become AI-accessible without a full rebuild.

    What is the WordPress 7.0 Abilities API?

    The WordPress 7.0 Abilities API provides agent-to-agent communication endpoints, allowing AI-powered systems to negotiate capabilities and permissions directly with a WordPress installation. This transforms WordPress from a content management system into AI-native infrastructure where automated pipelines can query what operations they’re authorized to perform without human middleware.

    What does AI passing the Turing test mean for content creators?

    A UC San Diego study published in PNAS found that OpenAI’s GPT-4.5 and Meta’s Llama-3.1-405B both passed a standard three-party Turing test in 2026 — GPT-4.5 was identified as human 73% of the time with persona prompting. For content creators, this permanently raises the quality bar — the only content that wins is content with elements AI cannot fake: lived experience, proprietary data, operational specifics, and first-person field reports that no model can generate from training data alone.

    What is Generative Engine Optimization (GEO) and how does it work?

    Generative Engine Optimization is the practice of structuring web content so AI systems — including ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews — cite, reference, and recommend it. GEO involves entity enrichment, structured data (JSON-LD schema), authoritative citations, and machine-readable formatting. Unlike traditional SEO which targets search engine crawlers, GEO targets the large language models that increasingly mediate how users discover information.

    How should small businesses approach AI infrastructure in 2026?

    Start by moving from Lane 1 (using AI as a productivity tool) to Lane 2 (building AI into your operational infrastructure). Practical first steps include implementing structured data and schema markup on your website, setting up AI-optimized content pipelines, ensuring your site is crawlable by AI systems via protocols like LLMS.txt, and testing agentic workflows where AI handles multi-step operational tasks autonomously rather than single-prompt interactions.

    What is a custom schema engine and why build one instead of using plugins?

    A custom schema engine is a purpose-built WordPress plugin that generates structured data (JSON-LD) tailored to specific business objectives — in this case, AI citation optimization. Unlike off-the-shelf schema plugins that generate generic markup, a custom engine outputs precisely the entity relationships, author signals, and speakable content markers that AI systems use when deciding which sources to cite. The bcesg-knowledge-api plugin generates a seven-type @graph array from 13 custom meta fields, providing a level of control that no general-purpose plugin offers.

    What is the significance of AI reviewing AI-written code in production?

    When Claude Fable 5 peer-reviewed code written by Claude Opus for a production WordPress plugin, it demonstrated a mature AI development workflow where different model tiers serve different roles — one for generation, another for quality assurance. This mirrors human development practices (developer writes, senior reviews) but at machine speed and cost. It’s a practical example of how AI agent collaboration is already operational in real business infrastructure, not just research demos.

    The Signal is published daily on Tygart Media by Will Tygart. Each edition distills the day’s most consequential AI, search, and technology developments into actionable intelligence for agencies, small business operators, and builders shipping real AI infrastructure.