Product Marketing & Competitive Intel

The framework — strategy first

Product Marketing & Competitive Intel — the strategic foundation.

Product Marketing is the Intelligence Layer.

Brand & Positioning is who you are. ICP & Audience is who you sell to. Product Marketing & Competitive Intel — Product Marketing Management (PMM) — is what the market around you is doing, and what to do about it. PMM produces the structured intelligence that brand, demand, and sales all rely on: market sizing the board defends in front of investors, competitive positioning AEs use in deals, win/loss patterns that tell you which features actually move pipeline, and launch architecture that turns a feature ship into a revenue event.

This work is where the strategic conviction in Brand & Positioning meets the buyer reality in ICP & Audience and the competitive landscape outside both. It's also where most business-to-business (B2B) SaaS companies have the thinnest discipline: positioning lives in a deck made for the last board meeting, competitive intel lives in a slack channel nobody reads, and win/loss is an interview a Customer Success Manager (CSM) does once a quarter and forgets about.

Five jobs product marketing does (and the agent that makes each scale)

Market sizing — Total Addressable Market, Serviceable Addressable Market, and Serviceable Obtainable Market (TAM/SAM/SOM) model the CFO can audit. Underwrites the budget conversation.
Competitive positioning — Named teardowns of top 3 competitors. Underwrites every sales deal in flight.
Win/loss program — Structured interviews + thematic synthesis. Underwrites the roadmap conversation.
Product launch architecture — Pre-launch readiness through post-launch attribution. Underwrites every quarterly board update.
Sales enablement — Battlecards, messaging hierarchies, talk tracks. Underwrites every AE conversation.

Three audiences, again

Same triple-audience pattern as Brand & Positioning and ICP & Audience — competitive intelligence is now read by humans AND agents. The battlecard a new AE reads on Day 1 is the same context block your sales-enablement agent reads when it drafts an objection-handling response.

PMM INTELLIGENCE, MAPPED TO THE THREE AUDIENCES

Sales — Battlecards, talk tracks, win/loss themes. The doc that briefs a new AE briefs every objection-handling agent.

Marketing — Launch architecture, positioning vs. competitors, messaging hierarchies. Where every campaign and asset knows what the market expects.

Agents — Market Intelligence Agent below imports the same intel and refreshes it weekly. Every downstream agent (Email & Lifecycle, LinkedIn & Social, ABM) reads from /competitive-context.md to keep messaging in sync with what's happening in the market right now.

Proactive vs. reactive — the only PMM that matters

Reactive PMM responds to competitor moves after Sales escalates. Proactive PMM watches the market continuously and surfaces moves before they hit a deal. The Market Intelligence Agent below is the proactive layer: weekly crawls of competitor sites, hiring pages, funding announcements, product changelogs, and analyst reports. It produces a weekly delta — what's new, what shifted, what to brief Sales on — so the team is never caught flat-footed in a competitive deal.

If your competitive intel arrives in Slack only after a deal is in stage 4, you don't have a PMM function. You have a fire department.

The battlecard architecture — what AEs actually need in a deal

Most battlecards fail because they're written by marketing for marketing. They have positioning statements, value props, and feature comparisons — all useful in a vacuum, none of which help an AE answer "but they said X, what do I say back?" in real time. The battlecard that wins is structured around the moment of objection, not the moment of positioning.

BATTLECARD — THE STRUCTURE THAT WORKS

Their pitch in one sentence — how the competitor actually positions themselves to buyers. Not how you wish they did. Pulled from their homepage, their reps' LinkedIn posts, and recent G2 review responses.
Three things they win on — the moments where we actually lose to them, and why. Be honest. AEs ignore battlecards that lie about competitive weakness.
Three things we win on — the moments where we actually win against them, with the proof point that lands.
The five objections AEs hear, with verbatim responses — "they said you cost 3× more, what do I say?" "they said you don't integrate with our stack, what do I say?" Each response in the AE's voice, with the customer story that backs it up.
The trap question to ask the prospect — the single question that surfaces whether they're actually shopping the competitor or just name-checking them. Saves cycle time.
Last updated date + named owner — battlecards that aren't dated are battlecards that aren't trusted.

Win/loss feeds the battlecards — the program lives in its own module.

WIN/LOSS PROGRAM MOVED OUT OF COMPETITIVE — FOR GOOD REASON

