Score in LinkedIn for $35. Add who to talk to today for $49. Add the RevOps layer for $59. Flat monthly prices. No credits. Card required.
Coming soon means the feature is not live today.
| Feature | INTELLIGENCE $35 | OUTREACH $49 | PIPELINE $59 | TEAM Quote |
|---|---|---|---|---|
| Side-panel ICP scoring on LinkedIn | Yes | Yes | Yes | Yes |
| New connections arrive scored | Yes | Yes | Yes | Yes |
| ICPs | Yes | Yes | Yes | Yes |
| Contacts with relationship status (stage, connected date, connect sent date) | Yes | Yes | Yes | Yes |
| CSV export of contacts | Yes | Yes | Yes | Yes |
| Base analytics (activity, acceptance and reply rates) | Yes | Yes | Yes | Yes |
| Enrich with your own Apollo, Lusha or Clay key | Yes | Yes | Yes | Yes |
| Reply tracking and who owes a reply | No | Yes | Yes | Yes |
| Check-in heat map | No | Yes | Yes | Yes |
| AI copilot with your selling style and guardrails | No | Yes | Yes | Yes |
| Cadences | No | Yes | Yes | Yes |
| Analytics by ICP | No | No | Yes | Yes |
| Stale-contact cleanup | No | No | Yes | Yes |
| HubSpot push and activity sync | No | No | Yes | Yes |
| CRM and Clay webhooks and API | No | No | Coming soon | Coming soon |
| Seat management and ICP lock | No | No | No | Yes |
| Rolled-up team activity | No | No | No | Yes |
What each plan includes, what it does, and why you need it.
Know who's worth your time, inside LinkedIn.
What's included: A 0 to 100 score and fit tier on every LinkedIn profile you open, with why they fit and the risks.
What it does: Reads the profile and scores it against your ICP in the Vaunzo side panel. You stay on LinkedIn.
Why you need it: You decide in seconds whether someone is worth a connect, instead of reading every profile top to bottom.
What's included: One or more ICPs with titles, industries, company size, locations, signals, red flags and your value proposition.
What it does: Paste a paragraph about who you sell to and Vaunzo fills in the fields. Every score runs against it.
Why you need it: A score is only as good as the ICP behind it. Write it once and every profile is judged the same way.
What's included: Your contact list with ICP score, stage, connected date and connect sent date. CSV export.
What it does: Tracks where each relationship stands as you work on LinkedIn.
Why you need it: You see who accepted, who is still pending and who you have not touched, without a spreadsheet.
What's included: Scoring for new connections as they accept, plus your existing network on the sync.
What it does: When someone accepts your invite, Vaunzo marks them connected, moves their stage and scores them against your ICP.
Why you need it: Your newest connections are often your warmest. You know right away which ones fit.
What's included: Connects, DMs, replies and acceptances over time, plus acceptance and reply rates.
What it does: Shows how your LinkedIn activity turns into conversations.
Why you need it: You can see what is working before you change your approach.
What's included: Enrichment through your own Apollo, Lusha or Clay account. For Clay, add your API key and your Clay function.
What it does: Adds email and phone to the contacts you choose, one at a time, using your key. With Clay, the contact you pick runs through your own Clay function and the result comes back to Vaunzo.
Why you need it: You spend enrichment credits only on strong fits. Vaunzo does not charge for enrichment and does not resell data.
Know who to talk to today.
What's included: One inbox for your LinkedIn DMs, with filters for needs reply, unread, sent and InMail.
What it does: Syncs your conversations and flags the ones where the other person spoke last.
Why you need it: Deals stall when replies sit. You see who is waiting on you before they go cold.
What's included: A month-by-month view of each relationship: messages you sent, messages they sent, both, or a light touch. Days since your last DM.
What it does: Weighs real back-and-forth over one-way sends, and counts birthday and anniversary notes as light touches.
Why you need it: You spot the relationships going quiet and check in before they fade.
What's included: Connection notes, DMs and InMails. You choose an outreach framework and a message style in Settings. Guardrails shape every draft.
What it does: Writes in the voice you set, with your selling style and guardrails, plus the profile, your ICP, and what you have already said to that person.
Why you need it: The note is specific to how you sell and to that prospect. Better than pasting the profile into ChatGPT or another generic AI tool.
What's included: Follow-up plans with steps and day offsets. Apply a cadence to a contact.
What it does: Creates a task on the day each step is due.
Why you need it: Follow-up stops living in your head. You open Vaunzo and see what to do today.
One ICP and one view for the whole team.
Connect LinkedIn. Describe your ICP. See who fits.
Card required. Cancel any time.
Pipeline. $59/mo
The LinkedIn layer of your modern RevOps stack. Built for you instead of building it yourself.
What's included: Acceptance, reply and velocity broken down by ICP.
What it does: Filters every analytics view to one ICP.
Why you need it: You see which segment converts, and where to spend your LinkedIn time and your enrichment budget.
What's included: Push contacts to HubSpot, with LinkedIn connects, messages, InMails and scores logged to the timeline as you work.
What it does: Creates or matches the contact in HubSpot and keeps LinkedIn activity next to it.
Why you need it: Only qualified contacts reach your CRM, with context. That is how cost per qualified lead goes down.
What's included: A review queue of low-fit 1st connections with no recent engagement, a stale filter on contacts, and an optional email alert.
What it does: Suggests connections to review. You remove them on LinkedIn yourself, then mark the row. Vaunzo never removes a connection.
Why you need it: A cleaner network means a cleaner feed and fewer low-fit contacts in your reports.
What's included: Coming soon. Not live today.
What it will do: Send qualified contacts to your CRM or Clay table by webhook, and let your systems read from Vaunzo by API.
Why you will want it: Vaunzo becomes the qualified-contact feed for the rest of your stack.