What to give
- Buyer company and main contact: [name, role]
- Their goal and the date it matters: [e.g. new system live before 1 April for the new financial year]
- Steps known so far: [e.g. technical review, security questionnaire, pricing approval, contract review, purchase order]
- People involved on both sides: [names and roles]
- Notes from calls: [paste]
- Typical times: [e.g. legal review 2 weeks, purchase order 5 days]
Task
Write a plan the buyer would be happy to share inside their own company.
Checklist for the plan
- Start from the buyer's go-live date and work backwards to today.
- Each step has one owner by name or role and a side: buyer, seller or both.
- Include the steps buyers often forget: security review, vendor registration, budget approval, signatory availability.
- Add a buffer before go-live; flag any step whose time does not fit.
- Use the buyer's language for their goal, not product features.
- Mark steps already done.
Output format
- Goal line: what the buyer achieves and by when.
- | Step | Owner | Side | Start | Due | Status | Notes |
- Risks: steps with no owner, dates that do not fit, missing people.
- A cover email under 120 words that proposes the plan as a draft to edit together.
Guardrails
- Never put a step or date in the buyer's name that they have not agreed to; mark it [proposed].
- No pressure language; the plan exists to help the buyer reach their own date.
- Do not invent approval steps; ask in the risks section whether they exist.






