Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

managing-marketing-ops

Étoiles5

Forks1

Mis à jour22 février 2026 à 09:40

Use when the CRM is unreliable or inconsistently used, when lead routing is manual and slow, when marketing tools are disconnected or underutilized, when there are no documented SOPs for repeatable marketing processes, when marketing and sales lack shared definitions and handoff SLAs, or when data quality is degrading. Use when operational infrastructure is blocking execution of other marketing skills.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

amogha-dalvi

amogha-dalvi/Marketing_GTM

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	managing-marketing-ops
description	Use when the CRM is unreliable or inconsistently used, when lead routing is manual and slow, when marketing tools are disconnected or underutilized, when there are no documented SOPs for repeatable marketing processes, when marketing and sales lack shared definitions and handoff SLAs, or when data quality is degrading. Use when operational infrastructure is blocking execution of other marketing skills.
user-invocable	true
metadata	{"version":"1.0.0"}

Marketing Ops & Tech Stack

Overview

Marketing Ops is the operational backbone that makes every other marketing skill run. This skill builds the tech stack, CRM infrastructure, automation workflows, RevOps alignment, and AI agent deployments that turn strategy into repeatable execution.

When to Use

CRM is partially configured, inconsistently used, or full of duplicates
Lead routing is manual and leads sit for hours or days
Marketing, sales, and finance each report different numbers
Tools are disconnected with CSV exports and manual data entry
No documented SOPs for campaigns or lead management
Lead scoring does not exist or reflect actual buyer behavior

Don't use when: CRM is clean and trusted, lead routing is automated under 1-hour SLA, SOPs are documented, and tools are integrated with validated data flows.

Quick Reference

Phase	Duration	Output
Tech stack audit and blueprint	Day 1-5	Tool inventory, target architecture
CRM setup and data infrastructure	Day 6-10	Lifecycle stages, data quality standards
Automation workflow build	Day 11-18	Lead routing, nurture, onboarding, reporting
Integration architecture	Day 19-22	Integration map, data flow validation
RevOps alignment	Day 23-25	Shared definitions, SLAs, feedback loops
SOPs and AI agent deployment	Day 26-30	Process docs, AI agent playbook

Core Deliverables

Tech Stack Audit and Blueprint -- Tool inventory plus target architecture
CRM and Data Infrastructure -- Lifecycle stages, scoring, data quality
Automation Workflows -- Lead routing, nurture, onboarding, reporting
Integration Architecture -- Tool connections and data flow validation
RevOps Alignment -- Shared definitions, SLAs, feedback loops
Marketing SOPs -- Campaign, lead management, reporting checklists
AI Agent Playbook -- Routing, reporting, cleanup, personalization agents

Common Mistakes

Buying enterprise tools for startup problems
Automating a broken process (fix process first)
Skipping CRM hygiene (bad data compounds monthly)
Integrating everything to everything
Letting tools drive process instead of defining process first
Teams using different definitions for the same terms
Ignoring lead score decay
Going live without testing the full lead flow

Integration

Feeds into: Loops back to all skills as operational infrastructure

Refresh: Tech stack audit quarterly. CRM cleanup monthly. Scoring and automation audit quarterly. Integration check monthly. Full ops assessment every 6 months.

See workflow.md for detailed phase-by-phase execution, tech stack blueprints by ARR level, CRM setup checklists, automation workflow diagrams, integration maps, and SOP templates.

Plus depuis ce dépôt

même dépôt

accelerating-pipeline

amogha-dalvi/Marketing_GTM

Use when pipeline velocity is flat or declining, win rates are below 20 percent, sales cycles are lengthening, deals are single-threaded, or lead routing is slow. Use when MQL volume is prioritized over pipeline quality, when marketing and sales define funnel stages differently, or when signal-based engagement has not replaced linear nurture drips.

2026-02-225

building-positioning-messaging

amogha-dalvi/Marketing_GTM

Use when messaging is inconsistent across sales and marketing, homepage conversion is low, buyers cannot articulate what makes you different, or positioning was never formally defined. Use when entering a new category, responding to competitive repositioning, launching a major product, or when customer research reveals a gap between how customers describe you and how you describe yourself.

