# Give a prospect a one-page comparison their internal reviewer can use

Manual worksheet; invented situation, no automatic product import.

## Owned work

- Identify the receiving decision — Account representative — The internal reviewer needs exclusion clarity, not a general feature tour.
- Prepare the bounded packet — Evaluation owner — The annotated sample, assumptions and untested distribution boundary stay together.
- Check usefulness with the receiver — Coordinator — The reviewer can identify the remaining choice without attending the original call.

## Workflow questions

### Is a larger deck always worse?

No. Add material when the actual receiving decision needs it; avoid unrelated claims that obscure the comparison.

### Should limitations stay in the one-page version?

Yes. Removing them can make the sample imply coverage that was not demonstrated.

### How does TeamBoost fit this sales handoff?

Its documented task ownership and notes can keep the evaluation packet and reviewer follow-up tied to the work. No native CRM, external distribution or commercial-proposal approval is established here.

## Job to be done

When a prospect needs to brief a reviewer who missed the call, I want a bounded comparison packet so the recipient can make the actual evaluation decision.

A prospect evaluated whether a report makes exclusions clear. Their internal reviewer missed the call and needs the sample, its context and the untested distribution question.

### Recognizable symptoms

- A broad product deck replaces the specific comparison.
- A sample travels without its assumptions or limitations.
- Recipients infer that an untested capability was demonstrated.

### Shortcut that fails

More feature slides do not necessarily make the reviewer’s exclusion decision easier or preserve what was not evaluated.

### Before

Send our full feature deck; the example should speak for itself.

### After — invented worked answer

Evaluation packet: one annotated report example showing its scope and exclusions, the assumptions behind that example and the remaining reviewer question. Automatic distribution was not evaluated and is not promised. Ask the internal reviewer whether the exclusion explanation supports their decision, or which specific comparison remains missing.

### Conditional next moves

- If The receiving decision is narrow: Send a bounded annotated comparison. Scope and assumptions matter more than slide volume.
- If The receiver needs broader verified evidence: Add only relevant material. Do not fill gaps with unverified product promises.
- If A capability was not evaluated: Keep it explicitly unresolved. A sample is not proof of every delivery mode.

### TeamBoost route — confirm account availability

- Track the reviewer follow-up: Name the evaluation-packet preparation and receiving question with an owner. Your check: The task output is a useful comparison, not a guaranteed sale.
- Keep assumptions with the sample: Record what the example does and which capability was not evaluated. Your check: Use verified product evidence before stating coverage.
- Report the next evaluation action: State the reviewer’s question or feedback and the bounded next comparison. Your check: A human reviews any prospect-facing capability claim.

### Success check

The internal reviewer understands what was evaluated, what remains untested and which question the next comparison should answer.

### Editable draft facts

- Evaluation job [job]: Understand report exclusions — Use the recipient’s actual decision.
- Sample and context [sample]: Annotated report with scope and exclusions — Keep the source assumptions visible.
- Coverage actually evaluated [covered]: Exclusion explanation in the supplied example — Describe demonstrated scope only.
- Not evaluated or unresolved [untested]: Automatic distribution not evaluated — Keep this attached to the sample.
- Question for the receiver [ask]: Does this explanation support your decision, or what specific comparison is missing? — Give the packet a receiving purpose.

### Draft pattern — replace every placeholder

```text
Internal evaluation recap
Job: {job}.
Example: {sample}.
Evaluated scope: {covered}.
Untested boundary: {untested}.
Reviewer question: {ask}.
Retain assumptions and limitations when sharing the recap.
```

### Limits

The sample is fictional and does not prove TeamBoost report distribution, CRM coverage or a completed product evaluation.

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