Inject client-specific context and tone
Packaged know-how that tells an agent how to do a job well.
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 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.
Trigger: Use as the last editing pass before QA, after all sections are assembled and reviewed.
I/O: Assembled artefact + client context notes → personalised, relationship-appropriate artefact
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