Annotate a client artefact with inline judgement
Reads a client-submitted deck, memo, or model and returns inline comments plus a covering note flagging what is strong, weak, and what to change.
In / outClient artefact (deck, memo, model) → inline annotations + covering note (strong/weak/change)
You might say…
“They needed more than typo fixes — they needed to know which argument the board would pick apart.”
What it does
Reads a client-submitted deck, memo, or model and returns inline comments plus a short covering note flagging what is strong, what is weak, and what the advisor would change. Used the moment a discrete artefact lands for review.
Trigger: Use the moment a discrete client artefact arrives for review, when the deliverable is annotated feedback rather than a rewrite.
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