2026-02-225

conducting-customer-research

amogha-dalvi/Marketing_GTM

Use when starting any marketing initiative, entering a new market, refreshing ICP, or when downstream marketing decisions lack customer evidence. Use when messaging isn't resonating, churn patterns are unclear, or positioning feels like guesswork. Foundational skill that feeds all other marketing skills.

2026-02-225

creating-sales-enablement

amogha-dalvi/Marketing_GTM

Use when sales reps lack deal-stage-specific content, when the founder's sales knowledge lives in their head instead of a system, when win rates are declining or sales cycles are lengthening, when no buying group content map exists, or when reps spend significant time creating content that should already exist. Use when sales and marketing lack shared definitions and feedback loops.

2026-02-225

defining-icp-segmentation

amogha-dalvi/Marketing_GTM

Use when targeting feels unfocused, CAC is too high, churn patterns suggest bad-fit customers, or the ICP lives only in the founder's head. Use when entering a new market, conversion rates are low, or sales wastes cycles on wrong-fit accounts. Use after customer research is complete and before any channel or campaign decisions.

2026-02-225

designing-gtm-strategy

amogha-dalvi/Marketing_GTM

Use when the user needs to translate foundational marketing insights into an operational growth plan, select a GTM motion, prioritize channels, or create a 90-day execution plan. Use when marketing efforts feel like disconnected tactics without a coherent system connecting them to revenue targets.

2026-02-225

name	managing-marketing-ops
description	Use when the CRM is unreliable or inconsistently used, when lead routing is manual and slow, when marketing tools are disconnected or underutilized, when there are no documented SOPs for repeatable marketing processes, when marketing and sales lack shared definitions and handoff SLAs, or when data quality is degrading. Use when operational infrastructure is blocking execution of other marketing skills.
user-invocable	true
metadata	{"version":"1.0.0"}

Marketing Ops & Tech Stack

Overview

When to Use

CRM is partially configured, inconsistently used, or full of duplicates
Lead routing is manual and leads sit for hours or days
Marketing, sales, and finance each report different numbers
Tools are disconnected with CSV exports and manual data entry
No documented SOPs for campaigns or lead management
Lead scoring does not exist or reflect actual buyer behavior

Don't use when: CRM is clean and trusted, lead routing is automated under 1-hour SLA, SOPs are documented, and tools are integrated with validated data flows.

Quick Reference

Phase	Duration	Output
Tech stack audit and blueprint	Day 1-5	Tool inventory, target architecture
CRM setup and data infrastructure	Day 6-10	Lifecycle stages, data quality standards
Automation workflow build	Day 11-18	Lead routing, nurture, onboarding, reporting
Integration architecture	Day 19-22	Integration map, data flow validation
RevOps alignment	Day 23-25	Shared definitions, SLAs, feedback loops
SOPs and AI agent deployment	Day 26-30	Process docs, AI agent playbook

Core Deliverables

Tech Stack Audit and Blueprint -- Tool inventory plus target architecture
CRM and Data Infrastructure -- Lifecycle stages, scoring, data quality
Automation Workflows -- Lead routing, nurture, onboarding, reporting
Integration Architecture -- Tool connections and data flow validation
RevOps Alignment -- Shared definitions, SLAs, feedback loops
Marketing SOPs -- Campaign, lead management, reporting checklists
AI Agent Playbook -- Routing, reporting, cleanup, personalization agents

Common Mistakes

Buying enterprise tools for startup problems
Automating a broken process (fix process first)
Skipping CRM hygiene (bad data compounds monthly)
Integrating everything to everything
Letting tools drive process instead of defining process first
Teams using different definitions for the same terms
Ignoring lead score decay
Going live without testing the full lead flow

Integration

Feeds into: Loops back to all skills as operational infrastructure

Refresh: Tech stack audit quarterly. CRM cleanup monthly. Scoring and automation audit quarterly. Integration check monthly. Full ops assessment every 6 months.

See workflow.md for detailed phase-by-phase execution, tech stack blueprints by ARR level, CRM setup checklists, automation workflow diagrams, integration maps, and SOP templates.