MKT.Preface:9 - Architectural Rationale - A repertoire with connected results
A single chronological sales sequence would be easy to display but would conceal returning, parallel and noncommercial work. A list of independent tactics would preserve choice while leaving practitioners to invent the connections. This edition instead provides separately usable methods with explicit receiving results and shared applications. It allows a local answer without requiring every body, while developing the connections that make a larger answer possible.
Research and qualification remain distinct from offer construction because new evidence can change the problem without producing a solution. Offer positioning, experience design and execution remain distinct because a meaningful promise, a desired experience and available provision can fail separately. Customer success and continuation remain distinct from purchase because useful change and remaining obligations outlive the transaction. Intervention evaluation remains distinct from repeatability because a supported effect in one setting does not establish a sustainable commercial arrangement elsewhere.
MKT.14 owns construction of a programme for selected customer organisations. Its contribution is to combine shared preparation, individual opportunities and whole provision under change. A conventional single-customer enquiry can use MKT.1/2/4 without it. An advertising platform or customer database may assist the programme but does not establish the programme’s useful result, permissible commonality or receiving work.
Specialised contributions stay with their owners. Marketing can identify a missing service and consume a constructed variant without supplying systems engineering. It can frame the commercial question of an experiment without owning the organisation of search. It can offer education without defining how human capability develops, and it can take part in community activity without making that activity a stage of acquisition. These boundaries preserve usable differences when several methods address the same event.