Skip the Claude mode debate

Most marketing teams I’ve worked with this past year are running similar setups. ChatGPT or Gemini lives in a permanently open browser tab, and the team’s saved prompts live in a Slack channel or Google doc that they copy and paste from. That’s a great way to get started, but as usage matures, the team needs more coordination and better tooling. Teams have seen all of the hoopla around Claude Code, and many of my clients are moving in that direction. Inevitably, they always end up asking the same question. How do I get started with Claude and which mode (Chat, Cowork, or Code) should I be using?

Take a gander around Substack and you’ll see an endless debate about which mode to use when. Chat for quick questions, Cowork to help connect your files and tools like Gmail, and Code for the technical bits. My recommendation is the same one I follow myself. Use only Claude Code. That’s it.

Remember the movie The Matrix? This is the same red pill / blue pill choice that Neo had. The browser tab is the blue pill. It’s easy and familiar, every conversation is a fresh start, and nothing compounds. Claude Code is the red pill. The editor is unfamiliar for a day. After that, you can’t unsee what’s on the other side and there’s no turning back.

The install takes 15 minutes, the vocabulary another 10. This post covers both, plus the case for skipping the debate.

A tool is not a stack

Installing Claude doesn’t change the AI itself. The model in your browser tab and the model in Claude Code are the same Anthropic model. But, the wrapping and context around the model differ. The additional context you build inside Claude Code turns the AI from a tool into a full-fledged marketing operating system. You can use it on your own, or, as your team scales, you can share context across your entire marketing or GTM function.

Browser-tab AI gives you the model and a chat window. That’s it. Memory exists, but it’s behind a separate settings screen, and you update it manually. The memory itself may leak across contexts you didn’t ask it to span. When you advise multiple clients or work on anything sensitive like product roadmaps, acquisitions, and launch plans, that can be problematic to say the least. The conversation you had about your upcoming product launch is one ambient prompt away from showing up in your conversation or content that’s being pushed to public channels before you’re ready. Consultants don’t want info from Client A leaking into Client B. You have better control over this in Claude Code.

Chat-only setups don’t share very well. Your colleague can’t inherit the prompts and context you’ve built up. Every team conversation is like a Saturday Night Live (SNL) cold open. Claude Code gives you the model plus four pieces that surround it that are transformative..

1. Memory you can scope to a project, so what Claude knows about Client A stays with Client A.

2. Skills you write once and reuse across the team with a slash command.

3. CLAUDE.md is a markdown file the team can read and edit, so the brand voice and deliverable formats are the same whether you’re drafting or your colleague is.

4. MCPs wire Claude into the tools you already use, like Gmail, Sheets, and Calendar. You don’t switch tabs or copy data into a chat. Claude reaches into the tools where the data lives.

Skills, CLAUDE.md, and MCPs all live in Code mode. Memory follows you across modes, and Code lets you scope it per project. That’s not coincidence. It’s why the rest of this post leans toward Cursor.

The 15-minute install

Four installs, about 15 minutes total. You can do this between meetings. I’ve run this install on my Mac and helped clients on Windows machines, and it doesn’t take long. To get started, follow these steps:

1. Start with a free GitHub account (2 minutes). This is where your team’s repo lives. Have the repo owner add you and accept the invite when it lands in your inbox.

2. Next, download Cursor and sign in with your work account (5 minutes). Cursor is the workspace where Claude Code runs. Defaults are fine and there is no need to buy a subscription.

3. Then install the Claude desktop app (3 minutes). You’ll mostly live in Code, but the desktop app is where you manage your account, and it pairs with Claude Code on the same login.

4. Finally, install Claude Code itself (5 minutes). Open Cursor’s terminal (View → Terminal) and paste the install command for your OS. On macOS or Linux, that’s curl -fsSL https://claude.ai/install.sh | bash. On Windows PowerShell, it’s irm https://claude.ai/install.ps1 | iex. Type claude and sign in when prompted. Claude Code requires a paid Anthropic plan (Pro, Max, Team, or Enterprise).

Here’s the checklist:

• Open Cursor and sign in

• Open the Claude desktop app and sign in

• Run claude in Cursor’s terminal without errors

• See your team’s repo on your GitHub account

When you get stuck, ask Claude. It can walk you through any install error, terminal command, or path issue you hit.

The three modes (and the one you need)

“Chat answers. Cowork connects to your tools. Code does all of that and more.”

— David Sweenor, Founder/CEO, TinyTechGuides

You’ll see three modes in the docs. Here’s what each one does, then what to do with that information.

• Chat: Back-and-forth conversation in a window. Best for quick questions, drafts, and brainstorming.

• Cowork: Claude plans and executes a task on your files, apps, and browser. Best for multi-step work that doesn’t live in a repo.

• Code: Terminal-based, runs inside a repo. Best for shared team docs, branded decks, and anything you want versioned.

Each mode has its own use case in the docs and its own corner of the marketing AI internet defending it. Last week, I saw a debate about whether spreadsheet research belongs in Cowork or Code. The week before, someone argued that brainstorming should never happen anywhere except Chat.

Each of the modes above is technically true, but none of them gets you to a marketing OS. Code does.

Code is where Skills, CLAUDE.md, and MCPs live. MCP stands for Model Context Protocol, the way Claude connects to other systems like Gmail, Asana, Canva, and Calendar. Code is where work compounds across sessions, where memory gets project-scoped, and where the team can see and edit what you made (via GitHub).

The most underrated benefit shows up when you need something none of those four pieces provide. An action-item tracker that pulls from your meeting notes. A status-report rollup across all your clients. Or a one-off Python script to clean up your Downloads folder. Code writes that on the fly. Browser-tab AI can’t write code that touches your files. Code can.

Teams matter too. When you ship work in Code to GitHub, your colleague clones the repo and inherits everything you’ve built. The Skills you wrote. The CLAUDE.md that defines the brand voice. The project-scoped memory rules. Browser-tab AI doesn’t ship. Your work stays on your account, where no one else can use it.

The Cursor interface is unfamiliar for the first day. The first 30 seconds are the worst. There’s a sidebar, a file tree, and a terminal pane. Push through it. After that, you’ve crossed the line, and you don’t go back, ever.

The four components that make Claude Code so powerful

Four components configure Claude. Three define how Claude works. The fourth wires Claude into the tools where your work already lives.

Memory is about you. Your role, your voice preferences, and how you like content formatted. Personal and portable across every project you work in. You set it once, and Claude carries it from session to session. After three months of corrections, the memory you’ve built is what makes Claude sound like you instead of a smart intern.

Skills are about the task. A Skill is a reusable recipe (instructions plus examples) that you call with a slash command. /write-blog. /generate-deck. /prep-podcast. Each one bundles the steps Claude should take for that task and the format of the output. For anyone already writing prompt workflows, Skills are how those workflows become team-shareable assets in your repo. Write a Skill once, and it works the same way every time you call it.

CLAUDE.md is about the project. It’s a markdown file in the project’s repo that Claude reads every time it works in that scope. It’s where you write down what’s true for this project. Brand voice. Audience. Deliverable formats. Drop one in your TTG repo, drop another in your client repo, and Claude switches voices without you reminding it.

MCPs wire Claude into the tools where your work already lives. Where Memory, Skills, and CLAUDE.md tell Claude how to work, MCPs tell Claude where to reach. Each MCP connects Claude to a specific tool, like Gmail, Sheets, Calendar, or Asana. You don’t have to copy data into a chat. Install one and Claude reaches into that tool. Install several and Claude works across your whole toolchain.

“Memory is about you. Skills are about the task. CLAUDE.md is about the project, and MCPs connect your apps.”

— David Sweenor, Founder/CEO, TinyTechGuides

A growing set of community patterns extends the same idea. A popular one is napkin.md, a per-repo runbook that Claude reads at session start and curates as you work. It catches mistakes once and stops repeating them. You commit it or you don’t, your call.

Your first move

You finished the install. Now what?

Open Cursor’s terminal, run claude, and have a five-minute conversation. Tell Claude who you are. Tell it what you do. Tell it the three things you reach for most often in a week. Save what you tell it as memory.

That’s the first move. Anything more is week-two work. Your first Skill conversion, your first CLAUDE.md, and your first MCP can wait. None of that matters in week one. Build the habit of opening Cursor, typing claude, and treating it like a colleague who started Monday.

Take the red pill

Fifteen minutes is the easy part. The IDE filters out most marketers. The marketing OS rewards the ones who push through.

Most marketers won’t cross the gate, which is why their AI output never compounds. You’re reading this, which means you’re closer than you think. Cross the gate. Take the red pill.

This post is the entry point for the Claude for Marketing Operators series on TinyTechGuides. The next eight posts walk through each layer of your marketing OS. The four-layer mental model. CLAUDE.md teardowns from real client projects. The MCPs that pull their weight, and the ones that don’t. What six months of memory looks like across multiple clients. How a solo consultant runs four engagements on one brain. Why your marketing OS becomes the moat your competitors can’t copy.

If you want each one as it drops, subscribe to the Marketing section on Substack.

Share

Leave a comment

Frequently asked questions

What is Claude Code?

Claude Code is the terminal-based mode of Anthropic’s Claude AI assistant, built for work that lives in a code repository. For marketers, it runs inside an editor like Cursor and lets you maintain a project rulebook (CLAUDE.md), reusable Skills, scoped memory, and connectors (MCPs) to tools like Gmail and Sheets. It’s also the only mode that can write Python on the fly to handle tasks none of those four pieces cover, like building an action-item tracker or a status-report rollup across clients.

How does Claude Code differ from Chat and Cowork?

Chat is back-and-forth conversation. Cowork lets Claude plan and execute multi-step tasks across your files, apps, and browser. Code runs in your terminal inside a code repository, so the work compounds across sessions through Skills, CLAUDE.md, scoped memory, and MCPs. Chat and Cowork are useful for narrow tasks. Code is where reusable assets live and where teams can share what one person built. For marketing operators using Claude in production, the recommendation is to skip the mode debate and run everything in Code.

Do I need to be a developer to use Claude Code?

No. Claude Code runs in a terminal, but you don’t need to write code to use it. You install it once, then talk to Claude in plain English. The terminal interface is unfamiliar for the first day, but most marketing tasks (drafting blog posts, building decks, summarizing client meetings, packaging prompts as reusable Skills) work the same way they do in a chat window. The benefit is that everything you do compounds across sessions and can be shared with your team through a repo.

Does Claude Code require a paid Anthropic plan?

Yes. Claude Code requires a Pro, Max, Team, or Enterprise plan from Anthropic. The free Claude.ai plan does not include Claude Code access. The desktop app, browser-based Claude.ai, Cursor, and GitHub are all free — only the Claude Code CLI itself needs a paid plan. You can install all four pieces (GitHub, Cursor, Claude desktop app, Claude Code) before deciding on a plan, since the install completes before authentication.

What’s the difference between memory and a CLAUDE.md file?

Memory is personal and portable across every project you work in: your role, voice preferences, and how you like content formatted. CLAUDE.md is project-specific. It’s a markdown file in a project’s repo that Claude reads every time it works in that scope, capturing brand voice, audience, deliverable formats, and anything else that’s true for that project. Memory follows you across modes; CLAUDE.md stays with the project. A solo consultant runs one memory and many CLAUDE.md files, one per client.

Where should I start if I want to use Claude for marketing work?

Install the four pieces (GitHub, Cursor, Claude desktop app, Claude Code) in about 15 minutes. Then open Cursor’s terminal, run claude, and have a five-minute conversation. Tell Claude who you are, what you do, and the three things you reach for most often in a week. Save what you tell it as memory. That’s the entire first move. Skill conversion, CLAUDE.md drafting, and MCP setup are all week-two work. Week one is opening the terminal and starting to use it.

About David Sweenor

David Sweenor is the founder and host of the Data Faces podcast, where he talks with the people who are making data, analytics, AI, and marketing work in the real world. He is also the founder of TinyTechGuides and a recognized top 25 analytics thought leader and international speaker who specializes in practical business applications of artificial intelligence and advanced analytics.

With over 25 years of hands-on experience implementing AI and analytics solutions, David has supported organizations including Alation, Alteryx, TIBCO, SAS, IBM, Dell, and Quest. His work spans marketing leadership, analytics implementation, and specialized expertise in AI, machine learning, data science, IoT, and business intelligence. David holds several patents and consistently delivers insights that bridge technical capabilities with business value.

Books

• Artificial Intelligence: An Executive Guide to Make AI Work for Your Business

• Generative AI Business Applications: An Executive Guide with Real-Life Examples and Case Studies

• The Generative AI Practitioner’s Guide: How to Apply LLM Patterns for Enterprise Applications

• The CIO’s Guide to Adopting Generative AI: Five Keys to Success

• Modern B2B Marketing: A Practitioner’s Guide to Marketing Excellence

• The PMM’s Prompt Playbook: Mastering Generative AI for B2B Marketing Success

Follow David on Twitter @DavidSweenor and connect with him on LinkedIn.

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Consensus Path Planning and Deal Acceleration

Created by insights.tinytechguides.com

What this workflow does

I’ve watched deals die where every single stakeholder privately supported the purchase. No one objected. No one said no. The deal just stalled because nobody created a mechanism to turn all that private support into a collective decision.

When a deal goes quiet, sales teams usually blame a lack of motivation. The champion went dark. The economic buyer stopped responding. The technical team wants more data. These look like engagement problems. They’re structural failures. The committee never reached a specific consensus milestone, and nobody noticed because the pipeline report tracks stages, not alignment.

This workflow maps the path from first engagement to signed deal. It identifies the sequence of stakeholder engagements, the milestones the committee must reach, the mechanisms that build collective commitment, and the recovery protocols for when deals stall. The output is a deal architecture document that gives sales a stage-by-stage engagement plan and gives marketing visibility into where their content supports committee alignment.

This workflow does not create messaging, map the committee, or surface hidden objections. That’s what the first three workflows in this series do.

It answers one question: what is the specific path from fragmented interest to collective commitment, and what do you do when that path breaks?

Workflow steps summary

Step 0: Define inputs

Step 1: Define the consensus milestones

Step 2: Map the stakeholder engagement sequence

Step 3: Identify consensus-building mechanisms

Step 4: Design the stall recovery playbook

Step 5: Build the deal architecture timeline

Step 6: Assemble the consensus path plan

This is the fourth and final workflow in the buying committee series. It builds on the outputs from the first three:

• Buying Committee Decision Mapping Workflow

• Hidden Objection and Risk Surface Analysis

• Committee-Aware Messaging and Content Mapping

The workflow was created by insights.tinytechguides.com and connects to these existing workflows:

• Prompt Workflow: Voice of Customer

• Prompt Workflow: Competitive Landscape Mapping

• QuickStart Battlecard for Competitive Sales Wins

• Strategic Battlecard Workflow for Competitive Wins

Step 0: Define inputs

Before running the workflow, gather these inputs:

• {account_type} = target account profile or segment

• {deal_examples} = recent won, lost, and stalled deals

• {sales_inputs} = call notes, objections, deal commentary

• {customer_inputs} = outputs from Voice of Customer workflow

• {competitive_context} = outputs from Competitive Landscape Mapping

• {committee_map} = output from Buying Committee Decision Mapping Workflow

• {risk_analysis} = output from Hidden Objection and Risk Surface Analysis Workflow

• {messaging_map} = output from Committee-Aware Messaging and Content Mapping Workflow

• {avg_sales_cycle} = average sales cycle length for this deal size

• {sales_process} = current sales stages or methodology (e.g., MEDDPICC, Sandler, custom stages)

Step 1: Define the consensus milestones

A signed deal is the final milestone, but it is the result of many smaller consensus events that happen inside the buying organization. Before a committee can approve a purchase, they must collectively agree on a series of intermediate decisions. That the problem is worth solving. That the category of solution is right. That this vendor is the best fit. That the timing is right. That the terms are acceptable. Missing any of these intermediate consensus points creates a stall, and most sales teams cannot tell you which milestone their deal has actually reached versus which one they have assumed.

Prompt:

Role

You are a senior B2B sales strategist who designs deal architectures for complex enterprise sales involving multi-stakeholder buying committees.

Context

A signed deal requires the committee to reach consensus on five intermediate decisions: problem significance, solution category, vendor preference, timing, and terms. Missing any of these creates a stall that shows up as a “stuck” deal in the pipeline.

Task

Using {committee_map}, {risk_analysis}, {sales_inputs}, and {deal_examples}, define the internal consensus milestones for a purchase in {account_type}.

Format

For each of the five milestones (problem consensus, category consensus, vendor consensus, timing consensus, terms consensus):

• Description of what agreement looks like at this stage

• Key stakeholders who must be aligned

• Evidence they need to reach alignment

• The gatekeeper for this milestone

• The most common reason this milestone stalls

• The event or evidence that unlocks it

Deliver as a table. After the table, provide a narrative summary (3-5 sentences) describing the typical sequence and where the buying process most often breaks down.

Tone

Strategic and grounded in real-world sales dynamics. Write as someone who knows the difference between a milestone that has been genuinely reached and one that has been assumed.

Your pipeline isn’t stuck. It just skipped a milestone nobody noticed.

Step 2: Map the stakeholder engagement sequence

The order in which you engage stakeholders matters as much as the message. Engaging the economic buyer too early, before the technical team has validated feasibility, undermines credibility. Engaging procurement too late, after expectations are set without their input, creates adversarial dynamics. The right sequence builds momentum by creating a chain of internal endorsements where each stakeholder’s support makes the next engagement easier.

Prompt:

Role

You are a senior enterprise sales architect who designs multi-threaded engagement strategies for complex B2B deals with large buying committees.

Context

Buying committees do not engage in a linear sequence. Some stakeholders can be engaged in parallel. Others must be sequential. The wrong order creates friction that compounds across the deal cycle.

Task

Using the consensus milestones from Step 1, {committee_map}, and {sales_inputs}, design the optimal stakeholder engagement sequence for {account_type}.

Format

1- Engagement timeline table with columns: Stakeholder, First Engagement Timing, Engaged By, Goal of First Engagement, Prerequisites

2- Multi-threading strategy describing which stakeholders can be engaged simultaneously, which must be sequential, and where the champion should make introductions versus where sales should request meetings directly

3- Escalation triggers table with columns: Stall Signal, Escalation Action, Who to Involve, Anti-Pattern to Avoid

4- A text-based engagement sequence showing the flow across deal stages

Tone

Tactical and specific. Build this for a sales team executing on real deals, not a training manual.

Step 3: Identify consensus-building mechanisms

Individual stakeholder buy-in does not automatically become committee consensus. A committee where every member privately supports the purchase can still fail to act because no one created the mechanism for converting private support into collective commitment. Consensus requires structure. Shared evaluation criteria, visible commitment signals, and events where alignment is tested and confirmed rather than assumed.

Prompt:

Role

You are a senior organizational psychologist and B2B sales strategist who specializes in the dynamics of group decision-making within enterprise buying committees.

Context

The gap between individual interest and collective commitment is where most deals die. Consensus requires shared frameworks, commitment events, and coalition management, not just good meetings with individual stakeholders.

Task

Using the outputs from Steps 1-2, {committee_map}, and {risk_analysis}, identify the mechanisms that build consensus within this buying committee for {account_type}.

Format

1- Shared evaluation framework with 5-8 weighted criteria the committee can use to evaluate together rather than in isolation

2- Commitment escalation events table with columns: Event, Purpose, Success Signal, Facilitation Notes

3- Coalition-building tactics as a numbered list, each with a 2-3 sentence description covering alliance strengthening, friction neutralization, swing vote conversion, and blocker isolation

4- Commitment artifacts table with columns: Artifact, Associated Milestone, Owner, Why It Matters

Tone

Practical and psychologically informed. Write as someone who understands both the organizational dynamics and the tactical moves that convert understanding into action.

Step 4: Design the stall recovery playbook

Every complex B2B deal stalls at some point. The question is not whether stalls happen but whether the team can diagnose the cause and execute a recovery before the deal slips to “no decision.” Most sales teams treat stalls as a motivation problem when they are actually a structural problem. A specific consensus milestone was not reached, or a specific stakeholder’s concern was not addressed, and no one noticed until the deal went quiet.

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Committee-Aware Messaging and Content Mapping

Created by prompts.tinytechguides.com

What this workflow does

Most B2B messaging frameworks build one core value proposition with three or four supporting pillars underneath. That structure works for demand generation. It breaks down the moment a deal enters committee evaluation.

A buying committee has five to ten stakeholders who evaluate the same purchase through different lenses. The CFO is filtering for cost predictability. The VP of Engineering is scanning for integration risk. The end user wants to know if this thing will make their life easier or harder. A message that resonates with the champion may be irrelevant to the blocker and threatening to the person who owns the budget.

This workflow builds a messaging architecture that maps specific messages, proof points, and content assets to each committee role at each stage of the buying process. It includes a champion enablement toolkit and an objection-to-message bridge that connects every anticipated concern to a pre-built response.

This workflow does not map the committee or surface hidden objections.

That’s what the first two workflows in this series do.

It answers one question:

“What should we say, to whom, at what stage, and through what channel to move the entire committee toward a decision?”

Workflow steps summary

Step 0: Define inputs

Step 1: Define messaging pillars by committee role

Step 2: Map message-to-stage alignment

Step 3: Identify content gaps and build asset briefs

Step 4: Build the champion enablement toolkit

Step 5: Create the objection-to-message bridge

Step 6: Produce the messaging and content map

This is the third workflow in the buying committee series. It builds on the outputs from the first two:

- Buying Committee Decision Mapping Workflow

- Hidden Objection and Risk Surface Analysis

The workflow was created by prompts.tinytechguides.com and connects to these existing workflows:

- Prompt Workflow: Voice of Customer

- Prompt Workflow: Competitive Landscape Mapping

- QuickStart Battlecard for Competitive Sales Wins

- Strategic Battlecard Workflow for Competitive Wins

Step 0: Define inputs

Before running the workflow, gather these inputs:

- {account_type} = target account profile or segment

- {deal_examples} = recent won, lost, and stalled deals

- {sales_inputs} = call notes, objections, deal commentary

- {customer_inputs} = outputs from Voice of Customer workflow

- {competitive_context} = outputs from Competitive Landscape Mapping

- {committee_map} = output from Buying Committee Decision Mapping Workflow

- {risk_analysis} = output from Hidden Objection and Risk Surface Analysis Workflow

- {current_messaging} = your current messaging framework, value propositions, or sales deck narrative

- {existing_content} = list of current content assets (case studies, white papers, blog posts, webinars, ROI tools)

Step 1: Define messaging pillars by committee role

Traditional messaging builds a single value proposition hierarchy. One core message, three supporting pillars, proof points underneath. That structure collapses when a committee of seven people reads it through seven different lenses.

Prompt:

# Role

You are a messaging architect building role-specific messaging for a complex B2B buying committee.

# Context

B2B buying committees contain stakeholders who evaluate the same purchase through different priorities. A value proposition that resonates with the champion may be irrelevant to the blocker.

# Task

Using {committee_map}, {risk_analysis}, {current_messaging}, and {sales_inputs}, define messaging pillars for each committee role in {account_type}.

# Format

For each role:

- Primary messaging pillar (the single most compelling message for this stakeholder)

- Supporting proof points (2-3 specific evidence types that make the message credible)

- Language register (how this stakeholder prefers to receive information)

- Message to avoid (the framing that would backfire with this stakeholder)

Then provide the overarching narrative thread that connects all role-specific messages into a coherent story the champion can use to build consensus.

# Tone

Strategic and precise. The same product needs to mean different things to different people without contradicting itself.

Your champion’s pitch fails the moment it reaches someone who wasn’t in the room

Step 2: Map message-to-stage alignment

