CRM Entry Writer

The reason CRM hygiene fails is friction. A 10-minute writeup after every call doesn't happen, so the field gets left blank or filled with "good call." Two weeks later the deal stalls, the rep needs to rescue it, and there is nothing useful in the record. This skill collapses the writeup into the time it takes to paste in raw notes — whatever shape they're in.

The structure is six categories: metadata, key discussion points, deal intelligence, commitments, next steps, and a stage recommendation. The deal-intelligence layer is the real value — anyone can summarise a call, but extracting "they mentioned evaluating two competitors" as a risk signal, or "champion has no direct line to the CFO" as an authority gap, is the part that changes how the next call gets prepped. Buyer signals, risk signals, budget signals, timeline, champion, decision maker — each surfaced as its own line rather than buried in prose.

Commitments get their own table with deadlines on both sides. Missed commitments kill deals, and a CRM entry that lists "us: send proposal Friday / them: confirm with legal by Tuesday" is harder to forget than three paragraphs of recap. Next steps are specific actions with owners and dates — "follow up soon" is rejected and replaced. The stage recommendation is honest: if the deal is stalling, the skill says so rather than letting optimistic pipeline forecasts build on wishful notes.

Gaps get flagged explicitly. If the raw notes don't mention budget, the entry says "Budget: not discussed" and adds it to the suggested questions for the next call. Nothing gets invented. And anything the prospect shared off the record is held back by default with a flag to the user — because the CRM is for future-you and your team, not for the prospect to ever read.