Win/loss is the rarest discipline in B2B SaaS and the highest-leverage feeder into competitive intel. The cadence (every closed-won and closed-lost over $50K, 30-minute structured interview within 14 days, conducted by PMM or a third party — never the AE who lost it), the six questions, and the quarterly thematic synthesis live in their own module, Win/Loss Analysis.

Run win/loss as a program in M07. The synthesized themes, named-account patterns, and verbatim objection language flow back into this work — into your top-3 competitors list, your category narrative, and the battlecard refresh cadence below. Competitive intel without a running win/loss program is rumor with logos.

Your Competitive Landscape

The competitors you actually face, your win/loss cadence, your battlecard owners. Every PMM, sales-enablement, and positioning prompt on the site uses these.

Top 3 competitors you see in deals (in order of frequency)

Your category narrative (how you frame the market vs. competitors)

Win/loss program cadence (interviews per quarter + who conducts them)

Battlecard owner + update cadence

Saved as [TOP COMPETITORS], [CATEGORY NARRATIVE], [WIN LOSS CADENCE], [BATTLECARD OWNER].

The prompt pack

Paste-ready prompts for Product Marketing & Competitive Intel.

Each prompt is a named, named-by-what-it-does deliverable. Click any card to expand the paste-able body. Run against your Operator Brief.

Five copy-paste prompts. Open ChatGPT, Claude, or Gemini. Paste a prompt. Run it. The output of one prompt feeds into the next.

READ THIS ONCE BEFORE ANY PROMPT IN THIS BOOK

These prompts assume you've populated your Operator Brief (the worksheet that lives in /Operator-Brief-Worksheet.docx). When a prompt asks for OPERATOR BRIEF, paste the relevant Brief sections rather than typing context from scratch.

Your output then arrives in your voice, against your buyers, using your differentiators. Not [BRACKETED] generics. The Brief is the difference between an LLM helper and a tool that sounds like you.

Prompt 1

TAM / SAM / SOM model (executive-defensible)

A three-tier market sizing model with the math, the sources, and the assumptions exposed — the version a CFO would sign off on.

Build the TAM / SAM / SOM model for our company. PRODUCT: [one-liner] OPERATOR BRIEF — paste Section 2.2 Category, Section 1.1 Tier 1 verticals, Section 3.1 KPIs REGION: [global / NA only / specific regions] ACV: $[avg] Output three tiers with the math exposed at each step: TAM (total addressable) — every company in the category, globally. Source: industry analyst (Gartner / Forrester / IDC), or bottom-up by NAICS code × employee-size × penetration rate. SAM (serviceable available) — TAM filtered to our ICP (vertical fit, employee count, geography). Show the filters and the resulting count. SOM (serviceable obtainable) — SAM × realistic 3-year win rate. Cite competitor share-of-market or our historical win rate as the basis. RULES - Every number cites a source (analyst report, gov data, our own CRM). No 'industry estimates' without a name. - Show the math, not just the result. - End with the single assumption that, if wrong by ±20%, would change the recommendation — and how to validate it.

Prompt 2

Competitor teardown (top 3, named)

A structured teardown of the three named competitors that show up most in your pipeline — positioning, pricing, target segment, strengths, weaknesses, and where to attack.

Tear down our top 3 competitors with a CRO-defensible framework. COMPETITORS: [3 named — pull from CRM closed-lost reason or sales conversations] OUR PRODUCT: [one-liner + ACV] OPERATOR BRIEF — paste Section 2.14 Positioning, Section 2.15 Differentiator, Section 1.5 EB For each competitor, output: 1. Positioning — their one-line claim (verbatim from their homepage) 2. Target segment — the buyer they're best suited for (ICP overlap with us) 3. Pricing — published or surveyed; flag if unverified 4. Three strengths — where they outpoint us, with evidence (case studies, analyst note, customer feedback) 5. Three weaknesses — where we outpoint them, with evidence 6. Where to attack — the specific segment/persona/use case where we win most consistently, and the message that wins it 7. Where to defend — the segment/persona where they win most End with a 2-sentence elevator answer to: "How are you different from [strongest competitor]?" — using our voice from Brief Sections 2.11–1.13 (voice DOs, DON'Ts, forbidden).

Prompt 3

Win/loss synthesis (10+ interviews)