Not every stakeholder is active at every stage. A message that works during early education feels repetitive during evaluation. A message designed for final approval feels premature during discovery. Timing the right message to the right person at the right moment is where most go-to-market motions fall apart.

Prompt:

# Role

You are a demand generation strategist designing multi-stakeholder engagement sequences for complex B2B deals.

# Context

Buying committees do not engage with vendors all at once. Different stakeholders enter at different stages with different information needs.

# Task

Using the messaging pillars from Step 1, map message delivery across these buying stages: Awareness, Education, Evaluation, Consensus Building, and Negotiation/Approval.

# Format

A matrix with stakeholder roles as rows and buying stages as columns. In each cell:

- Message summary

- Content format (case study, ROI calculator, technical brief, etc.)

- Delivery channel (website, email, sales conversation, champion shares internally)

- Who delivers it (marketing, sales, champion, executive sponsor)

Mark “Not active at this stage” where a stakeholder is not yet engaged.

After the matrix, identify the 2-3 most critical message-timing combinations where getting it right has the highest impact on deal progression.

# Tone

Operational and specific. Build this for a team that needs to create campaigns from it.

Step 3: Identify content gaps and build asset briefs

Most B2B content libraries are built around product features or thought leadership themes rather than buyer committee needs. This creates gaps where critical stakeholders at critical moments have no relevant content available, and surplus where content exists but doesn’t map to any specific buying decision.

Prompt:

# Role

You are a content strategist auditing a B2B content portfolio against buying committee needs.

# Context

Content should map to specific stakeholders at specific stages. Content that doesn’t serve a stakeholder-stage combination is either a gap or clutter.

# Task

Using the message-to-stage matrix from Step 2 and {existing_content}, conduct a content gap analysis.

# Format

1- Coverage matrix matching Step 2’s structure, with each cell marked as Covered, Partially Covered, or Gap

2- Prioritized list of content gaps ranked by impact (high-influence stakeholder at a deal-critical stage = higher priority)

3- Asset briefs for the top 5 gaps, each including: asset type, target stakeholder, buying stage, key message, required proof points, and estimated production effort

4- Content retirement candidates that don’t map to any stakeholder-stage combination

# Tone

Analytical and practical. Write for a content lead planning next quarter’s production calendar.

Because a case study nobody needs is worse than a gap you know about

Step 4: Build the champion enablement toolkit

The internal champion is the most important and most under-supported person in a B2B deal. They carry the burden of building consensus, but most vendors equip them with product decks and datasheets designed for vendor-to-buyer conversations. The champion needs materials for buyer-to-buyer conversations. Materials that sound like something a colleague would say, not something a marketing team wrote.

Prompt:

# Role

You are a sales enablement strategist arming internal champions with tools to build consensus inside buying committees.

# Context

Champions lose credibility when they forward vendor materials that read like marketing copy. They need internal-facing narratives, talking points, and business case structures that work in hallway conversations and internal emails.

# Task

Build a champion enablement toolkit using the messaging architecture from Steps 1-3 and the risk analysis from {risk_analysis}.

# Format

1- Internal pitch narrative (3-5 sentences the champion can say to peers about why this purchase matters now, in plain language)

2- Stakeholder-specific talking points table with columns: Target Stakeholder, Emphasize, Avoid, Proof Point to Reference

3- Internal business case outline with section names, required data points, and narrative arc

4- Objection preemption scripts for the 3 most likely committee objections (conversational, not rehearsed)

5- “What if we do nothing” argument (3-4 sentences about organizational cost of inaction, not product benefits)

# Tone

Conversational and human. Everything should sound like something a real person would say to a colleague.

The champion’s credibility dies the moment they start sounding like a vendor

Step 5: Create the objection-to-message bridge

Objection handling in most B2B organizations is ad hoc. Sales reps develop their own responses based on experience, and marketing creates content without knowing which specific objections it needs to address. The result is inconsistent messaging and missed opportunities to neutralize concerns before they escalate.

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Hidden Objection and Risk Surface Analysis

Created by prompts.tinytechguides.com

What this workflow does

Most sales teams prepare for the objections buyers raise in meetings. Price. Timeline. Feature gaps. Integration concerns. Those are the objections people feel comfortable voicing because they sound rational and defensible.

The objections that actually kill deals are the ones nobody says out loud.

A VP of IT who says “we need more time to evaluate” is really thinking “if this implementation fails, that’s my reputation on the line.” A CFO who pushes back on price is really wondering whether the board will question the spend. A line-of-business leader who keeps requesting more references is stalling because their IT peer hasn’t been consulted and could undermine the project later.

This workflow surfaces those hidden fears, maps the structural conditions that make “no decision” feel like the safest option, and produces a risk mitigation playbook your team can actually use.

This workflow does not create content or messaging.

That’s the next workflow in this series.

It answers one question:

“What is everyone on the committee afraid to say out loud, and what do you do about it?”

Workflow steps summary

• Step 0: Define inputs

• Step 1: Surface hidden objections by role

• Step 2: Map the “no decision” incentive structure

• Step 3: Identify organizational risk triggers

• Step 4: Build the risk mitigation playbook

• Step 5: Produce the risk surface analysis

This workflow builds on the Buying Committee Decision Mapping Workflow, which maps who is involved in the decision and where power sits. If you haven’t run that workflow yet, start there. The committee map it produces feeds directly into this one.

- Buying Committee Decision Mapping Workflow:

The workflow was created by prompts.tinytechguides.com and connects to these existing workflows:

- Prompt Workflow: Voice of Customer: https://prompts.tinytechguides.com/p/prompt-workflow-voice-of-customer

- Prompt Workflow: Competitive Landscape Mapping: https://prompts.tinytechguides.com/p/prompt-workflow-competitive-landscape

- QuickStart Battlecard for Competitive Sales Wins: https://prompts.tinytechguides.com/p/prompt-workflow-battle-card-development

- Strategic Battlecard Workflow for Competitive Wins: https://prompts.tinytechguides.com/p/strategic-battlecard-workflow-for

Step 0: Define inputs

Before running the workflow, gather these inputs:

- {account_type} = target account profile or segment

- {deal_examples} = recent won, lost, and stalled deals

- {sales_inputs} = call notes, objections, deal commentary

- {customer_inputs} = outputs from Voice of Customer workflow

- {competitive_context} = outputs from Competitive Landscape Mapping

- {committee_map} = output from Buying Committee Decision Mapping Workflow

- {win_loss_data} = deal post-mortems, win/loss analysis, notes on why deals stalled or were lost

Step 1: Surface hidden objections by role

Buyers voice proxy objections in meetings because the real concerns feel too personal or too political to say to a vendor. This prompt separates what buyers say from what they actually think.

Prompt:

# Role

You are a B2B sales psychologist analyzing the gap between what buyers say and what they actually fear.

# Context

Enterprise buying committees voice rational-sounding objections in vendor conversations. Price, timeline, features. These are proxies. The real concerns are career risk, political exposure, and the fear of championing a decision that could fail publicly.

# Task

Using {deal_examples}, {sales_inputs}, {win_loss_data}, and {committee_map}, identify the hidden objections for each role on the buying committee for {account_type}.

# Format

For each role:

- Surface objection (what they say)

- Hidden objection (what they actually think)

- Root fear (the career, political, or operational fear underneath)

- Behavioral signal (how this fear shows up in the buying process)

# Tone

Psychologically precise. Write as someone who knows the difference between what buyers say and what they mean.

No one loses their job for saying “we need more time to evaluate”

Step 2: Map the “no decision” incentive structure

Across industries, 40-60% of qualified B2B pipeline ends in no decision because committee decision-making creates asymmetric incentives. The personal cost of championing a purchase that fails is high, and the personal cost of doing nothing is almost zero. When nobody gets fired for maintaining the status quo, inaction becomes the rational default.

Prompt:

# Role

You are a behavioral economist analyzing why enterprise buying committees default to inaction.

# Context

“No decision” is the largest competitor in B2B sales. Committee decision-making creates asymmetric personal incentives that favor inaction over action, even when the business case is sound.

# Task

Using the hidden objections from Step 1, analyze the incentive structure for this buying committee.

# Format

For each role:

- Personal gain if the purchase succeeds

- Personal loss if the purchase fails

- Personal loss if no decision is made

- Asymmetry direction (favors action or favors inaction)

Then provide:

- A short analysis of the collective action problem (why the group defaults to inaction even when individuals might benefit)

- The status quo anchors (existing tools, processes, or workarounds that make “good enough” feel acceptable)

# Tone

Analytical and unsentimental. Incentives, not intentions.

Share this with someone wondering why their pipeline is “stuck”

Step 3: Identify organizational risk triggers

A buying committee’s willingness to act depends on timing and context as much as product value. Budget cycles, leadership changes, a failed competitor implementation, a regulatory deadline. These conditions either create urgency or amplify risk aversion.

Prompt:

# Role

You are a market strategist analyzing the organizational and market conditions that influence enterprise buying behavior.

# Context

A buying committee’s appetite for action depends on timing and context as much as product value. Conditions inside and outside the organization can accelerate or stall decisions.

# Task

Using {deal_examples}, {sales_inputs}, and {competitive_context}, identify the conditions that affect this buying committee’s willingness to act.

# Format

- Urgency accelerators (conditions that push the committee toward a decision, and which roles they affect most)

- Risk amplifiers (conditions that increase reluctance, and which roles they affect most)

- Timing windows (when in the fiscal year or organizational rhythm this committee is most and least likely to approve a purchase)

- Trigger events (3-5 specific events that would force this committee to act, even if the incentive structure otherwise favors inaction)

# Tone

Strategic and observational. Timing matters as much as product value.

Because timing a deal right is harder than building a business case

Step 4: Build the risk mitigation playbook

The goal is not to overcome objections through argument. Arguments trigger defensiveness. The goal is to change the conditions that make objections feel necessary in the first place. Each hidden concern has a structural root, and the most effective mitigation strategies address the structure rather than the symptom.

Read more

For every product marketer, personas and ICPs are foundational content that inform much of the content, sales plays, demand-gen programs, and enablement content. I’ve spent years building detailed personas, the kind with headshots, job titles, link-outs to LinkedIn profiles, goals, pain points, and objections neatly organized in a slide deck that looked great in a quarterly business review (QBR). At SAS, Dell, Alteryx, Alation, and now many of my clients, I’ve watched teams invest weeks refining these documents, convinced that if we could just describe the buyer precisely enough, the pipeline would follow.

Here’s what I’ve learned. Personas describe individuals. Groups make purchase decisions in B2B, and those groups are uncoordinated and messy.

The belief that buying decisions are driven by individuals acting on clearly defined needs is one of the most persistent myths in B2B marketing. Entire marketing motions and demand-gen campaigns are built around it. Teams create a hypothetical buyer’s goals, segment them into top of funnel (TOFU), middle of funnel (MOFU), and bottom of funnel (BOFU), map their pain points, catalog their objections, and then build campaigns aimed squarely at that one profile. The problem with personas is that they are radically incomplete. They capture a slice of the picture and treat it like the whole thing.

In real B2B environments, decisions are rarely made by a single person optimizing for a single outcome. They are made by groups of people with overlapping authority, misaligned incentives, and very different definitions of risk. What looks like a straightforward purchase from the outside is, internally, a negotiation about tradeoffs, accountability, and exposure. This is why so many deals that appear healthy simply stall.

Why deals stall without a “no”

Most experienced marketers and sales leaders have encountered some version of the same pattern. The buyer is engaged, and the solution is aligned. The conversations are going well and are constructive. There is no explicit objection, no formal rejection, and no stated competitor win. And yet the deal fails to close. Isn’t “No competition” the most frequent “loss reason” in Salesforce? So why didn’t the deal close?

I watched this happen in many deals over my career. Every signal said “yes.” The champion was enthusiastic, the technical team had validated the solution, and leadership had even nodded along in the executive briefing. Then nothing happened. Weeks turned into months, and the deal just sat there, ghosted.

