MKT.2 - Construct and Test an Offer and Its Positioning

Type: Marketing Method pattern Status: Stable

MKT.2:1 - Problem frame

Use this pattern when people cannot tell what a proposed product or service will do for them, why it is worth considering against their actual alternatives, or what obtaining its result requires. It also applies before an offer exists: a useful capability must be turned into an understandable, supportable proposal for a particular customer situation.

The result is a proposed offer with a clear recipient, contribution, conditions, consideration and grounds for comparison, together with what its test established and left open. Positioning is the context that helps the intended customer interpret that offer. A headline, pricing page or sales conversation can express it; none is the offer’s complete content by itself.

The intended reader understands the product or service and can obtain customer evidence and a competent supply answer. Start from a qualified situation through MKT.1 or an equally sufficient existing account. When a suitable understood offer already exists, use it. When the customer problem is still unknown, investigate that question before polishing an assumed answer.

MKT.2:2 - Problem

A list of capabilities does not tell a customer which useful change it enables under their conditions. A compelling claim can also imply capabilities, support or terms that the provider cannot supply. Teams then try to repair the resulting misunderstanding with more messages while the actual proposal remains inconsistent.

Construct the contribution, its context of comparison and its supply conditions together. Test what the intended people understand and can use. Let failed understanding, failed usefulness and failed feasibility lead to different repairs.

MKT.2:3 - Forces

MKT.2:4 - Solution

MKT.2:4.1 - Establish the receiving result and what could contribute

Recover the customer’s activity, important difficulty, existing alternative and the roles that can change the proposal. Ask what useful difference is sought, who receives it and how it could be recognised. If the purchaser wants a lower fee while users need less repeated work, retain both questions. Do not let one convenient indicator become the goal of every participant.

When the useful result is contested or not yet known, use DOCA.3 to separate the problem, proposed contribution and acceptance expectation. The people involved can then choose a shared limited result, retain distinct goals, or decline the wider proposal. A narrower agreed contribution may be possible without pretending that all goals coincide.

Connect a candidate capability to that result through a concrete use: who would use what, under which conditions, to change which part of the work? A new or changed product-service arrangement may need SYSE.2’s linked use and system concept, followed by the relevant engineering and supply work. Ask its owner for the needed result and constraint; do not replace a missing function with stronger promotional wording.

MKT.2:4.2 - Select a truthful context for comparison

Recover what the intended customer could actually do instead. Compare the contribution with those alternatives, identify the useful difference that its capabilities can support, and identify the circumstances in which that difference matters. Then choose a familiar description or category that helps the intended people interpret it without implying an unavailable result.

For example, “automated reporting platform” may invite an expectation of continuous integration and unattended reports. “Assisted file-mapping trial for periodic reports” gives a different context. Choose between them from the actual proposal and its receivers, not from which phrase sounds larger. A category can help recognition while a qualifier makes the material boundary clear.

If the customer already has an adequate alternative, determine whether the proposal offers a worthwhile difference in result, effort, access, risk or terms. It need not be unique in the world. If no worthwhile difference is supported for this situation, change the contribution, select a different appropriate situation or stop. Competitor claims and the provider’s own claims both need grounds where comparison relies on them.

Ask each relevant participant two questions: what supported difference favours this option among feasible alternatives, and what missing condition would exclude it? Use the first answer to explain preference and the second to retain the conditions for choice or supply. Classify the capability for this situation: dependable support can be a prerequisite in one acquisition and a reason to switch or renew in another.

Keep the comparison open when evidence changes. A new feasible alternative can defeat the proposed advantage without altering the product. A misunderstood category can require another explanation while the underlying contribution remains suitable.

MKT.2:4.3 - Construct the complete proposal

Make the customer able to recover the following content from the offer’s actual presentation:

Use the amount of detail the decision needs. An ordinary standard service may already carry this content in established terms. A new compound service may need explicit coordination among providers. The purpose is a recoverable proposal, not a mandatory form.

