Pitch tracking

# Pitch tracking

Pitch tracking is how a development team remembers every approach to a buyer — who was pitched, when, how it went, and what to do next — so the same broadcaster or streamer is never re-pitched from memory and a follow-up is never lost. It lives in Forbairt → Pitches (pitches.php), group-shared across the slate.

What you log per pitch

• Project and buyer — the buyer is picked from your Buyers roster (or typed free-text); picking from the roster bumps that contact's last-contacted date.
• Format — In-person · Video call · Email · Deck only · Event / market.
• Pitched date.
• Outcome — Pending · Pass · Pass with feedback · Interested · Option · Commission · On hold.
• Pass reason — captured when the outcome is a pass, so the slate learns why things don't land.
• Feedback, attendees, venue, and a next step + next-step due date.

What it does for you

• Outcome date auto-stamps when a pitch moves off "pending."
• A pitch with a next-step due date raises a pitch follow-up nudge in your approvals inbox as the date approaches — the mechanism that stops follow-ups slipping.
• You can view a buyer's whole pitch history, or a project's pitch timeline.

How it connects

• Reading log is the inbound counterpart (material that comes in); pitches are what goes out.
• The Packaging view's buyer-interest pillar reads pitch outcomes, and you can move a pitch forward inline there.
• Pitches record the project → buyer approach; the Agents & writers CRM records the agent / writer relationship over time. Use both: the CRM for the people, pitch tracking for the projects you take to market.

See the Forbairt module guide for how pitch tracking sits in the wider development workflow.