Stop Bolting On AI. Start Building With It.

Stop Bolting On AI. Start Building With It.

There’s a familiar pattern in AI products:

  1. Take an existing app.
  2. Add a chatbot.
  3. Call it “AI-powered.”

This is the bolt-on mentality — AI as frosting on the same old cake.

The problem isn’t that the chatbot exists. It’s that nobody asked what the customer is actually trying to get done, and whether a chat box is the best way to help them do it.

The more useful design questions:

Sometimes the answer is to rethink the workflow. Sometimes it’s a small assisted feature in exactly the right place. Done well, AI can collapse some complexity, take routine busywork off people, and shift more of their time from “doing” to “deciding”. None of that is automatic, and the biggest redesign isn’t always the most valuable thing to build.

Compare the options for one outcome

Illustrative example, invented. You build invoicing software. The customer outcome is getting paid on time without awkward chasing.

ApproachWhat it looks likeStrengthsRisks
AssistanceA “draft reminder” button that writes a polite chaser from the invoice and the client’s history; the user edits and sends itCheap to build; the user keeps control of tone and relationshipsSaves less time; relies on the user remembering to use it
Fixed automationScheduled reminders at set points after the due date, from templates the user approves oncePredictable, easy to explain, no model involvedBlunt: it reminds a client who has already said payment is on its way
Workflow redesignThe product tracks each overdue invoice to payment, reads replies, adjusts the schedule, and escalates to the user when a client disputes or goes quietHandles the messy middle; closer to the outcome itselfMost to build and test; it messages your customer’s own clients, so a mistake lands on their relationships

For plenty of customers, the assisted button plus fixed reminders is the better product: cheaper, clearer, and nothing goes out without the user knowing what it says. The redesign earns its complexity only if the messy middle is where customers actually lose money and time, and only if you can bound what it may send.

Who owns what, if you build the redesign

Illustrative example, continuing the invented invoicing product. Before the redesigned version sends anything, settle who holds each responsibility:

An illustrative failure

Illustrative example, invented. The redesigned version reads a client’s reply saying they’re disputing one line of the invoice as a promise to pay, marks the invoice resolved, and stops chasing. Nobody notices for weeks. Or it sends a firm final notice to the user’s biggest client in the middle of a renegotiation the product knew nothing about. Either way, the message can’t be unsent, and it’s your customer’s relationship that takes the hit.

Operators running agents report the same shape of failure. Writing about his team’s go-to-market agent stack, SaaStr’s Jason Lemkin recounts an agent sending an invitation that couldn’t be recalled, from a sender address its rules had prohibited for years (SaaStr, undated). His takeaway was to size review to how far a mistake could spread, not to how small the task looks. That’s one operator’s account, not a measure of how often this happens. The lesson I take from it is narrower: a written rule isn’t the same as a boundary the system can’t cross.

When not to hand it over

In the invoicing example, keep sending with the user, or stick with assistance, when:

Before your product can send or spend

Pick one customer outcome your product serves, and sketch the assistance, fixed-automation and redesigned versions side by side. Before you give any version authority to send messages or spend money on your users’ behalf, decide what you’ll evaluate across all three:

If the small assisted feature wins on those terms, ship that. Run any version that can send or spend through the autonomy test first. And if you’re deciding what to hand over in your own operations rather than in a product, I’ve covered that side in AI is not your assistant, it’s your process.

Updated:

Related

Glenn Gillen is a product leader, early-stage investor, and writer.

Want help turning ideas like these into reality? Let's talk.