Distinguish the provider’s deliverable, the customer’s later result and the evidence for each. A prepared report is different from a timely management decision; a course place is different from an acquired ability. State the contribution and the conditions on which a further benefit depends. A guarantee is a specific stronger commitment whose means and terms require their own support.

Construct price and terms alongside the contribution. Identify the unit—such as a trial, period, case or available capacity—and the costs or obligations outside the headline figure. Use ECO.3 to compare the parties’ contributions and alternatives. Use ECO.5 when private information, later effort or risk makes a choice of terms consequential. Their economic construction does not establish a legal permission or enforceability claim.

MKT.2:4.4 - Obtain a supply answer before relying on the promise

Ask the responsible supplier for the result that can actually be provided under the named conditions: configuration, available capability, people, time, access, dependencies, support and unresolved constraints. Separate a planned improvement from an available contribution. Include preparation and continuing support when comparing feasible versions.

For each important promise, follow the required contribution to a responsible provider or to an explicit gap. Resolve incompatible timings, shared scarce resources and conflicting claims made to different roles. A technically possible service can still be unavailable in the proposed window. Return an unsupported part for engineering, operational or organisational work, or reduce the proposal to a supported part.

The supply answer constrains both the offer and its positioning. If only batch processing is supported, “continuous” must disappear from the current promise. If an operator must inspect every output, the offer must leave that work visible.

MKT.2:4.5 - Test the uncertain connection

Choose a test from the uncertainty that could change the proposal. For understanding, present the actual description to an appropriate person and ask what they expect to receive, what they must do, what it costs and where it would not fit. Let them explain before supplying the intended answer. Compare their account with the proposed content; a repeated sentence can reflect recall without usable understanding.

For usefulness, place the proposal beside the person’s actual alternative and ask them to work through a concrete situation. What would change? Which required contribution is missing? A suitable sample or limited trial can expose a mismatch that an opinion about attractiveness cannot. If willingness to acquire is the unresolved question, use an attainable next choice with honest terms through MKT.4. Do not report hypothetical enthusiasm as a completed purchase.

For supply, obtain the provider’s relevant demonstration, observation or qualified answer. Customer understanding cannot establish supplier capacity. For a claimed benefit caused by the intervention, use the distinct causal question and evidence design; a successful presentation is not that evidence.

After the test, identify the failed connection. Misunderstanding may change wording or context; an unwanted result may change the target or contribution; an unavailable prerequisite may change supply or scope. Return to MKT.12 only for a question whose answer is still needed. Keep adequate parts instead of repeating the whole inquiry.

MKT.2:4.6 - Use and revise one coherent offer

Return the proposal, grounds, test result and unresolved conditions at the strength supported. Keep its expressions consistent across a quotation, demonstration, acquisition interface and delivery instruction. Different roles can need different explanations, but they must not receive incompatible commitments.

Pass MKT.4 enough content to make the next choice feasible. Pass the delivery owner the result, scope and conditions actually agreed if an acquisition occurs. A material change in target, alternative, result, price, supplier capacity or conditions of data use reopens the dependent part. Editing the words without changing the affected operating arrangement leaves the inconsistency in place.

MKT.2:5 - Archetypal Grounding

MKT.2:5.1 - Turn a broad automation claim into an inspectable trial

In this stipulated case, Sever’s reporting department wants less repeated entry while keeping a human inspection step. Its feasible alternative is the existing spreadsheet procedure. Engineering confirms a bounded file-mapping operation for one compatible file family; continuous integration is unavailable. The purchaser can consider a fixed-fee trial, and the access owner must approve the particular sample.

“Eliminate reporting work with our automation platform” implies more than this contribution. The constructed proposal is an assisted trial over two working weeks: configure one permitted file mapping, provide the mapped output and exception explanation, and help the operator compare the resulting work with the current procedure. The offer names the sample, operator inspection, limited support, quoted fee, access prerequisite and end of the trial. It does not promise production integration or a specified time saving before evidence exists.

The proposed reason to prefer this trial is reduced repeated entry; permitted data and operator inspection keep it feasible. If recurring support failures prompted the search, dependable assistance could itself become a supported reason to choose.

