Verbiflow is sequencing infrastructure for growth teams. Run multi-step sequences across email, LinkedIn, and cold calls from one platform, handle sending and deliverability, and land replies in one shared inbox so your whole team stays aligned.

What can I do for free?

Sign up free with no credit card. You get three starter sequences personalized to your company, and you can build sequences, import a CSV, and connect a mailbox to test. Launching real sends requires a paid plan, starting at $50/month.

Can I run it from my AI agent?

Yes. Run npx -y growth-mcp install to add Verbiflow to Claude, Cursor, or Codex. It turns your coding agent into a GTM operator that can research accounts, build lists, draft sequences, and run plays from chat.

Do you support cold calling?

Cold calls are in early access. Today, sequences run across email and LinkedIn. If calling is part of your motion, book a demo and we'll get you access.

Do I need to bring my own mailboxes and domains?

You can do either. Connect your existing Gmail or Microsoft accounts, or buy sending domains and provision outbound-ready mailboxes directly in Verbiflow. We handle warming and run inbox-placement checks so your deliverability stays strong.

Email and LinkedIn replies land in one shared inbox where your team can respond directly. You're alerted by email and Slack the moment a prospect replies, and all send and reply activity syncs to your CRM so the whole team stays aligned.

A play is a complete outbound motion: we retrieve a targeted list of accounts and contacts, qualify and segment them, then sequence them across email and LinkedIn. The examples above are real plays we ran. Build your own with the agent, or have us build a custom one for your accounts.

How does pricing work?

Verbiflow is free to explore, with paid plans from $50/month. Plans are priced on monthly contact credits plus sending seats (mailboxes and LinkedIn accounts). Credits cover sourcing and enrichment. See the pricing page for full details.

All posts

Outbound infra·Jun 8, 2026·3 min read

Why the Verbiflow SDK comes before a Verbiflow agent

By The Verbiflow team

Customers ask when we’re shipping a Verbiflow agent. We may. But the first thing to get right was the interface underneath it. Verbiflow already handles the outbound infrastructure: sequences, connected mailboxes, reply inbox, CRM checks, and reporting sync. The MCP and SDK let Claude Code, Cursor, Codex, and eventually a Verbiflow agent build custom plays on top of that same system instead of rebuilding the workflow from scratch every time.

Why the SDK comes first

A Verbiflow agent without a great SDK would just be another chat box with opinions. It might build a play one way today and a slightly different way tomorrow. That is not good enough for outbound.

The SDK is the repeatable shape. It tells Claude Code, Cursor, Codex, and eventually a Verbiflow agent how to build a play the same way every time: pull data with the right batching and parallelism, use the right connected tools, generate the audience, and stage a sequence draft. If custom logic is needed, Claude Code can modify the play code inside that scaffold. The play is still running through Verbiflow’s infrastructure once it is ready to send.

Data providers should keep making their data moats better. Apollo should be great at contacts. Crunchbase should be great at company signals. Clay should be great at tables and enrichment workflows. Verbiflow should make the orchestration work across them.

What Claude Code adds

Claude Code is useful for the work before launch: research, list logic, custom play steps, and copy. With the Verbiflow SDK, it can follow the same outbound structure our team uses instead of improvising a new workflow every time.

For list building: pull from connected data providers with the right parallelism, enrich the contacts, and stage the audience.
For custom plays: add or modify the play code when a customer needs a workflow that is not already in the template.
For copy: use the Verbiflow SDK to draft sequence copy that matches the play, the audience, and outbound best practices.

Verbiflow handles the platform work regardless of Claude Code: CRM and sequence checks, connected mailbox health, sending, email and LinkedIn replies, and reporting sync. Claude Code can help create a better play; it does not replace the system that runs the play.

What this looks like

A GTM lead should be able to ask:

“Use connected Crunchbase and Apollo to build a Series A SaaS audience, draft copy for heads of GTM, and stage the sequence in Verbiflow.”
“Take this Clay export, add the HubSpot suppression rules, improve the copy with the Verbiflow SDK, and prepare the remaining contacts for review.”

The output is not another CSV. It is a play staged in Verbiflow, ready for the team to review, launch, track replies, and report on.

Where the Verbiflow agent fits

We may ship our own agent. When we do, it should not invent a new workflow. It should use the same MCP and SDK our customers already use with Claude Code, Cursor, and Codex. That way the play works the same whether it starts in Claude Code today or inside Verbiflow later.