Est. somewhere between RE: and FW:

Your email is too simple.

For twenty years the industry has pursued clarity, brevity, the empty inbox. We ask the braver question: what if, instead, more? We are the world's first email complication practice. We take a clean thread and give it texture.

Discretion assured. Discretion then forwarded to eleven stakeholders for visibility.

74
average replies per delivered thread
1,206
stakeholders looped in per engagement, minimum
0
decisions reached to date. Our record stands.
scope

Practice areas

Six disciplines. One deliverable: more.

Each engagement is bespoke, layered, and reply-all by default.

01

Reply-All Strategy

We identify the precise moment a private aside becomes everyone's business, and we engineer that moment to arrive early and often.

02

CC Architecture

A bespoke hierarchy of people who must be kept in the loop about the loop. Includes loop governance, loop stewardship, and a loop steering committee.

03

Subject Line Drift

By reply three, the subject no longer describes the contents. By reply nine, it describes a lunch. This is craft, and we are its custodians.

04

Attachment Versioning

final_v2_FINAL_revised(3)_USE-THIS-ONE.docx, as a service. Provenance available on request. Provenance is also versioned.

05

Thread Forking

One conversation becomes five. None conclude. Each privately believes it is the main thread. We nurture this belief in all five.

06

Out-of-Office Orchestration

Cascading autoreplies, tuned to answer one another across time zones, indefinitely. Our most self-sustaining product. It is running right now.

Methodology

The Tangle Framework™

Three phases. No exit criteria, by design.

Phase 01

Discovery

We audit your correspondence and locate the threads at risk of resolving. Risk is everywhere, once you know how to look.

Phase 02

Entanglement

Stakeholders are introduced. Context is removed. A calendar invite appears, recurring, with no agenda and nine optional attendees, all required.

Phase 03

Sustainment

The thread achieves self-sufficiency. Nobody can leave, and, crucially, nobody remembers entering. Our work here is done. Our invoice is not.

Live engagement

A thread, maturing in real time.

Observe a routine question entering its productive phase.

inbox · engagement #0044 · VagueCorp● live

Results

Selected engagements

"They CC'd my predecessor, my successor, and a man named Cláudio whom none of us have met. Cláudio now chairs the steering committee."

Director of Alignment, Hazely

VagueCorp, all-hands announcement. Engaged to complicate a two-line memo. Delivered a 340-reply thread spanning four time zones and a public holiday. The original question was never identified, let alone answered.

REPLIES: 340 · FORKS: 5 · DECISIONS: 0 · RETAINER: EVERGREEN, RENEWS BY REPLY-ALL

VagueCorp's identity-resolution vendor reports the engagement also produced "measurable downstream ambiguity." We bill for that separately.

Questions

Asked frequently. Answered at length, elsewhere, in a thread.

We are contractually, constitutionally, and emotionally unable.

Engagements do not end. They are handed over, with ceremony, to a successor thread. The successor thread has questions, which is how the next engagement begins.

Our fees are communicated by email, across several emails, none of which contains the number. The number is in an attachment. The attachment is the wrong version.

complicated.email is a working mail domain. Somewhere beneath this practice, a person simply sends and receives messages. We have advised against it in writing, several times, in one thread.

Ready to make it complicated?

It already is. You simply have not been CC'd yet. We can fix that today, and we will keep fixing it, daily, forever.

Response time: immediate, then contradictory.