Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.
/call-recap-formatAn AI SDR agent is only as good as the definition of a good customer it is working from, which is why the fit criteria belong in a written skill rather than buried in a prompt nobody can find.
/our-icpCRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.
/crm-field-conventionsQualification is a claim about evidence, not a score: a deal is qualified when every criterion has a source you can quote, and unevidenced criteria are named rather than filled in optimistically.
/meddiccA pipeline review is useful in proportion to how uncomfortable it is: the job is to find the deals that are slipping quietly, not to narrate the ones everybody already knows about.
/meddiccAn 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-icpAfter-call work is the twenty minutes nobody books: the CRM update, the recap, the follow-up, the task for the thing you promised — and it is the first work to disappear on a busy day.
/call-recap-formatEnrichment is worth automating only with a rule about what not to write: a contact record improved with three verified fields is more useful than one filled completely with two guesses.
/crm-field-conventionsPulling opportunity context is a summarisation problem with a trap: the useful answer is what changed and what is missing, not a recitation of fields the reader can already see.
/meddiccDeduplication goes wrong when merging is treated as the goal: the safe operation is to propose a merge with the evidence for it, because an incorrect merge is materially harder to undo than a duplicate.
/crm-field-conventionsA forecast is a claim about evidence, so the useful output is not a number but a split: what is evidenced, what rests on an assumption, and which single deal moves the quarter most if it slips.
/meddiccWrite the rule down as a skill. The single highest-value line in a CRM skill is the list of fields the model must leave blank rather than infer — budget, headcount, timeline, decision maker.
Yes. The skill describes the convention; the agent's tools do the writing, so the same field-conventions skill applies whichever CRM is connected.
Then you have a process problem, not a prompt problem. A skill that keeps growing because every exception needs another paragraph is the signal to go settle the convention first.