@ava-morgangrowth-marketing-automation-playbookएकल टेक्स्टसार्वजनिक14 जून 2026 को अपडेट किया गया

Growth Marketing prompt that maps a manual workflow into safe tool-assisted automation and returns workflow map, tool schema, approval gates, and rollback plan.

AI Workflow Experiments Growth Lifecycle Marketing

48Star0Fork94कॉपी

Prompt

पूर्वावलोकन

ChatGPT में खोलें

# Role
You are a growth strategist who balances experimentation, positioning, and customer psychology. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Map a manual workflow into safe tool-assisted automation for AI-assisted acquisition, lifecycle messaging, creative testing, and funnel diagnosis.

# Inputs
- Project context: a self-serve AI analytics product entering a new vertical
- Target audience: growth marketers, lifecycle teams, founders, demand-gen leads
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: CRM, ad manager, web analytics, email platform, heatmaps
- Constraints: no dark patterns; clear hypothesis; one primary metric per experiment
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- funnel metrics
- ad comments
- CRM stages
- landing page analytics

# Known risks to control
- vanity metrics
- brand mismatch
- overfitting to a single channel

# Method
1. Separate read actions from write actions
2. Put irreversible actions behind explicit approval
3. Define idempotency and retry behavior
4. Add audit logs

# Required output sections
1. Current workflow
2. Automation candidates
3. Tool interfaces
4. Approval gates
5. Failure recovery
6. Implementation slices

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

आउटपुट

1 आउटपुट

Example Output: Growth Marketing Tool Automation Playbook

Inputs used

Project context: a self-serve AI analytics product entering a new vertical
Target audience: growth marketers, lifecycle teams, founders, demand-gen leads
Success metric: activation, quality, and risk reduction
Available tools and data: CRM, ad manager, web analytics, email platform, heatmaps
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

workflow map, tool schema, approval gates, and rollback plan

Current workflow

Start with the manual path that uses funnel metrics. Automate the read/summarize/draft steps first; keep approval, notification, and destructive writes outside the first release.

Automation candidates

Start with the manual path that uses ad comments. Automate the read/summarize/draft steps first; keep approval, notification, and destructive writes outside the first release.

Tool interfaces

Use web analytics as the primary working surface. Read actions are allowed by default; write actions require an explicit human approval step and an audit entry containing source, reviewer, and rollback path.

Approval gates

Use landing page analytics as evidence, apply the constraint "no dark patterns", and explicitly note how the plan reduces vanity metrics. The output should be ready for a practitioner to act on without a follow-up explanation.

Failure recovery

Use funnel metrics as evidence, apply the constraint "clear hypothesis", and explicitly note how the plan reduces brand mismatch. The output should be ready for a practitioner to act on without a follow-up explanation.

Implementation slices

Use ad comments as evidence, apply the constraint "one primary metric per experiment", and explicitly note how the plan reduces overfitting to a single channel. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on funnel metrics and ad comments. Treat vanity metrics as the primary launch blocker. The first milestone should prove that the workflow produces a usable experiment brief, campaign matrix, and measurement plan with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI-assisted acquisition, lifecycle messaging, creative testing, and funnel diagnosis.
It includes the required sections: Current workflow, Automation candidates, Tool interfaces, Approval gates, Failure recovery, Implementation slices.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: vanity metrics.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Growth Marketing: Tool Automation Playbook

Use this prompt when you need workflow map, tool schema, approval gates, and rollback plan for AI-assisted acquisition, lifecycle messaging, creative testing, and funnel diagnosis.

Best for

growth marketers, lifecycle teams, founders, demand-gen leads
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.