Sales is a memory-driven game running on systematically broken memory. By the end of a busy day, a rep cannot reliably tell you what was said in their first call that morning, let alone the third call last Tuesday. The CRM gets updated when the rep has time and motivation — which is to say, when the deal is going well. Hard calls, ambiguous calls, and calls where the rep is unsure of the read are exactly the calls that do not get logged. The failure isn’t effort. Reps work hard. The failure is that the unit of work — the deal — runs across many calls and many weeks, and human memory is not built for that timescale. This guide is a specific instance of the workflows pattern, applied to sales conversations. It pairs with the action items workflow — the next-step extraction at the bottom of every sales artifact is a specialized version of that workflow.Documentation Index
Fetch the complete documentation index at: https://docs.tryearmark.com/llms.txt
Use this file to discover all available pages before exploring further.
What the artifact looks like
A worked example — a first discovery call with a mid-market prospect, using MEDDPICC:The template that produces it
Save this as a workspace template. The version below is MEDDPICC-shaped; the dimension swap for BANT, SPICED, or CHAMP is mechanical — replace the section labels and keep everything else.Save it as a workspace template
Start from the Client Call template
The
Client Call built-in template is the closest starting point. Add it as a task from the template library and run a real discovery call through it.Rework into MEDDPICC shape in the Composer
Open the artifact in fullscreen. In the Composer, iterate the prompt toward the structure above — the Stated/Implied/Unknown discipline, the MEDDPICC sections, the single-next-step enforcement, the champion checklist. Watch the preview reshape until the artifact reads like the worked example.
Swap the framework if you don't use MEDDPICC
If your team uses BANT, SPICED, or CHAMP, replace the MEDDPICC section labels with your framework’s dimensions. The rest of the prompt stays the same. Consistency matters more than the choice — a mixed-framework pipeline is worse than a consistently-applied weaker framework.
Save with Workspace visibility
Open the Composer menu and choose Save as template. Set visibility to Workspace so every rep on the team produces the same shape. See Custom templates for permissions.
Run it on a single call
Pre-seed the meeting
Open the call in Earmark before it starts and add your saved Sales Discovery template as a task. See Before a meeting.
Use Customize context for prior-call carryover
For follow-up calls, paste the CRM update and the Risk signals from your last call with this account into the Customize context dialog. The template will read it and produce an artifact that reflects what changed since last call, not a cold first-call view.
State commitments and next steps out loud
Two habits sharpen the artifact dramatically:
- “Our next step is X by Y — agreed?” before the call ends. If the buyer hesitates, that hesitation is a signal worth capturing.
- “So we’re saying we’ll send the security questionnaire by Thursday.” Beats implicit handoffs.
Three-minute cleanup
Within the hour, before the next call:
- Read the Stated / Implied / Unknown tags. The model is sometimes optimistic. If it tagged something as “stated” that you wished the buyer had said, downgrade to “implied” or “Unknown.”
- Check the champion read honestly. If the model called the champion “Strong” but you cannot point to specific advocacy behaviors, downgrade. Champion overestimation kills more forecasts than any other failure.
- Confirm the single next step. If no real next step was agreed — the buyer said “let me get back to you” — write that. Do not invent a next step that was not agreed.
- Flag risk signals the model missed. Hesitation, vague language, evasion on budget — these often live in tone the transcript does not fully capture. Add them.
- Finalize the CRM update text. This is what gets pasted.
Push to the CRM same day
Paste the CRM update block into the opportunity activity log. Update stage, next-step field, forecast close date, and stakeholder contacts. The full Earmark artifact stays in Earmark — the CRM gets the curated summary with a link back, not the full transcript. A sales workflow whose outputs do not reach the CRM the same day is not a workflow.
Variations
Same skeleton, two close relatives.Demo and technical evaluation
For demo calls, POCs, technical deep-dives, and pricing discussions. The shape shifts because the conversation centers on fit, objections, and reactions rather than discovery. Add a section after Pain:Win/loss debrief
After a deal closes — won or lost — run this on the post-decision call with the buyer. A 15-minute call one to two weeks after the decision is the highest-fidelity source of information about what actually drove it. Most prospects will take this call if you frame it neutrally.What this workflow doesn’t do
Earmark generates and refines artifacts within a single call. The two natural next things a sales team wants — deal-level synthesis across all calls in an opportunity and manager-level pipeline aggregation — are not one-click actions inside Earmark today. Practical workarounds:- Manual deal-level rollup before major moments. Before an executive sponsor meeting, a pricing conversation, or a forecast call, the rep pastes the CRM update and Risk signals sections from the last three or four call artifacts into a single Customize-context block, then runs a synthesis prompt that produces a current state-of-deal view. Fifteen minutes of work; produces an artifact comparable to what the original “Template C” would have produced automatically.
- Use the command menu (
Cmd+K/Ctrl+K) to find prior calls with the same account when assembling the rollup. - Export local transcript files when you want to run an external agent across an entire deal’s worth of calls and produce a true synthesized rollup.
- The CRM is the deal-level aggregator. If every call’s CRM-update block lands in the opportunity activity log, the CRM is the place to see the deal’s history. The rep’s job is to feed the CRM faithfully; the manager’s filters in the CRM are what produce pipeline visibility.
Common pitfalls
- Skipping the cleanup on hard calls. The calls where reps skip cleanup are the calls where the artifact is most valuable — hard calls contain the signals that predict deal risk. Run the cleanup harder on hard calls.
- Champion overestimation. A champion is not someone who is nice to you. If you cannot point to specific advocacy behaviors, downgrade the strength read.
- Inventing next steps. “We’ll circle back” is not a next step. If no real next step was agreed, write that. A deal with no agreed next step is a deal in trouble.
- Hearing what you want to hear. Buyers say “interesting” and “we’ll think about it” because it’s easier than saying no. The Risk Signals section is where you catch yourself.
- Treating discovery as a one-call event. MEDDPICC dimensions get filled in over multiple calls. “Unknown” on call one and still Unknown on call four is a different problem than “Unknown” → “Strong read” by call four. Track the trajectory by using Customize context to carry prior reads into the next call.
- Single-threading. A deal with one contact at the buyer is a deal at high risk regardless of how strong that contact is. The multi-threading section forces you to confront this.
- Logging only the good news. Reps reflexively log deals going well and skip deals going badly. The opposite is correct. Hard deals are where the artifact most needs to exist.
- Letting deals age in stage without a fresh rollup. A deal in “Demo” for five weeks needs a fresh deal-level synthesis (the manual workaround above). Otherwise it’s running on stale signal.
- Skipping win/loss on lost deals. Lost deals contain more useful information than won deals. Default Template D on every closed deal above a low ACV threshold.
- Pasting the full artifact into the CRM. The CRM gets the curated CRM update block. The full artifact lives in Earmark, linked from the CRM entry. Pasting transcripts into CRMs is what makes nobody read them.
- Wrong framework dogma. If your team uses BANT and the template says MEDDPICC, swap the labels. The workflow does not care which framework — only that you use one consistently across every deal.
Where to go next
- Workflows — the general shape this is an instance of
- Custom templates — visibility, sharing, and edit permissions
- Before a meeting — pre-seeding and using Customize context for prior-call carryover
- Action items workflow — the next-step extraction this workflow specializes; useful for non-sales calls too
- Email follow-up workflow — for the external customer follow-up email that goes out after a call
- Customer research workflow — for the pain-points and verbatim-quotes side of customer conversations