Positioning it as a file-mapping trial makes the relevant comparison intelligible. In a stipulated understanding test, the purchaser correctly recovers the limited result but expects the fee to include future production use. The team clarifies the trial’s end and the separate continuation decision. That repairs the offer’s interpretation; it does not establish willingness to buy or achieved benefit.

MKT.2:5.2 - Change a whole condition

Now the available operator cannot inspect outputs during the trial window. The same technical mapping no longer supports the proposed arrangement. Possible responses include another qualified operator, another window, an actually supported additional service or no trial now. Removing inspection from the description would conceal the missing contribution. MKT.4 must receive the revised feasible choice.

For a learning product, the analogous distinction is between supplying worked material and helping someone acquire a contribution to later work. A generated explanation can serve the former. An offer of the latter must include the needed practice, feedback and capability observation from HCD, with the learner’s required work visible.

MKT.2:6 - Bias-Annotation

Teams often prefer the capability they built most recently or the category with the largest apparent market. Challenge that preference with the customer’s actual alternative and a use condition that could defeat the promise. A friendly participant who knows the team can also fill an explanation gap; distinguish their prior knowledge from what the presented offer supplies.

MKT.2:7 - Conformance Checklist

• The intended recipients, useful contribution and consequential conditions can be recovered from the offer.
• The comparison concerns feasible alternatives and a supported difference for the stated situation.
• Deliverable, later benefit, proposed promise, supplier ability and actual fulfilment remain distinct.
• Supply, preparation, support, consideration and customer effort are included at the scope of the promise.
• The selected test answers the live uncertainty and its result retains the proper strength.
• Different expressions and role-specific explanations carry compatible commitments and a usable next choice.

MKT.2:8 - Common Anti-Patterns and How to Avoid Them

MKT.2:9 - Consequences

The customer can assess a proposal whose meaning and conditions are inspectable, and the provider has a more precise request for the work needed to fulfil it. Construction can reveal that the offer should become smaller, be directed elsewhere or not be made. Coordination and testing cost effort; an existing suitable offer remains the cheaper choice when no material uncertainty changes its use.

MKT.2:10 - Architectural Rationale

An offer joins the customer’s situation, a useful contribution, a context for comparison and feasible terms of supply. Positioning belongs in that construction because it can change which capabilities and limits the customer infers. It cannot settle the truth of those capabilities or the customer’s choice.

A messaging-only remedy is sufficient for a local expression problem. Product engineering is needed when the contribution does not exist. This method identifies which connection failed and joins the appropriate results without turning every offer into a new product project or taking over the supplier’s professional work.

MKT.2:11 - SoTA-Echoing

For making a contribution intelligible, adapt April Dunford, A Quickstart Guide to Positioning, 2021. The selected line relates actual alternatives, differentiated capabilities, customer value, fitting customers and an intelligible market context. It improves §4.2 over a category-first fill-in statement whose assumptions remain untested. The extra investigation is worthwhile when context changes understanding; a sufficient established category remains cheaper. The guide’s B2B cases are explanatory examples, not evidence of universal growth effects. The 2025 distinction between preference and exclusion sharpens §4.2 without assigning a capability or profession a fixed role in every choice. Reopen the comparison when another alternative, audience or category changes the inferred promise.

For constructing the complete offer, adopt the developed DOCA.3, SYSE.2 and ECO.3/5 contributions used in §§4.1, 4.3 and 4.4. They supply the useful problem, compatible use and supply concept, and feasible exchange terms. A persuasive value statement alone leaves these dependencies unanswered. The trade-off is more construction effort for an offer that the customer and supplier can both interpret.

MKT.2:12 - Relations

MKT.1 supplies a qualified situation and relevant differences; MKT.12 supplies evidence and receives unresolved questions. MKT.4 turns the understood proposal into a feasible choice and acquisition.

MKT.5 expands the design of client experience, MKT.6 develops shared useful outcomes and help in obtaining them, and MKT.11 coordinates promises and delivery. Their changed results reopen dependent promises here. Engineering, Operations, HCD and economic coordination retain their respective contributions; a marketing offer does not establish their results.

MKT.2:End