--- title: "How to Make AI Watch Your Most Important Business Numbers" date: 2026-04-13 author: Matt url: https://www.mattwarren.co/2026/04/how-to-make-ai-watch-your-most-important-business-numbers/ --- # How to Make AI Watch Your Most Important Business Numbers Most businesses don’t have a data problem. They have an attention problem. The numbers are already somewhere — Shopify, Triple Whale, Looker, a spreadsheet somebody updates on Fridays, a finance model only one person fully understands. The issue is not access. It’s whether anyone is still looking at the right number often enough to matter. That’s where AI can be useful. Not as a replacement for judgment.** Not as some magic strategy layer. Just as a way to keep one important business number visible every day, without relying on memory or good intentions. That sounds small. It isn’t. In an operating business, the difference between “we noticed it early” and “we noticed it too late” can be expensive. ## The real problem is drift Here’s what usually happens. When a company is small, the important numbers are close enough to the surface that you can feel them. Spend goes up. Sales move. Repeat orders change. Margins tighten. You can usually tell when something is off. Then the company gets more complex. More channels. More campaigns. More SKUs. More meetings. More people touching the numbers. More noise. The KPI doesn’t disappear. It just gets crowded out. That’s when drift becomes costly. CAC creeps up for a few weeks before anyone reacts. Retention softens, but revenue still looks fine. Margins compress in a way that seems temporary until it isn’t. Usually it’s not one dramatic mistake. It’s a series of ordinary misses that compound because nobody stayed close enough to the basics. That’s the opportunity here: use AI to make the important number harder to ignore. ## A concrete example: CAC-to-90-day-LTV at Psychedelic Water At Psychedelic Water, one useful workflow is a daily Slack report on one relationship: CAC to 90-day LTV** That number tells you whether growth is healthy or just getting more expensive. If CAC rises while 90-day LTV stays flat, the business is becoming less efficient.** If LTV improves while CAC stays stable, you have room to push. If both move the wrong way, you want to know immediately. So instead of relying on someone to remember to check it, we automated the update. AI pulls the relevant numbers, formats a short summary, and posts it in Slack. It follows the same logic behind [mini AI automations](https://www.mattwarren.co/2024/04/mini-ai-automations/): automate the repetitive part, then make the output easy for a human to use. Not a dashboard with ten charts. Not a memo nobody reads. Not a raw data dump. Just the metric, the comparison, and a plain-English note about what changed. That’s the point. AI isn’t “running the business” here. It’s protecting the operating rhythm around one number that matters. It is really an example of [building AI-operable systems](https://www.mattwarren.co/2026/01/claude-code-first-development-building-ai-operable-systems/) instead of relying on isolated prompts. ## Why this works better than another dashboard Dashboards are passive. They wait for someone to remember to check them. A daily AI report is active. It shows up on its own. That small difference changes behavior. A metric buried in a dashboard competes with everything else on someone’s list. A metric that lands in Slack becomes part of the daily environment. It stays visible. It stays discussable. It has a better chance of shaping decisions while there’s still time to do something about it. Most businesses don’t fail from a lack of information. They fail because the right information never becomes part of the operating cadence. The best system is usually the one people actually see, trust, and use. For one team, that might be Slack. For another, email, a text summary, a Notion page, or a morning note in a leadership channel. The channel matters less than the habit. ## Start with one KPI, not a reporting empire If you want to build something like this, don’t start by monitoring everything. Start with one KPI that genuinely matters. A good test is simple: If this number moved against you for two weeks and nobody noticed, would that create a real business problem? If the answer is yes, you’ve got a candidate. Depending on the business, that KPI might be: - CAC - 90-day LTV - Churn - Gross margin - Fill rate - Conversion rate - Inventory weeks on hand - Average order value - Contribution margin by channel The right KPI is not the one that sounds smartest in a meeting. It’s the one that changes your decisions. That’s the number worth putting in front of the team every day. ## What the report should actually include A useful daily AI report should be short enough to read in under a minute. At minimum, it should answer three questions: 1. What happened?**** Show the current number. 2. How does it compare?**** Show yesterday, last week, or the relevant baseline. 3. Why does it matter?**** Add one line of plain-English context. For example: > CAC-to-90-day-LTV today: 2.8x > 7-day average: 3.1x > Driver: higher paid social CAC while repeat purchase rate held flat > Action: watch closely if this trend continues That’s enough. The goal is not a polished memo. The goal is to reduce friction, keep the number visible, and catch drift early. ## The hidden value is discipline The obvious benefit of this kind of system is speed. The less obvious benefit is discipline. Once the report exists, the business has a daily moment of truth. Nobody has to remember to pull the numbers manually. Nobody has to stitch together an update from four tabs. Nobody gets to say, “I hadn’t looked at that in a while.” I wrote recently in [what you’re really avoiding isn’t the work](https://www.mattwarren.co/2026/02/what-youre-really-avoiding-isnt-the-work/) about how visibility lowers the friction around hard operational work. The same thing happens here. That sounds boring. It is boring. But boring is underrated. A lot of expensive business problems start small: - a metric slips a little - the slip gets rationalized - the team waits for more data - the delay becomes normal - the habit becomes a miss A daily AI report interrupts that sequence. And in an operating business, earlier is usually cheaper. ## The part people skip: the basics This is where a lot of AI projects go sideways. People get excited about prompts, agents, and automation before they’ve handled the operating basics. Those basics matter more than the tooling: - Is the KPI defined clearly? - Is there one trusted source of truth? - Does the report arrive at the same time every day? - Is it short enough that people will read it? - Is there a clear owner when the number moves the wrong way? - Is there a threshold that triggers action? If those basics are weak, AI doesn’t fix the process. It scales the mistake. A broken reporting process with AI attached can feel sophisticated while making the business slower and sloppier. The number gets delivered every day, but it’s the wrong number, the wrong definition, or the wrong interpretation. That’s worse than no automation. AI should strengthen a clear operating system, not cover up a messy one. That is also why [making the right context easy to surface](https://www.mattwarren.co/2026/01/building-a-personal-knowledge-base-how-i-created-a-semantic-search-engine-over-everything-ive-ever-made/) matters so much: retrieval only helps when the underlying source of truth is clear. ## A simple setup any operator can copy If you want to build this, keep it simple. ### 1. Choose one KPI Pick the number that matters most right now. ### 2. Define the source of truth Make sure the report pulls from one reliable place, not three competing versions of reality. ### 3. Decide the comparison window Use yesterday, a 7-day average, last week, or target. Pick the benchmark that helps people make better decisions. ### 4. Keep the output tight One metric. One comparison. One short explanation. One action note if needed. ### 5. Deliver it where the team already works Slack is great if that’s where attention lives. If not, use the place people already check. ### 6. Add an action rule If the KPI crosses a threshold, who gets pulled in? What gets reviewed? What decision gets made? That’s the system. You do not need a giant AI initiative to make this useful. You need a reliable loop around one important business number. ## The broader takeaway The best AI workflows in an operating business are usually not the flashy ones. They are the ones that quietly keep the company close to reality. They make it harder to miss the obvious. They reduce the lag between signal and response. They protect attention around the basics. And the basics matter more than people want to admit. Most businesses don’t lose because they lacked advanced tools. They lose because they stopped watching the number that would have told them something important was changing. So the useful question is not: How can AI help with everything?** It’s this: **What is the one number this business cannot afford to stop watching?** Start there. Then use AI to make forgetting it much harder. ## Reader exercise Take 10 minutes and write down: - the one KPI that matters most in your business right now - where that number currently lives - how often it is actually checked - who needs to see it - what should happen if it moves the wrong way Then answer one final question: **What is the simplest daily AI report that would make this number hard to ignore?** If you can answer that clearly, you’re probably closer to a useful AI workflow than you think.