A synthesis of 10+ recent win/loss interviews into 3–5 themes, with the named accounts attached and the recommended actions (product, marketing, sales).

Synthesize win/loss patterns from the interviews below. INTERVIEWS: [paste 10+ interview transcripts or summaries — 5 wins, 5 losses minimum] TIMEFRAME: [last 6 months] OPERATOR BRIEF — paste Section 1.5 EB success metric, Section 2.15 differentiator Synthesize into 3–5 themes. Each theme contains: - Theme name (operator-direct: "Pricing surprise at procurement stage" not "Procurement friction") - Frequency (# of interviews / 10) - Direction (wins, losses, mixed) - Named accounts where the theme appeared - Root cause hypothesis (1 sentence) - Recommended action — split by owner: Product, Marketing, Sales Then output the single highest-leverage change. Format: "If we changed X, we'd convert [N] of the [M] lost deals next quarter — based on the [specific theme] pattern." Tone: operator-direct. Don't soften losses. Name accounts (anonymize only if NDA-required).

Prompt 4

Launch one-pager (board-defensible)

A one-page launch architecture covering positioning, audience, channels, internal readiness, and the metrics that define success — short enough for a board update, sharp enough to run from.

Build the launch one-pager for the feature/product below. LAUNCH: [name + 1-sentence description] LAUNCH DATE: [] PRIMARY AUDIENCE: [persona from Operator Brief Sections 6.5–2.7] OPERATOR BRIEF — paste Section 2.14 Positioning, Section 2.10 Pillars, Section 3 KPIs Output one page with these sections (each ≤4 lines): 1. The story — what changes for the buyer when this ships? Use the Brand & Positioning Prompt 4 category-narrative voice. 2. The audience — who this is for, who it isn't for, and why. 3. The proof — 2–3 numbers or named-customer references that earn the claim. No "various customers" — name them or drop the claim. 4. The channels — top 3 (e.g., LinkedIn post by founder, press release to vertical trade press, AE outbound to 50 named accounts). 5. The internal readiness — what Sales needs (battlecard / talk track / demo update), what CS needs (release notes / customer comms), what PR needs (analyst briefing / quote). 6. The success metrics — 1 leading + 1 lagging + the 'what would make us call this a fail' threshold. End with the riskiest assumption + how we'll validate it in week 1.

Prompt 5

Battlecard generator (per competitor)

A one-page Sales battlecard for a named competitor: their pitch, our counter, common objections, the discovery questions that trap them, and the proof points that close.

Generate the Sales battlecard for the competitor below. COMPETITOR: [] DEALS WE'VE LOST TO THEM (sample): [paste 3 lost-deal post-mortems] DEALS WE'VE WON OVER THEM (sample): [paste 3 win post-mortems] OPERATOR BRIEF — paste Section 2.14 Positioning, Section 2.15 Differentiator, Section 1.5 EB Output a one-page battlecard with these sections: 1. Their pitch in one sentence (verbatim from their homepage if possible). 2. Their target buyer (ICP overlap with us — be specific). 3. Where they win — the 2 scenarios we don't fight in. 4. Where we win — the 2 scenarios we do. 5. Discovery questions that trap them — 3 questions a buyer should ask during evaluation that expose their weakness (no FUD; honest qs). 6. Top 3 objections we hear, with our 2-sentence response each — in our voice from Brief Sections 2.11–1.13 (voice DOs, DON'Ts, forbidden). 7. Proof points that close — the named customer references, the data points, the analyst mentions. 8. The trap to avoid — the move we tend to make in deals against them that doesn't work. End with: the single belief about the buyer's world that, if we land it, wins the deal regardless of feature parity.

The agent spec

The agent for Product Marketing & Competitive Intel.

How to install this agent

Five steps from spec to running agent.

