# Give the next prospect meeting a decision worth attending

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Name the unresolved buying question — Account representative — The outstanding question is report exclusion behavior, not general interest.
- Offer a bounded next contact — Sales coordinator — The prospect can choose a written comparison or a focused walkthrough.
- Agree the return condition — Account lead — The next live meeting is tied to reviewer feedback or a specific unresolved question.

## Workflow questions

### Does pausing a meeting mean abandoning the prospect?

No if the next evidence route and contact responsibility are agreed.

### When is another demo useful?

When it addresses a named question with new relevant evidence, rather than repeating the product tour.

### Can TeamBoost manage this follow-up?

Use the documented task owner and task context to track the unresolved review question and next contact work. This does not establish a native CRM, sales pipeline or customer email integration.

## Job to be done

When the prospect’s reviewer has not answered, I want the next contact to resolve a real comparison so we do not use another demo as a substitute for evidence.

A weekly prospect demo is still booked although the internal reviewer has not checked the report exclusion example. There is no new comparison to discuss.

### Recognizable symptoms

- Calendar recurrence is mistaken for buying progress.
- The same demo is repeated while the actual reviewer remains absent.
- Artificial urgency replaces a useful evidence request.

### Shortcut that fails

A broader feature tour cannot answer the specific exclusion question waiting on the prospect’s reviewer.

### Before

Let’s keep the weekly demo and show more features.

### After — invented worked answer

Next-contact note: the reviewer’s exclusion feedback is still pending. Send the bounded comparison and ask whether a focused exclusion walkthrough would help. Pause the recurring general demo by agreement; resume a meeting when the reviewer has a specific question or decision-ready feedback.

### Conditional next moves

- If There is no new decision-ready evidence: Offer an agreed written update or pause. Recurrence alone is not a meeting purpose.
- If A specific question needs demonstration: Arrange a focused comparison. Keep claims within demonstrated coverage.
- If The reviewer prefers a live discussion: Agree its question and output. Meeting preference should be respected rather than optimized blindly.

### TeamBoost route — confirm account availability

- Own the actual follow-up: Track the reviewer-response follow-up rather than treating the calendar event as the result. Your check: The prospect agrees the communication preference.
- Preserve comparison context: Record the exclusion example and what the reviewer still needs to decide. Your check: Only supported product coverage belongs in the comparison.
- Report the real next step: State that feedback is pending and what contact is planned. Your check: Do not convert meeting frequency into sales-progress evidence.

### Success check

The prospect can choose the next evidence contact and explain why a live meeting would be useful.

### Editable draft facts

- Unresolved comparison [question]: Does the report make exclusions clear? — Name the decision the prospect is evaluating.
- Evidence still awaited [waiting]: Internal reviewer’s response to the example — Keep the actual prerequisite visible.
- Useful contact option [offer]: Written comparison or a focused exclusion walkthrough — Offer help tied to that question.
- Follow-up owner [owner]: Account representative — Keep the response route owned.
- When a meeting becomes useful [return]: Reviewer feedback or a specific new exclusion question — Avoid a meeting for its own sake.

### Draft pattern — replace every placeholder

```text
Next prospect contact
Comparison: {question}.
Waiting for: {waiting}.
Offer: {offer}.
Follow-up owner: {owner}.
Resume a live discussion when: {return}.
Agree the contact preference; do not invent urgency or product capabilities.
```

### Limits

This is a manual sales-coordination guide, not a CRM feature claim or a guaranteed conversion technique.

Local text preparation only; no workspace read, task creation, send or approval. Source interfaces do not establish account availability or live feature completion.