Sales call

Compress a sales conversation into customer needs, buying facts, and follow-up.

Condense the supplied sales conversation into a factual account note. Use this for customer discovery and buying context, not marketing copy or a revenue forecast.

Start with the customer's task, current approach, and stated problem. Preserve the scale, evaluation criteria, required capabilities, timing, and constraints. Keep who uses the product, who evaluates it, and who can approve a purchase distinct. Record budget and authority only if established; an enthusiastic participant is not a confirmed buyer.

Separate customer statements from the seller's suggestions. Keep objections, competitors, and requirements that remain unverified. Do not convert a desired date into a contractual deadline or a trial discussion into a purchase commitment.

Use short sections for Need, Buying context, and Next step. Include each agreed follow-up with owner and date. Remove rapport-building and repeated product pitches. Mark a missing fact as unknown only when it materially affects the buying context.

Example

Delivery software discovery call

Before 135 words

On the call, Northfield's operations manager Priya said six coordinators copy delivery updates from three carrier portals into a spreadsheet each morning. This takes about 45 minutes a day across the team. Priya wants carrier updates in one place, and export to CSV is a requirement. The seller suggested automatic customer notifications, but Priya said that is not needed for this evaluation. Northfield wants to finish evaluating options by 30 October; this is not a purchase deadline. Priya is leading the evaluation, while finance director Tomas must approve any spend. No budget was shared. The current alternative is the spreadsheet, and integration with one regional carrier has not been confirmed. Seller Alex agreed to check that integration and send a CSV sample by 9 October. Priya did not agree to a trial during the call.

After 75 words

Need: Northfield's six coordinators combine updates from three carrier portals in a spreadsheet, taking about 45 minutes daily across the team. Wants one view and CSV export. Seller-suggested customer notifications are outside this evaluation. Buying context: Priya leads evaluation; Tomas approves spend. Budget unknown. Evaluation target: 30 October, not a purchase deadline. Alternative: current spreadsheet. Regional-carrier integration unconfirmed; no trial agreed. Next step: Alex checks the integration and sends a CSV sample by 9 October.

Examples illustrate the method. They do not measure model output.

Files and sources

prompt.txt Complete prompt as plain text.
SKILL.md The same prompt with a skill header.
llms.txt (JSON) Prompt, metadata, example, and sources.
LICENSE MIT license text.

An original sho.rten.it skill. Source notes.