SoloCMO.ai

How to know
when you actually
need a build.

I would rather tell you “not yet” than sell you a build you will regret. A short framework for working it out yourself.

Reading time · 5 minutes Honesty level · may talk you out of hiring me

A personal AI can save a small business a lot of time. It can also be a very expensive distraction at the wrong moment in a business's life. The difference is usually obvious once you know what to look at.

Here is how I think about it. If you run through the two lists below and you still are not sure, the third section tells you what to do.

Chapter 01

You probably do not need one yet if…

  • You have fewer than five paying customers a month. More customers first. Tooling later.
  • You switched to new software in the last month. Give the new software a fair run before layering anything on top.
  • You have never done the task you want to automate more than about ten times. The pattern is not clear enough yet to automate well.
  • The task you want to automate takes less than thirty minutes a week. Even a cheap build costs more than you would save.
  • You have not described the problem out loud to at least two people. Often somebody has already solved it in a way you have not seen.
  • You are mid-rebrand, mid-move, mid-hire, mid-divorce. Wait for the current storm to pass. Helpers built under stress fit the stressed version of the business, not the calm one.
Chapter 02

You probably do need one if…

  1. You do the same specific task more than five times a week, and it takes real attention each time.
  2. You have tried two off-the-shelf tools for the job and neither fits the way your business actually runs.
  3. Your workflow depends on your specific rules. Compliance, pricing logic, client preferences, the way your senior person thinks. A generic tool cannot know those.
  4. You are losing work at a specific bottleneck. Slow quotes, slow replies, slow paperwork.
  5. A staff member has asked “why is this still manual?” more than once.
  6. You can picture, specifically, what the perfect helper would do. Not generally. Specifically.
Chapter 03

If you are not sure.

Two things. Do one or both.

Track the task for a week. A pen and paper is fine. Write down every time you do the thing. How long it took. Whether you were interrupted. By the end of the week you will know two things: how much time you would actually get back, and whether the task is worth automating at all.

Send two or three builders a brief. The one you can paste into an email is here. The replies will tell you more than the builders themselves intended. Vague proposals mean vague work. Specific proposals mean somebody has actually thought about your business. If every proposal comes back vague, the work is probably not yet clear enough to build.

Last thing.

If you run through this and decide now is not the time, good. You have saved yourself money and the wrong version of a helper. If you run through this and decide now is the time, you already know more about what you want than most people do when they email a builder. That makes the next step easier.

Back to the guide · hello@solocmo.ai