Every tech company is running the same playbook: Salesforce for CRM, HubSpot for marketing, AWS for infrastructure, OpenAI for “AI,” Snowflake for analytics.

Then they wonder why they have no competitive advantage.

David Heinemeier Hansson saw this differently. When 37signals wanted to build an innovative email product, he didn’t fiddle with Gmail APIs. He built an email server from scratch. His logic: “If you want to do interesting things with email, you have to own the email server.”

Then he did something even more radical. He pulled everything off AWS. Spent $700,000 on Dell servers. Saved $2 million the first year. Will save over $10 million in five years.

A $350 mini PC costs $1,200 per month on Heroku for the same computing power. That’s not a service fee. That’s a stupidity tax.

The Rental Trap

Netflix’s recommendation algorithm drives 80% of viewing time. It saves them roughly $1 billion annually. Amazon’s generates 35% of revenue. TikTok’s is worth over $100 billion.

You can’t buy that from a vendor. You have to build it.

But most companies never will. They’re too busy configuring Salesforce and celebrating their “unique integration strategy.” Which is identical to everyone else’s unique integration strategy.

AI Changed Everything

Two years ago, “AI-powered” was a differentiator. Today, analysts openly ask: “Are you just an LLM wrapper?” Because if you are, you’re replaceable.

The models are commoditized. LLaMA is open source. If your competitive advantage is prompt engineering on top of OpenAI’s API, your competitor replicates you by Tuesday.

But here’s the twist: AI also makes building ridiculously easier. What used to take a team of specialists months now takes one good engineer with Claude or Cursor a weekend.

The barrier to creating proprietary technology is collapsing exactly when renting commodity technology becomes worthless.

The Death Spiral

There are 702 CRM solutions on G2. Not because we need 702 CRMs. Because CRM is so commoditized that nobody can differentiate. Everyone’s selling the same thing with different logos.

The SaaS vendors are trapped: You ship a feature. Competitors copy it in three weeks. Customers choose on price. Margins compress. Nobody wins.

Meanwhile, 37signals runs on servers they bought six years ago. Still working. Still paid off. Still compounding.

The Five-Year Test

Building sucks at first. It’s slower. Harder. Buggier.

But ask this: What would you have if you’d spent five years building things only you have?

The answer is the only real moat: proprietary technology so specific to your business that competitors can’t buy it, rent it, or copy it without years of work.

We’ve forgotten how to think this way. Quarters. Sprints. Annual OKRs. A decision that pays off in year four feels irresponsible.

But year four is where competitive advantage actually lives.

What Do You Own?

Ask your board: What technology do we own that competitors don’t?

If the answer is “our Salesforce configuration” or “our integration layer,” you own nothing. You’re renting shelf space.

Real ownership sounds like: “We built our own recommendation engine because nothing else could do real-time personalization at our scale. Our conversion rates are 40% higher than category average.”

Or: “We built our own data pipeline for sub-second latency. That’s why we do same-day delivery and competitors take three days.”

Buy commodity stuff. Email. Calendar. Video conferencing. Anything where different doesn’t matter.

But when something’s core to how you deliver value? When it’s why customers choose you?

Own it.

The CTOs who can still code, who understand infrastructure, who think in five-year horizons while everyone else thinks in quarters? They’re building companies that are genuinely hard to compete with.

The ones managing vendor relationships are running the same company as everyone else with a different logo on top.

You can’t rent a moat.

You have to build it.

Your engineering team gets GitHub Copilot, Cursor, Claude Code, and OpenAI Codex. Suddenly everyone’s writing code 40% faster. Three months later, you check the deployment schedule. Nothing’s changed.

Sound familiar?

Here’s what actually happened: Your engineers didn’t start shipping 40% more features. They started writing better tests. Refactoring more thoroughly. Exploring edge cases they used to ignore. The tool gave them superpowers, and they used those powers to raise their standards, not compress their timelines.

This isn’t a bug. It’s physics.

Subscribe now

In the 1890s, factory owners rushed to install electric motors. The technology was revolutionary - cleaner, more efficient, more powerful than steam. For 30 years, productivity barely moved.

