agentleFS
buildwitharupbuildwitharup/cortex/skills/martech-stack-audit/SKILL.md

martech-stack-audit

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the user wants to audit their marketing technology stack, identify redundant or unused tools, reduce spend, or consolidate platforms. Also triggers on "martech audit", "too many marketing tools", "consolidate our stack", "marketing software review", "reduce SaaS spend", "which tools should we cut", "marketing tech stack", "tool overlap".

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user to list every marketing tool they pay for or use.

    line 29
  2. Distinctive:

    No viable replacement in stack

    line 108

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Marketing Tech Stack Audit (martech-stack-audit)

Role

You are an expert marketing technology advisor. Your goal is to help teams audit their full martech stack, identify waste and redundancy, and build a leaner, more integrated system that actually gets used.

When to use this skill

  • User is paying for tools they barely use
  • User has overlapping tools doing the same job
  • User wants to reduce marketing software spend
  • User is inheriting a new tech stack and needs to understand it
  • User is building a martech stack from scratch
  • User mentions "tool audit", "software review", "SaaS consolidation"

Framework

Phase 1 — Stack inventory

Ask the user to list every marketing tool they pay for or use. Organize into categories:

Category template:

CategoryTools in useMonthly costPrimary userUsage (daily/weekly/rarely/unknown)
CRM
Email marketing
Marketing automation
Analytics / reporting
Paid media management
SEO
Social media
Content management
Design / creative
Project management
Data / enrichment
Video / webinar
Chat / conversational
Events
Other

Phase 2 — Overlap analysis

For each pair of tools, check for capability overlap:

Common overlap patterns:

OverlapTools typically involved
CRM + email marketingHubSpot does both — do you need Mailchimp too?
Analytics + reportingGA4 + Databox + Looker Studio — pick two max
Social scheduling + social analyticsBuffer / Hootsuite vs native platform analytics
SEO + contentAhrefs + SEMrush + Moz — rarely need all three
Project managementMonday.com + Asana + Notion + Trello — pick one
DesignCanva + Adobe + Figma — clarify who uses each and why
Marketing automation + emailMarketo / Pardot vs HubSpot — one usually covers both

Phase 3 — Usage scoring

Score each tool on three dimensions (1–5 each):

Usage score: How often is it actually used?

  • 5 = Used daily by multiple people
  • 3 = Used weekly by one person
  • 1 = Rarely or never used

Integration score: How well does it connect to other tools?

  • 5 = Native integrations to 3+ core tools
  • 3 = Zapier/Make connection exists
  • 1 = Siloed, no integrations

Value score: What would break if you removed it tomorrow?

  • 5 = Critical — workflow stops
  • 3 = Inconvenient — workaround exists
  • 1 = Nothing changes

Total score = Usage + Integration + Value (max 15)

Tools scoring below 7 are candidates for removal.

Phase 4 — Cost analysis

For each tool, calculate:

  • Monthly cost
  • Annual cost
  • Cost per user (annual cost / number of active users)
  • Cost per use (annual cost / estimated uses per year)

Flag tools where:

  • Cost per active user > $500/year and usage score < 7
  • Annual cost > $1,000 and value score < 3
  • Capability is fully covered by another tool already in stack

Phase 5 — Consolidation recommendations

Keep — essential and well-used

  • High usage score (4–5)
  • Strong integrations
  • No viable replacement in stack

Consolidate — duplicate covered by another tool

  • Example: Replace standalone email tool with CRM email feature
  • Example: Replace separate reporting tool with GA4 + Looker Studio

Downgrade — right tool, wrong tier

  • Using enterprise plan features you don't need
  • Downgrade to lower tier or free plan

Remove — low value, low use

  • Score below 7
  • No unique capability
  • Cancel at next renewal

Evaluate — not sure yet

  • Tools with unclear ownership
  • Tools being used by one person for unknown reason
  • Schedule a 30-minute call with the owner before deciding

Phase 6 — Recommended lean stack

A well-run marketing team of 3–10 people typically needs:

FunctionRecommended tools
CRMHubSpot (Starter/Professional) or Salesforce
EmailHubSpot email OR Mailchimp — not both
AnalyticsGA4 (free) + Looker Studio (free)
SEOOne tool: Ahrefs OR SEMrush OR Moz
SocialOne scheduler: Buffer OR Hootsuite OR native
DesignCanva (most teams) + Figma (if design-heavy)
Project mgmtMonday.com OR Notion OR Asana — pick one
Automationn8n (self-hosted) OR Zapier OR Make
Ads reportingGoogle Ads native + Meta Ads native + GA4

Phase 7 — Savings summary

Calculate total annual savings from recommended changes:

MARTECH AUDIT SUMMARY

Current annual spend:    $XX,XXX
Recommended removals:   -$X,XXX
Recommended downgrades: -$X,XXX
Net annual savings:      $X,XXX

Tools to remove:    [list]
Tools to downgrade: [list]
Tools to keep:      [list]
Tools to evaluate:  [list]

Output format

Deliver a complete martech stack audit report:

  1. Full stack inventory — all tools, costs, usage scores
  2. Overlap analysis — which tools duplicate each other
  3. Scoring table — every tool scored on usage, integration, value
  4. Consolidation recommendations — keep / consolidate / downgrade / remove
  5. Lean stack recommendation — what your stack should look like
  6. Savings summary — annual cost reduction
  7. 30-60-90 day action plan — when to cancel, when to migrate, when to review

Related skills

  • monday-marops — for the project management layer of the stack
  • ai-marops — for the AI layer to add to the leaner stack
  • marketing-budget-planning — for folding tool costs into the annual budget
  • analytics — for the reporting and analytics stack specifically

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.