A proposal bundles necessary work with add-ons and your approver needs a transparent comparison.
The useful bits
- Proposal version
- Required outcome
- The response should let the approver understand a complete usable option and the value of each addition.
Before you write
Use this example when a proposal bundles necessary work with add-ons and your approver needs a transparent comparison. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Proposal version
- Required outcome
- Optional services needing separate pricing
An email you can adapt
The subject “Separate required and optional items in [proposal]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Separate required and optional items in [proposal] Hi [name], Please revise proposal [reference] to show which items are required for [outcome] and which are optional additions. For each optional item, identify its purpose and any dependency it creates. Please show the full totals for the proposed alternatives, using the same scope and term basis where possible. We are seeking a clearer comparison, not accepting the bundled proposal or authorizing work through this request. Best, [sender]
Check the boundary
An optional label is misleading if omitting the item makes the required outcome impossible.
What a useful reply should settle
The response should let the approver understand a complete usable option and the value of each addition.
Compare equivalent scope and commitment before recording the approved purchasing decision.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction
