Meta Tools Stack Evaluation

Meta Tools Stack Evaluation

Purpose

Produce a structured, client-specific martech tools recommendation calibrated to Uganda/East Africa budgets, infrastructure, and team capacity. Apply the free-tier-first principle and Uganda DPA 2019 compliance throughout.

Use When

• Use this skill for evaluating the wider marketing technology stack for workflow fit, duplication and total cost.
• Confirm that meta-ai-tools-audit is not the closer route before proceeding.

Do Not Use When

• Use meta-ai-tools-audit when its narrower output is requested.
• Do not publish, spend, change a live account, certify compliance, or invent missing client evidence.

Required Inputs

Outputs

Evidence Produced

Capability and permission boundary

Read and search access to the supplied artefacts are required; calculation or file-rendering capability is optional. This is read-only by default: inspect and report without changing source records, accounts, skills or campaigns. Editing the deliverable requires explicit authorisation; publishing, production mutation, destructive action, spend, and certification claims require separate explicit authority and evidence.

Degraded mode

If files, platform access, network, rendering, fonts, or calculation tools are unavailable, return the narrowest useful qualified martech stack recommendation and migration priorities. Mark each blocked check not assessed, state the consequence, and provide the exact evidence needed to resume. Never convert an unavailable check into a pass.

Decision rules

Workflow

1. Confirm the requested decision, consumer, market, period and permission boundary; route to meta-ai-tools-audit if its contract is closer.
2. Inventory the required inputs and their provenance. Stop any decision whose critical evidence is absent; recover by requesting it or recording a bounded assumption.
3. Apply the domain method in the core sections below, following the decision table whenever evidence conflicts or scope changes.
4. Verify calculations, dates, named platforms and claims against the supplied sources; label inference and uncertainty.
5. Produce the martech stack recommendation and migration priorities, decision/source register and explicit next owner. Do not mutate live systems without separate authority.
6. Run the repository anti-slop ship gate. If a blocking factual, permission or evidence defect remains, fix it or withhold release.

Quality Standards

The output is client-specific, uses British English and the stated market/currency, distinguishes observed fact from inference, exposes gaps, and gives a checkable acceptance condition. Recommendations must be feasible within the confirmed budget, capacity and permissions.

Anti-Patterns

• Using an undated benchmark as the client's result. Fix: use account evidence or label the benchmark as a provisional comparator.
• Producing the martech stack recommendation and migration priorities without current stack. Fix: stop the affected decision or issue a clearly bounded partial output.
• Treating missing access or data as a successful check. Fix: record not assessed, its risk and the recovery input.
• Absorbing meta-ai-tools-audit into this workflow. Fix: route the neighbouring output and hand over verified inputs.
• Publishing, spending or editing a live account during planning or review. Fix: obtain separate explicit authority and retain action evidence.

Worked example

Given verified current stack, the skill produces a martech stack recommendation and migration priorities with source dates and named assumptions. If that evidence cannot be accessed, it returns only the supported sections plus a recovery list; it does not fill gaps with East African defaults.

Read next

• meta-ai-tools-audit for the neighbouring contract.
• anti-ai-slop during production.
• ai-slop-audit at the release checkpoint.

References

• Anti-AI slop production gate
• Follow the directly linked repository skills above and any domain references named in the core sections below. Verify current platform, price, legal and regulatory claims before use.

Required Input

Ask for all of the following before generating any output:

1. Client business name and industry — e.g., "Kampala Creameries, dairy FMCG"
2. Country/city — default East Africa/Uganda if not specified
3. Team size — how many people will use the tools daily or weekly?
4. Current tools in use — list every tool the client currently pays for or uses regularly
5. Monthly budget for tools — state in UGX or USD; note that most tools price in USD
6. Primary pain points — what specific problems must the tools solve? (e.g., "we miss posting schedules", "we cannot track leads", "design takes too long")
7. Technical capacity — can the team learn new tools independently, or do they need simple/intuitive tools only?

Do not proceed until all seven inputs are collected.

Section 1 — Tool Stack Principles

Apply these five principles before making any recommendation.

1. Solve real problems, not hypothetical ones Only recommend tools that address a pain the client has today. A sophisticated analytics dashboard is worthless if the client does not review analytics. Map every recommended tool to a named pain point from the client's input.

2. Free tier first Start with free tools. Upgrade only when the free tier is genuinely limiting the work. Most EA SME clients are over-tooled and under-skilled — fewer tools used well beats many tools used poorly. Default to zero-budget stacks and justify every paid upgrade explicitly.

3. Mobile-accessible All recommended tools must work on a mobile phone. Many EA team members manage social media from a smartphone, not a laptop. Reject any tool that is desktop-only or that degrades significantly on mobile data speeds.

4. Data locality and Uganda DPA 2019 compliance Avoid tools that require uploading customer personal data to external servers without a privacy policy review. The Uganda Data Protection and Privacy Act 2019 applies to all client data processing. For any tool that stores customer data (CRM, email platforms), confirm a Data Processing Agreement exists before recommending.

