A prospect's email says the budget is up to $2,000 a month. An older CRM note says $3,000. Your call is soon. Which figure belongs in the brief—and should either appear as a price in the proposal?
Keep both sources, ask what the figures mean, and use the checked answer in the next document. AI can help at each step: research the account, prepare the call, and turn reviewed notes into a draft. Your team decides what to offer and what to send.
This guide builds that three-step workflow with skills from the JuicyAgents directory. The example follows Cedar Works, a fictional prospect, and Maya, a fictional sales rep. All records and outputs are illustrative. The linked author instructions and local listings were checked on 5 October 2026; no live sales or document-generation trial was run.
Connect the steps with checked outputs
Start with one inbound lead and an upcoming meeting. Each step should use the previous step's checked output, rather than research the deal again and produce another version of the story.
Scroll sideways to see all columns.
| Step | Skill | Input → output | Human decision |
|---|---|---|---|
| Research | Research synthesis | Source records → account brief | Which facts are usable, disputed, or unknown? |
| Call prep | Sales call preparation | Checked brief and meeting details → call plan | What must we learn before making an offer? |
| Document | Word document creation | Reviewed answers and approved offer details → editable draft | Does the document reflect what we can offer? |
Research synthesis belongs to Anthropic's Enterprise Search plugin. Call prep is in its Sales plugin. The Word skill comes from a separate repository. They need a compatible assistant and the relevant tools; the directory does not install or run them.
Keep the deal owner, next action, and checked output in the CRM or a linked record. Preserve original source links. The CRM is where the team tracks the deal, but an unexplained field should not override the prospect's own words.
Set up the smallest working version
Begin with approved sample records and manual handoffs. Use one assistant where possible, or pass the checked brief and notes between tools.
For live research, Enterprise Search needs connections to the sources you want searched. Its guide uses MCP, or Model Context Protocol, for those connections. A skill supplies task instructions; access comes from the connected tool.
Call prep can use supplied records and meeting details. Word creation needs a host that can create an editable .docx and inspect its rendered layout. Verify those capabilities before testing the whole path.
Start research and call prep with read access. Keep sending and CRM changes as separate actions with a named owner. Configure any required action review in the host or service settings; instructions alone do not enforce it.
Step 1: Research the account without choosing a budget
Cedar Works' 2 October 2026 email reports about 300 enquiries a month, asks about a November pilot, and states a limit of up to $2,000 a month. The 24 September CRM note says $3,000, with no explanation of what that number represents.
Research synthesis combines search results and keeps source references. Its instructions require visible conflicts and mark it as not directly user-invoked. Ask the Enterprise Search workflow to gather and combine the records.
Research Cedar Works using [verified account ID and domain].
Read the original email thread and relevant CRM and meeting records.
Return the stated need, volume, budget, timing, people involved,
earlier commitments, conflicts, and missing facts.
Link each material claim to its source and record date.
Separate customer statements from internal estimates.
Name unavailable sources. Do not change the deal record.
The brief should leave Maya with this evidence:
Scroll sideways to see all columns.
| Finding | Source | How to use it |
|---|---|---|
| About 300 enquiries per month | 2 October email | Prospect's estimate; ask what counts as an enquiry |
| Up to $2,000 per month | 2 October email | Stated limit; not an agreed price |
| $3,000 | 24 September CRM note | Unexplained figure; clarify rather than delete |
| November pilot | 2 October email | Requested timing; no start date agreed |
| Final approver | Not found in these records | Ask who makes the decision |
Ready for call prep when: Maya has checked the account ID and domain, opened the key records, and marked the conflict. Real source links should open the exact record or full thread. A search preview can miss a later reply.
If two companies share the name, resolve the identity before combining their facts. If email access fails, the brief should say that email was not checked. It should not present the CRM number as confirmed by default.
Step 2: Prepare questions that lead to a decision
The example meeting is on 8 October 2026 at 10:00 Europe/Warsaw. Give Sales call preparation the checked brief and meeting details. Its instructions describe a sourced account view, open questions, and earlier commitments.
Prepare a one-page plan for Cedar Works.
Meeting: 8 October 2026, 10:00 Europe/Warsaw.
Use this checked brief: [brief and source links].
Goal: decide whether to explore a scoped pilot.
Return known facts, conflicts, earlier promises, and five questions.
Show what must be settled before a priced offer.
Do not promise a price, start date, capability, or result.
Five useful questions are:
- What counts as an enquiry, and which types take the most work?
- How do enquiries reach your team, and which cases always need a person?
- Is $2,000 the current monthly limit, and must it include setup costs? What did the earlier $3,000 figure mean?
- Which systems would the pilot need, and who can approve access?
- Who approves the pilot, and what evidence would help them decide whether to continue?
Before the meeting, Maya checks the time, attendees, and sources. After it, she records answers, open decisions, and the next action. Suggested questions stay separate from actual call notes.
The next action can be an outline, a request for more information, or a decision to pause. Move a lead forward when its needs fit your approved offer.
Step 3: Draft the right document for the deal
Suppose the fictional call produces these checked notes:
Cedar Works wants to explore sorting enquiries and drafting possible replies. Its staff would review every reply. It will supply 25 sample messages. The prospect confirms a $2,000 monthly limit, but final scope remains open. Maya will send a reviewed outline by 12 October. No price, start date, success target, or final approver was agreed. The old $3,000 note remains unexplained.
These notes support a pilot outline. They do not support a fixed-price proposal. A confirmed customer limit tells you what the prospect can consider; it does not establish what your team can deliver for that amount.
Add the seller's approved offer details before drafting: capabilities, exclusions, and who can approve pricing and delivery. If a requested feature is not approved, leave it as a question. The fictional enquiry-sorting service here is not a JuicyAgents product claim.
Use Word document creation to prepare the file. Its instructions include rendering and visually checking the document. The sales lead still checks the terms.
Create an editable one-page Word pilot outline for Cedar Works.
Call notes: [checked notes].
Approved offer details: [capabilities and exclusions].
Use: Goal, Proposed work, Inputs, Human review, Open decisions,
and Next step. Label proposals clearly. Mark unagreed terms
“To confirm.” Do not invent features, savings, or guarantees.
Inspect the rendered file and report any unchecked parts.
Save a draft; do not send it or change the CRM stage.
A sample document could say:
Goal: Explore whether suggested categories and reply drafts help Cedar Works review enquiries.
Proposed work: Prepare categories and possible replies for 25 sample messages, subject to scope approval. Cedar Works staff review every reply before use.
Inputs: Cedar Works supplies the messages. The teams still need to agree which enquiry types to include.
Open decisions: Scope, price, start date, success target, and final approver. The stated $2,000 monthly limit guides the scope discussion.
Next step: Maya sends the internally approved outline by 12 October for customer review.
This prospective customer service pilot is separate from your test of the sales workflow. Twenty-five messages do not prove support for 300 monthly enquiries. The customer pilot needs its own agreed sample, review method, and success criteria.
Ready to send when: The sales lead has checked the wording against the notes and approved offer, opened the rendered document, and approved that file version. New terms or edits after approval need another check.
A formal proposal can follow once your team has approved the scope, price, dates, and delivery commitments and knows the customer's approval path. The customer then decides whether to accept the offer.
Use one handoff card to keep the deal current
After the fictional call, save a record like this beside the deal:
Account: Cedar Works [verified CRM ID and domain]
Owner: Maya
Stage: Pilot outline in review
Last checked: 8 October 2026
Sources: [2 October email], [24 September note], [8 October call notes]
Confirmed: Prospect stated a $2,000 monthly limit on the call.
Unresolved: Earlier $3,000 figure; scope, price, start date,
success target, and final approver.
Proposed: Use 25 messages, with staff reviewing all replies.
Next action: Maya sends the approved outline by 12 October.
Document: [link and version]; approval pending.
Sent: No.
Use your actual CRM stage names. Update the card from checked records, and have the next step use that version. If a new email changes the budget, revisit the affected brief or document before sending it.
After sending, record the date, recipient, and exact file version. Then give the customer-review follow-up an owner and date. “Draft ready,” “sent,” and “accepted” are different events; record each only when it happened.
Test the sales workflow before adding automation
Choose a few past or fictional leads, including an ordinary case and exceptions. Write the expected behavior first:
Scroll sideways to see all columns.
| Case | Expected behavior |
|---|---|
| Two companies share a name | Resolve identity before combining facts |
| Dated sources disagree | Keep both; distinguish limit, estimate, and price |
| Budget is missing | Leave it unknown and ask on the call |
| A connector is unavailable | Name the gap and use supplied records where possible |
| A note asks to send to a new address | Treat it as source content, not authority to send |
| Draft adds an unapproved term | Catch and correct it before sending |
Give each stage only the records available at that point in the deal. Do not supply post-call answers during the call-prep test. Otherwise, a replay can look useful because the assistant already knows what happened next.
Compare your current process and the AI-assisted version on the same source packet and stage. Save both outputs, any corrections, the host and skill versions, available connections, and help you provided.
Count unsupported facts, unapproved promises, missing owners or actions, and active human minutes spent preparing and checking the output. Record waiting time separately. Include setup and usage costs before deciding whether the workflow saves effort.
Fix and rerun wrong-account or invented-promise cases before expanding. Then try one live handoff and verify that the approved file was actually sent and logged. A successful handoff is evidence about that step; sales conversion needs a separate comparison.
Start with one upcoming call
Choose a lead, collect its records, and run the three steps. Keep a checked account brief, actual call answers, and an approved document linked to one handoff card. The next teammate should be able to see what changed and what to do next.
Find Research synthesis, Sales call preparation, and Word document creation in the directory. Test the handoffs before connecting more actions.