How to use the Sales Handoff Brief Generator.
A sales handoff should preserve promises and exclusions exactly. Delivery teams need to know what was agreed, not what might help close a future deal.
Make the workflow fit your task.
Extract the agreed scope, promises, exclusions and owner information into a delivery brief. Keep contract facts separate from sales hopes and identify missing implementation details before the handoff meeting.
- What you provide
- Closed-deal commitments and onboarding needs.
- What you get
- Delivery-team handoff of promises, owners and dates.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Agreement includes onboarding for two users and excludes custom integration work. Customer contacts, kickoff date and delivery owner are not yet supplied. Produce a handoff brief.
Completed example
Committed scope: onboarding for two users. Explicit exclusion: custom integration work. Customer contacts: not supplied. Kickoff date: not agreed in the provided material. Delivery owner: to be assigned. Before kickoff: confirm the two users, owner and schedule; keep any integration request outside the committed scope until separately agreed.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a handoff include features discussed but not purchased?
Label them as uncommitted context or future possibilities. Do not place them in the delivery scope unless they were actually agreed.
Why does the delivery team discover unexpected work after kickoff?
Check whether sales discussions were mistaken for commitments or exclusions were omitted. Preserve the source of each scope statement.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