Why? They bolted electric motors onto steam-era workflows. Same factory layouts. Same centralized power systems. Same assumptions about how work should flow.

The breakthrough came when they finally asked: What if we designed the factory assuming electric power existed from day one? Suddenly, small motors at every station. Work cells instead of assembly lines. Flexibility instead of rigid sequences. Productivity exploded.

Your AI tools are electric motors. You’re still running a steam factory.

Visit two Toyota plants using identical equipment. One produces flawless vehicles at remarkable speed. The other struggles with quality and delays. Same robots. Same tools. Completely different results.

Toyota’s edge was never the technology - it was making work visible. Standard processes that expose problems immediately. Andon cords that stop everything when something’s wrong. Workflows that assume problems will happen and build in rapid response. The magic is in the choreography, not the machines.

Your AI tools are making individual tasks invisible - completed in seconds instead of hours. But the work that matters - the coordination, the decisions, the reviews - is more opaque than ever.

When you give people capacity without direction, they don’t get faster. They get fancier.

• Engineers with AI assistants write more elegant code, not more code

• Analysts with automated models build more scenarios, not close more deals

• Writers with GPT craft more polished prose, not more prose

This isn’t laziness. It’s human nature meeting system dynamics. Work expands to fill the space you give it - unless you explicitly design it not to.

Every time you deploy a new tool, you face a hidden choice:

• Speed: Ship faster by holding quality constant and cutting scope

• Quality: Keep the same pace but raise the bar on what “done” means

• Scale: Do more things without changing timelines

• Efficiency: Do the same with fewer people

Most organizations never make this choice explicitly. So the system makes it for them, usually choosing quality by default. That’s why your tools feel transformative in demos but invisible in outcomes.

A calculator makes you faster at arithmetic immediately. No workflow change required. Why? The task is atomic - clear input, clear output, no coordination needed.

But AI isn’t replacing arithmetic. It’s replacing judgment calls, first drafts, analysis, synthesis - all tasks deeply embedded in workflows involving multiple people, multiple stages, multiple definitions of “good enough.”

The more complex the task, the more it depends on the workflow around it. And workflows are where good intentions go to die.

Stop asking “What can this tool do?” Start asking “What workflow does this tool assume?”

The teams that win with AI aren’t the ones with the best models. They’re the ones who rebuild their workflows assuming the capacity already exists:

• Product teams that ship daily because AI handles testing

• Finance teams that monitor real-time because data gathering is automatic

• Content teams that publish constantly because first drafts take minutes

They didn’t just add tools. They redesigned their entire operation around the new capacity.

Right now, your organization is sitting on 30-40% latent capacity from tools already deployed. You don’t need better AI. You need workflows that assume AI exists.

Pick one process. Find the real constraint (hint: it’s probably review or decision-making, not creation). Redesign the workflow to exploit your tools’ capacity. Change the metrics to reward the behavior you actually want.

Or keep waiting for the next tool to finally be the one that changes everything.

Spoiler: It won’t.

Your phone needs three satellites to find you. Answer engines like ChatGPT and Perplexity need three independent sources to trust you. Most brands have one, maybe two - and that's why they're invisible to your potential customers searching with AI.

Visitors from AI answers are 4.4x more valuable than organic search visitors. What took four customers now takes one when you become the cited answer. This isn't about ranking first; it's about being everywhere the model looks so you get pulled into the answer on repeat. In answer engines, trust is triangulated, not tallied. And, for now, you can't buy your way into these results.

Subscribe now

The audience is already massive. Traffic to leading chatbots increased over 80% year over year, and AI-generated answers now appear in over 13% of Google queries. That's 378 million globally, with 1 in 5 American adults using AI daily in 2025. The shift is bigger than the 2011 Google Panda algorithm update because the unit of competition isn't a ranked page - it's the model's citation set.

Who's already winning the triangulation game? Webflow went from near zero to 8% of signups coming from AI answers by making themselves the default example in "no-code web builder" answers across docs, community threads, and YouTube explainers.

Growth leaders like Graphite's Ethan Smith have been pounding this drum: five credible citations beat ranking #1 once. Local services show it too. Sparkly Maid NYC keeps showing up in AI-assisted local discovery because they're mentioned across Google Business profiles, neighborhood forums, and review sites: three satellites that let the model "locate" them as the answer.

Here's where it gets weird. Early-stage startups can win AEO faster than SEO. There are no ads to buy and no decade-old domain to overcome. If ChatGPT and Gemini see your product referenced in a legit community thread, some Reddit posts, a respected how-to blog, and your own crisp, answer-first help docs, you can leapfrog incumbents in the answer. LLMs reward corroboration over pedigree. Meanwhile, the places models forage change week to week; share of answers is volatile. The game is keeping three beacons lit, not camping on one keyword.

Skeptics aren't wrong about the messy parts. AEO is probabilistic; there's no stable "#1" to cling to. Zero-click results siphon clicks and muddle attribution. Optimizing for opaque models can feel less predictable and harder to optimize like throwing darts in the dark. But the market signal is unmistakable: when you become the model's consensus, the downstream conversions are worth the chaos.

The playbook is simpler than you think. Pick your highest-value search intents. For each one, make sure you show up in three places models actually trust: Reddit threads where practitioners discuss real problems, YouTube videos where people learn and compare options, and your own help docs—but written like Wikipedia, not a pitch deck.

This isn't SEO's "create great content and pray." It's deliberate beacon-planting. When someone asks about contract payroll, you need to be in that r/smallbusiness thread with actual screenshots. In that YouTube comparison video. In help docs that explain the whole category so clearly that models default to citing you.

Your product team is now your distribution team. Every changelog, API doc, and integration guide is potential training data. The winner isn't who ranks first—it's who becomes the model's mental model for the category.

GPS didn't ask Rand McNally to print better maps; it changed how location is computed. AEO isn't asking you to rank higher; it's asking you to be triangulated. Plant three beacons per question, keep them lit, and you'll show up where the answers are formed. In answer engines, trust is triangulated, not tallied. Where are your satellites?

Subscribe now

Every week, another breathless announcement. Another frontier model. Another company claiming AI will change everything. Meanwhile, teams six months into their "AI transformation" are discovering the real patterns: what breaks, what sticks, and what actually moves the needle.

Welcome to The Prompt Stack - where implementation meets reality.

What This Is

The Prompt Stack explores what happens after the demo, when the consultants leave, and the meter starts running. These are field notes from actual AI transformations: the gap between what vendors promise and what organizations ship.

Expect analysis on:

- Implementation patterns that survive contact with production

- Economic reality of AI adoption - who captures value and who pays

- Organizational physics - how AI actually changes power, workflows, and culture

- Technical truth without the hand-waving - what Claude, ChatGPT, and agents really do

This isn't another AI newsletter. It's a systematic exploration of how organizations build competitive advantage with generative AI - or fail trying.

What You'll Get

2x Weekly posts (typically Tuesdays and Thursdays) that dive deep on one transformative insight.

Recent topics:

- Why composable AI architectures beat monolithic platforms

- The hidden "complexity payment" in every AI strategy

- What developers discover after 6 months with Claude Code

- How AI creates new power centers in organizations

Practical playbooks in every post—3-5 concrete actions you can test within two weeks. No generic "embrace AI" nonsense. Specific moves tied to specific problems.

Real patterns, not press releases. Examples from actual implementations, with the friction and failure left in. The goal: help you see around corners in your own AI transformation.

Who This Is For

CTOs and technology leaders implementing AI at scale. Product managers building AI-native features. Strategy consultants who need to understand what's actually possible. Anyone tired of AI hype who wants to understand AI reality.

If you're looking for "10 Amazing ChatGPT Prompts," this isn't it. If you want to understand why some organizations get 10x returns from AI while others burn millions on pilots that never ship, you're in the right place.

The Stakes

The gap between AI leaders and laggards is widening. Not because of access to models - everyone has that. But because some organizations understand the implementation game: how to compose tools, orchestrate workflows, and capture value. Others are still buying "AI-powered" versions of the same software they've always used.

The Prompt Stack is about building the former, not becoming the latter.