VANTAGEWIRE INTAKE CHECKLIST

Account Team → Complete Before Build Starts

This checklist must be completed before any VantageWire build begins. Every field matters. If you can't answer something, that's fine — flag it and we'll discuss. But don't submit a half-blank form and expect a build to start. The more specific you are, the faster this goes live.

0
Client Information
1
What Type of Wire Is This?
Pick one primary category. Some wires blend categories (e.g., Flock = Hyperlocal + Issue). That's fine — pick the primary driver.

Organizational

"Tell me every time our organization is in the conversation."

Competitor

"Show me what our competitors are doing before our client reads about it."

Issue & Policy

"Track how this policy issue is developing across news and social."

Hyperlocal

"Show me how national stories play out in the markets we care about."

2
Who Are We Watching?
This is the foundation. If you don't know who to watch, we can't build.
3
What Sources Do You Read?
"Where do you go first thing in the morning?" — This is what drives VantageWire. Keywords help us search and classify, but the sources are the foundation. If a source isn't in the system, adding a keyword won't help.
Reminder: VantageWire uses keywords to search and classify content, but the sources are the driver. If someone says "add a keyword" — the real question is "which source is publishing about this that we're not watching?"
4
What Social Accounts Matter?
We monitor X/Twitter and Reddit. Give us specific accounts and communities.
5
What Are the Issues?
These become the filter categories on the dashboard. Every article and post gets classified into one of these buckets. Aim for 5-8 topics. We always add a "General" catch-all.
Too broad = noisy dashboard. "Track everything about tech" gives you a mess. "Track Adobe vs Canva vs Figma across creative tools" gives you signal. The more specific the issues, the more useful the dashboard.
6
What Geography Matters?
Only needed for Hyperlocal wires. Skip if this is Organizational, Competitor, or Issue-only.
7
Deliverable Preferences
Standard is a live dashboard. Some clients also get a daily brief (Google Doc, email). Confirm what they need.

STOP — CHECK BEFORE SUBMITTING

Sections 2, 3, 4, and 5 must have at least one answer each. If any are blank, go back to the client and get specifics. Open-ended requests with no defined sources = no build.