An account plan is worth the hour only if it names the one unknown that would most change your approach — everything else in a plan template is decoration you will never re-read.
/our-icpA QBR earns the meeting only if it says something the customer does not already know, which means leading with what changed on their side rather than with your usage charts.
/proposal-structureOnboarding fails on dependencies rather than on effort, so the skill worth writing is the one that names what you need from the customer, by when, and what happens to the date if it does not arrive.
/call-recap-formatAnswering from documentation is safe only with an explicit rule about the boundary: say what the docs say, cite where, and escalate rather than reconstruct an answer that is not written down anywhere.
/our-writing-voiceIt can define what risk looks like for your product — a sponsor leaving, usage dropping in a specific workflow, a support pattern — so an agent watching accounts knows what to flag.
The structure and the bar for each section, especially what to do when the numbers are bad. That is the part every generic QBR template skips.
Only for usage-based signals. Most CS skills work from the CRM, the calendar and the inbox.