When deals stall like this, the post-mortem often defaults to surface explanations like budget cycles, shifting priorities, and internal delays. Those factors may be present, but they usually obscure something more fundamental. In Modern B2B Marketing, I cited Forrester’s B2B Buying Survey, which found that 60% of B2B purchases involve groups of four or more people, with committees of seven to ten members engaging in an average of 27 interactions across cycles that often exceed four months. With that many people, touchpoints, and months in play, the committee simply could not reach internal consensus without someone taking on unacceptable risk.

In these situations, no one wants to be the person who champions a decision that peers, superiors, or adjacent functions could later question. The safest option becomes inaction. The deal doesn’t die; it simply never resolves. What looks like indecision from the outside is usually self-preservation on the inside.

The limits of persona-based thinking

Traditional persona frameworks struggle to account for this reality because they assume coherence where none exists. They describe buyers as if priorities are stable, aligned, and internally consistent. In practice, those priorities are negotiated across roles with different incentives over a span of time that can last months or even years.

A CFO evaluating a purchase is often optimizing for predictability and downside protection. A functional leader may be optimizing for speed or performance. A technical stakeholder may be primarily concerned with long-term maintainability or security exposure. Each of these perspectives is rational, but they don’t naturally align. As I wrote in Modern B2B Marketing, every stakeholder involved in a B2B purchase must be convinced of three things: 1) that they have a need, 2) that the solution addresses it in a unique way, and 3) that they need it now. Getting seven to ten committee members to arrive at all three convictions simultaneously is where most deals break down.

When marketing speaks to “the buyer” as if these tensions don’t exist, it inadvertently creates content that fails to genuinely resonate with any member of the committee. Worse, it can amplify internal disagreement by validating one role’s priorities while ignoring another’s. The result is paralysis, and it’s almost invisible from the outside.

Why marketing needs to understand decision mechanics

This is where most teams fail. They treat buying committee dynamics as a sales problem, something to be solved at the deal stage. But by the time a buying committee is actively negotiating tradeoffs, many of the underlying narratives have already been set.

Marketing plays a critical role earlier in the process by shaping how problems are framed, how risk is understood, and what “good” decisions look like for the organization. When marketing fails to account for buying committee dynamics, the messaging may be directionally correct while completely missing how the decision actually gets made.

Strong thought leadership does more than persuade individuals. As I noted in Modern B2B Marketing, prospects consume five to seven pieces of content during their journey toward engaging with vendors, and many of those interactions happen outside the vendor’s website. When each committee member is independently consuming that much content with different concerns, aligning the group requires more than good messaging aimed at a single profile. Thought leadership helps groups align by providing a shared language for trade-offs and outcomes. That kind of alignment doesn’t happen by accident. It requires an explicit understanding of who is involved in decisions, how power is distributed, and where friction typically emerges. This is where persona-based thinking needs to give way to decision-based thinking.

From personas to decision reality

Instead of asking “Who is our buyer?” the more useful question is “What has to be true inside the organization for a decision to happen?” Answering that question requires mapping the buying committee as a system and treating it as an interconnected set of roles rather than a collection of isolated profiles. It means understanding authority alongside preferences, and surfacing the risks people are unwilling to own, along with the objections they’ll voice openly.

When teams do this work explicitly, the picture quickly changes. They see why certain messages resonate with some stakeholders and quietly alarm others. They understand why champions struggle to build momentum internally, even when they are personally convinced. And they gain visibility into the specific tensions that must be resolved for consensus to form. This clarity doesn’t guarantee a closed deal, but it does reduce the number of deals that drift into no-decision outcomes, and it gives marketing and sales a shared map for how to move a committee forward.

The buying committee decision mapping workflow

What follows is the full workflow used to make buying committee dynamics explicit and reusable. It builds on existing market, customer, and competitive insights to create a shared map of how decisions actually happen within target accounts. The workflow focuses on identifying who holds real authority, surfacing the unspoken risks that cause stalls, and translating those dynamics into content and messaging that help committees reach consensus rather than default to inaction.

Where this leads

I’ve watched teams spend months producing content that speaks eloquently to a buyer who doesn’t exist in isolation. The CFO reads it and worries about cost exposure, while the VP of Engineering reads it and worries about migration risk. The line-of-business leader reads it and wonders who will own the rollout, and everyone nods without moving forward.

Buying committees don’t need more content. They need help getting to a decision that everyone can live with, and that work starts with making the mechanics of the decision visible. Marketing is uniquely positioned to do it.

Leave a comment

Share

About David Sweenor

David Sweenor is the founder and host of the Data Faces podcast, where he talks with the people who are making data, analytics, AI, and marketing work in the real world. He is also the founder of TinyTechGuides and a recognized top 25 analytics thought leader and international speaker who specializes in practical business applications of artificial intelligence and advanced analytics.

With over 25 years of hands-on experience implementing AI and analytics solutions, David has supported organizations including Alation, Alteryx, TIBCO, SAS, IBM, Dell, and Quest. His work spans marketing leadership, analytics implementation, and specialized expertise in AI, machine learning, data science, IoT, and business intelligence. David holds several patents and consistently delivers insights that bridge technical capabilities with business value.

Books

• Artificial Intelligence: An Executive Guide to Make AI Work for Your Business

• Generative AI Business Applications: An Executive Guide with Real-Life Examples and Case Studies

• The Generative AI Practitioner’s Guide: How to Apply LLM Patterns for Enterprise Applications

• The CIO’s Guide to Adopting Generative AI: Five Keys to Success

• Modern B2B Marketing: A Practitioner’s Guide to Marketing Excellence

• The PMM’s Prompt Playbook: Mastering Generative AI for B2B Marketing Success

Follow David on Twitter@DavidSweenor and connect with him on LinkedIn.

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Buying Committee Decision Mapping Workflow

Created by prompts.tinytechguides.com

What This Workflow Does

This workflow maps how B2B buying decisions actually get made inside target accounts.

It identifies:

• Who is involved in the decision

• Who has power vs influence

• Where decisions stall or die

• What alignment must exist for a “yes”

This workflow does not create content or personas.

It creates decision mechanics.

It answers one question:

“What has to be true inside the buying committee for a decision to happen?”

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Identify Buying Committee Roles

• Step 2: Map Decision Power & Influence

• Step 3: Define Role-Level Success Criteria

• Step 4: Identify Decision Friction & Stall Points

• Step 5: Produce the Decision Map
  

