Campaign Request Prioritizer

The problem this kills

Your marketing queue fills up faster than the team can clear it. Sales wants a webinar, the product team wants a launch push, the founder wants a LinkedIn series, and someone in finance just "needs a quick email blast" by Friday. Everyone's request is the most important request - to them. So work gets done in the order people shouted, or whoever has the most political weight, not in the order that actually moves the business.

Then the hard part: explaining why you said no. When a stakeholder corners you about why their campaign slipped, "we were busy" doesn't hold up. You need a defensible, repeatable way to rank requests - and a record of how each decision was made.

A RICE-style score (Reach, Impact, Confidence, Effort) gives you exactly that. The math is simple. The pain is doing it consistently, with your team's real weights, showing the breakdown so it's explainable, and turning a spreadsheet of guesses into an approved backlog someone signed off on.

What you'll build

A small private web app for your team that:

• Imports a list of pending campaign requests from your intake tool or a CSV.
• Scores each request on Reach, Impact, Confidence, and Effort using a RICE-style model with weights you configure in the interview.
• Generates a ranked backlog - highest-value campaigns at the top - and shows the full score breakdown so every ranking is explainable.
• Factors in your team's current capacity so the backlog reflects what can realistically be done.
• Lets your marketing lead review, adjust any factor with a logged reason, and approve the prioritized list before it's published.
• Publishes the approved priority list to the team and exports a clean CSV for planning.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook. It opens by interviewing you about your business - your current intake process, your real request fields, how you'd weight each RICE factor, your team's capacity, your approval rules, and the messy edge cases - so the tool scores campaigns the way you actually think about priority, not a generic template. The agent reads a short spec back to you and waits for your thumbs-up before it builds a thing.

From there it walks you, step by step, through standing up the database, the import screen, the scoring engine, the ranked backlog, the lead's adjust-and-approve gate, the publish step, and the CSV export - each step ending in a ready-to-copy prompt you paste into your AI coding agent.

The governance it includes (this is the point)

This is not a throwaway script. Every build includes:

• Login so only your team can open the tool.
• Row-level security so each organization only ever sees its own requests and scores.
• A full audit trail - who imported what, who changed which factor and why, who approved the backlog, and exactly when.
• A hard human-in-the-loop approval gate - the computed scores and ranked backlog are drafts until your lead reviews, adjusts, and approves; only then is the priority list published.
• Duplicate guards keyed on request ID / title so the same request can never be scored twice.

Who it's for

Marketing ops leads and managers who have to defend "why we said no" to stakeholders - and who want a repeatable, auditable way to prioritize campaign requests instead of working in the order people asked.

You've got this - paste the first prompt and let the agent interview you.