How to add AI to your SaaS (without a rebuild)

Most SaaS teams don't need an AI strategy. They need one AI feature that earns its place, shipped without breaking the product that already pays the bills. Here is the sequence I use to get there.

Start with one workflow, not "AI"

"Add AI" is not a project. Find the single workflow where AI moves a number you already track: support response time, onboarding length, time-to-first-value, hours lost to a manual task. Pick one. Teams that try to "become an AI company" in a quarter ship nothing; teams that fix one painful workflow ship in two weeks and learn what to do next.

Where AI actually fits in a SaaS

In practice the first feature is almost always one of these:

• A support or docs assistant that deflects repetitive tickets.
• A drafting step that turns a blank field into a starting point (replies, summaries, descriptions).
• A retrieval layer so users can ask questions across their own data.
• A behind-the-scenes classification or routing task no user ever sees.

None of these is "a chatbot bolted to the homepage." The best AI features disappear into a workflow users already have.

Build vs. buy, the honest version

Before building anything, check whether an existing tool does 80% of the job. If one fits, use it and spend the budget elsewhere. Build custom only when the feature touches your proprietary data or your core differentiation. I've talked clients out of builds more than once — it's the fastest way to earn trust. (More on that call in what an AI architect does.)

The 14-day path to your first feature

• Days 1–2: pick the workflow and the metric; define what "good enough to ship" means.
• Days 3–6: prototype the riskiest piece (usually retrieval quality or the prompt) behind a flag, with a small eval set so you can measure it.
• Days 7–11: wire it into the real product surface, with guardrails and a human fallback for low-confidence cases.
• Days 12–14: instrument it, ship to a slice of users, and watch the metric.

The point isn't speed for its own sake. A live feature in front of real users teaches you more in two weeks than a quarter of planning.

What not to do