On this page
The core idea
AI can organize discovery notes, but it cannot know which commercial commitments have been approved unless they are provided. Separate the customer’s problem, proposed deliverables, assumptions, responsibilities and open questions. A proposal becomes easier to review when each promise has a source and each unresolved item remains explicit.
A practical approach
Step 1
Normalize discovery notes into goals, audience, constraints, success criteria and unresolved questions. Confirm contradictions before drafting.
Step 2
Draft scope around concrete deliverables and acceptance conditions. Keep pricing, dates and contractual language under the responsible person’s review.
Step 3
Check the proposal against the notes and identify any added promise. Remove unsupported claims or label them as options for discussion.
Worked example
A company requests an introductory AI workshop for its operations team. The proposal can describe exercises and expected participant outputs, but it should not add ongoing support, custom software or guaranteed productivity gains unless those are part of the agreed offer.
A mistake to avoid
Reusing an old proposal can carry over the wrong client name, schedule or deliverable. Treat templates as structure, not as a source of current facts.
Try it yourself
Create a proposal checklist that links every deliverable to a discovery requirement. Ask a reviewer to identify assumptions without reading the original conversation.
Your implementation checklist
- Scope maps to confirmed needs.
- Assumptions and exclusions are visible.
- Commercial commitments receive human review.
- Template leftovers are checked.
Share or cite this guide
Innovate with Ajay Editorial (2026-10-04). Prepare Proposals from Verified Discovery Notes. https://innovatewithajay.com/blogs/prepare-proposals-from-verified-discovery-notes