Engagement
Five alliance shapes
Alliance is our word for how we sit beside your team — sprint, build, programme, system project or standing advisory. Each shape sets a different tempo and a different handover weight.
Positioning sprint
For leadership groups that need a shared sentence before a launch window. We compress interviews, territory drafts and decision sessions into a short, visible arc. Output is a positioning narrative and a record of what was rejected, so old debates do not reopen silently.
Narrative build
For companies whose story spans multiple offers or regions. We work chapter by chapter with named reviewers on your side. The alliance lasts through several draft cycles and ends with a master document your board can read without a presenter.
Editorial programme
For teams that publish on a rhythm — quarterly letters, monthly notes, seasonal campaigns. We design the programme, draft early editions alongside your writers, then transfer the charter so the voice holds when we step back.
Brand-system project
For organisations about to onboard partners or open regional offices. We document naming, templates, file conventions and the approval path for materials that leave the building. The alliance includes partner packs and a walkthrough for agencies.
Standing advisory
For marketing leads who want a consistent editorial eye. Reserved review slots, marked-up drafts, quick calls when a sentence feels wrong before it ships. Scope is bounded in writing so advisory does not become invisible production.
Choosing a shape
Shape follows friction. If the friction is indecision at the top, a positioning sprint may be enough. If the friction is volume — many pages, many writers, many partners — a brand-system project or editorial programme is usually the honest answer. We will say when a smaller alliance serves you better than a large one; reputation here is built on fit, not on maximising scope.
Alliances are agreed in writing before work begins. The document names deliverables, participants, review cadence, confidentiality expectations and what happens if timelines shift because internal approvals stall. We do not quote numeric fees on this site; numbers belong in proposals after we have read your materials.
Inside the room
Whether sprint or standing advisory, our alliances share habits: pencils on paper for first reactions, read-aloud for headlines, no anonymous feedback channels that hide ownership. We ask for a single decision-maker on your side even when many contributors review — otherwise drafts circle indefinitely.
Handover differs by shape. Sprints end with a narrative and decision log. Programmes end with templates and a seasonal calendar. System projects end with manuals and a partner call. Advisory continues until you end it with notice described in the agreement.
After the alliance
Most clients retain internal ownership deliberately. We celebrate when your writers no longer need us for every paragraph — that means the voice guide worked. Some return for the next launch or when a new region opens; others keep a thin advisory line. Both patterns are sound.
Questions about which shape fits your brief belong on the Matters page or in a direct note via Letter.
Timing and internal approvals
Alliance documents include realistic review windows. If your organisation needs legal or brand committee sign-off, tell us before dates are printed. We build slack for revision rounds rather than pretending first drafts are final. Rush requests are sometimes accommodated when scope is narrowed — fewer pages, fewer contributors — rather than when quality is compressed silently.
Standing advisory clients often keep a shared folder where drafts appear with a note field describing audience and deadline. That habit reduces back-and-forth and keeps the rose-clay marker of our comments easy to find among internal track changes.
Documentation alongside alliances
Every alliance ends with written confirmation of what was delivered, even when deliverables are intangible language assets. That habit protects both sides when staff change or when a partner asks why a phrase looks unfamiliar months later.
We note alliance shape on invoices only in plain language — sprint, programme, advisory — never in coded jargon that finance teams must decode separately from creative teams.
Blair Road · Outram