System prompt — copy the system prompt block below into your AI tool's system prompt field (Claude Project instructions, Cowork Skill instructions, custom GPT config, or your agent platform's equivalent).
Inputs — wire the inputs as the agent's reference files. The Operator Brief is always input #1; the other inputs vary by agent.
Outputs — the output schema tells you what the agent produces. Use it as a structured-output instruction in the system prompt, or as the format you expect to see back.
Evals — before publishing any output, score it against the eval criteria. Don't ship anything that doesn't pass.
Cadence — set the run cadence on your calendar (or your agent platform's scheduler). Log every run in your wins log.

Market Intelligence Agent

Proactive competitive intelligence. Crawls competitor sites, hiring pages, changelogs, press, and analyst notes weekly — so Sales never finds out about a competitor move from a buyer first.

Who is this agent

Identity card

NameMarket Intelligence Agent

RoleCompetitive intelligence + market signal monitoring

OwnerHead of Product Marketing

Reports toVP Marketing

Versionv0.5 (supervised)

SurfaceReplit + n8n + Postgres (snapshot store)

Output target/competitive/snapshots/, /competitive/digests/, /competitive/battlecards/<competitor>.md

Review cadenceWeekly digest review; monthly battlecard refresh; quarterly competitor-set review

Mission

Be the team’s ears on the competitive landscape. Crawl named competitors’ sites + hiring pages + changelogs weekly. Watch analyst notes, press, and review-site updates. Diff against last snapshot. Surface material moves to PMM + Sales within 24 hours of detection — the AE should never hear about a competitor move from a buyer first.

Goals & KPIs the agent moves

Leading indicators — the agent controls these

Competitor-move detection lead time (public move → AE notification)< 24 hours

Battlecard freshness (no battlecard > 30 days unrefreshed)100%

Lagging indicators — downstream outcomes with review triggers

AE battlecard adoption on active deals > $50K. Trigger: adoption < 50% for 2 consecutive months pages the Director PMM for sales-enablement review.Target ≥ 65–75%

Competitive-loss rate against named competitors (Win/Loss tagged). Trigger: rate worsens 2 quarters in a row or jumps > 5 pts QoQ pages the VP Marketing for positioning review.Trend flat-to-down

What it does

Task list

Daily Crawl top-3 competitor homepages + pricing pages. Diff against yesterday. Flag material wording changes.
Daily Watch named-competitor hiring pages (Greenhouse / Lever / public job feeds). Surface new senior hires + strategic role openings.
Daily Watch named-competitor changelogs, release notes, and product-update feeds. Flag any feature shipping in our differentiator space.
Daily Watch press feeds (TechCrunch, The Information, Pitchbook, vertical trade press) for named competitor coverage.
Weekly Review G2 / TrustRadius / Capterra new reviews for our competitor set. Surface pattern shifts in praise / complaint.
Weekly Compile the weekly Competitive Digest — what moved, what didn’t, the 3 things AEs need to know.
Weekly Update battlecards for any competitor with material change this week. Refresh proof points + objection handles.
Monthly Analyst watch: Gartner / Forrester / IDC report updates. Magic Quadrant + Wave shifts.
Monthly Competitor set audit: which competitors are showing up most in lost deals? Recommend additions / removals from the watched set.
Quarterly Full competitive teardown of top 3 — positioning, pricing, target segment, strengths, weaknesses, where-to-attack.
Event When Win/Loss surfaces a competitor we’re losing to that’s not on the watched list, add to the watched set within 24 hours.
Event When a competitor announces a category-shifting move (acquisition, major product launch), draft AE talking points within 4 hours.

Schedule grid

Task	Frequency	Duration	Output goes to
Daily site / pricing crawl	Daily 05:00	~15 min	Snapshot store + alert queue
Daily hiring page scan	Daily 05:30	~10 min	PMM + Talent Intelligence
Daily changelog watch	Daily 06:00	~10 min	PMM + Product
Daily press watch	Daily 06:30	~15 min	PMM + PR Comms Agent
Weekly review-site scan	Weekly Mon 09:00	~30 min	PMM + Reviews Agent
Weekly Competitive Digest	Weekly Mon 11:00	~45 min compile	All AEs + PMM + VP Marketing + Sales Director
Weekly battlecard refresh	Weekly Tue 10:00	~60 min	AEs + Sales Director
Monthly analyst watch	Monthly 1st	~90 min	VP Marketing + Head of PMM
Quarterly full teardown	Quarterly Q-1 days	~6 hours	VP Marketing + CRO + CEO

Triggers

Scheduled (cron-style):

Schedule	What it runs
`0 5 * * *`	Daily site / pricing crawl
`30 5 * * *`	Daily hiring page scan
`0 6 * * *`	Daily changelog + press watch
`0 11 * * 1`	Weekly Competitive Digest
`0 10 * * 2`	Weekly battlecard refresh
`0 9 1 * *`	Monthly analyst watch
`0 9 10 1,4,7,10 *`	Quarterly full teardown

Event-driven:

Event	What it runs
Competitor homepage hero changes > 30% of words	Flag to PMM within 1 hour; refresh battlecard
Competitor pricing page changes	Page Pricing Intelligence Agent + Head of PMM within 30 min
Competitor announces acquisition or funding	Draft AE talking points within 4 hours; brief CRO
Win/Loss flags new competitor	Add to watched set within 24 hours; build v0.5 battlecard within 7 days
Competitor wins an analyst placement (Leader quadrant, etc.)	Brief VP Marketing + draft counter-positioning within 48 hours

Who it works with

Inputs

Source	Type	Cadence	Required?
Operator Brief (Sections 4, 5, 6)	Markdown	Read every run	Required
Watched-competitor registry (names + URLs + tracking points)	YAML	Versioned	Required — core config
Competitor homepage / pricing / feature page HTML	HTML crawl	Daily	Required
Job posting feeds (Greenhouse / Lever / Workday public)	API / scrape	Daily	Required
Changelog feeds (RSS / public docs)	RSS / scrape	Daily	Required
Press feeds (Google News + curated sources)	RSS / API	Daily	Required
Review-site APIs (G2, TrustRadius, Capterra)	API	Weekly	Optional
Analyst report subscriptions (Gartner / Forrester / IDC)	PDFs / portal	Monthly	Optional
Win/Loss Agent themes	Markdown	Per-interview	Required — surfaces new competitors

Outputs

Output	Format	Target path	Audience
Daily competitor snapshots	HTML diffs + metadata	/competitive/snapshots/YYYY-MM-DD/	Internal store
Daily alerts (when triggered)	Slack DM + ticket	Slack #competitive + Linear	PMM + AE if material
Weekly Competitive Digest	Markdown + Slack message	/competitive/digests/YYYY-WW.md	All AEs + PMM + VP Marketing + CRO
Per-competitor battlecard	Markdown (refreshed weekly)	/competitive/battlecards/<competitor>.md	AEs + Sales Director
Monthly analyst-watch report	Markdown	/competitive/analyst/YYYY-MM.md	VP Marketing + Head of PMM
Quarterly competitive teardown	Markdown + chart bundle	/competitive/teardowns/Q<n>.md	CEO + VP Marketing + CRO + CPO

↑ Upstream — agents/sources that feed this one

Operator Brief (human-maintained). Section 5 declares the competitor set; Section 6 positioning anchors counter-messaging.
Win/Loss Agent. Themes surface new competitors + confirm where we’re losing to whom.
Signal Router. Routes competitor-related signals from CRM closed-lost reason fields.
Account Intel Hub. Per-account competitor mentions inform deal-level prioritization.

↓ Downstream — agents/humans that consume its output

Every AE (human). Reads battlecards mid-deal; uses talking points during competitor pushback.
Pricing Intelligence Agent. Receives competitor pricing changes for cross-reference.
PR Comms Agent. Receives press + analyst signals for narrative coordination.
Brand & Positioning Agent. Receives category-shift signals that may require positioning updates.
Web Operations Agent. Receives material-page-change signals for counter-update consideration.
Performance Marketing Agent. Receives auction + share-of-voice intel for paid-channel response.
Brief Sync Agent. Receives material moves that may require Brief Section 5 updates.

Human escalation paths

Trigger condition	Escalate to	Within
Competitor announces a category-shifting move	VP Marketing + CRO + CEO	< 4 hours
Competitor wins analyst Leader placement we’re below	VP Marketing + Head of PMM	< 48 hours
Battlecard > 30 days unrefreshed	Head of PMM + Sales Director	Same week
Win/Loss surfaces a competitor not in watched set 3+ times in a month	Head of PMM + VP Marketing	< 7 days
Pricing page change with no Pricing Intelligence cross-reference within 24h	Head of PMM	Same business day

How to build it

System prompt

You are the Market Intelligence Agent for [COMPANY]. YOUR JOB Be the team's ears on the competitive landscape. Watch named competitors daily. Diff snapshots. Surface material moves to PMM + AEs within 24 hours. The AE never hears about a competitor move from a buyer first. INPUTS (always read in this order) 1. /operator-brief.md (Sections 4 RtW, 5 Competitive, 6 Brand) 2. /competitive/watched-set.yaml - registry of competitors + tracking points 3. /competitive/snapshots/ - historical snapshots for diffing 4. Today's crawl output (raw HTML, hiring posts, changelogs, press) OUTPUTS - /competitive/snapshots/YYYY-MM-DD/ (raw + diffs) - /competitive/digests/YYYY-WW.md (weekly) - /competitive/battlecards/<competitor>.md (per-competitor) - /competitive/teardowns/Q<n>.md (quarterly) RULES 1. Every claim cites a snapshot URL + date. 2. Material change = >30% wording shift on hero/pricing, OR named senior hire, OR shipped feature in our differentiator space, OR press at top-3 source. 3. Battlecards have 8 sections: their pitch, target buyer, where they win, where we win, discovery questions, top 3 objections + 2-sentence responses, proof points, trap to avoid. 4. Never invent positioning claims about a competitor - cite their copy. 5. Never share competitor URLs / data outside the marketing + sales scope. 6. When competitor moves into our positioning space, flag the conflict for Brand & Positioning Agent to address. ESCALATION - Category-shifting move: VPM + CRO + CEO within 4h. - Analyst Leader placement we're below: VPM + Head PMM within 48h.

Tools & integrations

Platform / tool	Used for	Required?
Replit + n8n (crawl + diff runner)	Daily snapshot orchestration	Required
Postgres (snapshot store)	Historical diff baseline	Required
Python + BeautifulSoup + Playwright	HTML scraping for SPA + dynamic content	Required
Greenhouse / Lever / Workday public APIs	Hiring page intelligence	Required
Google News API + RSS	Press monitoring	Required
G2 / TrustRadius / Capterra APIs	Review-site monitoring	Optional
Slack API	Daily alerts + weekly digest	Required

Guardrails — what it must not do

Never crawl behind login walls without explicit license. Public-page only.
Never invent competitor positioning claims — cite their copy verbatim.
Never include un-sourced competitor pricing — cite the page URL + snapshot date.
Never share watched-set or battlecards outside the marketing + sales scope without VP Marketing approval — competitive IP.
Honor robots.txt + crawl rate limits.
Never use competitor data to draft ads or content that names them in comparative claims without legal review.
Never store competitor employee personal data — track roles + titles only.

Evals + hallucination defense

Evals — output quality checks:

Detection lead time. When AEs encounter a competitor move, was the agent ahead of them? Target ≥ 90% — ahead vs. behind ratio.
Battlecard adoption. Monthly: % of late-stage deals > $50K where the AE pulled the battlecard. Target ≥ 70%.
Signal-to-noise. Weekly: of alerts flagged material, what % did PMM confirm as material? Target ≥ 60%.
Win-rate impact. Quarterly: win-rate against the named-competitor set vs. trailing 4Q. Target +5 pts after agent + battlecards live.

Hallucination defense — specific checkpoints:

Competitor positioning claims must cite the homepage / pricing page URL + snapshot date.
Pricing claims must cite the page or a documented sales-call source (no “industry knowledge”).
Hiring signals must trace to the specific job posting URL.
Analyst placements must cite the report name + year + page.
When competitor data is missing for a battlecard field, mark it “not yet observed” rather than guess.

Maturity curve + first-run checklist

v0.1 — Manual-assistAgent runs crawls on-request. PMM does diffs by hand. Useful from day 1 to replace ad-hoc competitor research.

v0.5 — SupervisedDaily crawls + diffs + alerts. Weekly digest + battlecard refresh. PMM reviews edge cases. Default ship state.

v1.0 — Semi-autonomousAfter 90 days of clean evals + AE adoption ≥ 70%, agent auto-publishes weekly digest to all AEs without PMM gate. Battlecard refreshes still PMM-approved.

First-run checklist — 5 steps from spec to running agent:

Author the watched-set YAML with PMM + Sales Director. Start with top 3 competitors; expand to 10 over the first quarter.
Stand up the crawl runtime + snapshot store. Verify daily crawls land cleanly.
Author the v0.5 battlecards for the initial 3. Tune the structure with AE input.
Run in shadow mode for 2 weeks. PMM reviews alerts daily; tunes the material-change threshold.
Turn on AE distribution. Subscribe all AEs + PMM + VP Marketing to the weekly digest. Log every run.

Product Marketing & Competitive Intelligence