A marketing automation platform, built by the people who run them.

veloquent is a marketing automation platform — the system a marketing team uses to build audiences, send email, run multi-step journeys, and keep all of it in sync with a CRM. It is organized around three ideas the incumbents treat as add-ons: every asset belongs to a campaign, every send passes a human review gate, and an agent can do the assembly work an operator shouldn't have to.

The platform pages go deep on each piece. The manifesto is the argument for why it should exist at all.

veloquent is the work of Joe Reitz and a small team of marketing operations practitioners — people who have stood up a lead lifecycle, debugged a broken sync, and explained to a CMO why attribution numbers are directional. The QA sequence built into the review gate is the one Joe ran by hand in marketing operations roles at companies including AWS and Vercel: the same checks, in the same order, now running automatically before anything reaches a reviewer.

veloquent is under construction, and says so on every page. There is no public sign-up, no free trial, and no published pricing. The product screenshots on this site are captures of real, running software rather than mockups, and the build log on the homepage tracks what has shipped, what is in progress, and what is next.

When a capability is on the roadmap rather than in the product, we label it as a roadmap item — on these pages, in the build log, and in the machine-readable version of the site that AI agents read. Being early is the whole proposition here; being vague about how early would waste your time.

The platform runs end to end on Vercel primitives: Fluid Compute for scale-to-demand compute, durable Workflows and Queues for sends and journey steps, Crons for scheduled work, Blob for media, and AI Gateway for model routing. That is a deliberate choice, not a résumé line — it is why a journey step can retry itself instead of dropping someone mid-nurture, and why the team spends its time on marketing operations problems instead of on plumbing.

The intake form is the way in. It is read by the people building the product, and submissions that describe a real, recurring problem end up on the roadmap and in the public build log. The same page has a low-volume email list — one message when something ships. What this site collects and why is written out in the privacy notice.