5. Training time budget Every new tool carries a learning curve. Budget 2–4 hours of training time per tool. Only introduce 1–2 new tools per quarter. A tool the team ignores is a liability, not an asset.

Section 2 — Core Tools Reference Table

Use these tables as the primary reference when building a recommendation. Apply EA-specific notes to every client context.

Social Media Management and Scheduling

Design and Content Creation

Analytics

Email Marketing

CRM (Customer Relationship Management)

Project Management

Section 3 — Recommended Stacks by Budget

Generate one of the following stacks as the default recommendation, then adjust based on the client's specific pain points.

Zero Budget — Free Tools Only

• Scheduling: Meta Business Suite
• Design: Canva (free tier)
• Video: CapCut (free)
• Analytics: Meta Business Suite Insights + Google Analytics 4
• Email: Mailerlite (free, up to 1,000 subscribers) or MailChimp (free, up to 500 contacts)
• CRM: Google Sheets (internal use only)
• Project management: Trello (free)
• Total monthly cost: UGX 0

Apply this stack as the starting point for all new clients. Introduce upgrades only after the team has demonstrated consistent use of the free tier for at least one quarter.

Starter Budget — UGX 50,000–150,000/month (~$13–40)

Build on the zero-budget stack and add:

• Canva Pro (~UGX 50,000/month) — biggest ROI of any single tool upgrade; brand kits, background remover, content scheduler
• Buffer paid (~UGX 22,000/month) — scheduling across multiple platforms beyond Meta
• Total: ~UGX 72,000/month

Recommend this stack when the client has stabilised on free tools and design quality or multi-platform scheduling is a bottleneck.

Growth Budget — UGX 150,000–400,000/month (~$40–105)

Build on the starter stack and add:

• Mailerlite paid (~UGX 34,000/month) — up to 5,000 subscribers with automation
• HubSpot Starter (~UGX 56,000/month) — proper pipeline CRM with email integration
• Publer (~UGX 45,000/month) — WhatsApp scheduling for customer communications
• Total: ~UGX 207,000/month

Recommend this stack when the client has active email list growth, a sales pipeline that needs CRM, or is running structured WhatsApp marketing.

Section 4 — Tool Evaluation Framework

When a client asks "should we use [tool]?", apply this five-question test before responding.

1. Does it solve a specific, named problem we have today?
2. Is there a free tier we can test before committing budget?
3. Will the team actually use it? (Unused tools cost money and damage morale.)
4. Can it be used on a smartphone as well as a laptop?
5. Does it require entering customer personal data? If yes, is there a DPA-compliant data processing agreement in place?

Decision rule: If the answer to question 1, 3, or 5 is No — do not recommend the tool. Document the reason clearly in the output.

Include this framework as a named section in every tools evaluation deliverable so the client can apply it independently in future.

Output Format

Produce a structured tools evaluation document with the following sections in order:

1. Current Stack Audit — list every tool the client currently uses, its monthly cost, and whether it is earning its place (used regularly / partially used / unused)
2. Recommended Stack — table of recommended tools mapped to pain points, with free/paid tier, monthly cost in UGX, and rationale
3. Tools to Remove — any current tools that fail the five-question test, with brief justification
4. Implementation Roadmap — quarter-by-quarter plan introducing no more than 2 new tools per quarter, with estimated training time
5. Total Monthly Cost — zero/starter/growth tier clearly labelled in UGX
6. DPA Note — flag any tool in the recommended stack that processes customer personal data and confirm a Data Processing Agreement is required

Quality Criteria

• All six tool categories (scheduling, design, analytics, email, CRM, project management) are covered with a reference table and at least one recommendation per category
• Three budget stacks are presented with costs stated in UGX and USD equivalents
• The five-question evaluation framework is present and applied to the client's specific tool enquiries
• Mobile-accessibility is stated as a hard requirement and applied to reject or flag any desktop-only tools
• Uganda DPA 2019 is cited and applied to all tools that process customer personal data
• Free-tier-first principle is stated explicitly and the zero-budget stack is always the starting point before upgrades are introduced
• Training time budget (2–4 hours per tool, maximum 1–2 new tools per quarter) is included in the implementation roadmap
• Every recommended tool is mapped to a named client pain point from the Required Input — no hypothetical recommendations

Related Skills

• meta-budget-planner/SKILL.md — use when calculating total martech spend as part of a broader marketing budget
• playbook-ai-content-workflow/SKILL.md — use when AI writing or content generation tools are part of the recommended stack
• meta-testing-framework/SKILL.md — use when the client wants to A/B test tools before committing to a paid tier
• playbook-agency-operations/SKILL.md — use when building a tools stack for an agency managing multiple clients rather than a single brand

References

• Chaffey, D. (2024) Digital Marketing: Strategy, Implementation and Practice — martech stack principles and RACE framework
• Bodnar, K. and Cohen, J. (2012) The B2B Social Media Book — ROI framework for tool investment decisions
• Uganda Data Protection and Privacy Act 2019 — applies to all tools processing customer personal data