Hello world: building the MAP we always wanted
veloquent is a marketing automation platform built by former MAP administrators, and this is the first post explaining what already runs and what doesn't. Working today: a single campaign tree where every asset belongs to a campaign, folder tokens that cascade with a visible inheritance map, and review as a real object with approvals in-app or from Slack. The build log and roadmap are published openly so operators can see the difference between shipped and planned — and submit the problems their current platform won't fix.
I’ve worked in Marketing Operations for almost 20 years, and the truth is… Not a whole lot has changed. We still send emails in a series, we still run plays based on behavioral triggers, the gears of industry turn another revolution. It… kinda sucks, right? Feels like especially now, that the Operators should play a greater role in product design and management.
So: hello world. This is the first post on the veloquent blog, and the honest version of what this is.
What veloquent is
veloquent is a marketing automation platform being built by people who ran the incumbents for a living. The goal is to make it the best marketing automation platform in the world, full stop.
There are so many great ideas across the span of marketing automation platforms… Accelerating campaign builds with folder and program-level tokens, liquid syntax and split tokens, automatically creating new events on ingestion, Salesforce Campaign syncing, configurable multivariate tests, workflow management… One challenge is often that not all of those solutions live under the same roof. But there are also other tools to build: qualitative as well as technical review, approval chains, slack integration… This is where our experience as Operators makes us uniquely qualified as the best product designers and managers.
Why we're building it in public
To be honest… Because it’s fun, and attention begets feedback. The more use cases veloquent can solve before it’s integrated across your tech stack, the better a final product it will be.
But moreover, MOPs is a community that solves the same problems in isolation, over and over, in a hundred different instances. The intake form on this site exists so you can hand us the thing your platform won't fix, the workaround you're embarrassed by, the ticket that's been open for three years, the export-to-spreadsheet ritual you do every Monday. The bottom line we hold ourselves to is that if an operator has lived with a pain anywhere in their career, it should be either already solved in veloquent or on the roadmap. We can't hold that line without hearing from you.
How you can use it
One decision we made early: operators choose how they want to work, and the platform meets them there. Run everything through the assistant and describe what you want in plain language. Run approvals and quick changes through the Slack agent, where your team already lives. Or build every asset by hand and never talk to the AI at all. All three produce the same objects, because they use the same primitives. Your org's process doesn't have to bend around our opinion about AI.
What's next
Now that the core campaign functionality is seated, I’m refining other areas of the app, Emails to start. I need to think through how best to manage a library of emails, how to build and edit, and even think through how approvals can work between veloquent and Slack even if the approver does not hold a veloquent seat.
As always, if you’d like to stay apprised of the latest escapades here, there's a signup on this site. If you'd rather just throw us a hard problem, the intake is right there too. Either way — hello, and thanks for being early!