Every AI-native services firm has a name on its method. The naming is the moat.

Open Every's Compound Engineering essay. The method runs in four named steps — Plan, Work, Assess, Compound — and Every ships a Claude Code plugin so any team can install the loop on their own repo. Pace's Sequoia announcement names its version AOPs, Agent Operating Procedures, framing the work as converting a firm's Standard Operating Procedures into a system an agent can run end-to-end. Decagon's customer-support product page uses the exact same vocabulary in a different vertical.

Three AI-native services firms in three different verticals — Every in software engineering, Pace in insurance ops, Decagon in customer support — all do the same unusual thing on their public site: they publish a named operating method as the actual artifact. If you are deciding how to position a services firm in 2026, this convergence is the story. The naming is not a brand-voice flourish. It is doing four jobs at once: shortening the sales cycle (a buyer reads the method before the call), attracting operators who already share the worldview, justifying productized pricing (the buyer is buying a documented system, not hours), and making the firm defensible against generic competitors that cannot easily be lined up on a comparison page. The naming is the moat.

The smuggled assumption inside every "we use AI" agency pitch is that delivery is invisible — that what AI is actually doing inside the engagement is the agency's private business and the buyer should trust the result. Named methodologies break that assumption open by putting the messy middle on the page.

The four jobs the naming does

Sales-cycle compression. A buyer who reads the published method walks into the call halfway-pitched. Crosby has a public agent architecture — a paralegal-tier agent routing the work, with junior- and senior-associate-tier agents in the build pipeline, and human attorneys holding the judgment. The buyer arrives knowing the model. The discovery call is about fit, not explanation. Marked-up contracts come back in under an hour because the architecture, not the headcount, is doing the work.

Operator-talent attraction. Services firms with named methods recruit the operators who already think in that vocabulary. Compound Engineering attracts engineers who already work in agent loops. AOPs attracts ops people who think in SOP-converted terms. The naming pre-filters the candidate pool — and it does it for free.

Productized-pricing justification. When the method is named and published, hourly billing becomes incoherent. Crosby ships per-document pricing instead of billable hours. That is not consulting; it is a documented system priced like a product. The 4As "Agency as Marketing Purveyor" thesis maps the same pattern at industry scale — productized services and licensed IP, not bespoke retainers.

Defensibility against generic competitors. A generic "we use AI" agency cannot easily be compared against itself, because there is nothing on its page to compare. A named method gives the buyer a comparison axis. The named-method firm wins the comparison by default — there is no comparison page for the agencies without one.

The published methodology landscape (May 2026)

Compound Engineering — Every. Plan → Work → Assess → Compound. Public chain-of-thought essay plus a GitHub Claude Code plugin teams can install. The fourth step exists so each loop teaches the next one — the system is what compounds, not the headcount.

Agent Operating Procedures (AOPs) — Pace and Decagon. Two different verticals (insurance ops and customer support) using the same vocabulary, both publishing the explainer. Pace's Series A announcement frames the move as converting insurance SOPs into AOPs that agents can run end-to-end. Decagon's product page positions AOPs as the architectural commitment under their entire customer-support agent platform.

Workflow ownership — Harper. Series A announcement publishes the thesis: an AI-native brokerage that owns the workflow end-to-end, achieving roughly 30x revenue per sales rep versus traditional brokerages. The architecture is the product.

Hierarchical agent architecture — Crosby. Paralegal-tier agent triages the work, junior- and senior-associate-tier agents are in the build pipeline, attorneys hold the final judgment. Marked-up contracts in under an hour. The structure is published; the comparison axis is the structure.

Lifecycle marketing as an AI-native engagement — Propel (trypropel.ai). Direct Leanboat-lane peer. AI ingesting brand data, auditing the customer journey, surfacing the biggest revenue leaks, building flows that go live in roughly a week. The methodology is not branded with a single name on the homepage, but the engagement structure is documented at every step on the public site.

Codified Engagement — Leanboat. The artifact is the per-client CLAUDE.md — a codified file the agent reads on every invocation, paired with an MCP stack tuned to that client, named approval gates where human judgment lives, and a kill switch when something goes sideways. Same architecture as Compound Engineering and AOPs. Different domain.

Where the pattern breaks down

The naming is sometimes ahead of the product. Some firms publish a method that is more brand page than delivery system. The test: is the method documented down to artifacts a buyer could actually verify — config files, plugins, runbooks, public guides? Compound Engineering passes — the plugin is on GitHub. AOPs passes — both Pace and Decagon publish the architecture in detail. Some 2026 "we have a methodology" agency pages do not. The reader should not be impressed by a name without an artifact.

Methodology naming alone is not a defense. A named method that is not anchored in a primary-source artifact (paper, plugin, public guide, runbook) is a brochure. The defensibility comes from the pairing — the name plus the published artifact plus the citations from independent third parties using the same vocabulary. Pace got to defensibility because Decagon also publishes AOPs. Compound Engineering got to defensibility because Every shipped the GitHub plugin.

Vocabulary will commoditize. AOPs already showed up in two verticals within months of Pace's launch. The first-mover advantage on a name is real, but it has a half-life. The compounding asset is the proprietary data that accumulates under the name (per-client CLAUDE.mds, AOPs, Compound runbooks) — not the name itself. The name opens the door. The data behind the name is what keeps it open.

The convergence is the actual story

AOPs at Pace and Decagon. Compound Engineering at Every. Codified Engagement at Leanboat. The hierarchical agent architecture at Crosby. Workflow ownership at Harper. Forward Deployed Engineer pods, the broader pattern in software services. These are not six different things. They are six vocabularies for the same shift: services firms publishing the messy middle of their work as a documented, named system, then pricing the system instead of the hours. The naming is the moat because it forces the firm to actually have the system in writing — and once it is in writing, the buyer can read it, the operator can recruit on it, the pricing can index to it, and the next firm without a name has nothing to put on the comparison page.

If your services firm cannot name its operating method in two words in May 2026, the gap is not a marketing gap. It is an operations gap. The marketing is downstream.