Discover. Expose. Wire. Operate.
Every engagement runs the same four moves. Read this and you'll know what happens in each one, what you'll experience, and what you walk away with.
Move one: Discover.
Discover is a structured inventory of what your company knows: where truth lives, where it's duplicated, and where it's forgotten. It takes one to two weeks and ends in a map your leadership signs off on.
We read your systems the way an agent would: the CRM, the site, the docs, the automations, the folders nobody admits to. Every source of truth gets logged with an owner, a freshness, and a trust level. Duplicates and contradictions get flagged, not fixed. Fixing comes later; Discover is about seeing.
What you experience: interviews that feel short because we arrive having read everything public, and a working session where your team argues about which system is right. That argument is the deliverable working.
What you walk away with: the intelligence map. One artifact showing what you know, where it lives, and which of it a machine could read today.
Move two: Expose.
Expose makes your knowledge legible. Content gets structure, data gets schema, process gets written down. At the end, a machine asking a fair question about your company gets a correct answer.
This is where the Surface and Voice work happens: answer-first pages, schema on every claim, your brand codified as a prompt system, your positioning stated once and reused everywhere. It's also where internal knowledge gets the same treatment, because your agents will read it before your buyers do.
What you experience: writing and structure decisions at a pace that feels aggressive, because we're not inventing content. We're converting what Discover found into forms machines can cite.
What you walk away with: pages that answer, a voice system every tool loads, and internal knowledge that stops depending on who's in the room.
Move three: Wire.
Wire connects the layers: every tool reads from the kernel, every signal writes back to it, and nothing depends on a human ferrying data between systems. It's the move most teams skip, and the reason the method holds.
Skipping Wire is why AI pilots die. A company can have a clean CRM, good content, and a paid agent license, and still run on copy-paste, because nothing is connected. Wire is integrations, MCP servers, workflow automation, and the unglamorous mapping decisions that make one record the record.
Wire is also where the work stops being reproducible by the next vendor. Anyone can write pages. Anyone can configure a CRM. The specific graph of connections between your systems, tuned to your process, is the part a competitor can't copy from your website, because it isn't on your website.
What you experience: fewer meetings, more short approvals. Wiring is detailed work with visible checkpoints: this connector live, this signal flowing, this manual step retired.
What you walk away with: a stack where data moves because it's wired to, not because someone remembered. Retired spreadsheets are the receipt.
Move four: Operate.
Operate turns the wired stack into a running system: agents with owners, reviews with cadence, and reporting that reads from one truth. It's the move that never fully ends.
Agents get deployed against the clean kernel with governance from day one: a named owner, a scope, a log, a review loop. Reporting shifts from what happened to what to do next. Your team learns the operating rhythm, because the goal is their system, not our retainer.
What you experience: the first boring week. An agent answers correctly, a report updates itself, and nobody had to do anything. Boring is the success state.
What you walk away with: an operating cadence, a governed agent roster, and a team that can run the platform without us. Ongoing partnership is available; dependence isn't the product.
Do the moves always run in order?
Yes, but they overlap. Expose starts while Discover is finishing, and Wire begins wherever the kernel is already clean enough. What never works is starting at Operate. An agent deployed against an unmapped, unwired company automates its confusion, which is the failure mode most teams have already paid for once.
Can we do just one move?
Single-layer engagements exist, and they still run all four moves scoped to that layer. What we won't do is a Wire-only project on a company that's never done Discover, because wiring unmapped systems hardens the mess. Engagement shapes covers how the scoping works.
What does 90 days actually include?
The first full pass: Discover complete, the revenue-critical parts of Expose and Wire live, and Operate started with at least one governed agent or automated report in production. It doesn't mean everything is done. It means the platform exists and compounds from there.