How an engagement works · designed and proposed

Fixed shapes, fixed prices, designed to be absorbed.

Each engagement has a fixed scope, a fixed duration and a fixed price agreed before it starts. Each one is designed so that the team who ran it can carry it on without us. That is the point: proof that travels with the work, not a dependency on the people who introduced it.

01 · Readiness check

Where your workflow can carry proof today.

A short audit of the path your marketing work already takes, from brief to reporting, to find where a receipt could be attached now with no change to the tools, where a small change would open the path, and where the gaps are. You get a map of your current path, a list of the joins, and a sequenced plan for the first proof.

Duration: Two to three weeks.
What you give: Access to two or three people who run the work day to day, one live campaign to walk, and the reporting you already use.
What you get: The path map, the joins, the first-proof plan, and a plain-English note of what is designed, what is proposed and what is already true in your stack.
Price: Fixed price, quoted on the call.
Status: Designed. Offered now as a consultancy engagement; no software is sold.

02 · Proof pod

Ninety days inside your own flow.

A proof pod, embedded in your existing production flow, that signs assets at render, carries the pointer through activation, and returns the receipts as work moves. At the end you get a three-meter report: human contribution, infrastructure contribution, and outcome, on one view, with the receipts behind every line. The pod is fixed price and IP-shared. It is designed to be absorbed: the handover is part of the scope, not an extra.

Duration: Ninety days in three phases: attach the mark, return the echo, read the measure.
Who is in the pod: Stewards work in pods. There are three pods: people, consulting architect, and engineering. A pod is a minimum of three stewards; pods inter-harness to another pod. Our people, consulting architect and engineering pods sit alongside theirs. Each pod has journals and terminals, and syncs to the central archive via overnight inter-harness. Designed and proposed.
What you get: Signed assets in your own flow, receipts through activation, the three-meter report, and a team of your own who can run it on.
Price: Fixed price, quoted on the call, with the handover included.
Status: Designed and proposed. The signing rails rest on open content-credential standards; no vendor is named or required.

03 · Partnership rail

A provenance pattern your teams can reuse.

For organisations that must carry proof into many accounts or workflows without becoming dependent on the people who introduced it. We bring a governance line (how exceptions are governed, how consent becomes evidence, how the boundary between private and decision-ready is drawn) and a provenance rail your delivery teams can apply again. Our stewards sit alongside yours. The proof stays with the organisation that did the work.

Shape: Shared delivery. Named steward on each side. Reporting agreed up front.
What you get: The governance line as a document your teams can use, the rail as a repeatable delivery pattern, and a proof pod as the worked example.
Commercials: Agreed per engagement: consultancy at a fixed price or day rate for the delivery we do with you.
Status: Proposed. No partners, clients or vendors are named here by design.

Before any of it

Watch the explainer first. It is two minutes and it carries the whole mechanism, with an evidence ledger that says exactly what is designed, what is proposed and what has been observed. Watch the explainer.