MQL-to-Sales Handoff Tracker

The problem this kills

Marketing says: "We send great leads and sales never calls them." Sales says: "These leads are junk, that's why we don't bother." Neither side has the numbers, so the meeting turns into a vibe contest - and the loudest person wins.

The truth is sitting in the gap nobody measures: which marketing-qualified leads (MQLs - leads marketing thinks are ready for a salesperson) actually got handed off, whether a rep accepted or rejected each one, why they rejected it, and how long it took to make first contact. Without that, you can't fix scoring and you can't hold follow-up accountable. You just keep arguing.

This tool ends the standoff by recording the handoff itself: every MQL gets one record, an SLA clock (the promised follow-up deadline, like 24 business hours) starts the moment it's handed off, and a rep has to formally accept or reject it with a reason. Breaches get flagged automatically. Now the weekly scorecard says exactly what's happening - and it's nobody's opinion.

What you'll build

A private, login-only web app for your marketing and sales teams:

• A handoff inbox where marketing pushes MQLs (typed in, or bulk-imported from your scoring tool or a CSV) and an SLA clock starts ticking.
• A rep disposition screen where each rep accepts or rejects every lead assigned to them, picks a rejection reason from your own list, and logs the first-touch time.
• Automatic SLA breach flags when first contact misses your follow-up window.
• A weekly scorecard - acceptance rate, top rejection reasons, average time-to-first-touch, breach count - that marketing ops must approve before it's shared with leadership.
• A CSV export of the full handoff log and SLA detail, in the exact columns your CRM or BI tool expects.

What's inside the Implementation Plan

The plan is a complete runbook you paste into Claude Code (an AI coding assistant). It builds the whole app step by step, and it opens by interviewing you about your business - your handoff process, your scoring source, your real lead fields, your SLA window, your rejection-reason list, your team structure, and your messy edge cases. It reflects a short tailored spec back to you and waits for your thumbs-up before it builds anything, so you get a tool shaped around how you actually work - not a generic template you have to bend to fit.

Inside you'll find: the discovery interview, the data model tuned to your answers, secure login and per-team data isolation, the handoff and disposition screens, the SLA clock and breach logic, the approval gate for the scorecard, email notifications, duplicate guards, and the CSV import/export fallback - each step ending in a ready-to-paste prompt.

The governance it includes (this is the point)

This isn't a toy spreadsheet replacement. The plan bakes in real controls:

• Login so only your team can open the app.
• Row-level security so each organization only ever sees its own leads and dispositions.
• A full audit trail - who handed off, who accepted or rejected, who approved the scorecard, and exactly when.
• A human-in-the-loop approval gate - the weekly scorecard is drafted automatically but a real person (marketing ops) must review and approve it before it commits and goes out.
• Duplicate guards - the lead ID is the dedupe key, so the same MQL can't create two competing handoff records.

Who it's for

Marketing operations and sales operations teams who are tired of the lead-quality argument and want one shared source of truth. If you run lead scoring, manage SLAs, or get asked "what happened to all those leads?" - this is for you. No coding background needed; if you can describe your process and paste prompts, you can build it.

You've got this - paste the first prompt and let the interview tailor the rest.