Draft a considered written reply
Composes a substantive written response to a client question, stating a clear point of view, the reasoning, and the recommended next step.
In / outClient question or situation update, engagement context → considered reply (POV + reasoning + next step)
You might say…
“They don't need another nuanced 'it depends' — they need my actual view, with the reasoning they can use.”
What it does
Reads the client's question or situation update and composes a substantive written response that states a clear point of view, the reasoning behind it, and the recommended next step. Used for any async question where the deliverable is a message, not a document or call.
Trigger: Use for any async question where the deliverable is a direct written reply rather than a document or call.
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