Help Buyers Compare and Choose My Offer

Insivia buyer-centric website playbook · P07 · Version 0.5.1

Insivia's position

A comparison that awards your company a checkmark in every row is a sales claim. Buyers still have to work out whether your strengths matter, what the price covers, and what work you are leaving them to do.

Start with their decision. Establish what they need, what they already understand, and which tradeoffs they can accept. Then compare credible options on that basis. Your feature inventory does not get to define the buyer's priorities.

A useful comparison can recommend another provider or the current approach. Explain who your offer fits, what it asks the buyer to accept, and why that tradeoff may be worthwhile. You do not build confidence by concealing the conditions under which someone should choose differently.

Price belongs beside scope, responsibilities, and dependencies. A lower subscription price does not establish a lower total cost. A service fee does not establish that the buyer has no work left.

Purpose and boundaries

Decision: Which option fits this buyer's actual priorities?

Use this to review or plan a comparison between your packages, another provider, a different approach, or the buyer's current process. Keep one buyer, one decision, and the same required outcome while comparing alternatives.

Owned output: A buyer-led comparison, a scope-and-effort table, a reasoned fit recommendation, and the conditions or missing facts that could change it.

This playbook owns the choice and its explanation. Evaluation resources handle format and access; buyer confidence handles deeper proof and delivery concerns; internal buy-in handles the group's decision. Those are optional handoffs. All essential instructions, worksheets, and the worked comparison are in this file.

Start with one real choice

Bring a short buyer brief and the facts available for the options. If you have little buyer evidence, say so. Ask the few questions that could change the recommendation; do not invent a full persona to fill the gap.

For a first review, return the most consequential comparison problem and its correction. For a complete plan, fill the worksheets below. For public website copy, use only facts that can be substantiated; internal uncertainties belong in the owner's worklist until resolved.

Buyer decision record

When a fuller decision analysis is requested, use this record for consequential choices alongside the task worksheet. A narrow answer need not reproduce the record. Start with the buyer's situation, not the section your team wants to defend. A useful record explains why the buyer would care and what the company should change as a result.

Record field	What to write
Buyer starting point	Situation and prior exposure; pain, desired progress, interest or belief; buying factor; next decision. Name the source and what is uncertain.
Company assumption	What the team wants to say, show, include, remove, or request. Explain why that feels obvious or useful internally.
Buyer interpretation	What this buyer could understand or infer, and how that could affect relevance, belief, perceived effort, fit, or readiness. Distinguish evidence from a hypothesis.
Decision and alternative	The concrete choice that serves the buyer using supported offer facts. Consider a reasonable alternative and explain the tradeoff.
Check and reversal	A neutral question or observable task, and the finding that would make you change the choice. Record actual results only after checking.

Keep the terms honest. A buyer need is something to understand, change, or judge; a verified capability is what the offer does; task-level value is what that capability lets someone do; a measured result needs outcome evidence. Confidence concerns a particular buyer and action, not a site-wide percentage. Routes are available now, planned, or unknown.

Company expertise can establish product facts. It cannot establish what every buyer thinks. Record supplied facts, inspected observations, hypotheses, and unknowns separately. You may explore a plausible buyer interpretation if you label and test it; do not promote it into an established priority or observed reaction. An unanswered product question is owner work, not permission to invent the answer.

This is Insivia's reasoning discipline, not a compulsory funnel or a validated psychological score. Do not fill every field with variations of the same recommendation. Show the buyer reason that changes the decision.

Buyer psychology: make the tradeoff understandable

A buyer can understand both offers and still hesitate. One costs less; the other requires less work from their team. One gives them more control; the other puts more execution with a provider. The difficulty is deciding which consequence matters more in their situation.

Do not interpret that hesitation as ignorance or resistance. They may be protecting scarce time, preserving a familiar process, checking a requirement, or trying to avoid a commitment they cannot support. Establish the actual concern. A job title does not tell you which one applies.

