HN/← All posts
AI BASICS / 18 Sept 2026 / 4 min read

"Add AI" explained: where it saves real hours and where it's a gimmick

A developer's plain-English guide for founders: what AI is genuinely good at, where simple rules beat it, and a quick test for whether your task is a fit.

Every founder I talk to has been told to "add AI" to their business. Investors say it, competitors announce it, and your LinkedIn feed is full of it. Almost nobody explains what it means in practice.

Here is my plain-English version, from someone who builds this stuff. AI is a very fast, very well-read assistant that is sometimes wrong. If you use it for what it is good at, it saves you hours every week. If you use it for the wrong job, it creates more work than it removes.

What AI is genuinely good at

Modern language models are strongest when the work involves words. That covers a lot of a typical business day:

  • Reading and sorting. Triage support emails, tag leads, route enquiries to the right person.
  • Pulling out facts. Take an invoice, contract or enquiry and extract the dates, amounts and names into a clean table.
  • Summarizing. Turn a 40-minute call transcript or a long document into five bullet points.
  • First drafts. Reply drafts, product descriptions, proposals, which a person then edits.
  • Answering from your own material. A search box over your handbook, your policies, or your past projects.

Notice what these have in common: the input is messy text, there are many repetitions, and a person can glance at the result and fix it in seconds.

Where it's a gimmick

AI gets in the way when you need something to be exactly right every time, or when a plain rule would do the job.

  • Exact calculations. Tax, payroll, inventory counts. Use a normal program, or a spreadsheet formula. They don't make things up.
  • Simple if-this-then-that logic. "If the order is over 5,000, ask for approval" is a rule. Writing a rule is cheaper, faster and more reliable than asking a model.
  • High-stakes decisions with nobody checking. Loan approvals, medical advice, legal commitments. A wrong answer here is expensive.
  • A chatbot nobody asked for. If your customers email you five questions a month, you don't need a bot. You need a good FAQ page.

Is your task a good fit?

Here's a quick test I run with clients before building anything. Think of one specific task you want to hand to AI, and answer honestly.

InteractiveIs this task a good fit for AI?
Probably not an AI job

A plain rule, a better form, or a person with a checklist will likely be cheaper and more reliable here.

How the best setups actually work

The best AI systems I've built aren't magic. They are boring and layered:

  1. A rule handles the clear cases (spam gets deleted, VIP customers get flagged).
  2. AI handles the messy middle (what is this email actually about? how urgent is it?).
  3. A person reviews anything uncertain, or anything that can't be undone.

Each layer is cheaper and more reliable than the one above it, so you only pay for AI where it earns its keep. The AI also shows its work, for example the exact sentence it based its answer on, so that checking takes seconds.

What to ask before you spend money

  • What exact task does this replace, and how many hours does it take today? If nobody can answer, it isn't ready to automate.
  • What happens when it's wrong? Good answers involve a review step, not "it won't be".
  • What does each run cost? AI is billed per use. Cheap for a hundred tasks a day, worth watching at a hundred thousand.
  • Where does my data go? Customer details should not casually leave your control. Ask which provider is used and what they keep.

Start with one small, boring task. Get it working, measure the hours saved, and only then move to the next. The founders who benefit most from AI are rarely the ones with the grandest plan. They're the ones who picked a Tuesday-morning chore and quietly deleted it.

WORK WITH ME

Want this working in your business?

Tell me what's eating your time. I'll reply with an honest view of what's worth building.

Email me ↗