Inject client-specific context and tone
Final editorial pass that weaves the client's name, situation, and bespoke context through the narrative, adjusts tone to suit the relationship, and applies any agreed additions or omissions so the document reads as written for them, not batch-produced.
In / outAssembled artefact + client context notes → personalised, relationship-appropriate artefact
You might say…
“The content is solid — but it still reads like a template with names swapped in, not something written for this client.”
What it does
Final pass over the assembled artefact: weaves the client's name, situation, and bespoke context through the narrative and commentary, adjusts tone/framing to suit the relationship, and applies any agreed client-specific additions or omissions — so the document reads as written-for-them, not batch-produced. Used as the last edit before QA. Pure editorial judgement; must not alter analytical conclusions.
Trigger: Use as the last editing pass before QA, after all sections are assembled and reviewed.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation