APRIL 2026  ·  6 MIN READ

I Almost Lost $350K Because I Forgot to Text a Guy Back

You know what nobody tells you about building an AI system that runs your business? The AI doesn't care about your pipeline.

I've spent months building Dolphin — an AI operations platform that manages my schedule, tracks commitments, runs analytics, deploys tools, writes its own journal entries. Before going independent, I spent five years building data and analytics products at enterprise scale. Dolphin is what happens when you take that experience and point it inward. It monitors 75 tools across three machines. It has a daily heartbeat. It has a context capsule that tells it everything it needs to know about my world every time it wakes up.

And none of that mattered when a prospect went quiet after a great discovery call, because I had no system for "text him back on Wednesday."

---

Think about that for a second. Seventy-five tools. Three planes of infrastructure. A knowledge graph with 300+ megabytes of structured data. And the thing that nearly killed my first real deal was a follow-up reminder.

The CRM already tracked staleness. It knew the contact hadn't been touched in 14 days. But staleness is passive — it's a yellowing row in a dashboard nobody's looking at. What I needed was active. Aggressive. Something that grabs you by the collar at 8 AM and says: this person is waiting for you to do a specific thing today.

Mental reminders don't work. I tried. They get overwritten by whatever's on fire at 9:15. One-off cron hacks don't work either — I had a couple, and they didn't connect to anything. An SMS in a vacuum is just noise. The reminder needs to be wired into every surface you actually look at during the day, or it's decoration.

So I built it.

---

What the CRM Reminder System Actually Does

Two hours. Here's what exists now:

A remind subcommand on my existing CRM CLI. You give it a contact name, a date (or "wednesday" or "+3d"), and a specific message — not "follow up" but what you're actually going to do. It creates an append-only event in a JSONL file. That's the entire data layer. No database. No migration. No ORM. One file, one line per event.

At 8 AM every morning, a cron job reads that file, figures out which reminders are due, and sends an SMS to whoever owns the reminder. Stuart's reminders go to Stuart's phone. Jason's go to Jason's. If you ignore it for three days, it starts nagging you. The nag says OVERDUE in caps. It's annoying on purpose.

But the SMS is the least interesting part.

The same data feeds into the daily schedule that Dolphin generates every morning. When I sit down and ask "what's today look like," CRM reminders show up in the work items — after overdue commitments, before regular tasks. Right where they belong: urgent but not emergency.

And the context capsule — that dense payload of state that Dolphin reads at session start — now has a CRM REMINDERS section. Today's reminders, next seven days upcoming, anything overdue. Color-coded. So when I'm in a session and Dolphin is helping me think through my day, it already knows that a prospect needs a response and can factor that into whatever plan we're building.

Four integration points. One JSONL file. Shell scripts and jq.

---

You could build this in Salesforce. It would take you three weeks and a consultant. (I know. I am the consultant.) You'd get a reminder system that lives in Salesforce, sends notifications through Salesforce, and exists nowhere else in your workflow. An island.

The thing that makes this work isn't the reminder. It's the wiring.

When a reminder fires, it touches your phone, your schedule, and your AI agent's context. Three surfaces, one event. The AI doesn't just know about the reminder — it knows what it's for, who owns it, how overdue it is, and what the contact's full history looks like in the CRM. The reminder isn't a Post-it stuck on a monitor. It's a thread pulled through the entire system.

And when you complete the reminder? One command. It marks it done in the JSONL, and optionally logs a CRM touch — so the contact's timeline updates automatically. The loop closes itself.

---

There's a move in consulting where you build your own tools, use them to run your own business, and then sell the methodology to clients. Everyone talks about it. Almost nobody does it because the tools you'd build for yourself are ugly, specific, and small — they don't look like products.

That's the wrong frame. Clients don't need products. They need results. And the proof that your approach works is that you're running on it.

I'm pitching a prospect on AI operations automation for a mid-size company. My pitch is: I'll build you systems that make sure nothing falls through the cracks, that connect your tools together so information flows instead of sitting in silos, and that put the right data in front of the right person at the right time.

The CRM reminder system is exactly that pitch, built for a team of two, in two hours, out of shell scripts. For a company that size, the same architecture scales — the data layer gets a proper database, the notification layer adds Slack and email, the AI context plugs into whatever tools the team already uses. Same principle: one event, every surface.

When a prospect asks "can you show me what this looks like in practice," I don't open a slide deck. I show them the text I got at 8 AM reminding me to follow up.

---

Here's what I didn't build:

Recurring reminders. (I have a separate tool for recurring check-ins.)
Email notifications. (I read texts, not system emails.)
Calendar sync. (My schedule tool is the calendar.)
An LLM to parse the reminders. (Shell script + jq. AI is not the answer to "tell me to do X on date Y.")

Every feature I left out is a feature someone at a SaaS company is building right now and calling innovation. The discipline isn't in what you add.

---

The first reminder that fires will be Wednesday. "Send specific meeting dates if no reply to Friday email."

I'll get the text at 8 AM. It'll show up in my schedule. Dolphin will know about it. And when I sit down to work, the system will have already decided that this follow-up is the first thing I do today.

That's the whole point. Not the reminder. The decision being made before I'm awake enough to forget it.

---

I help 100-500 person companies build operations systems that make sure nothing falls through the cracks. If your follow-up process runs on someone's memory, start here.