Verb
Back to blog
Building2 min read

An AI strategy for a SaaS that has no AI yet

One job, shipped small inside the product, measured, then the next decision.

Quick answer

Start from your users, not from the technology. List the tasks they ask for help with or abandon, pick the one that costs them or you the most, and ship one AI capability for that job within weeks, inside the product they already use. Measure whether it saves time or lifts use, then decide the next step from those numbers. Hiring an AI team or rebuilding comes later, if at all.

Most AI strategy decks for an existing SaaS start with the technology: which model, which vendor, which team to hire. The ones that ship start with a list of what users struggle with, and pick one item from it.

Step 1: list where users get stuck

Pull the last three months of support email, chat transcripts and sales call notes. Write down every task users asked how to do, asked you to do for them, or abandoned. Group them. You now have a ranked list of jobs, in your users' own words.

Step 2: pick one job

Choose by two things:

  • Cost: how much time it takes users, or your support team, each week.
  • Fit: whether it is a task with clear steps your product can already do through its own features, so AI can do it rather than just talk about it.

Step 3: ship it small, inside the product

Put the capability where the work happens, not in a separate AI section. For a one-screen task, that is an AI feature on that screen. For a multi-step task, it is an assistant that does the steps as the signed-in user, asking before anything changes data. Either can ship in weeks without rebuilding anything. How to add AI to an app you already have covers the build.

Step 4: measure, then decide what is next

Track how often it is used, how often it completes the task, and the time it saves. After a month you know whether to widen it, pick the next job from your list, or change course. Measuring a 30-day pilot lists what to track.

What to leave for later

Hiring an AI team, training your own models and rebuilding around AI make sense once AI is the product itself, or once real usage shows what is worth owning. Deciding them first is how AI strategies stall.

The verdict

An AI strategy for a SaaS with no AI is a list of user problems, one chosen job, a small capability shipped inside the product, and a measurement after a month. Repeat. The strategy becomes clear from what users actually use.

Frequently asked questions

Does every SaaS need an AI strategy?

Every SaaS needs an answer to what its users will expect, because other software they use now does things for them when asked. The strategy can be small: one useful AI capability for the job your users find hardest, rather than a plan to put AI everywhere.

Where should a SaaS start with AI?

With the task users most often ask how to do, or give up on. Support email, chat and sales calls list them. An assistant that does that task inside the product, as the signed-in user, is usually more valuable than a chatbot that explains it.

Do I need to hire AI engineers first?

Not to start. One AI feature is a model call from your backend, and an in-app agent can be embedded rather than built. An AI team makes sense once AI is the product itself, or once you know from real usage what is worth building yourself.

Vishnu

Vishnu, founder of AskVerb @itsvishnups

Building the AI agent that lives inside a SaaS product and does the work its users ask for. Writing down what I learn along the way, including the parts I got wrong first.

More articles

Give your SaaS its own AI agent

It calls your own API as the signed-in user, confirms before it changes anything, and logs every action. Start with a free 30-day pilot, then we price it on what it actually does for your users.