Buyers may also clarify their priorities while learning what the options involve. Consumer-choice research describes preferences as responsive to the decision task and information available [S2]. Ask how the buyer judges the difference after explaining it. Do not replace that conversation with weights designed to make your offer win.

Research on decision conflict found circumstances in which attractive competing options increased deferral [S3]. Our application is to help a buyer judge the tradeoff and identify the next useful check. It is not a reason to hide alternatives, create a deliberately weak option, or claim that more choice always harms conversion.

Give the buyer a reason to care about the difference. “Includes report preparation” matters when their team needs help producing the report. “Editable templates” matters when they need direct control over changes. Explain the connection using their stated needs. Neither attribute is a universal benefit.

Inputs: establish the same decision for every option

Supply what you know:

• Buyer: current situation, pain or desired progress, prior knowledge, buying factors, available capacity, and next decision. Include the source of this understanding.
• Common requirement: the output or job each option must support, important conditions, and the period being compared.
• Alternatives: genuine options, including the current approach when relevant. Explain any difference in delivery model before comparing scope.
• Option facts: included and excluded work, buyer/provider responsibilities, dependencies, limitations, actual price basis, and evidence with dates where relevant.
• Company preference: which option or claim the team wants to emphasize, and why.

Label an owner estimate as an estimate. A stated price may be confirmed while the buyer's likely effort is still uncertain. A supplier claim is not automatically independently verified. Unknown competitor information remains unknown; it is not a negative checkmark.

Workflow: compare on the buyer's terms

1. Fix the buyer, outcome, and decision

Complete: For [buyer in this situation], compare [real options] for [same required outcome] before [next decision].

If the options do different work, make that visible. A managed service and software can both support a reporting job, but they place execution with different people. Compare those responsibilities; do not pretend their scope is identical.

Hold the brief constant while judging the alternatives. A changed buyer priority belongs in a separately labelled what-if, not a convenient new buyer halfway through the recommendation.

2. Separate requirements from tradeoffs

First identify conditions that must be met. Then identify differences the buyer is willing to weigh. A nice feature cannot compensate for failing an essential requirement.

Rank the remaining criteria from reported pain, desired progress, buying factors, and willingness to accept work or limitations. Keep a priority provisional when the evidence is incomplete. Do not invent percentages.

Run the criteria-origin exercise: remove your brand and feature names. Would these still be useful questions for this buyer? If the answer is no, replace the criterion with the decision it was supposed to help.

3. Explain the consequence of each supported difference

Use the same terms and scope across options. State the fact, then what that fact means for this buyer. “The provider prepares the agreed pack” establishes who does that work. It does not prove better commercial performance.

Give both options their strongest supported case. If the alternative has no meaningful advantage, check whether it is a real option or a convenient opponent. An option can genuinely be unsuitable; explain the verified mismatch rather than manufacturing one.

4. Compare scope, effort, and price together

Record what is included, excluded, and dependent on the buyer. Separate setup from recurring work. Include important control or change limits: who can change the output, what changes cost, and what must wait.

Use the same comparison period and identify one-off charges, recurring fees, usage conditions, and unknown extras. Do not call quoted fees “total cost” when internal work or required charges are missing. Do not monetize hours without supplied assumptions or claim savings from an untested estimate.

5. Recommend a fit and name the accepted tradeoff

Write: Given [stated priority], prefer [option] because [supported consequence], accepting [real disadvantage]. [Other option] remains credible because [its supported advantage]. Check [unresolved condition] before [commitment].

You may recommend further investigation rather than a purchase. Missing facts can make a recommendation conditional or leave the choice open. Explain what would settle it instead of forcing a winner.

Challenge the recommendation: what would make the alternative preferable for this same buyer? First look for new evidence about the options. If you change the buyer's capacity, budget, or priority, label that as a different scenario.

Worksheet: buyer criteria and consequences

Criterion and source	Essential requirement or ranked tradeoff	Option A: fact and status	Option B: fact and status	Consequence for this buyer	Missing answer or check
[Buyer need; source]	[Required, priority, or provisional]	[Supported fact, claim, estimate, or unknown]	[Same basis]	[Advantage and accepted disadvantage]	[Owner or neutral check]

