Offer Proposal Options Without Creating Version Confusion
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A buyer replies, “We’ll take the lower-priced option, but with the workshops from the other proposal.” Both documents looked current. Neither made clear whether the workshops were transferable. The seller now has a selection that sounds definite but does not identify a deliverable scope.
To present options in a sales proposal, put mutually exclusive packages in one controlled comparison, separate optional additions from base inclusions, and record the buyer’s exact configuration against a specific revision. A package choice should identify one base scope. An addition should change that scope only under an explicit compatibility rule.
The goal is not merely a tidier proposal. It is to let the buyer, seller, and delivery team independently reconstruct the same scope and price from the selection record—without searching through messages for implied exceptions.
1. Distinguish a package choice from an optional addition
Start by classifying each decision before formatting the proposal. Otherwise, attractive columns can conceal incompatible promises.
- Base package: a complete scope the buyer can select on its own. If packages are alternatives, the buyer selects exactly one.
- Optional addition: extra scope available with specified packages. It is not included merely because it appears somewhere in the proposal.
- Substitution: a defined replacement for something already included. State what is removed, what replaces it, and the resulting price adjustment.
- Custom configuration: a combination that needs a revised scope and price before it becomes selectable.
Do not put these decision types into one undifferentiated list of checkboxes. A buyer should not be able to select two alternative bases as though they were independent extras.
Also distinguish “not included” from “not available.” An excluded item might be available as an addition. An incompatible item cannot be selected with that package under the current proposal. Those are different instructions, and they lead to different buyer decisions.
If an addition is required for a package to achieve its stated purpose, reconsider the structure. Either include it in the base or clearly identify the dependency. A supposedly complete package should not quietly depend on an unselected extra.
2. Keep the alternatives inside one proposal revision
Separate documents are sometimes necessary, but they create extra opportunities for buyers to compare different assumptions. One document may contain the latest price while another contains an older inclusion list.
Prefer one proposal with a shared identifier, revision, scope assumptions, and option matrix. Give each base and addition a stable code. Use those codes in the comparison, detailed scope, selection record, and handoff.
For the fictional worked example below, the controlling reference is PR-248, revision R3. Its base options are B1 Guided and B2 Facilitated. The codes identify scope choices, not separate proposal versions.
When revising, identify the replacement explicitly: “R3 replaces R2 for new selections.” Preserve earlier records for reference, but mark them as superseded rather than leaving several apparently current files in circulation.
A summary email or message can point to the options, but it should not create a parallel version of them. If the message changes an inclusion, quantity, or price, update the controlling proposal before asking the buyer to select.
3. Use a filled options matrix that exposes the boundaries
Fictional worked example: A service provider is proposing a workflow documentation project. All names, identifiers, quantities, prices, and commercial assumptions in this example are hypothetical. These are not Alactic offerings or customer results.
The matrix is presented as text blocks so it can be copied into a proposal draft. Each base describes a complete alternative. Addition prices are incremental to the selected base.
PROPOSAL: PR-248 | REVISION: R3 PROJECT: Workflow documentation for one customer onboarding process CURRENCY: USD PRICE BASIS: Fixed project fees; hypothetical example assumes no tax SELECTION RULE: Choose exactly one base, then compatible additions. SHARED BASE SCOPE - One customer onboarding workflow - Up to six stakeholder interviews - One current-state workflow map - One recommendations document - One consolidated revision round on those documents BASE B1 — GUIDED | $4,800 Includes: - All shared base scope - One remote findings presentation, up to 60 minutes Excludes: - Facilitated redesign workshops - Staff training - System configuration and ongoing support Compatible additions: A1, A3 Incompatible additions: A2 BASE B2 — FACILITATED | $7,200 Includes: - All shared base scope - Two remote redesign workshops, up to 90 minutes each - One agreed future-state workflow map - Findings presented during the workshops Excludes: - A separate findings presentation - Staff training unless A2 is selected - System configuration and ongoing support Compatible additions: A1, A2, A3 A1 — ADDITIONAL INTERVIEWS | +$600 Adds: One block of up to three additional stakeholder interviews Compatible bases: B1 or B2 Maximum: One block under this proposal Does not add: Another workflow or another revision round A2 — STAFF TRAINING | +$900 Adds: One remote training session, up to 90 minutes, using the future-state workflow map included in B2 Compatible base: B2 only Incompatible combination: B1 + A2 Does not add: Recorded course production or ongoing coaching A3 — EXTRA DOCUMENT REVISION | +$450 Adds: One further consolidated revision round on the workflow maps and recommendations included in the selected base Compatible bases: B1 or B2 Maximum: One additional round under this proposal Does not add: New interviews, workshops, or a new workflow COMBINATION RULES - B1 + B2: Not selectable; choose one base. - B1 + A2: Not selectable; A2 depends on B2's future-state map. - A1 + A2 + A3: Compatible when B2 is selected. - Workshops from B2 cannot be transferred into B1. - Additional quantities or substitutions require a revised proposal.
The most important detail is not the number of rows. It is the visible boundary around each choice. “Extra interviews” has a quantity limit and does not expand the project to another workflow. “Extra revision” does not create another workshop. Training has a stated dependency rather than a hidden prerequisite.
This matrix deliberately restricts flexibility. That is a trade-off: fewer selectable combinations make the proposal easier to interpret, but some buyers will need a custom revision. That is preferable to presenting a combination as valid when its scope has not been defined.
4. Write compatibility rules where the buyer makes the choice
Do not hide selection rules in a distant assumptions section. Put the relevant dependency next to the addition, then repeat the resulting configuration in the selection record.
A useful rule answers three questions: what can be selected, what cannot be combined, and what the buyer should do instead.
- Weak: “Training available on request.”
- Clearer: “A2 training is available only with B2 because it uses B2’s future-state workflow map. If you want training with a different scope, request a revised proposal.”
For substitutions, identify the displaced item. “Swap the presentation for a workshop” is incomplete unless the proposal also defines the workshop’s duration, outputs, and price effect. If those details are not settled, treat the request as custom scope rather than a selectable substitution.
Watch for inclusive-sounding labels such as “everything in the previous option.” They save space, but make readers reconstruct scope across columns. If used, repeat the material inclusions in the final configuration summary so delivery does not depend on following a chain of references.
5. Capture a selection record, not just a package name
“Proceed with Facilitated” identifies a base but leaves the additions unresolved. “Proceed at the discussed price” is weaker still: it depends on which conversation each person remembers.
Use an explicit selection record that includes the controlling proposal revision, one base, the status of every addition, the price calculation, and any unresolved request. Here is the completed record for the fictional example.
BUYER SELECTION RECORD — HYPOTHETICAL Buyer organisation: Northfield Studio (fictional) Buyer contact: Morgan Lee, Operations Lead (fictional) Proposal reference: PR-248 / R3 Selection reference: SEL-248-01 BASE SELECTED B2 — Facilitated: $7,200 B1 — Guided: Not selected ADDITIONS A1 — Additional interviews: Selected, one block, +$600 A2 — Staff training: Selected, one session, +$900 A3 — Extra document revision: Not selected, $0 PRICE CALCULATION Base B2: $7,200 A1: $600 A2: $900 Total selected project fee: $8,700 USD Example tax assumption: No tax applies RESULTING SCOPE - One customer onboarding workflow - Up to nine stakeholder interviews in total - One current-state workflow map - One recommendations document - Two remote redesign workshops, up to 90 minutes each - One agreed future-state workflow map - One consolidated document revision round - One remote staff training session, up to 90 minutes NOT INCLUDED - Separate findings presentation - Additional document revision round - System configuration or ongoing support - Recorded course production or ongoing coaching CUSTOM REQUESTS OR SUBSTITUTIONS: None COMPATIBILITY CHECK: Passed against PR-248 / R3 BUYER CONFIRMATION: Confirmed B2 + A1 + A2 against PR-248 / R3 SELLER REVIEW: Scope and arithmetic checked; ready for handoff
In a real proposal, replace the example tax assumption with an explicit treatment appropriate to the quote; do not leave the displayed total ambiguous. Also state whether fees are one-time or recurring and identify any separately calculated charges.
This record clarifies configuration. It does not replace your organisation’s separate approval, purchasing, or agreement process. Keep configuration confirmation and any required commercial authorisation distinguishable.
6. Check the selection before sending it to delivery
Whether the buyer selects through a document, email, or digital form, use the same review sequence:
- Reference check: Does the selection identify the current proposal revision?
- Base check: Is exactly one mutually exclusive base selected?
- Compatibility check: Are all selected additions available with that base, with dependencies satisfied?
- Quantity check: Are quantities within the stated limits, without duplicating something already included?
- Price check: Does the total use prices from the same revision and distinguish one-time from recurring charges where relevant?
- Scope check: Can the resulting inclusions and exclusions be stated without referring to an informal conversation?
These are recommended operating checks, not claims about controls in a particular product. A shared document and a named reviewer can support the process; a digital configurator is not a prerequisite.
If using a form, group the alternative bases separately from additions and write dependency instructions beside the relevant choices. A disabled choice without an explanation can look like a technical fault. The buyer needs to understand how to request a different configuration, not just encounter a blocked control.
7. Recover cleanly when the buyer mixes versions or scopes
When a buyer selects an invalid combination, do not silently substitute the nearest valid package. Equally, avoid treating an understandable request as buyer error. Identify the conflict and offer a clear route forward.
For the fictional example, a suitable response would be:
You selected B1 with A2 training. In revision R3, A2 uses the future-state workflow map included only in B2, so that combination does not yet define a complete scope. You can select B2 with A2, keep B1 without training, or ask us to prepare a revised custom scope. Please confirm which route you prefer; we have not treated the current combination as ready for delivery.
If the buyer refers to an older revision, establish which scope they want before recalculating. Do not automatically combine an old price with a newer inclusion list.
For changes after selection, preserve the original selection record. Create a linked change record or revised proposal that states what changes, what remains, and the resulting price. Obtain confirmation of that configuration through the appropriate process before handing off changed work. Overwriting the original removes the evidence needed to understand the difference.
8. Test whether someone else can reconstruct the order
Before issuing your next proposal, ask a colleague who did not prepare it to select a valid configuration and write its resulting scope and total. Then ask them to try an incompatible combination. Can they identify why it is unavailable and what to do next?
Use three observable checks on your next batch of option-based proposals:
- Selection completeness: How many returned selections identify the revision, base, additions, quantities, and total without follow-up?
- Configuration corrections: How many need correction for incompatible choices or mixed revisions?
- Handoff clarification: How many require delivery staff to ask what the buyer actually selected?
Record the counts and the reason for each exception. A high number of compatibility questions may mean the rules are misplaced. Repeated requests for the same unavailable combination may justify defining a new option—not silently allowing exceptions.
The immediate next action is small: take one live proposal, put its alternatives into a single revision, and fill out a selection record yourself. If you cannot produce one unambiguous scope and price from it, resolve that gap before asking the buyer to choose.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications