David Caspillo

Data isn't the new king. It has always been king. Every AI platform is racing for the same thing: the transaction data sitting in your SAP system. Models are getting cheaper. Your business context isn't. linkedin.com/pulse/data-isnt…

One Bot, One Job How I cleaned up the AI assistants I spun up too fast, and the one rule none of them gets to break. Over the past few weeks I set up a lot of AI assistants: email, X, LinkedIn outreach, travel between my two home bases, and a few for the software side. Each one made sense the day I created it. Together, they were a mess. Today I approved a fix. It's simple, and it's something 30-plus years in business taught me long before AI showed up: every person needs one clear job. That goes for bots too. THE PROBLEM: I HIRED FAST AND NEVER WROTE JOB DESCRIPTIONS I asked one assistant to review the others and report what each was actually doing. Here's what it found: • Email was split between two bots. Both were working in my inboxes. Neither had a clear lane. • Technical work on my internal app was spread across four bots. • A meeting requirement got drafted twice. Two bots wrote it up from the same call, on the same day. • Outbound sales sat in two places. One bot owned LinkedIn outreach. Another wrote a go-to-market plan for outreach on its own. • One bot had sat idle for about a month. It got stuck waiting on a sign-in and nobody noticed. • There was a blank bot nobody had ever used. None of this was the bots' fault. I'd done what a lot of founders do with new hires: brought them on, said "help out," and walked away. THE FIX: ONE BOT, ONE JOB The new roster has 9 working bots, each with a single job: • Courier: correspondence and research. Drafts replies to real people in email and Slack, and handles one-off research and writing. • Inboxer: mailbox hygiene. Files junk, rescues real mail, watches for spoofing, and flags what needs me. It doesn't write replies. • Dex: engineering lead. Owns the code for my internal app, an AI-native task and CRM system, plus its pull requests. Also owns the daily decision packet (more on that below). • Scout: AI and tech scout. Watches for new models and tools and writes short "should we adopt this" memos. Anything worth building goes to Dex. • Minutes: meeting notes. Turns calls into summaries, action items, and draft requirements. It's now the only bot that writes requirements. • Pipeline: pipeline outbound. Account research, warm intros, and outreach drafts in my voice. • Postbo: X and personal brand. Posts, threads, and images. • Wayfinder: travel desk. Flights, trip options, and calendar holds for my back-and-forth between two home bases. • Gridiron: sports and fantasy. Personal. Weekly picks and lineup reminders. Not everything has to be work. The other bots now hand their findings to the owner instead of doing the work themselves. If Scout finds a better search tool, it writes a memo for Dex. It doesn't go off and start building. THE FLOW: RESEARCH, THEN DRAFT, THEN DECIDE Work moves in one direction. Research comes from the bots closest to the information: Scout for tools, Pipeline for accounts, Courier for one-off questions. Drafting belongs to whichever bot owns the channel. Courier drafts email and Slack. Postbo drafts X posts. Pipeline drafts LinkedIn messages. Minutes drafts meeting notes and requirements. One writer per channel means no more duplicate drafts. Deciding is my job, and it happens in one place. By 6:45 AM, every bot drops a few lines into a shared folder: what it needs me to decide, plus anything I should know. Dex merges all of it into one 7 AM decision packet. Decisions come first. Each one is written as an exact action I can approve: "Send this reply." "Post this thread." "Book this flight." Not "you might want to look at the travel situation." An end-of-day summary works the same way. THE HARD RULE Nothing leaves the box without my explicit OK for that exact action. That means no sending, posting, publishing, booking, buying, or submitting until I've approved that specific thing. A general "go ahead with outreach" doesn't count. And nothing gets deleted. This is the part I'd hold onto even if everything else changes. Bots are fast, and fast mistakes in your inbox or on your public accounts are expensive. WHAT'S STILL ROUGH I approved this today, so I'm not going to tell you it works yet. Here's where it actually stands: • The handoffs went out this afternoon. Each bot got its job description and is updating its own profile and routines to match. • The first 7 AM packet is tomorrow. That's the real test: does one merged list beat nine bots pinging me all day? • 7 AM follows me. It's 7 AM local time wherever I happen to be. When you split your life between two places, that has to be decided up front. • The idle outbound bot needs me. It's waiting on one sign-in from me before it can restart, and I still have to decide whether I want LinkedIn outreach at all. • The blank bot is still there. I haven't decided whether to retire it. • The inbox cleanup might be too noisy. It runs 6 times a day. Most runs flag nothing for me, so cutting to 3 is on the table. • No saved skills yet. Five repeatable workflows were identified. Two are drafted. None are saved. I'll report back once it's actually been running for a while. WHAT I'D TELL OTHER FOUNDERS Treat bots like hires. If you wouldn't bring on a person without a role, don't do it with a bot. Write one job description per bot. One job, the sources it owns, what it delivers, and what it needs your approval for. If you can't write it in a line, the job is too big. Decide who owns each source. One bot per inbox, repo, or social account. Shared ownership is how you get two bots in the same mailbox. Run one morning decision queue. Don't let every bot ping you all day. Make them line up, and make every item an exact action you can approve or reject. Turn repeated wins into saved skills. When a bot does something well, save the method so it isn't reinvented every time. YOUR TURN If you were hiring your first AI assistant tomorrow, what's the one job you'd give it? And what would you never let it do without asking you first? Tell me in the replies. (Header image is AI-generated.)

Underwater humanoids tired of leaving beneath Easter Island decide to show off their lighter side. Watch until the end

What's one thing in this image that shouldn't be there? The superintelligence war won't be won by the best demo. It'll be won by whoever ships working AI into factories, grids, and defense first. The U.S. can win that. Only if we stop confusing announcements with deployment. AI concept image, not a real event.

No possible way he got 2nd.

If SMX built a Legends League tomorrow, who wins it? One name. Settle it in the comments. AI concept video, not a real race. #MXLegendsLeague #Supercross #Motocross #WhoStillHasSpeed

New hit: Don’t Let the Lies divide us suno.com/s/AfsYVdgV4Cfosgv1

Did you know some energy drinks add L-theanine, the same compound that’s naturally in tea? It apparently takes a bit of the jittery edge off you get from a cup of coffee. Cool and refreshing pick-me-up you can buy in bulk at Costco.

Ok I’m going to tell the truth, this is incredible, but I think it is worth the slightly more or less to just go somewhere similar. Bali, Kaua’i, etc.

This fire 🔥 is crazy. I’m right here near it. If you have questions ask…

Well maybe a little of both. I definitely feel way more productive, but burnout is a real potential because I feel like in order to keep pace with the AI changes you have to think in a 24/7 pattern. That can cause real burnout if you are not careful. I recommend do not change your walk the dog and gym routine. The work will be there when you get back.

Lots of opportunity here to not only secure the border but to increase state by state revenue. Good thread!

I don’t see it

I did that once and the other person standing waiting to select a seat said that was the new CIO you are presenting to. 😰

Awesome