One principal, many hands

How a small studio ships like a larger one — and why the practice itself is the proof of the change we accompany.

At a glance

Subject. How YawningHero works in the new work environment — not a client deliverable, the studio’s own operating rhythm.
Shape. One principal. Coding agents on the building and the analysis. Human judgment on framing, taste, and what is allowed to ship. Review gates between.
Worked example. Three family sites repositioned and rebuilt in a concentrated week in August 2026 — positioning lock, bilingual copy, assets, and live publish.
What it is not. A product pitch. The same pattern holds whether a company ends with a platform, a process, or neither.

The claim

The shift companies are living through is not only new tools. It is new work: who decides, who drafts, who reviews, how long a passage of work is allowed to run before someone intervenes. A change companion that only shows finished surfaces is incomplete. The third proof has to be how the work is made.

We use ourselves as the case. Nobody can fake their own practice for long.

How we actually work

One human owner of the thesis. Dr. Jürgen Wöckl sets the frame: positioning, what is in and out of scope, the register of the voice, the risk that would embarrass the brand. That role does not scale by adding account managers; it scales by making the frame so clear that agents can execute inside it.

Agents on the long middle. Research passes, draft copy, code edits, asset path fixes, bilingual mirrors, structural hygiene across sites — the volume work that used to need a small team. Agents draft; they do not own the claim. When they invent or over-sell, the human stops the ship.

Review gates, not vibe. What ships is decided by rules the studio already holds: bare product names where the canon says bare, product-agnostic voice, trademark lines, honest deferrals. Agents accelerate compliance; they do not invent new rules mid-passage.

Long passages over thrash. The unit of work is a coherent multi-day (or multi-week) passage with a locked brief, not a scatter of half-hour tickets. That is the same rhythm we recommend to clients under change: fewer interrupts, clearer ownership, agents as throughput, humans as judgment.

The worked example

In one concentrated August 2026 week the family moved through a full positioning and surface pass:

  1. Decisions first — who each domain is for, what claims are allowed, what is deferred.
  2. Surfaces for machines — agent-readable structure and content layer (see the AXO case).
  3. Surfaces for people — editorial rebuild and shared register across the three sites.
  4. Publish under load — bilingual EN/DE, asset consistency, live validation — agents on the bulk edits, the principal on tone and cuts.

The point is not speed for its own sake. It is that a one-person craft layer plus agents can hold a multi-site family without looking like a design shop that only ships decks.

What we used / What we skipped

What we usedWhat we skipped
Coding agentsHeadcount
Review gatesHurry
Plain filesTools that did not fit
GitCeremony for its own sake

Judgment made visible. The same discipline we bring to client work: use what fits, skip what does not.

What clients actually hire

The same pattern transfers:

  • Frame — what must stay true when the tools get louder.
  • Passage design — where humans stay in the loop, where agents run, what “done” means.
  • Surfaces — so the company stays legible to people and to machines while it changes.
  • Operate — selective roles when the engagement is to run something, not only to describe it.

We recommend the tool that fits — including no product at all. A media agency shows what it made. A change companion shows how it works. This case is the second kind of proof.

Published · Updated