Worksheet: scope, effort, and commercial basis

Comparison item	Option A	Option B	Evidence, assumption, or open question
Included output and work	[What is actually supplied]	[Same required job]	[Source and limits]
Excluded work	[Important exclusions]	[Important exclusions]	[Extra scope and fees if known]
Buyer work: setup / recurring	[Tasks and effort status]	[Tasks and effort status]	[Estimate versus measured work]
Dependencies and control	[Inputs, owners, change limits]	[Inputs, owners, change limits]	[What can block or alter delivery]
Price and comparison period	[One-off, recurring, usage]	[Same period and basis]	[Unknown charges and cost exclusions]

Worked comparison — fictional and unbranded

Every business detail, price, and effort figure below is invented for teaching. These are not market benchmarks, supplier claims, client results, or BuyerTwin findings. Only the scenario supplies these facts; do not transfer them to another business.

One buyer and one reporting job

A marketing director at a mid-market B2B company needs the same agreed monthly pipeline and campaign report for the next six months. It must use two supplied CSV exports and produce a PDF pack plus a CSV of the agreed tables. The team understands its reporting task and wants fewer production demands so it can concentrate on campaign decisions.

The director can allocate up to eight internal hours each month and sixteen setup hours. The external budget permits $3,000 per month plus $1,500 setup. After meeting the output and budget requirements, the director ranks preserving internal capacity ahead of minimizing fees. Direct control of template changes is useful, but the agreed report is expected to remain stable during this period.

The current spreadsheet approach produces the required pack but is reported in the fictional brief to take about twelve hours a month. It remains a fallback, not an equally qualified choice under the stated eight-hour capacity limit. That says nothing about spreadsheets for a buyer with different capacity.

The two credible options

• Option A — managed reporting service: the provider prepares and checks the agreed monthly pack from the two supplied exports. The package includes one revision round per monthly pack. The buyer supplies clean files, confirms definitions, and approves the result. Template changes outside the agreed pack need a separate scope decision.
• Option B — reporting software operated internally: the package provides CSV import, editable report templates, PDF and CSV export, and initial onboarding. The buyer configures the report, prepares each month's inputs, builds and checks the pack, and makes changes directly. Monthly report production by the vendor is excluded.

For this illustration, both options support the required formats and the buyer's stated data-handling conditions. Both can support the first run within the scenario's four-week preparation window if their required inputs and setup work are completed. Those are fictional package facts, not findings from a product test.

The buyer's planning estimates, not measured supplier performance, are six setup hours and three hours per month for A, versus fourteen setup hours and seven hours per month for B. The monthly estimates include file preparation and approval for A, and file preparation, report production, and checking for B. Actual effort needs checking before commitment.

Completed scope, effort, and commercial comparison

Comparison item	A — managed service	B — software run by the buyer	Meaning for this buyer
Same required output	Agreed PDF pack and CSV tables from two exports	Tools to produce the same agreed PDF pack and CSV tables	Both can meet the specified reporting job; execution differs
Included recurring work	Provider prepares and checks the pack; one revision round	Software functions; buyer performs monthly production and checks	A places more execution with the provider; B retains it internally
Exclusions	Source-data correction, extra data sources, changes beyond agreed scope	Vendor-run production, source-data correction, extra implementation work	Neither fixes the source data or supplies unlimited additional work
Buyer setup	Six hours, planning estimate	Fourteen hours, planning estimate	Both fit sixteen allocated hours; B leaves less setup capacity
Buyer recurring work	Three hours/month, planning estimate	Seven hours/month, planning estimate	Both fit eight allocated hours on current assumptions; B leaves little room for extra work
Control and changes	Requests go through provider; one included revision per pack	Buyer changes supported templates directly	B offers more direct control; A asks the buyer to accept a narrower change process
Delivery dependencies	Clean exports and agreed definitions; buyer approval	Same inputs plus an internal report owner	Neither option removes the need for buyer participation
Quoted fees in this scenario	$1,200 setup + $2,400/month	$1,200 setup + $800/month	Both fit the external budget; B has the lower quoted fees
First six months of quoted fees	$1,200 + 6 × $2,400 = $15,600	$1,200 + 6 × $800 = $6,000	B is $9,600 lower on this fee basis; this is not total cost or proven savings

The fee comparison excludes tax, internal labor, data correction, and any separately scoped changes. Their costs are not supplied. Do not invent them or claim that the fee difference pays for a particular number of internal hours.

Completed buyer-criteria worksheet

Criterion and source	Essential requirement or ranked tradeoff	A: fact and status	B: fact and status	Consequence for this buyer	Missing answer or check
Agreed report, formats, and data conditions; fictional buyer brief	Essential	Supported by fictional package facts	Supported by fictional package facts	Both remain candidates	Inspect samples and confirm actual contract conditions in a real task
Setup and monthly capacity; buyer's stated limits	Essential, based on provisional effort estimates	Six setup / three monthly hours estimated	Fourteen setup / seven monthly hours estimated	Both appear feasible; B has less room for variation	Confirm tasks and effort against a representative reporting cycle
Preserve internal capacity; buyer's stated first tradeoff priority	Priority 1 after requirements	Provider handles recurring production	Buyer retains recurring production	A better serves the stated priority; accepts higher fees and provider change limits	Check the buyer effort omitted from either estimate
Lower fees within an acceptable budget; buyer brief	Priority 2	Higher quoted fees, still within budget	$9,600 lower quoted fees over six months	B has a substantial valid advantage; no total-cost conclusion	Confirm exclusions and any required additional charges
Direct control of changes; buyer brief	Priority 3	One included revision; additional change scope needs agreement	Buyer edits supported templates directly	B offers more control; buyer must accept the work	Confirm expected change needs and permitted changes

These priority labels come from the fictional buyer brief. They are not a numerical score or a claim about all marketing directors.

Recommendation for this same buyer

Take A forward for sample and scope confirmation. Preserving internal capacity is the director's leading tradeoff priority, the report is expected to remain stable, and the service fits the stated external budget. In return, the director accepts higher quoted fees and less direct control over changes. The service still needs clean inputs, definitions, approval, and a checked effort estimate.

B remains a reasonable choice for this same buyer. Seven estimated monthly hours are within the eight-hour allocation. B retains direct control and has $9,600 lower quoted fees over the same period. The director could reasonably accept the greater internal workload to keep that fee advantage. Given the stated priority order, A is the initial recommendation; B is not disqualified or described as inferior software.

Do not turn either recommendation into a purchase instruction. Confirm the real output, full scope, participation, terms, and effort before committing. If necessary charges or required work remain unknown, keep the choice conditional.

Completed buyer decision record

Record field	Completed decision
Buyer starting point	Knows the reporting task and wants to protect campaign capacity. Needs the same six-month reporting job within the stated budget and time allocation. These are fictional supplied priorities; effort figures remain estimates.
Company assumption	The service provider wants recurring production work to decide the comparison. Because capacity is the buyer's priority, the team thinks its execution advantage deserves the page while continuing buyer work, revision limits, and the software's fee advantage deserve little attention.
Buyer interpretation	Hypothesis: the director may see similar outputs at very different prices and not understand what the higher fee changes. A claim of comprehensive support may also hide continuing buyer work. A comparison of responsibilities makes the capacity and control tradeoff inspectable.
Decision and alternative	Replace the broad superiority claim with output, responsibility, scope, effort, fees, and change-control comparisons. Prefer A for this buyer's stated capacity priority; preserve B's lower fees and direct control as a credible alternative for the same brief.
Check and reversal	Ask the director to explain the tradeoff and accepted disadvantage, then check representative work and terms. If A's required work exceeds eight monthly hours while B remains within it, A fails this buyer's capacity requirement. If A fits but requires seven rather than three hours, reassess whether its remaining execution help warrants the fee premium. No test result is claimed.

What changes: the company keeps its relevant execution advantage and explains its conditions. The buyer can inspect the work being purchased, the work still required, the limits being accepted, and the advantage the alternative retains.

A direct way to explain the comparison on the website

Illustrative copy for this fictional offer only:

Choose who produces your monthly report.

With the managed service, the provider prepares the agreed pack from your files. With the software, your team builds and checks it using editable templates. Both require clean source data. The service carries higher fees and a defined revision process; the software gives your team more direct control and leaves production with you.

Place the relevant scope and fee details beside that explanation. Do not publish the fictional planning hours as typical performance.

Separate what-if, not a different buyer hidden in the answer

If the director later makes minimizing fees the leading priority and can reliably commit the required internal time, B may become preferred. That is a changed priority, not the original brief. Record the change before revising the recommendation. New evidence about A or B can change the original recommendation without changing the buyer.

Build the page around the buyer's choice

Use a direct heading naming the decision, a short explanation of the delivery difference, and comparable attributes. Put essential conditions and the most important tradeoffs where a scanning reader can find them. Give evaluators access to definitions, scope, source dates, and deeper evidence [S1, S4].

Avoid a wall of equally prominent features. Avoid a row called value with an unsupported winner. A price difference needs an explanation of the work and conditions behind it. A provider should be able to state the alternative's genuine advantage without undermining its own truthful offer.

Choose the next step from the actual unresolved question. Link only to resources that exist. A proposed sample, calculator, or consultation process remains owner work until available.

Applying this playbook with your AI

Shared rules for facts, resources, and response scope

Use Insivia's method; use the user's facts. This file supplies a buyer-centric method. Its fictional examples supply no facts about another business. Similar subject matter does not make their features, prices, roles, assets, constraints, or findings applicable. Use supplied business facts and sources actually inspected for this task. A faithful paraphrase or task-level explanation is useful only when those facts support it. Do not add formats, fields, controls, outcomes, approvals, or process steps because they seem likely.

Keep each item's status intact. Available, approved, proposed, feasible, incomplete, and unknown mean different things. Feasible does not establish a draft. Incomplete does not establish that work never started. An available destination does not establish a built link, accessible contents, booking, or a response service. Name the exact item when recording status. Unknown is not confirmed absence. Reuse an existing approved answer when it serves the buyer; proposed resources remain unavailable. Respect explicit publication and source-use restrictions, including prohibitions on deriving examples from restricted material.

Answer the requested task, then stop. The user's requested count, format, and shorter length control the answer. One sentence, one table, or one decision does not trigger a full plan, worksheet, validation kit, or closing offer. For copy-only requests, return copy only. For a factual correction, preserve the verified capability wording; add no new capability, purpose, benefit, route, or promise. Correct the affected claim without expanding to unrelated work. Never retain a known false claim as an alternative or wait for a future feature to substantiate it.

Ask only for facts that could change this decision. If essential buyer context is missing for strategic work, ask at most three focused questions and stop. Do not block a narrow correction with irrelevant intake questions. A known buyer question with an unknown business answer is an owner gap, not permission to invent an answer. A verified incompatibility with a fixed buyer requirement warrants a clear no-fit finding; do not invent a workaround or reopen that requirement under company pressure.

Connect the recommendation to the actual buyer. Use their supplied prior knowledge, pain, motivation, buying factors and next decision. Possible interpretations are hypotheses, not observed reactions. Do not invent a company preference, psychological motive, alternative or conflict to fill a reasoning template. No change can be the supported conclusion. For a fuller review, make the buyer reason and consequential company choice explicit without repeating the same record for every row.

Represent inspection and tests honestly. Supplied notes are not direct inspection. A URL alone does not establish that it was read. Text cannot establish visual quality, interactions, or delivery. Proposed checks have not run. Keep neutral questions free of expected answers and unsupported steps. Generic AI role-play is not human research or BuyerTwin analysis. Attribute Insivia in explanatory output, outside proposed public copy; exact copy-only output needs no added attribution.

