Field research · coherence architecture in practice
These are not testimonials. They are field research — honest accounts of what a coherence architecture engagement actually produces, what the yield looks like in practice, and what the pattern is across different kinds of founders and systems.
what you will find here
Every engagement is defined in advance. The work builds what the founder couldn't yet see how to build, trains the team on it, and departs. It is not an ongoing retainer — it is a designed completion.
The playbooks, the governance structures, the exit strategies — these continue to function after the engagement ends. The test of coherence architecture is whether the system holds without the architect present.
These engagements do not begin with applications or RFPs. They begin with a conversation between people who are operating at the same level and recognise something in each other's work.
The framework lands most deeply with founders who already sense the architecture of what they're building. The engagement names what they already know — and builds the structure that makes it operational.
field note 01
A founder with a working business, two strong right hands, and an exit instinct she hadn't yet named or structured. The engagement built the coherence architecture that made the exit legible, the governance distributable, and the business attractive to enterprise buyers at a level she hadn't previously accessed.
$500k
Immediate contract value — Rocket Money, Abbott, Celebrity Cruises
$6M+
Projected value in the 18 months following engagement
2 yr
Structured exit strategy — succession to two internal right hands
2×
Revenue doubled within the first six months of engagement
A two-year exit strategy with a clear succession path to two existing team members. A client development framework that made the business legible at enterprise scale — enabling the conversations with Rocket Money, Abbott, and Celebrity Cruises that had previously stalled at the pitch stage. A governance structure that reduced founder dependency across both arms of the business: incentive travel and the AI platform.
The founder's vision was already coherent. The engagement gave it structure and language. The playbook outlasted the engagement. The exit strategy is on track. The enterprise clients are active. What the founder built with 40 hours per month of coherence architecture would have required a full-time Chief of Staff, a fractional CMO, and a strategy consultant — simultaneously. The yield was a hundred-fold in the most literal sense.
field note 02 — the pattern across four corporate engagements
Coursera (2020-2022), Airbnb (2023), UX Content Collective (2022–2026), and a financial services organisation (2024) — four organisations that engaged with coherence architecture and then attempted to institutionalise what was built without the originating intelligence. Each engagement was treated as paid research into whether the framework applies at scale. It does. The pattern that emerged is now the framework.
Built the content ops infrastructure and design system that became the shared architecture across all cross-vertical teams. Millions of learners. Still in active use. Confirmed: the framework applies at platform scale. The challenge was not the work — it was the organisation's subsequent attempt to institutionalise what had been built without the person who built it.
Proposed and launched Airbnb's first internal AI model for the help centre — from strategy through training data, evaluation, and rollout. The first proof that the framework applies at AI/ML scale. The model is still in use. The engagement ended the same way: the IP became a role description. The pattern held.
Four years of Intro to Content Ops and AI Content Strategy workshops — training practitioners at Fortune 100 and 500 companies. A genuine collaboration under the original founder. When leadership transferred in Q2 2024, proposals were declined and derivative offerings built from my research and materials were launched without attribution. Requests for participant lists to support playbook implementation produced consistent disengagement. The clearest case study in what thorny ground looks like from the inside.
Value is recognised — then the system attempts to absorb it without the originating intelligence. The IP becomes a job description. The consultant becomes a candidate. The framework becomes a methodology attributed to the institution. This pattern is now documented, named, and is the reason the practice enters through relationship and invitation only.
a note on the nature of these engagements
Every engagement listed here ended with the system more coherent than it began — with or without the architect present. That is the test. The playbook holds. The governance distributes. The exit strategy is on track. The yield, in good soil, is always more than anyone predicted at the outset.
If you are a founder who recognises something in these field notes — the workshop begins at Step 0. No discovery call required. Steps 0 through 3 live on Techtuition. The field is always accessible.
Visit techtuition.ai →