# veloquent — the MAP to replace all MAPs

> veloquent is a marketing automation platform built by marketing operations professionals: campaign-first, review-native, and agentic. It is under construction and shipping in public.

## Status

Under construction, on purpose. The screenshots on the site are the real
product, the build log is the real status, and anything still on the roadmap is
labelled as a roadmap item. There is no public sign-up yet — you can follow the
build or send us a problem to solve.

## Built by Operators

We've run all the big platforms. We know the forty-minute program clone, the
token nobody dares touch, the approval that gets lost in a Slack thread, the
sync queue you check before your coffee. veloquent is the platform we kept
waiting for someone else to build.

## The product, in four parts

### The assistant

"Draft the launch email for enterprise trial accounts, run QA, and submit it
for review." The assistant queries your warehouse, sizes the audience, drafts
the email, wires the send, and submits it — narrating each step as a tool call
you can open. Details: https://www.veloquent.io/platform/assistant

### Campaigns

What it builds is a real campaign, not a pile of loose assets: every workflow
with its audience, email, and delivery in view, tokens inherited from the
folders above it, and review status rolled up where you can see it. Details:
https://www.veloquent.io/platform/campaigns

### Review

Nothing sends until a human says so. Every workflow the assistant — or anyone
else — builds waits in one review queue. Approve it in the app, or right from
Slack, where the notification carries the same buttons. Details:
https://www.veloquent.io/platform/review

### Workflows

Sends, waits, event branches, a step that writes a line of copy per person, a
50/50 test. Each step runs as its own job, which is what makes the boring
guarantees hold: a one-week wait is still a week later, a step that errors
retries instead of quietly dropping someone, and a flow can check your
warehouse mid-journey. Details: https://www.veloquent.io/platform/stack

## The pieces, and where they stand

- **One tree.** Batch sends, evergreen journeys, emails, and audiences all live
  inside a campaign, and every campaign lives in one tree.
- **Tokens that show their work.** Set a token once on a folder and everything
  underneath inherits it; override it on one campaign when you need to. The UI
  shows exactly where each value came from.
- **Approvals that don't live in email.** Mark a send or journey ready for
  review and it lands in one queue, with status rolled up on the campaign.
- **An agent that speaks fluent MOPs.** Ask in plain English or click it
  together yourself — same objects either way, and nothing sends until a human
  approves.
- **Drafts from your own data.** Emails, workflows, and audiences generated
  from the sources you connect, routed through Vercel's AI Gateway.
- **A Slack agent riding along.** Approvals and status checks today; a
  conversational agent is on the roadmap.
- **Plugged into your stack.** Query your warehouse for audiences and sync
  Salesforce both directions.
- **QA you define.** Link and UTM checks run before review today;
  user-configurable brand-voice and guideline checks are on the roadmap.

## The stack

veloquent runs on Vercel primitives end to end, which in practice means three
things: queries don't time out when the database gets big, there's no
maintenance window the week of your launch, and we spend our time on the
product instead of the plumbing.

| What it buys an operator | Why |
| --- | --- |
| Compute that follows demand | Your 9am send doesn't wait in line behind anyone else's. |
| Tracked jobs and queues | A failed step retries itself instead of dropping the person. |
| Scheduled runs | Recurring sends fire on time without a server we babysit. |
| Managed storage | Images and files are someone else's uptime problem. |
| One AI gateway | The right model per job, and no vendor lock-in. |
| Agents | The assistant and the Slack agent run on the same rails. |

## Follow the build

One email when something ships — no drip sequence. Sign up at https://www.veloquent.io/#updates,
or read the build notes at https://www.veloquent.io/blog.

---

- HTML version of this page: https://www.veloquent.io/
- Every page as Markdown: https://www.veloquent.io/md
- Agent guide (llms.txt): https://www.veloquent.io/llms.txt
- Sitemap: https://www.veloquent.io/sitemap.xml