Bachelor Week 2026

Haleigh is currently visiting her family in Iowa. Which means I'm unsupervised at home all week.

This is an annual occurrence, usually towards the end of the summer before Haleigh has to go back to work (school). Every year, it's the same flow:

• Wow this is awesome - NO RULES
• ... This sure is boring
• Ugh, I feel like crap (spoiler: it's because I ate like a teenager while being a man in my early 40s)
• I can't wait for Haleigh to get back

Hilariously, that entire arc usually takes ~48 hours to fully transpire. Every year, I do the same thing, every year I get bored and feel like shit.

I want to tell you this year is different, and it is insofar as I don't feel like shit. Even that is only because I put half a pizza into the freezer before force-feeding myself pizza for the 3rd meal in a row.

I've actually been spending most of my free time split between playing Halo: Campaign Evolved (banger) and vibecoding a marketing automation platform.

veloquent - the Agentic MAP

I have a lot of work left to do, but in just a couple nights I've made significant headway. I have a campaign engine, email templates, and an agentic flow that can be accessed via the UI or via a companion slack agent.

The idea behind veloquent is that most MAPs today either do everything but don't scale well, work great but have steep learning curves and were clearly built by engineers who have never done ops work, or has core email sending functionality but otherwise fairly feature limited. As someone with access to claude code and an employer who encourages us to ship in public, I thought to myself this cannot stand.

I settled on veloquent for three reasons.

1. It's built entirely on Vercel Primitives – AI Gateway, Workflows, the eve agent framework, and more... Hell, even the design is on Vercel's Geist system. So a v-name was a cool nod.

2. velo = velocity. It's designed to be fast and scale well across millions of records.

3. eloquence. While I intend to build this in a way that you CAN use just the UI like a traditional MAP, the core user experience is also either using natural language with the assistant OR by interacting with a Slack agent.

The entire idea is to massively accelerate how companies ship marketing campaigns, and also democratizing who can do it. You don't need to be a platform admin or even a marketer. Anyone with an idea can describe it to veloquent, and it'll take a pass at creating it for you.

I'm only 2 nights of development into this, but it's shaping up well. I'm going to continue iterating on it and build more robust tools, then maybe try to dogfood it internally. We just migrated to Customer.io, so I have no intention of replacing that (lol the hubris of replacing a MAP with a vibecoded app). But I can't help but think how valuable a working prototype will be for driving change in the marketing automation space. I'm bullish on one point: with AI development tools, there's no good reason to have long development cycles and roadmaps that feel like they won't mature until 2064. Iterate, find the rough edges, and iterate some more.

We'll see how this goes. If it gets more mature, I'll probably make a dedicated post about it.

Now if you'll excuse me, I think I smell a pizza...