Tech With Tam
All work

Telepathic follow-up from one client call

  • sales systems
  • buyer intelligence
  • follow-up

The problem

Normal follow-ups summarize what was discussed but lose the buyer's exact language, quiet hesitation, absent decision-makers, and the one move most likely to advance the relationship.

What I built

A draft-first sales skill that runs a fact pass before interpretation, confidence-tags every read, writes one goal-led follow-up in the seller's voice, and preserves what changed across calls.

The output

A draft follow-up email, a three-line next-call brief, and an append-only deal log that tracks confirmed, changed, and newly surfaced buyer signals.

Why it mattered

The seller gets a concrete next move without pretending that one transcript is the whole truth or exposing private inferences to the buyer.

A recap is not a next move

Client calls contain explicit requests and quieter evidence: a phrase repeated three times, an enthusiastic response to one idea, a polite "this is great" that may still be a soft no, or a stakeholder whose absence changes what can be decided.

A generic recap records the meeting. It rarely decides what the follow-up must accomplish or what the seller should verify before moving forward.

What the skill actually does

Telepathic Follow-Up begins with one sales or client transcript. It can run with the transcript alone, or in a connected mode with an authorized email thread, meeting record, and existing deal context.

The order is deliberate:

  1. Identify the buyer, seller, and decision context.
  2. Run a fact pass for exact language and stated needs, with no interpretation.
  3. Run a separate inference pass for unspoken needs, anxieties, intent, drivers, and decision readiness.
  4. Attach evidence and confidence to every read.
  5. Turn missing information into one concrete question for the next call.
  6. Name the email's single goal, draft it, and cut everything that does not serve that goal.
  7. Match the seller's real voice, then return the draft for review.
  8. Save the three-line brief and append what changed to the deal log.

The load-bearing rule is simple: said does not automatically mean true. A verbatim quote proves that someone used the words. It does not prove their internal state. That distinction keeps a polite reassurance from becoming a false buying signal.

Evidence artifact

One call, three operator artifacts

A fully fictional demonstration from the skill's test fixture. No client transcript or identifying detail is used.

Source evidence

“The future of the business depends on our people. I want to make sure we're giving them really great coaching.”

“Moving everything into a new tool is a whole thing. I don't want to blow up what the team already has running.”

Draft follow-up

Subject: The team coaching build

Hey Tom and Nate,

Good call today. The team coaching piece is where I'd start too.

You already have the raw material in the RAM reports, questionnaires, and transcripts. I'd turn that into one living file for each person, so you're not scrambling before every check-in.

We can build it beside TrackThat. Nothing has to move until the new setup earns it.

I'll send over a one-page first version before our next conversation so you have something concrete to react to.

More soon,
Jordan

Three-line next-call brief

The one thingDo thisClose this gap
Their real driver is better coaching, not new software.Lead with the living coaching record and keep the current tool in place.Confirm the migration concern with the person who owns the existing system.

The judgment encoded in the email

The buyer-facing email never exposes the private analysis. It does not say, "You seem afraid of switching tools." It addresses the concern sideways by proposing a parallel run with no forced migration.

The email also mirrors the buyer's own language rather than translating it into the seller's preferred pitch. It contains one request, not a menu of possible next steps. A mandatory voice pass removes generic AI phrasing and matches the seller's established cadence.

How the system compounds

The first call creates a deal-log snapshot. Each later call appends a dated delta:

  • what the new conversation confirmed;
  • what changed or became less certain;
  • which new stakeholder, anxiety, or deadline appeared;
  • what still must be verified directly.

The system does not freeze a buyer's state from one call. It preserves the evidence trail so the seller can see movement over time.

Evidence artifact

The trust boundary

The skill is intentionally draft-first. Connected actions are optional and authorization-bound.

The skill mayThe skill may not
Quote and confidence-tag a signalPresent an inference as settled truth
Draft an email in the seller's voiceSend the email automatically
Suggest a next step grounded in the callInvent proof, metrics, deadlines, or commitments
Append a buyer-state deltaOverwrite the history of earlier calls
Update approved deal fields in connected modeCreate duplicate deals or mutate unapproved records

The useful outcome is inspectable: one focused follow-up draft, one glanceable brief, and relationship memory that improves with each conversation. The seller, not the skill, decides what is true, what is appropriate, and what gets sent.

Want your follow-up to carry the real signal from the call?

If this made you think of a workflow in your own business, bring me the messy version. We'll map what is happening, where judgment matters, and whether there is a useful next move. No pitch deck. No pressure.