The workflow was created by prompts.tinytechguides.com (https://prompts.tinytechguides.com) and builds on these existing workflows:

- Prompt Workflow: Voice of Customer

- Prompt Workflow: Competitive Landscape Mapping

- Strategic Battlecard Workflow

- Monthly Market Signal Synthesis Workflow

Step 0: Define inputs

Before running the workflow, gather these inputs:

- {account_type} = target account profile or segment

- {deal_examples} = recent won, lost, and stalled deals

- {sales_inputs} = call notes, objections, deal commentary

- {customer_inputs} = outputs from Voice of Customer workflow

- {competitive_context} = outputs from Competitive Landscape Mapping

- {business_context} = company priorities for this segment

Step 1: Identify buying committee roles

B2B purchases are rarely made by a single decision-maker. Multiple roles participate, each entering the process at different stages with different incentives. This prompt surfaces who is actually in the room.

**Prompt:**

# Role

You are a B2B strategist analyzing how buying decisions actually happen inside real accounts.

# Context

B2B purchases are rarely made by a single decision-maker. Multiple roles participate, each entering the process at different stages with different incentives.

# Task

Using {deal_examples}, {sales_inputs}, and {customer_inputs}, identify all roles typically involved in buying decisions for {account_type}.

# Format

For each role:

- Role name (functional, not persona-based)

- Core responsibility in the organization

- Typical involvement stage (early / mid / late)

# Tone

Grounded, factual, and based on observed deal behavior.

Step 2: Map decision power and influence

Some roles formally approve decisions, others influence outcomes informally, and some can block progress without ever owning the final call. Understanding these dynamics is where most persona work falls short.

**Prompt:**

# Role

You are diagnosing power dynamics inside buying committees.

# Context

Some roles formally approve decisions, others influence outcomes, and some can block progress without owning the final call.

# Task

For each buying committee role, assess decision authority, influence, and blocking power.

# Format

For each role:

- Decision power (High / Medium / Low)

- Influence level (High / Medium / Low)

- Ability to block the decision (Yes / No)

- Notes on how this role typically exercises power

# Tone

Analytical, unsentimental, and realistic.

Step 3: Define role-level success criteria

Buying committee members optimize for different outcomes and are accountable for different risks. These differences are the root of most internal conflict, and most stalled deals.

**Prompt:**

# Role

You are uncovering how each role defines a successful outcome.

# Context

Buying committee members optimize for different outcomes and are accountable for different risks. These differences often drive internal conflict.

# Task

Define what success and failure look like for each role in the context of this decision.

# Format

For each role:

- Primary objective

- Key risks or fears

- What failure would look like to them

- Conditions under which they feel safe supporting the decision

# Tone

Empathetic but pragmatic.

Step 4: Identify decision friction and stall points

Most stalled deals fail because of unresolved internal tensions rather than product deficiencies. This step makes those tensions visible before they kill the deal.

**Prompt:**

Read more

I spent the first half of my career as a practitioner, designing data warehouses, building predictive models, and deploying BI systems at IBM. The second half has been on the dark side of product marketing at SAS, Dell, TIBCO, Alteryx, and Alation, where I’ve tried to explain those same technologies to prospective buyers. Since then, I’ve had the opportunity to apply my trade as a full-time PMM consultant and advisor to startups and behemoths alike.

Both sides taught me the same lesson. The best content teams produce less.

That sounds backwards because every marketing leader I know is under pressure to publish more blogs, more social posts, and more thought leadership. AI has made it easy to crank out content at scale. Unfortunately, most of it is garbage.

I wrote about this a couple of years ago in a piece called “AI Entropy: The Vicious Circle of AI-Generated Content.” The problem has gotten worse since then. We’re drowning in content that says nothing, written by systems trained on other content that also said nothing. When you train something on nothing, what do you get? The whole industry is racing toward the semantic middle, like a tradeshow buffet full of rubbery chicken that technically counts as food.

Diagnosing this problem is easier than fixing it, and this post is about the fix.

The decision problem

Most B2B content teams have the skills to execute. What they lack is a decision-making process.

They publish before they’ve decided what they believe. They run a trend report, see something interesting, and rush to get a piece out the door. Two weeks later, they’ve moved on, and the piece sits there orphaned like a faded memory, generating nothing.

The teams that build real credibility follow a different pattern. Their content gets cited, shared, and remembered because they move through a specific sequence before publishing.

Discover → Decide → Commit → Validate → Amplify

Most teams skip from discover straight to amplify and then wonder why nothing compounds, why every quarter feels like starting over, and why their thought leadership sounds like everyone else’s. They never decided what they believed. They just published what they found.

A system that forces the hard thinking first

Over the past year, I’ve been building a library of prompt workflows for B2B marketers. There are hundreds of them now, covering everything from persona development to competitive battlecards to analyst briefings. If you’ve read The PMM’s Prompt Playbook, you’ve seen some of this work.

But individual prompts aren’t enough. What most teams need is a system that connects market understanding to published POV to distribution.

Phase 1: Understand the market

Before you can have a point of view, you need to understand what’s happening in your market. Two workflows handle this monthly.

Trend discovery scans for signals like new tools, behavioral shifts, and emerging patterns without jumping to conclusions about what they mean.

Competitive landscape mapping analyzes what competitors are doing and saying, so you understand the landscape before figuring out where to stand.

Both workflows are strictly about gathering raw material for later synthesis.

Phase 2: Decide what matters

Most teams collect signals but never force themselves to prioritize. I watched this happen at Alteryx when we were tracking the analytics automation space. We had dashboards full of competitor moves, analyst reports, and customer feedback. What we didn’t have was a clear answer to the question: what do we actually believe about where this market is headed?

Monthly market signal synthesis takes outputs from trend discovery and competitive mapping and compresses them into one or two clear market narratives. The workflow answers a single question: given everything we know, what should we care about right now?

This step is the upstream governor of the entire system. Getting it wrong means everything downstream becomes noise.

Phase 3: Commit to a point of view

Once you’ve identified a narrative worth pursuing, you need to decide what you believe about it with enough conviction to publish.

Insight to thought leadership takes one market narrative and forces clarity on your POV, your argument, and your boundaries. There’s no writing at this stage, just decision-making about what you’re willing to defend.

Strategic POV validation pressure-tests the POV before you invest in creating the asset. Is this differentiated? Is it defensible? Is it useful to your audience? The workflow ends with a real decision to advance, revise, or kill the idea.

Nothing serious should skip this step. I’ve watched teams spend weeks on whitepapers that should have been killed in the first hour.

Phase 4: Amplify without flattening

Once you’ve created something worth reading, you need to get it in front of people without turning it into sludge.

Thought leadership to social distribution translates a validated piece into platform-native content, expressing one idea in many ways while keeping the same spine throughout.

Content calendar and editorial planning orchestrates cadence, channels, and capacity so content planning stops being reactive.

How this runs in practice

Monthly, you run trend discovery and competitive mapping, then market signal synthesis, and then select one or two narratives. Picking only one or two narratives per month is the constraint that makes everything else work.

For each thought leadership asset, you run the insight-to-thought-leadership workflow, then POV validation. Only after validation do you create the piece itself.

After publication, you run social distribution and let one idea work across channels.

This approach eliminates the scrambling that most teams experience. There’s no more “what should we post this week?” panic, and no more orphaned content sitting on your blog with no amplification plan.

Why this approach works

The system does two things that most content operations fail to do. First, it forces you to make decisions before you start writing. You can’t skip ahead because each workflow requires outputs from the previous one. Second, it treats judgment and execution as separate skills that happen at different times with different inputs. Most teams blur these together, which is how you end up with beautifully written pieces that have nothing to say.

The result is leverage. One validated POV validated across channels will outperform ten mediocre posts. I’ve seen small teams consistently outperform much larger ones by following this principle: their smaller volume of content carried real conviction, and their audience could tell the difference.

The bottom line

You don’t need more content. You need fewer ideas, stronger conviction, and better sequencing.

That’s what this system is for.

The workflows referenced above are available on TinyTechGuides. If you’re building a content operation and want to talk through implementation, find me on LinkedIn.

Share B2B Marketing Prompts by TinyTechGuides

Leave a comment

About David Sweenor

Books: Artificial Intelligence | Generative AI Business Applications | The Generative AI Practitioner’s Guide | The CIO’s Guide to Adopting Generative AI | Modern B2B Marketing | The PMM’s Prompt Playbook

Founder of TinyTechGuides, David Sweenor is a top 25 analytics and AI thought leader and influencer, international speaker, consultant and advisor, and acclaimed author with several patents. He is a product marketing leader, analytics practitioner, and specialist in the business application of AI, ML, data science, IoT, and business intelligence.

With over 25 years of hands-on business analytics experience, Sweenor has supported organizations including Alation, Alteryx, TIBCO, SAS, IBM, Dell, and Quest, in advanced analytic roles.

Follow David on Twitter @DavidSweenor and connect with him on LinkedIn https://www.linkedin.com/in/davidsweenor/.

Need help with PMM? Let me know.

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Thought Leadership → Social POV Distribution Workflow

Created by prompts.tinytechguides.com

What This Workflow Does

This workflow translates a validated long-form thought leadership asset (such as a whitepaper or flagship POV piece) into short-form social content while preserving the original thinking, argument, and intent.

It does not summarize.
It does not flatten ideas into marketing fluff.
It re-expresses the same POV across platforms in a way that is native, credible, and high-signal.

This workflow answers:

“How do we extend the reach of serious thinking without diluting it?”

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Extract Core Arguments & POV

• Step 2: Identify Social-Native Angles

• Step 3: Translate POV Into Platform Formats

• Step 4: Preserve Narrative Consistency

• Step 5: Finalize & Queue for Distribution

Step 0: Define Inputs

{source_asset} = final whitepaper or long-form thought leadership piece

{pov_statement} = validated POV from the Strategic POV Validation Workflow

{target_platforms} = social platforms for distribution

{audience} = intended social audience

{author_voice} = tone and perspective to preserve

{distribution_goal} = awareness, authority, engagement, traffic, etc.

Referenced workflows:

https://prompts.tinytechguides.com/p/not-every-point-of-view-deserves

Step 1: Extract Core Arguments & POV

Goal:
Identify the intellectual spine of the thought leadership asset.

# Role

You are an editorial translator extracting core ideas from long-form thought leadership.

# Context

Short-form content must preserve the same thinking, logic, and conclusions as the original asset.

# Task

Review {source_asset} and extract the core POV, key arguments, and conclusions that must be preserved across all derivatives.

# Format

- Core POV (1 sentence)

- 3–5 key arguments

- One non-negotiable takeaway

# Tone

Faithful, precise, and analytical.

Step 2: Identify Social-Native Angles

Goal:
Determine how the POV should enter each platform.

# Role

You are a social strategist aligning ideas to platform behavior.

# Context

Each platform rewards different entry points. The POV stays constant; the framing changes.

# Task

For each platform in {target_platforms}, identify the strongest social-native angle to introduce the POV to {audience}.

# Format

For each platform:

- Platform name

- Primary angle or hook

- Supporting tension or insight

- Intended reader reaction

# Tone

Platform-aware, strategic, and audience-centric.

Step 3: Translate POV Into Platform Formats

Goal:
Create high-signal social content that stands on its own.

# Role

You are a content creator translating thought leadership into short-form social posts.

# Context

Each post should deliver real value even if the reader never clicks through to the source asset.

# Task

Write platform-appropriate posts that express the POV and supporting arguments without oversimplifying the idea.

# Format

For each platform:

- Post text

- Optional CTA (if appropriate)

- Link placement guidance (if used)

# Tone

Clear, confident, and substance-first.

Step 4: Preserve Narrative Consistency

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Strategic POV Validation Workflow

Created by prompts.tinytechguides.com

What This Workflow Does

This workflow pressure-tests a thought leadership point of view before it is written or distributed.

Its job is to ensure a POV is:

• Differentiated (not obvious or generic)

• Defensible (you can stand behind it)

• Useful (it changes how the reader thinks or acts)

This workflow does not improve writing.
It decides whether the idea deserves amplification at all.

This workflow answers:

“Is this POV strong enough to represent us publicly?”

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Test for Differentiation

• Step 2: Test for Defensibility

• Step 3: Test for Usefulness

• Step 4: Identify Risks & Weaknesses

• Step 5: Decide: Advance, Revise, or Kill

Step 0: Define Inputs

• {pov_statement} = the POV defined in the Insight → Thought Leadership Workflow

  https://open.substack.com/pub/davidsweenor/p/thought-leadership-starts-with-a

• {argument_outline} = supporting arguments and evidence

• {audience} = intended reader

• {business_context} = company positioning, strategy, and constraints

• {publication_channel} = where this POV will be published

• {risk_tolerance} = conservative, balanced, or bold

Step 1: Test for Differentiation

Goal:
Ensure the POV is not obvious, consensus-driven, or already saturated.

# Role

You are a critical editor evaluating market differentiation.

# Context

Thought leadership that restates common beliefs fails to create authority or memorability.

# Task

Evaluate whether {pov_statement} meaningfully differs from common market narratives aimed at {audience}.

# Format

- Common market belief

- How this POV differs

- Differentiation score (High / Medium / Low)

- Brief justification

# Tone

Skeptical, sharp, and market-aware.

Step 2: Test for Defensibility

Goal:
Confirm the POV can withstand scrutiny.

# Role

You are a strategist stress-testing an argument.

# Context

A POV that cannot be defended damages credibility, even if it attracts attention.

# Task

Assess whether the {argument_outline} sufficiently supports {pov_statement}, considering counterarguments and edge cases.

# Format

- Strongest supporting evidence

- Likely counterarguments

- How well the POV holds up (Strong / Moderate / Weak)

- Gaps that need reinforcement

# Tone

Rigorous, fair, and intellectually honest.

Step 3: Test for Usefulness

Goal:
Ensure the POV creates value for the reader.

# Role

You are evaluating reader impact.

# Context

Thought leadership should change how a reader thinks, decides, or acts — not just inform them.

# Task

Evaluate how {pov_statement} helps {audience} make better decisions or see a problem differently.

# Format

- What the reader likely believes today

- What they should believe after reading

- Practical implications for the reader

- Usefulness score (High / Medium / Low)

# Tone

Reader-centric, practical, and outcome-focused.

Step 4: Identify Risks & Weaknesses

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Insight → Thought Leadership Workflow

Created by prompts.tinytechguides.com

What This Workflow Does

This workflow turns a validated market insight into a clear, opinionated thought leadership position that is ready to be written and published.

It does not write the article.
It decides the idea, the argument, and the boundary.

This workflow answers:

“What do we believe strongly enough to put our name on?”

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Select the Core Insight

• Step 2: Define the Point of View (POV)

• Step 3: Build the Argument Structure

• Step 4: Set Editorial Boundaries

• Step 5: Produce a Publish-Ready Outline

Step 0: Define Inputs

• {source_insight} = core insight or narrative from Monthly Market Signal Synthesis

https://open.substack.com/pub/davidsweenor/p/what-matters-this-month

• {audience} = who this thought leadership is for

• {business_context} = why this idea matters to the business

• {author_perspective} = founder, PMM, operator, practitioner, etc.

• {publication_channel} = primary publishing destination (e.g. Substack)

• {objective} = what this piece should change in the reader’s thinking

Step 1: Select the Core Insight

Goal:
Choose one insight worth developing — not a bundle.

# Role

You are an editorial strategist selecting a single idea to develop into thought leadership.

# Context

Strong thought leadership focuses on one clear insight. Combining ideas weakens conviction and clarity.

# Task

Review {source_insight} and select the single insight that is most relevant to {audience} and {business_context}.

# Format

- Selected insight (1–2 sentences)

- Why this insight matters now

- Why this audience should care

# Tone

Focused, deliberate, and confident.

Step 2: Define the Point of View (POV)

Goal:
Turn insight into an opinion, not an observation.

# Role

You are defining a clear, defensible point of view.

# Context

Insight becomes thought leadership only when it expresses a belief or stance that others may not agree with.

# Task

Translate the selected insight into a clear POV statement that reflects {author_perspective} and serves {objective}.

# Format

- POV statement (one clear sentence)

- Common belief this POV challenges

- What someone who agrees will now do differently

# Tone

Opinionated, grounded, and assertive without being inflammatory.

Step 3: Build the Argument Structure

Goal:
Ensure the POV can be supported, not just asserted.

# Role

You are an editor structuring a persuasive argument.

# Context

A strong POV requires a logical argument that guides the reader from problem to conclusion.

# Task

Outline the argument that supports the POV using evidence, reasoning, and examples.

# Format

- Core thesis

- 3–5 supporting arguments

- Evidence or examples for each argument

- Implications if the POV is true

# Tone

Clear, logical, and persuasive.

Step 4: Set Editorial Boundaries

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Monthly Market Signal Synthesis Workflow

Created by prompts.tinytechguides.com

What This Workflow Does

This workflow synthesizes pre-researched market, trend, and competitive inputs into 1–2 clear market narratives that guide content, positioning, and GTM decisions for the month. It does not perform raw discovery.

Instead, it consumes outputs from existing research workflows (already in Substack) and focuses purely on sensemaking, prioritization, and narrative clarity.

This workflow answers:

“Given everything we already know, what actually matters right now?”

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Review Research Outputs

• Step 2: Cluster Signals Into Patterns

• Step 3: Pressure-Test Signal Relevance

• Step 4: Synthesize Core Market Narratives

• Step 5: Document & Distribute Insights

Step 0: Define Inputs

• {time_period} = month or date range being analyzed

• {market_scope} = industry, segment, or category focus

• {trend_inputs} = summarized outputs from:

• {competitive_inputs} = summarized outputs from:

• {customer_inputs} = VOC summaries (calls, tickets, interviews, notes)

• {business_context} = internal priorities or GTM focus

• {audience} = who this synthesis is for (PMM, content, execs, etc.)

Important constraint:
Inputs should be synthesized findings, not raw links, transcripts, or research dumps.

Step 1: Review Research Outputs

Goal:
Establish shared context before interpretation begins.

# Role

You are a B2B strategist reviewing existing market research outputs.

# Context

Trend and competitive research has already been conducted using dedicated workflows. This step ensures those findings are understood before synthesis begins.

# Task

Review {trend_inputs}, {competitive_inputs}, and {customer_inputs}. Summarize the most salient observations without adding interpretation.

# Format

Three sections:

- Trend highlights

- Competitive highlights

- Customer highlights

# Tone

Neutral, factual, and observational.

Step 2: Cluster Signals Into Patterns

Goal:
Move from isolated findings to emerging patterns.

# Role

You are a strategist identifying patterns across validated research outputs.

# Context

Patterns emerge when multiple signals point in the same direction across trends, customers, and competitors.

# Task

Group related observations into signal clusters that suggest emerging shifts, tensions, or opportunities.

# Format

For each cluster:

- Cluster name

- Signals included

- Early hypothesis about what this cluster suggests

# Tone

Analytical and exploratory.

Step 3: Pressure-Test Signal Relevance

Goal:
Filter out interesting noise.

# Role

You are a senior marketer prioritizing focus.

# Context

Not every pattern deserves attention. This step ensures alignment with business reality.

# Task

Evaluate each signal cluster against {business_context} and {audience}. Decide which clusters matter now.

# Format

For each cluster:

- Relevance (High / Medium / Low)

- Reasoning

- Recommended action (advance, monitor, discard)

# Tone

Pragmatic and decisive.

Step 4: Synthesize Core Market Narratives

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Content Calendar & Editorial Planning Workflow

Created by prompts.tinytechguides.com

What This Workflow Does

This workflow helps a B2B marketing team (or a single, brave IC) create a clear, strategy-led content calendar for a defined planning period. It turns goals, audiences, and themes into a realistic publishing plan that aligns content, channels, and capacity — without chaos, guessing, or last-minute scrambles.

This workflow decides:

• What to publish

• Why it matters

• Where it goes

• When it ships

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Establish Planning Horizon & Content Goals

• Step 2: Select Core Themes & Narratives

• Step 3: Map Themes to Content Types & Channels

• Step 4: Sequence Content Into a Calendar

• Step 5: Validate Against Capacity, GTM, and Priorities

• Step 6: Lock, Publish, and Review

Step 0: Define Inputs

• {planning_horizon} = time period covered by the calendar (e.g. 30, 60, 90 days)

• {business_objectives} = primary goals this content should support

• {target_audience} = ICPs, personas, or buying committee

• {core_channels} = where content will be published

• {content_capacity} = realistic production bandwidth

• {key_dates} = launches, events, announcements, deadlines

• {content_pillars} = high-level themes or focus areas

• {success_metrics} = how content success will be evaluated

Step 1: Establish Planning Horizon & Content Goals

Goal:
Align the content calendar to business priorities so content supports real outcomes, not vibes.

# Role

You are a B2B marketing strategist responsible for aligning content planning with business goals.

# Context

Content is most effective when it is intentionally planned around clear objectives, audiences, and timelines. This step ensures the content calendar is anchored to real priorities for the defined planning horizon.

# Task

Using {planning_horizon}, {business_objectives}, {target_audience}, and {success_metrics}, define the primary purpose of content for this period and the outcomes it should support.

# Format

- Planning horizon summary

- Primary content goals (3–5 bullets)

- Audience focus for this period

- Success definition for the calendar

# Tone

Clear, pragmatic, and focused on outcomes over output.

Step 2: Select Core Themes & Narratives

Goal:
Decide what you will talk about before deciding what you will publish.

# Role

You are a content strategist translating business priorities into clear editorial themes.

# Context

Strong content calendars are built around a small number of repeatable themes that reinforce positioning and credibility over time.

# Task

Using {content_pillars}, {business_objectives}, and {target_audience}, identify 3–5 core themes and the key narratives or points of view within each theme.

# Format

For each theme:

- Theme name

- Why it matters to the audience

- Key narrative or POV

- Example topics this theme could produce

# Tone

Strategic, opinionated, and focused on clarity over breadth.

Step 3: Map Themes to Content Types & Channels

Goal:
Ensure each theme shows up in the right formats and places.

# Role

You are a B2B content planner responsible for aligning themes to channels and formats.

# Context

Not all content belongs everywhere. This step ensures themes are expressed through the most effective content types and channels.

# Task

Map each core theme to appropriate content formats and {core_channels}, considering audience behavior and intent.

# Format

Table with columns:

- Theme

- Content type (essay, post, video, etc.)

- Primary channel

- Secondary channel (if any)

- Intended audience action

# Tone

Practical, audience-aware, and execution-ready.

Step 4: Sequence Content Into a Calendar

Read more

This year, you stopped asking AI to write for you. You started asking it to check your work.

The data backs this up. Out of 115 posts and 150,000 words, your most-opened content focused on reviewing landing pages, tightening executive messaging, and validating claims before publication. “Editor” themed posts outperformed “creator” posts by a clear margin.

Meanwhile, this newsletter more than doubled in size. We went from around 135 subscribers to well over 300. And the engagement patterns reveal what brought you here. Competitive intelligence posts hit the highest open rates of any category. You want workflows you can reuse. And you want impactful messaging that win deals.

By the Numbers

• 115 posts (87 newsletters, 28 podcasts)

• ~150,000 words

• 39.1% average open rate

• 125% audience growth

Help support and promote small businesses by sharing this post with a friend.

Top 5 Workflows

These got bookmarked and reused. The Sales Plays and Buyer Personas workflows were reopened 4.5x each. You’re building a reference library over here. (I see you, fellow hoarders.)

1. B2B Prompt Engineering for PMMs: The foundation. Everything else was built on this.

2. Competitive Landscape Mapping: Strategic intel is hard. This made it systematic.

3. Executive Messaging Review & Harmonization: Getting execs to agree on messaging? There’s a workflow for that now.

4. Turn Web Pages into Marketing-Ready Data Sheets: Hours saved, every single time.

5. Landing Page Copy Review: Even the best writers need a second pair of eyes. And AI doesn’t get defensive when you ignore its feedback.

Top 5 Podcasts

Deep conversations with practitioners who’ve made the mistakes so you don’t have to. Note, these Top 5 are based on Substack newsletter open rates, not the number of YouTube views, which paints a different picture.

1. The Customer Hero Principle: Gabriela Contreras (Skyline Marketing) on ruthless audience prioritization and escaping jargon land

2. From “AI-Ready” to AI Reality: Shane Murray (Monte Carlo Data) on why building beats endless planning

3. Your Netflix Moment: Catalina Herrera (Dataiku) on why most AI agent pilots fail

4. Stop Chasing Hallucinations: Hyoun Park (Amalgam Insights) on fixing context gaps in agentic AI

5. The AI Agent Mistake 90% of Leaders Make: Chelsea Wise (Relevance AI) on why learning together beats rushing to implement

Top 5 How-To Guides

The stuff you read between meetings. Short-form guides actually outperformed long-form podcasts this year. Respecting your time pays off.

1. Should You Turn ChatGPT’s Memory On or Off?: The privacy vs. productivity tradeoff we’re all navigating

2. Tutorial: Prompt Engineering for PMMs: The companion piece to the #1 workflow

3. Deep Fake Dave & The Future of AI Personas: AI isn’t just writing anymore. It’s becoming.

4. Marketing Mad Libs: Prompt Variables: Level up with variables

5. Customizing GPTs for Authentic Content: Making AI sound like you

Looking at 2026

My bet for next year is that the conversation moves from “prompt workflows” to “automation.”

Not the “set it and forget it” kind, we’ve all been burned by that promise. I’m talking about automated workflows that run reliably on their own. Agents that check their own work and marketing systems, where you review exceptions instead of every single output.

The real question becomes: how do I trust the output enough to stop babysitting it?

I’ll be honest. I don’t have that figured out. But I’m spending 2026 working on it, and I’ll share what works. And what fails spectacularly.

Which workflow saved you the most time this year? Hit reply and tell me. Your answers shape what gets built next.

P.S. Saturday posts got +2% higher open rates. Turns out you prefer AI content when you’re not trapped in back-to-back meetings.

Leave a comment

About David Sweenor

David Sweenor is an expert in AI, generative AI, and product marketing. He brings this expertise to the forefront as the founder of TinyTechGuides and host of the Data Faces podcast. A recognized top 25 analytics thought leader and international speaker, David specializes in practical business applications of artificial intelligence and advanced analytics.

Books

• Artificial Intelligence: An Executive Guide to Make AI Work for Your Business

• Generative AI Business Applications: An Executive Guide with Real-Life Examples and Case Studies

• The Generative AI Practitioner’s Guide: How to Apply LLM Patterns for Enterprise Applications

• The CIO’s Guide to Adopting Generative AI: Five Keys to Success

• Modern B2B Marketing: A Practitioner’s Guide to Marketing Excellence

• The PMM’s Prompt Playbook: Mastering Generative AI for B2B Marketing Success

With over 25 years of hands-on experience implementing AI and analytics solutions, David has supported organizations including Alation, Alteryx, TIBCO, SAS, IBM, Dell, and Quest. His work spans marketing leadership, analytics implementation, and specialized expertise in AI, machine learning, data science, IoT, and business intelligence.

David holds several patents and consistently delivers insights that bridge technical capabilities with business value.

Follow David on Twitter@DavidSweenor and connect with him onLinkedIn.

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Better Together – Partner Messaging & Joint Value Prop Framework

created by prompts.tinytechguides.com

What This Workflow Does

This workflow helps two B2B companies create a unified joint value proposition that clearly communicates how their solutions are stronger together. By analyzing both companies’ core messaging and the technical integration, it builds a shared narrative, packaged in a Joint Solution Brief. A final role-play step simulates real-world sales reactions to validate the messaging before going live.

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Extract Core Messaging from Each Company

• Step 2: Identify Integration Value and Market Fit

• Step 3: Craft “1+1=3” Joint Value Proposition

• Step 4: Create Joint Solution Brief

• Step 5: AE Role-Play Review – Gut Check from Both Sides

Step 0: Define Inputs

{company_a_messaging} = Company A’s core messaging (value props, positioning, key differentiators)
{company_b_messaging} = Company B’s core messaging (value props, positioning, key differentiators)
{integration_details} = Technical or functional overview of how the two solutions work together
{target_persona} = Who we’re targeting (e.g., IT Director, CMO, etc.)
{pain_points} = Key pain points this joint solution addresses
{joint_use_case} = Primary use case enabled by the integration
{industry_focus} = Industry or vertical this solution is most relevant for
{cta} = Desired call-to-action (e.g., book a demo, download the whitepaper)

Step 1: Extract Core Messaging from Each Company

Goal: Summarize each company’s key positioning, differentiators, and value props.

#Role
You are a B2B messaging strategist helping distill partner company narratives.

#Context
Company A and Company B are collaborating on a joint solution. We need to understand each company’s standalone messaging to later blend them into a unified value prop.

#Task
Summarize the core messaging of Company A and Company B separately. Highlight their target market, top 2–3 differentiators, and tone of voice.

#Format
Bullet points under each company header. Label each clearly.

#Tone
Neutral, clear, and B2B professional.

Step 2: Identify Integration Value and Market Fit

Goal: Translate technical integration into meaningful customer value and market relevance.

#Role
You are a technical marketing consultant translating integrations into business value.

#Context
We have two integrated solutions. Now we need to define the combined functional value, key pain points solved, and which market segments are most affected.

#Task
Based on the integration details, pain points, and use case, explain the real-world impact of this integration. Who benefits most, and why?

#Format
- Summary paragraph of the integration’s value
- Top 3 pain points solved
- Top 2 market segments that benefit
- 1–2 ideal use cases

#Tone
Clear, consultative, with a “problem-solution” style.

Step 3: Craft “1+1=3” Joint Value Proposition

Goal: Build a unified, compelling value proposition that blends both brands.

Read more

This free prompt workflow was shared with me by Pablo Ylarri during a Product Marketing Alliance meet-up. Thanks, Pablo!

If you have a prompt to share, please do so, and you can be featured in the newsletter!

Workflow Name: Latin American Spanish Translation Workflow (Neutral + Professional)

created by prompts.tinytechguides.com

What this Workflow Does

This workflow guides you through creating clean, neutral, and professional translations of English content into Latin American Spanish. It’s crafted to ensure tone, formatting, and clarity stay intact — perfect for biz or marketing use across all Spanish-speaking countries in Latin America.

Workflow Steps Summary

Steps:

• Step 0: Define Inputs

• Step 1: Establish Translator Role, Guidelines, and Rules

• Step 2: Insert Source Text for Translation

• Step 3: Output Final Translation

Step 0: Define Inputs

{source_text} = Text that needs to be translated

{tone} = Tone of the original text (e.g., professional, friendly, technical)

{formatting_preserved} = Yes/No – should formatting (like bullets, bold, etc.) be preserved

Step 1: Establish Translator Role, Guidelines, and Rules

Goal: Clearly define the translator’s responsibilities, expectations, and style rules.

#Role

You are an expert English-to-Spanish translator specialized in **neutral Latin American Spanish**. You translate content in a way that sounds natural and professional to native Spanish speakers across Latin America — avoiding regionalisms and Spain-specific language.

#Context

You’ve been hired to translate a text into Latin American Spanish. The client requires high accuracy, professionalism, and formatting preservation. You must follow strict rules to ensure the translation is clean, neutral, and ready to use for business, marketing, or professional communications.

#Task

Translate the provided English text into perfect **Latin American Spanish**, maintaining the tone, formatting, grammar, and clarity.

#Rules

- Use **neutral Spanish**, avoiding regionalisms (e.g., no “ordenador”, no “vosotros”, no idioms from Spain)

- Respect proper grammar and capitalization rules of Spanish

- Keep **blank lines, bullet points, lists, and punctuation** as in the original

- Maintain a **professional tone** that sounds **natural to native speakers in Latin America**

- Do **not** translate company names, product names, or URLs

- Do **not** add any commentary — only return the translated text

#Format

Preserve the original formatting exactly: blank lines, bullets, line breaks, bold/italics (if any), punctuation — everything. Deliver only the translated Spanish version.

#Tone

Match the tone of the original text. For this job, the tone is: {tone}

Step 2: Insert Source Text for Translation

Goal: Feed the text into the prompt while reinforcing rules and tone.

#Role

You are continuing your task as a Latin American Spanish translator.

#Context

Below is the English content to be translated. This content should be converted following all guidelines, rules, and formatting expectations outlined above.

#Task

Translate this into professional, **neutral Latin American Spanish**, preserving formatting and tone. Avoid any regionalisms or informal/slang expressions. It should feel smooth and natural to a Latin American audience.

#Rules

- Use **neutral Spanish**, avoiding regionalisms (no “ordenador”, no “vosotros”, no idioms from Spain)

- Follow Spanish grammar and capitalization norms

- Keep formatting as-is (lists, punctuation, line breaks, etc.)

- Maintain professional tone

- Don’t translate company/product names or URLs

- Don’t include commentary — just the translated text

#Format

Return only the translated version of the text. Match the original formatting perfectly.

#Tone

The tone of this text is: {tone}

Text to translate:

{source_text}

Step 3: Output Final Translation

Goal: Deliver the final, client-ready Spanish version of the text.

#Role

You are delivering the final Spanish translation for client use.

#Context

The client expects a clean, final version that sounds fluent and natural in **Latin American Spanish**, free from regional quirks or awkwardness, and styled to match the original English tone.

#Task

Review the translated version to ensure tone, formatting, and grammar are perfect. This is the client-ready version — it should require no edits. Follow the established rules.

#Rules

- Use **neutral Spanish**

- No Spain-specific terms or idioms

- Follow proper grammar and punctuation

- Keep original structure, formatting, and layout

- Exclude translations of brand names, product names, and URLs

- No commentary — just return the translation

#Format

Output only the final translated Spanish text with the exact same formatting.

#Tone

Maintain the tone as: {tone}

Why This Workflow Works

• Embeds clear, enforceable translation rules that prevent localization issues

• Maintains formatting and tone so the output is plug-and-play

• Reduces back-and-forth by delivering polished, rule-following translations

Share B2B Marketing Prompts by TinyTechGuides

Leave a comment

About David Sweenor

Books: Artificial Intelligence | Generative AI Business Applications | The Generative AI Practitioner’s Guide | The CIO’s Guide to Adopting Generative AI | Modern B2B Marketing | The PMM’s Prompt Playbook

Founder of TinyTechGuides, David Sweenor is a top 25 analytics and AI thought leader and influencer, international speaker, consultant and advisor, and acclaimed author with several patents. He is a product marketing leader, analytics practitioner, and specialist in the business application of AI, ML, data science, IoT, and business intelligence.

With over 25 years of hands-on business analytics experience, Sweenor has supported organizations including Alation, Alteryx, TIBCO, SAS, IBM, Dell, and Quest, in advanced analytic roles.

Follow David on Twitter @DavidSweenor and connect with him on LinkedIn https://www.linkedin.com/in/davidsweenor/.

Need help with PMM? Let me know.

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: PR Headline Options Generator

created by prompts.tinytechguides.com

What this Workflow Does

This workflow helps you develop, pressure-test, and refine three PR messaging directions — each with a Headline, Subheadline, and Key Points — based on raw reference material and stakeholder insights (or simulated ones if you’re flyin’ solo). It walks you through extracting story themes, crafting narratives, running stakeholder feedback simulations, and adjusting final messaging so it lands with internal leadership and skeptical buyers alike.

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Analyze reference material for themes

• Step 2: Generate 3 distinct PR storylines

• Step 3: Write headline, subheadline, and 3 bullets for each storyline

• Step 4: Simulate stakeholder reviews

• Step 5: Harmonize and refine the final messaging directions

Step 0: Define Inputs

• {reference_material}

• {industry}

• {target_audience}

• {brand_tone}

• {goal_of_pr}

# Optional Strategic Inputs (simulated if left blank)

• {competitive_review}

• {cmo_review}

• {chief_sales_officer_review}

• {chief_product_officer_review}

• {skeptical_buyer_review}

Step 1: Analyze reference material for themes

Goal: Extract major story hooks, themes, and relevance to industry trends and stakeholder POVs.

#Role

You are a strategic PR planner working inside a high-performing marketing team.

#Context

You’ve been given raw reference material and optional executive/stakeholder insights. You need to extract the strongest narrative themes and positioning angles that align with market relevance and internal priorities.

#Task

Analyze the reference material and optional inputs. Identify 3-5 key story themes, trends, or market hooks that could anchor a future press release. Simulate missing inputs as needed.

#Format

List each theme in bullet format with a short explanation (1-2 sentences each). Label the section: “Key PR Themes”.

#Tone

Clear, strategic, marketing-savvy.

Step 2: Generate 3 distinct PR storylines

Goal: Explore multiple story directions based on the themes identified.

#Role

You are a senior messaging strategist creating story options for a press release brainstorm.

#Context

You’re working from reference material, market trends, and executive perspectives (real or simulated). Your job is to explore three different directions the PR could take, each grounded in a unique angle.

#Task

Create 3 different PR storyline directions. Each should have a title and a 2-3 sentence description of the narrative angle. These are not headlines — just high-level story arcs.

#Format

Label the section: “PR Storyline Options”. Use numbered sections (1, 2, 3) with title + description.

#Tone

Creative, strategic, narrative-driven.

Step 3: Write headline, subheadline, and 3 bullets for each storyline

Goal: Flesh out each storyline with headline-ready messaging components.

#Role

You are a PR messaging copywriter developing options for executive review.

#Context

You’re working from 3 approved PR storylines. You need to write a compelling Headline, a supporting Subheadline, and 3 Key Points for each. These options will be used to choose a final direction for a formal press release.

#Task

For each storyline, generate:

- A bold, concise Headline (under 12 words)

- A Subheadline that expands the value or angle

- 3 Key Points that summarize the why/what/impact

#Format

Label the section: “PR Messaging Options”. For each option, use this format:

Option 1:

Headline:

Subheadline:

Key Points:

- Point 1

- Point 2

- Point 3

Repeat for Option 2 and Option 3.

#Tone

PR-savvy, benefit-driven, aligned to {brand_tone}

Step 4: Simulate stakeholder reviews

Read more

This prompt has been updated from the one in the The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Testimonial Builder from Transcript Quotes

Created by prompts.tinytechguides.com

What this Workflow Does

This workflow extracts key customer quotes from transcripts and rewrites them as polished testimonials. It allows optional focus on a specific topic (like scalability), adapts messaging for a target persona, and includes attribution (job title and company) based on provided details or inferred from the transcript.

Workflow Steps Summary

Step 0: Define Inputs
Step 1: Analyze Transcript and Extract Relevant Quotes
Step 2: Select Most Impactful Quote(s)
Step 3: Rephrase Quote(s) into Structured Testimonial(s) with Attribution
Step 4: Apply Professional Formatting and Brand Voice
Step 5: Final Review for Clarity, Authenticity, and Impact

Step 0: Define Inputs

• transcript = “Full customer interview or feedback transcript”,

• subject_focus = “Optional topic to focus on (e.g., scalability, ease of use, support)”,

• persona = “Target reader persona (e.g., CIO, CDO, IT Manager)”,

• brand_tone = “Preferred tone or voice (e.g., straightforward, confident, friendly)”,

• quote_count = “Number of testimonials needed (e.g., 1, 2–3, etc.)”

If job title and company are not provided, infer them from the transcript. If unavailable, omit attribution.

Step 1: Analyze Transcript and Extract Relevant Quotes

Goal: Pull out quotes from the transcript that align with a subject focus (if provided).

#Role

You are a content strategist skilled at identifying high-impact messaging from customer interviews.

#Context

You’ve received a transcript from a customer interview. The goal is to extract authentic, compelling quotes that support product benefits. The user may have specified a subject to focus on, such as {subject_focus}.

#Task

Review the transcript and extract 3–5 quotes that clearly reflect the customer’s positive sentiment, ideally aligned with the subject {subject_focus} (if specified). If no subject is provided, choose the most impactful overall.

#Format

List each quote as a bullet point. Keep the original wording intact. If you detect a name, title, or company, include it as a separate line below the quote.

#Tone

Neutral and factual—this step is just extraction, not interpretation.

Step 2: Select Most Impactful Quote(s)

Goal: Choose the most testimonial-ready quote(s) from the extracted list.

#Role

You are a brand copy editor with a sharp eye for concise, emotionally resonant customer language.

#Context

You’ve been given a list of quotes extracted from a customer transcript.

#Task

Choose the top {quote_count} quote(s) based on clarity, emotional impact, and alignment with {subject_focus}. Prioritize quotes that would be meaningful to a {persona}.

#Format

List each selected quote along with 1–2 sentences explaining why it stands out. Include any inferred name, title, or company if available.

#Tone

Professional and analytical.

Step 3: Rephrase Quote(s) into Structured Testimonial(s) with Attribution

Goal: Rewrite selected quotes into polished, persona-relevant testimonials, including attribution if possible.

#Role

You are a B2B marketing writer skilled at crafting credible, professional testimonials.

#Context

You have selected {quote_count} customer quote(s) focused on {subject_focus}. These need to be rewritten as formal testimonials that resonate with {persona}. Attribution should be included if a job title or company was detected in the transcript.

#Task

Rephrase each quote into a 2–4 sentence testimonial. Highlight the product benefit clearly while keeping the voice authentic. Add attribution using any inferred job title and company from the transcript. If nothing is detected, leave attribution off.

#Format

Output each testimonial as a paragraph followed by an attribution line in this format (only if available):

— [Job Title], [Company]

#Tone

{brand_tone}—align with the company’s preferred tone while maintaining believability and clarity.

Step 4: Apply Professional Formatting and Brand Voice

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Workflow Name: Interview Guide Builder: Validate Competitive Claims with Customers & Prospects

created by prompts.tinytechguides.com

What this Workflow Does:

This workflow builds a structured, persona-specific interview guide designed to help internal teams gather real-world feedback on competitive claims. Whether you’re talking to current customers or lost deals, the guide helps you probe for insights on what claims resonate, which fall flat, and how your positioning stacks up in the wild. Ideal for PMM, sales enablement, or anyone lookin’ to keep it real with the market.

Workflow Steps Summary:

• Step 0: Define Inputs

• Step 1: Identify Competitive Claims to Validate

• Step 2: Define Interview Audience (Customers vs Prospects)

• Step 3: Draft Core Interview Questions

• Step 4: Add Probing Questions Based on Personas

• Step 5: Define Interview Flow (Intro → Claims → Wrap-up)

• Step 6: Generate Interview Guide Output

Step 0: Define Inputs

• {product_or_solution} = The product, service, or solution whose competitive claims you’re validating

• {industry} = The main industry or vertical focus (e.g., Fintech, Healthcare, SaaS)

• {competitive_claims} = Specific competitive claims or differentiators you want to validate (e.g., “faster implementation than Competitor X”)

• {interview_type} = Who you’re interviewing (e.g., current customers, recent lost prospects, open opps)

• {persona} = The main persona(s) you’ll be interviewing (e.g., CIO, Operations Manager, End User)

• {desired_outcome} = What you want to learn or validate from these interviews (e.g., messaging resonance, real-world performance, objection handling)

• {interview_style} = Preferred style or tone (e.g., casual convo, structured Q&A, open-ended discovery)

Step 1: Identify Competitive Claims to Validate

#Role

You are a Product Marketing Manager responsible for competitive positioning and messaging.

#Context

You are preparing an interview guide to validate specific competitive claims for {product_or_solution} in the {industry} industry. These claims may come from internal sales feedback, win/loss analysis, or positioning decks.

#Task

List and prioritize 3–5 competitive claims or differentiators you want to test with interviewees. Include a short rationale for each.

#Format

Return a bullet list with each claim followed by a short rationale.

#Tone

Professional but curious — you want to get to the heart of what really matters in the market.

Step 2: Define Interview Audience

#Role

You are a Customer Research Strategist helping internal teams clarify who to interview for maximum insight.

#Context

The interview objective is to validate competitive claims about {product_or_solution} by speaking with people in the {industry} industry.

#Task

Based on the provided {interview_type} and {persona}, define:

- Who should be interviewed

- Why their perspective matters

- The ideal number of participants per type

#Format

Output a short paragraph followed by a table with columns: Persona | Interview Type | Why They’re Important | Suggested Quantity

#Tone

Strategic and pragmatic.

Step 3: Draft Core Interview Questions

#Role

You are a B2B interview designer focused on extracting high-value insights from customer conversations.

#Context

You are designing interview questions to validate competitive claims for {product_or_solution} in the {industry} space. These questions should work for the {interview_type} and {persona}, and uncover how your solution compares to competitors.

#Task

Draft 5–7 core interview questions that explore the customer’s perception of your product, competitor solutions, and key decision factors.

#Format

List questions in bullet format. Include one sentence below each question that explains the purpose behind it.

#Tone

Curious, conversational, and neutral (no leading questions).

Step 4: Add Probing Questions Based on Personas

Read more

Workflow Name: Survey Design & Feedback Insight Generator

Created by prompts.tinytechguides.com

This prompt is part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

What this Workflow Does:

This workflow helps you craft a well-structured survey tailored to your specific goals—whether you’re gauging satisfaction, collecting feedback, or testing a hypothesis. It guides you through defining what matters, writing clear, unbiased questions, mixing up formats to keep it groovy, and setting up a process that delivers insights you can actually use.

Workflow Steps:

• Step 0: Define inputs

• Step 1: Identify key themes or areas to explore

• Step 2: Draft a balanced mix of survey questions

• Step 3: Apply neutrality and bias checks

• Step 4: Internal test for clarity and usefulness

• Step 5: Deploy and analyze results

Step 0: Define Inputs

• {survey_goal} = What is the main purpose of the survey?

• {target_audience} = Who will be taking this survey?

• {key_areas} = What are the primary themes or topics the survey should cover?

• {question_types} = Preferred mix of question types (e.g., multiple choice, rating scale, open-ended)?

• {desired_insights} = What kind of insights or decisions do you want this survey to help with?

• {survey_length} = Approximate number of questions or time it should take (e.g., 5 questions, 3 minutes, etc.)

Step 1: Identify Key Themes or Areas

Goal: Refine the focus areas the survey should cover.

# Role: Market research strategist

# Context: You’re helping design a survey to achieve the following goal: {survey_goal}.

The survey will be taken by: {target_audience}.

These are the high-level topics to explore: {key_areas}.

# Task: Identify 3–5 refined themes or categories the survey questions should cover.

Make sure they align with the goal and audience.

# Format: Bullet list with a 1-sentence explanation per theme.

# Tone: Professional and clear.

Step 2: Draft Survey Questions

Goal: Create an effective set of questions that cover key areas and meet time/length goals.

# Role: Survey design expert

# Context: You’ve identified the key areas as: {key_areas}.

The survey is aimed at: {target_audience}, with the goal of: {survey_goal}.

Preferred question types: {question_types}.

Survey length: {survey_length}.

# Task: Draft survey questions (up to {survey_length}) using a balanced mix of question types.

Each question should align with a key area and help meet the survey goal.

# Format: List questions by number. Include question type in parentheses after each.

# Tone: Neutral and clear, free of bias.

Step 3: Apply Neutrality and Clarity Checks

Goal: Ensure each question is unbiased and easy to understand.

# Role: Survey editor

# Context: You’re reviewing survey questions for a project targeting: {target_audience}.

The goal is: {survey_goal}, and key areas include: {key_areas}.

# Task: Review each question for bias, leading language, and unclear phrasing.

Suggest revisions to improve neutrality and clarity.

# Format: Table with columns — Original Question | Issue (if any) | Suggested Revision

# Tone: Analytical but constructive.

Step 4: Prepare Internal Testing

Goal: Create a simple plan to test the survey before launch.

# Role: Research coordinator

# Context: You’re preparing an internal test of a survey aimed at: {target_audience},

designed to achieve: {survey_goal}. The test should confirm clarity, flow, and estimated completion time ({survey_length}).

# Task: Write a checklist for internal testers and provide a simple feedback form template.

# Format: Bullet list of instructions + feedback form with open-ended fields (e.g., “What was unclear?”, “Any confusing questions?”, etc.)

# Tone: Friendly, efficient, and clear.

Step 5: Plan Deployment and Analysis

Read more

This prompt is not part of The PMM’s Prompt Playbook which has 30 ready-to-use prompts. If you’re looking for more cut-and-paste prompts, join the Substack! Paid subscribers receive new cut-and-paste prompts every week.

Get the PMM’s Prompt Playbook and Modern B2B Marketing today!

Need help with product marketing or prompts? Let me know.

Google Analytics Insight & Optimization Workflow

Created by prompts.tinytechguides.com

What this Workflow Does

This workflow helps B2B marketers and web teams turn Google Analytics data into real insights. It identifies top-performing pages, traffic sources, and user behavior trends — then generates actionable recommendations to improve engagement and conversions.

Workflow Steps Summary

• Step 0: Define Inputs

• Step 1: Identify Top-Performing Pages

• Step 2: Analyze User Behavior Metrics

• Step 3: Evaluate Traffic Source Performance

• Step 4: Assess Device Engagement Patterns

• Step 5: Summarize Findings and Recommend Optimizations

Data Collection Instructions (Before Step 0)

Before running the workflow, you’ll need to gather data from GA4. Here’s how:

📅 1. Set Your Date Range

Where: Top-right in GA4
-- Choose your analysis window (e.g., Last 30 days, Custom)

📄 2. Export Page Performance Data

Where: Reports > Engagement > Pages and Screens
What to include:
-- Page title
-- Views
-- Active users
-- Average engagement time
-- Event count
-- Engagement rate (GA4)
How to export:
Click the “Share” icon → Download CSV

🌐 3. Export Traffic Source Data

Where: Reports > Acquisition > Traffic Acquisition
What to include:
-- Default channel group (e.g., Organic Search, Direct, Referral)
-- Sessions
-- Engaged sessions
-- Engagement rate
-- Avg. engagement time per session
How to export:
Use the same “Share” > Download method

✅ 4. Identify Conversion Events

Where: Reports > Engagement > Events or Conversions
What to include:
-- Event names (scroll, click, form_submit, etc.)
-- Event counts
-- Engagement rate
-- Conversion paths if configured
Note: If conversions aren’t set up, use proxies like scroll depth or time-on-page

📱 5. Device Breakdown (Optional)

Where: Explore > Create new exploration → Add “Device category”
What to include:
-- Sessions by device (desktop, mobile, tablet)
-- Engagement rate and time per device

Step 0: Define Inputs

Step 0: Define Inputs  
{analytics_date_range} = Time period analyzed  
{analytics_data} = Exported GA4 data for pages, events, traffic sources, and devices  
{site_type} = Type of website (e.g., B2B blog, SaaS product site)  
{conversion_definition} = What counts as a conversion (e.g., time on page + scroll, form fill, click)  
{business_goal} = Main site goal (e.g., increase signups, improve time on site, reduce bounce)  

Step 1: Identify Top-Performing Pages

#Role  
You are a digital analyst reviewing GA4 data for a {site_type} website.

#Context  
You’re analyzing performance for the period: {analytics_date_range}. The goal is to identify pages that drive the most value based on {conversion_definition}.

#Task  
List the top 5–10 pages with the highest engagement based on views, engagement time, and events. Highlight any patterns (topics, page types, formats).

#Format  
Table or bullet summary with metrics for each page: views, avg engagement time, event count, engagement rate.

#Tone  
Objective, data-focused, concise.

Step 2: Analyze User Behavior Metrics

#Role  
You are a UX and behavior analyst interpreting GA4 engagement data.

#Context  
Your team wants to understand how users interact with content and where drop-offs occur.

#Task  
Analyze bounce rate or engagement rate, time on page, and event count across key pages. Identify which pages are underperforming and why.

#Format  
Short summary by page or page group. Highlight red flags (low time, low engagement, high exits).

#Tone  
Diagnostic, insight-driven, no fluff.

Step 3: Evaluate Traffic Source Performance

#Role  
You are a digital marketing strategist reviewing traffic acquisition insights.

#Context  
You’re evaluating the impact of various sources (organic, direct, social, email, referral) on engagement and conversions.

#Task  
Compare traffic sources by sessions, engagement rate, and conversion rate. Highlight which channels are high-performing and which need optimization.

#Format  
Ranked list or summary by source with performance notes.

#Tone  
Strategic, ROI-focused.

Step 4: Assess Device Engagement Patterns

#Role  
You are a web optimization specialist reviewing GA4 device data.

#Context  
You’re looking to uncover how mobile, desktop, and tablet users engage differently.

#Task  
Identify which device categories drive the most sessions and conversions. Highlight UX issues or opportunities (e.g., low mobile engagement despite traffic).

#Format  
Breakdown by device type: % of sessions, engagement rate, avg session duration.

#Tone  
Practical, mobile-conscious, user-first.

Step 5: Summarize Findings and Recommend Optimizations

Read more