Use this when the message needs to be clear and human without inventing deadlines or commitments.
| Best for | sales teams, founders, freelancers and operators |
|---|---|
| Final output | email options with subject lines, concise body copy, next step and fact-check list |
Why this workflow works
This playbook turns one broad AI request into a reviewable sequence. It asks the user to prepare source material first, then uses AI to organize the work, expose missing details and produce a draft that can be checked by a human editor.
For sales teams, founders, freelancers and operators, the value is not only speed. The value is a repeatable process: the same inputs, the same review points and the same standard for deciding whether the AI output is ready to use.
What to prepare before running it
- The real business or content goal behind the task.
- Source facts, notes, examples or policies the AI is allowed to use.
- Audience context and channel where the output will appear.
- Boundaries: claims to avoid, facts to verify and details that are unknown.
- The format you want at the end, such as email options with subject lines, concise body copy, next step and fact-check list.
Workflow steps
- State the relationship with the recipient.
- Define the real next action.
- Provide only verified facts and constraints.
- Ask AI for two tone options.
- Check names, dates, attachments and promises before sending.
Copy-ready prompt
Replace the bracketed fields with your actual source material before using the prompt. If a field is unknown, leave it as unknown and ask the AI to return missing-information questions instead of inventing details.
Example input fields
| Context | Describe the real task, source material and business situation. |
|---|---|
| Audience | Name the reader, buyer, customer, stakeholder or internal team. |
| Constraints | Include claims that must be avoided, facts that must be checked and format limits. |
| Review | Ask for assumptions, missing questions and a checklist before using the output. |
Evaluation rubric
| Clarity | The answer should make the next action obvious without requiring a second explanation. |
|---|---|
| Specificity | The answer should use the provided context and avoid advice that could fit any business. |
| Evidence | Claims, examples and recommendations should be traceable to source material or marked for review. |
| Usability | The final structure should be easy to copy into a document, page, email, ticket or planning tool. |
Common mistakes
- Using a polite tone that hides the decision.
- Inventing a deadline or promise.
- Forgetting the recipient relationship.
- Sending without checking attachments or names.
Human review checklist
- Check whether every claim is supported by source material.
- Remove details that the AI guessed.
- Confirm the output matches the intended audience and channel.
- Keep a copy of the source input with the final prompt.
- Revise the prompt when the same issue appears twice.