Keep the first response proportionate. Default to one priority decision and its buyer reason within 220 words. Expand only for a requested artifact or detail. Use the task guidance below conditionally; worksheets, examples and full workflows are reference resources, not a requirement to reproduce them all.

Task-specific application

Keep the same buyer, outcome, period and requirements across options. Give credible options their strongest supported case and real disadvantage. Unknown competitor facts are not absent capabilities. Compare fees with supplied scope and work; quoted fees exclude unpriced effort and are not total cost. Do not monetize missing labor rates or invent prices. Full comparison worksheets are on request.

For a full artifact, use this file's task worksheets and source limits. Other downloads and BuyerTwin are optional. The supporting tabs provide usage help, not missing essential rules.

Check the result

Give the comparison to someone representing the buyer and ask:

• What decision is this comparison helping you make?
• Which difference matters most in your situation, and why?
• What work stays with your team under each option?
• What would you give up by choosing the option you prefer?
• What information would you need before taking the stated next step?

Record their words before explaining your intended answer. Separately check the actual scope, fees, work, and requirements. A reader understanding the comparison does not prove the underlying claims are true.

If feedback changes a priority, record it. If evidence changes an option fact, update the comparison and date. If neither changed but the company still wants a different winner, challenge the criterion rather than quietly changing the buyer's brief.

Actual BuyerTwin analysis can supplement the work with modeled reactions to criteria and tradeoffs. Preserve the tested buyer, page version, questions, findings, and limits. A generic AI opinion is not BuyerTwin analysis, and a modeled preference is not an observed purchase.

Sources and evidence limits

Insivia's method incorporates Andy Halko's approved viewpoint: begin with essential buyer requirements, rank meaningful differences from pains and buying factors, put price beside scope and required work, and help the buyer choose even when another option fits better. The worksheets and reporting scenario are practitioner teaching tools, not validated psychological instruments.

• [S1] Comparison Tables — NNGroup — Moran and Dykes, 2024. Guidance on consistent attributes, comparable presentation, and decision support. It does not validate the fictional offer facts or this recommendation.
• [S2] Constructive Consumer Choice Processes — Bettman, Luce, and Payne — Journal of Consumer Research, 1998, 25, 187–217. The author-hosted paper's indexed abstract describes preferences and strategies as dependent on the decision task. Applying that to a B2B comparison is a practitioner inference; no universal buyer priority or conversion effect is claimed.
• [S3] Choice Under Conflict — Tversky and Shafir — Psychological Science, 1992, 3, 358–361. The publisher abstract reports circumstances in which conflict increased decision deferral or further search. It is not a B2B website experiment or a reason to suppress credible alternatives.
• [S4] Stanford Web Credibility Guidelines — Fogg / Stanford, 2002. Historical guidance supports inspectable evidence and clear presentation; it does not measure confidence or establish an offer's value.

Source check: November 12, 2026. The comparison and credibility pages and the decision-conflict abstract were read. The constructive-choice abstract was available through the author-hosted paper's indexed content; the scanned paper was not reviewed in full. No buyer study, client outcome, price benchmark, or BuyerTwin finding was created for this revision.

Optional next tasks

Each linked playbook answers a different next question. This file already contains its own essential method and working resources; no other download is required.

• Build a buyer-centric product or solution page when buyers first need a clearer explanation of the offer being compared.
• Strengthen buyer confidence when a consequential difference needs substantiation or delivery facts.
• Help buyers build internal buy-in when colleagues need to understand and defend the tradeoff.
• Help buyers evaluate before speaking to sales when buyers need an inspectable resource to continue evaluating the alternatives.

Method revision 0.5 replaces the earlier comparison with one buyer choosing between two credible approaches, including scope, effort, fees, control, a viable alternative, and a reversal check. Retain Insivia attribution, resource identity, canonical source, version, and evidence limits when adapting it.