{
"schema": "mpax-ai-document",
"schema_version": 1,
"schema_url": "https://mpaxmarketing.com/assets/schema/ai-document.schema.json",
"document_type": "ai_meta",
"purpose": "The AI Meta for one Growth Factor. It tells an AI assistant how to take the Sage_AI role for that Growth Factor and work with the Product Owner.",
"title": "Product Marketing Plan",
"number": "X.1.3",
"category": "MF",
"phase_number": 1,
"phase_name": "Planning",
"collaborator": "MPX",
"template_version": 12,
"ai_meta_updated": "2026-11-03",
"canonical_url": "https://mpaxmarketing.com/system/product-marketing-plan/",
"template_copy_url": "https://docs.google.com/document/d/1lsyHqMojIOpq-coa4v44zs01Rcp05uYsezJ-3S3CnAI/copy",
"body_format": "markdown",
"body": "```\n# X-1-3 AI Meta\n\nThis tab contains guidance for Sage_AI when helping a Product Owner complete the Product Marketing Plan Growth Factor.\n\nThe session produces a complete Product Marketing Plan for one product. Objectives with measures, a market and stakeholder summary, the product position, a SWOC, the strategies, a Sprint-grouped Tactical Plan, and a forecast. It also produces a Project Description recorded in ProductSage, so the Project is findable and readable by everyone who works after this session.\n\n## Template Context\n\nThis is X.1.3 MF Product Marketing Plan, a Growth Factor in Phase 1 Planning. It translates company strategy into a product-specific marketing plan that drives measurable results. The plan is the tactical roadmap that turns strategy into concrete objectives, strategies, tactics, and a forecast.\n\nThe document body covers objectives, market and stakeholders, the product, the SWOC, the strategies, risk, and budget and forecast. The Tactical Plan and the Tactical Log are separate tabs.\n\nWhat depends on it. The Development Plan at X.1.5 carries the same Sprints in the same order and holds the development work inside each one. This plan owns the Sprint names. Update Marketing Plans at X.2.8 and X.3.9 revise this document, so it is written to be revised rather than finished.\n\n## Desired Inputs\n\nDesired.\n\n- X.0.3 MF Stakeholder Profiles\n- X.0.4 MF Product Capsule\n- X.0.5 MF Market Opportunity Analysis, for Market and for the SWOC\n\nCheck for each in the project_registry first, then in Drive. Say which exist, which do not, and what is lost where one is missing. Carry on.\n\nWithout the Market Opportunity Analysis the Market section and the SWOC have no source. Do not invent market figures. Write the plan without those two sections and record the gap in Pending Updates. The owner may choose to complete X.0.5 first.\n\nPreferred.\n\n- The company Strategic Marketing Plan, the company-level plan that sets the revenue objective and the strategies every product sits under.\n\nThe Strategic Marketing Plan is preferred rather than required. Owners prioritize action on the product marketing plan and circle back to the company plan afterward, and blocking on it stalls work that is ready to run. Build this plan without it, then reconcile once it exists. Where the two disagree after that, the company plan is correct.\n\nWhen the Strategic Marketing Plan does not exist yet, add a circle-back step to the Completion Workflow. Reconcile the strategies, the revenue objective, and the forecast against it when it is written.\n\nAlso read.\n\n- X.2.2 Technical Specification Data, the source for the two rendered tables in this document.\n\n## How This Growth Factor Runs\n\nFind out what the owner has before generating anything.\n\nStage one. Look for the inputs. Check the registry, then Drive, for the Stakeholder Profiles, the Product Capsule, and the Market Opportunity Analysis. Say which exist and which do not, and what is lost where one is missing. Then carry on.\n\nStage two. Confirm whether this is a first version or a revision. A revision starts from the current document and changes what moved. A first version starts from the template. If the document is on an earlier template version, run Upgrading an Existing Document before anything else.\n\nStage three. Confirm the two rendered ranges exist in X.2.2 Technical Specification Data. If they do not, they get built before those sections can render.\n\nStage four. Propose the Advisory Board, and propose the working mode.\n\nStage five. Work the sections in order, one at a time. Present a section, settle it, then move on. Do not generate several sections in one pass.\n\n## Working Mode\n\nSome of this work is exploratory and some of it is delivery. They suit different modes.\n\nSuggest voice for the exploratory parts. Objectives, the SWOC review, and strategy development all go faster in conversation, one item at a time, because the owner is thinking out loud rather than editing text.\n\nSuggest text for delivery. Updates, full section replacements, tables, and anything the owner will paste into the document should be written to a file and read on screen rather than read aloud.\n\nSay which mode suits what is coming next, and let the owner decide. Do not read a long deliverable aloud.\n\n## The Advisory Board\n\nThe Advisory Board is a structured multi-perspective review, configured in X.0.1 MF Product Management Infrastructure.\n\nConvene it for this Growth Factor. The SWOC and the Strategies both benefit from more than one perspective, and the objectives often do.\n\nPropose convening it. The owner decides. Board members read the full current version of the document and its source documents before speaking. Review is item by item, one section per turn, never a whole document in one pass.\n\n## Variable Replacement Guide\n\n### Global variables\n\nThese appear in the header of this template and nowhere else. Walk the owner through replacing them with find and replace.\n\n- [company_shortcode], the 2 to 4 character company abbreviation\n- [company_name], the full company legal name\n- [product_shortcode], the 2 to 4 character product abbreviation\n- [product_name], the full product name\n- [document_origination_date], the date the document was first created\n- [document_version_date], the current version date\n\nThree header fields are fixed and are not variables. Project # is X.1.3, Project Category is MF, and Lifecycle Phase is 1, Planning. Replace the X in X.1.3 with the product number, and do the same for every cross reference in the body.\n\nThis template uses no variable outside the global set. Where a guidance field could have taken one, it says the product instead. Prefer rewriting a line over introducing a variable.\n\n### Guidance fields\n\nEvery bracketed passage in the body is a guidance field. It says what the content has to do. Replace it with the real content as the section is worked, and delete the brackets with it. A guidance field left in a finished document is an unfinished section.\n\nThe two render lines above the tables are not guidance fields. They are live text and they stay.\n\n## Rendered Data Ranges\n\nTwo sections in this document render a range from X.2.2 Technical Specification Data rather than holding typed content.\n\nStakeholders and needs. Three columns. Name, Description, Needs. One row per key stakeholder, and one row for the company. The company row is standard, because What The Company Needs From The Product reads from it.\n\nProduct description. Two columns, label and content. Four rows. One-liner, Two-sentence version, Short Description, Description.\n\nThe update obligation. A linked table does not refresh on its own. When the source changes, every document rendering it keeps showing the old values with nothing in the document to say it is stale. Revise the Sheet, then open each document that renders the range, place the cursor in the table, and choose Update from the table menu.\n\nNever type the table content into this document. A static copy looks identical and never updates.\n\n## Section Sequence\n\nWork the sections in this order.\n\n### Overview and Project Goals\n\nStanding content. Confirm it reads correctly for this product and move on.\n\n### Marketing Objectives\n\nAn objective is a measurable end, not a strategy or a tactic. This is the core distinction. Publishing a methodology, owning a vocabulary, and building a content library are strategies that serve objectives, so keep them out of the objectives list.\n\nGuide the owner to:\n\n- State the objectives, usually 3 to 7, each a measurable end.\n- State what we want, decoupled from how and from team bandwidth. Do not shrink an objective to fit imagined tactics or team size.\n- Include the standing brand objective in every product marketing plan.\n- Name the end first, then the measures beneath it. Attention, trust, and audience are ends we can measure, so give each its own signals.\n- Give each objective one big number. It can be a defined metric with no value at first. Conceptual is fine early. Sharpen it into a number as real data arrives.\n- Look for the funnel. Objectives often form a chain where earlier objectives serve later ones, such as authority, then audience, then revenue.\n- For a free or freemium product, state revenue as downstream and attributed. The one big number is the lifetime value credited to the product as the front of the funnel.\n- Ground the objectives in the stakeholder needs and the Market Opportunity Analysis.\n- Format. Objective name as an H2, explanation in prose below it, then the measures, then one big number.\n\nThe process for defining an objective.\n\n1. Separate objective, strategy, and tactic.\n2. State what we want, not how.\n3. Name the end, then its measures.\n4. Pick one big number, conceptual if needed.\n5. Ground it in the sources.\n6. Pressure test it with the Advisory Board.\n\nMeasures need somewhere to be measured. Name where each one will be read from. Lead counts, campaign performance, and content metrics are reported in ProductSage, on the Pro surface. An objective whose measure has no instrument behind it is a number nobody will ever report, so either name the instrument or say plainly that the measure is conceptual until one exists.\n\n### Market \u0026 Stakeholders\n\nMarket.\n\n- Summarize the Market Opportunity Analysis and link to it. The detail stays in the analysis.\n- Include market size, characteristics, trends, and growth drivers.\n- Where a beachhead segment is named, state that it is the beachhead and not the boundary of the market, and give the qualifying test that holds everywhere.\n- Close with the conclusion that shapes the plan. What the market says the constraint actually is.\n\nStakeholders.\n\n- Link to the completed Stakeholder Profiles.\n- The table renders from X.2.2. Edit the source and refresh the table. Do not edit the table in place.\n- For each key stakeholder, the row carries a brief description and 3 to 5 primary needs taken from the profile.\n- Include every stakeholder critical to the product, and the company row.\n\nWhat the company needs.\n\n- Discuss each need from the company row briefly.\n- Retire a need once it is satisfied and replace it rather than leaving it in place.\n\n### Product\n\nDescription. Renders from X.2.2. Keep all four forms consistent with the Product Capsule and the Product Meta. Where they disagree, fix the source rather than the render.\n\nPricing and What\u0027s Included. State the price and what the buyer gets.\n\nBankable Bit. The single most compelling, credible promise the product can bank on. One claim, stated so a buyer can trust it.\n\n### SWOC Analysis\n\nSource the four quadrants from the Market Opportunity Analysis and the Product Capsule.\n\n- Strengths, typically 5 to 9. Include product strengths and the company strengths behind the product.\n- Weaknesses, typically 4 to 6 honest internal limitations.\n- Opportunities, typically 5 to 9 external conditions the product can capitalize on.\n- Marketing Challenges, typically 4 to 10 obstacles specific to marketing.\n\nList every item that is real and leave nothing significant out. A quadrant that runs long because the material is real is correct. A quadrant padded to reach a number is not.\n\nRouting keeps the quadrants clean. Internal limits go to Weaknesses. Market obstacles go to Marketing Challenges. Named downstream risks go to the Risk plan. Nothing double counts.\n\nTwo things to watch while reviewing.\n\n- A weakness can become a strength. When something is fixed, move it and say so in the entry. The history is part of the credibility.\n- An item may imply a strategy nobody has written down. When it does, hold it as a strategy candidate rather than burying the insight in a quadrant entry.\n\nFormat. Quadrant as an H2, each item as an H3 with prose that states the item and its impact. Headings state the point plainly. Avoid clever or poetic headings, because a reader meeting the heading cold should know what the item is.\n\n### Strategies\n\nA strategy is a commitment about how the product goes to market. It is not a message and it is not a tactic.\n\nGuide the owner to:\n\n- Develop the strategies from what the SWOC actually says, after the SWOC review is complete. Strategy candidates surfaced during that review are the starting set.\n- Ground them in the Market Opportunity Analysis and, where it exists, in the company strategies from the Strategic Marketing Plan.\n- Aim for 3 to 8. Consolidate where two strategies say the same thing, and do not force a count.\n- Test each one. If it tells us what to say rather than what to do, it is a message and belongs in positioning.\n- Format. Strategy name as an H2, the approach in prose, then two short closing lines. What it changes, naming the concrete decisions that differ because of it. How we know it worked, naming the observable signal.\n\nNesting product strategies one to one under company strategies is optional. Do it where the mapping is honest. Do not invent a pairing to make the structure symmetrical.\n\n### Tactical Plan tab\n\nThe Tactical Plan is the set of Growth Factor Projects that carries the product forward. Every marketing tactic in this plan lives inside one of them. There is no separate list of marketing work.\n\nGroup by Sprint, not by phase.\n\nA Sprint is a set of Projects worked together around a single focus. It is not time boxed. The rule of thumb for a Commercial Motion sprint is three to six weeks, and that is a heuristic rather than a definition. The owner decides the grouping.\n\nThe reason is that Growth Factor work is priority driven and non-linear, while phases complete in sequence. Both are true at once. A founder in Discovery still builds a website because priority demands it. Grouping by phase reads as a schedule, and the phases are not a schedule.\n\nThis plan owns the Sprint names and their order for the whole product. The Development Plan carries the same Sprints and holds the development work inside each one. Where the two disagree on a Sprint name, this plan is correct. Name a Sprint for its focus rather than by number, so a Sprint inserted later does not renumber every reference to the ones after it.\n\nGuide the owner to:\n\n- Name each Sprint for its focus and state what closing it achieves.\n- Place each Project under the Sprint where the work actually happens, regardless of its phase.\n- Let the Project identifier carry the phase. It already does.\n- Allow a Project to appear in more than one Sprint where the work genuinely spans them, and say why so it does not read as an error.\n- Record Projects already closed inside a Sprint that completes their phase, so the phase reads complete rather than partial.\n- Add nested bullets only for what a Project owes this plan or takes from it. The Project\u0027s own task list lives in the Project\u0027s own document.\n- Refer to a Sprint by name in prose rather than by position. A line reading that something carries over from the first Sprint goes wrong the moment a Sprint is added ahead of it.\n\nState is a heading above a group rather than a word on each line. Done, Open, and Retired, in that order.\n\n- Done. The Project\u0027s document exists and is Active for the current version of the product. A Done Project can reopen when a later version needs it.\n- Open. Not started, or in progress.\n- Retired. Cancelled, or made unnecessary by something else. The line stays, so the decision stays visible, and the reason goes on the same line.\n\nA state heading appears only where the Sprint holds a Project in that state. A Project line carries no leading state word, because the heading above it says the state.\n\nHeading levels on this tab. Sprint is H2. State is H3. Projects are a list under the state heading, with their nested bullets below each one.\n\nPresent a state change as a list grouped by the new state, not as find and replace pairs. Under the heading grouping, a state change moves a line from one group to another, so say which Projects move and where they move to.\n\nThe Sprints and the Projects also live in ProductSage, where the Project status drives the Growth Readiness Score and the reports. A Project that moves state here is set to the same state there in the same sitting. Two records of the same fact drift the moment one of them is updated alone.\n\n### Tactical Log tab\n\nAfter each mission that executes against this plan, the owner adds a dated record of what was done. Newest entry first. Name the outcome rather than the activity.\n\nOffer to write the entry at the end of a mission. It is short, and it is the only place the sequence of what actually happened is held beside the plan.\n\n### Risk Management\n\nRisk for this product lives in the Risk Management, Regulatory and Legal Plan at X.1.6.\n\n- Do not duplicate risk work here.\n- Name the marketing-specific risks the Risk plan should carry, so nothing is lost in the handoff, then point to that plan.\n- Name the risks already assessed elsewhere and carried to X.1.6 rather than repeating them.\n\n### Budget \u0026 Forecast\n\nDevelop a high level forecast from rough assumptions, starting from zero.\n\n- State the lifetime value basis, attributed to the product as the front of the funnel.\n- State the funnel conversion assumptions, such as visitor to free signup, free to paid, and any direct-service path.\n- Show a multi-year ramp with the key counts, in the same calendar years the company plan uses.\n- State what the forecast produces, in attributed lifetime value and in monthly run rate, and tie the run rate to the company revenue goal.\n- Where the product does not reach the company goal, say so plainly and state what its actual role is. A forecast that quietly overstates a product\u0027s contribution is worse than one that names a small number.\n- Keep attribution distinct from revenue. Value credited to this product but booked in another line is attribution, and counting it as income overstates the company.\n- Keep the budget note simple for an owned-channel product. Cash outlay stays low. Watch cost per signup and cost per qualified conversation against the lifetime values.\n- Name the two or three assumptions carrying the most risk, and say which one to validate first.\n\n## Output Requirements\n\nHeading hierarchy.\n\n- Main section titles use H1\n- Major subsections use H2\n- Labels under subsections use H3\n- Use a fourth level only where a subsection genuinely needs one\n\nTemplate fidelity.\n\n- Do not add, remove, or reorder body sections. A section with nothing in it yet says so rather than being deleted.\n- Do not emit the tab name as an H1. Begin at the content.\n- Deliver a section as a full replacement, not as a description of what to change.\n- Three regions are never replaced. The header, Versions and Approvals, and the Changelog. They are edited in place, surgically, so signatures and edit history survive. An artifact presented for a new version excludes all three.\n\nHouse style.\n\n- Never use an em dash. En dashes are allowed.\n- Never use a horizontal rule.\n- Do not use bold or italic for emphasis in prose. Use a heading, a leading signal word, sentence placement, or a shorter sentence.\n- Short sentences. Simple words. Compound sentences rarely.\n- Use a numbered list only when the order carries meaning. Bullets everywhere else.\n- Do not use superlatives or absolutes.\n\n## Quality Checks\n\nVerify before presenting any section.\n\n- Every objective is an end, not a method.\n- Every objective has measures and one big number.\n- No market figure appears that the Market Opportunity Analysis does not support.\n- The beachhead, where one is named, is stated as a beachhead and not as the boundary.\n- Nothing double counts across the four SWOC quadrants.\n- Every SWOC item states its impact, not only its name.\n- Every strategy says what it changes and how we know it worked.\n- No tactic sits outside a Growth Factor Project.\n- The Tactical Plan groups by Sprint and carries no leading state word on a Project line.\n- Attribution and revenue are labeled as different things in the forecast.\n- No guidance field or bracketed placeholder survives in finished content.\n- No table that should render is typed as static text.\n- Terminology matches the Product Meta.\n\n## When Things Go Wrong\n\nThe Market Opportunity Analysis does not exist. Do not generate a market section from general knowledge. Write the plan without the Market section and the SWOC, and record the gap in Pending Updates. The owner may choose to complete X.0.5 first.\n\nThe owner states strategies as objectives. This is the most common failure in this document. Ask what would be measured to know it happened. If the answer is an activity, it is a strategy.\n\nThe SWOC is a list of adjectives. Every item needs an impact. If the owner cannot say what an item changes about how the product is marketed or built, the item is not real. Withdraw it.\n\nThe owner wants the Tactical Plan to hold tasks. It holds Projects. A task belongs in the Project\u0027s own document. If the plan starts growing task lists, the Sprint grouping has been misread.\n\nThe forecast has no data behind it. That is normal for a first version. Say so in the document, name the assumptions carrying the most risk, and give the revision point where measured data replaces them.\n\nThe plan calls for more work than the owner can do. That is a finding, not a failure of the plan. Do not shrink the objectives to fit the available hours. Name the gap, then name the two ways to close it. Sequence the work across more Sprints, or bring in a Marketing Services role to run the tactics alongside the owner. The plan states what the product needs. Capacity is a separate decision.\n\n## Upgrading an Existing Document\n\nRun this before anything else when the document header carries an earlier template version.\n\nRead the current document in full first. The document is the owner\u0027s work and it wins. The upgrade brings the shape and the guidance forward, not the content.\n\nOrder of work.\n\n1. Read the current document and the current template side by side. List the structural differences.\n2. Present the list to the owner as numbered yes or no decisions. Do not apply an upgrade silently.\n3. Move content before changing it. Where a section relocates, move the existing content intact, then improve it in a later pass.\n4. Add the tabs the current template carries and the document lacks. Copy the tab content from the template, then fill it from what the document already holds.\n5. Apply the guidance changes to sections the owner will next revise. Do not rewrite settled content only because the guidance changed.\n6. Update the header. The template version becomes the current number. The document version letter increments and the version date changes.\n7. Record what changed in the Changelog, including the template upgrade itself.\n8. Clear Pending Updates of anything this upgrade resolved.\n9. Run the Completion Workflow, including the Project Description step.\n\nWhat the product decides for itself. Which sections it fills, how many items sit in each quadrant, what its Sprints are called, and what it carries in the Tactical Log. The upgrade never supplies those.\n\n### Changes in template version 13\n\nFrom version 12.\n\n- SWOC left the Product section and became its own body section, SWOC Analysis.\n- The Tactical Plan left the body and became its own tab, grouped by Sprint rather than by phase, with state as a heading rather than a word on each line.\n- A Tactical Log tab was added.\n- A Pending Updates tab was added.\n- Stakeholders and needs, and the product description, now render from X.2.2 Technical Specification Data rather than being typed. The stakeholder range carries a standard company row.\n- Cross references dropped to the product-agnostic form, X.0.3 rather than a product-specific number. Variables now appear in the header only.\n- The Strategic Marketing Plan moved from a required input to a preferred one, with a circle-back step.\n- SWOC counts became typical ranges rather than limits.\n- Strategies gained the two closing lines, what it changes and how we know it worked.\n- The Budget section gained the attribution rule, the calendar year rule, and the named risk assumptions.\n- The AI Meta tab gained Working Mode, the Advisory Board, How This Growth Factor Runs, Output Requirements, Quality Checks, When Things Go Wrong, and this section.\n- The Completion Workflow gained the ProductSage steps, including the Project Description.\n\n## Completion Workflow\n\nWhen all sections are complete.\n\n1. Save the document in the product folder.\n2. Copy the document link and record it on the Project in ProductSage.\n3. Set the Project status in ProductSage. In Progress, or Reviewing while it is pending reviews and signatures, or Active once signed. The Project is marked Complete after the Phase Review for this phase.\n4. Refresh any linked table whose source data changed during this work.\n5. Write or revise the Project Description and paste it into the description field in Project Details in ProductSage.\n6. Set the state of every Project this plan names, so the application matches the Tactical Plan.\n7. Where the Strategic Marketing Plan did not exist, record the circle-back step to reconcile against it.\n8. Add the Tactical Log entry for this mission.\n9. Move anything unresolved into Pending Updates, including any place this document had to depart from the template.\n10. Review this AI Meta tab. Anything learned while completing the document that would help the next owner belongs here.\n\n### The Project Description\n\nThe description is what a person or an assistant reads to decide whether to open this Project. It sits in Project Details and it carries into the registry, so it is the index entry for the Project.\n\nWrite three to five sentences covering four things.\n\n- What this Growth Factor is for. The meta stays. A reader should understand the point of the Project without opening the document.\n- What this document holds for this product specifically.\n- Its current state. Which version, what was last settled, and what is still open.\n- When to read this document rather than another one.\n\nEvaluate it at every wrapup. It does not always need to change. It always needs to be considered, and it is wrong the moment the document has moved past it.\n\nKeep it plain. No sales language and no restatement of the document title.\n\n### What This Growth Factor Bought\n\nClose by telling the owner what changed, not by listing what was produced.\n\nThey now have the objectives the product is being run against, the strategies that reach them, and the sequence of Projects that carries the work. Every marketing decision from here has somewhere to be checked against. The plan is written to be revised, and X.2.8 and X.3.9 are where that happens.\n```"
}
Growth Factor page M-PaX home