Created from a single voice note with Agent Craft

My laptop was open at around 11pm on a Tuesday. Mark had just sent me…

My laptop was open at around 11pm on a Tuesday. Mark had just sent me a message saying he'd found something that could solve the one architectural problem we'd been circling for weeks. We needed Agent Craft to live inside Slack. Not link to Slack. Not send notifications to Slack. Actually live there, the way a colleague does. The kind of presence where an exec opens their Slack in the morning and gets a message from Craft the same way they'd get one from a team member. Natural. No friction. Nothing that feels bolted on. That's harder than it sounds. Mark had been digging through our existing setup with Vercel, the host that handles all our deployments and pipelines, and he found it. Vercel has a chatbot SDK that essentially handles the transportation layer between a product and platforms like Slack and Teams. We already had the relationship with Vercel. It was sitting right there. We had been so deep in researching the architectural options for the integration that we nearly missed what was already in our stack. That's the kind of thing that can cost a team weeks. Luckily, we caught it. Once we had that in place, combined with LangGraph on the backend giving Craft the ability to make its own queries and retrieve data, the whole thing stopped feeling like a workaround. It felt native. Not janky. The kind of interaction where a busy exec doesn't have to think about the tool, they just use it. And that matters so vitally, because the whole premise of Agent Craft is that marketing runs where your day already runs. You're in Slack. You're in Teams. You're already in Google Chat. The last thing anyone needs is another tab, another login, another platform demanding your attention in a separate window while everything else you actually need to deal with is somewhere else. So the product had to meet people where they are. Here's what happens in the first ten minutes after you connect. Craft introduces itself, tells you what it can do, and then lays out your daily content planner. You record a voice note. Craft processes it, generates content, and ships it to whichever of your connected destinations is scheduled. Then you get the notification that your post went live. You can review it, schedule it, edit it, add media to it. That notification is the magic moment. That's the first time the whole thing becomes real. It's not a demo. It's not a preview. It's your content, live, generated from a voice note you recorded in Slack while you were already doing your morning check-in. The ten minutes thing catches people off guard. I get it. There's a reasonable assumption that anything this connected to your workflow must require a long implementation window, a bunch of IT sign-off, and a migration of some kind. It doesn't. The onboarding loop, from role intake to first campaign generation to published content notification, closes in under ten minutes. We were deliberate about that. The blank page problem and the time constraint problem are two of the real reasons most founders and senior leaders stay invisible online even when they know they shouldn't. Solving the tool wasn't enough if the tool itself added a new obligation to the calendar. I've been in corporate environments long enough to know that anything requiring a separate context switch tends to get deprioritized. Slowly at first, then completely. The only way this works is if the friction goes to near zero and the habit forms around something people are already doing. That's what we built. Most of what's shipped now is just the beginning. The Slack integration, the voice note to published post loop, the LangGraph-powered queries that let you ask Craft for analytics or a new prompt mid-conversation, the built-in support trigger if anything goes wrong. That's the foundation. What I keep thinking about is this: there are leaders out there whose day already runs in one of these platforms, whose marketing is either nonexistent or inconsistent or expensive, and who haven't connected the two things yet. How long before that gap becomes the one their competitors close first?