Jacob SagerShow me your business
Business systems and AI · A guide for owners

Where should your business start with AI?

I’d start with a recurring task you can follow from request to finished result. Preparing a quote is one example. Look at the information someone needs, the decisions they make and what would count as an improvement. That gives us a question worth asking about AI.

Choose work you can examine.

“We should use more AI” does not give you much to work with. “Every proposal requires me to reconstruct the customer history” does. You can find a recent proposal, see where the information came from and count how often the same preparation occurs.

The first workflow should matter to the business and be small enough to inspect. Follow a real example through the awkward parts. Include the email somebody forwards, the spreadsheet nobody updates and the point where a colleague needs your memory to continue.

For a one-person company, follow your own working day. Work can move between roles even when the same person performs all of them.

Look for the AI Gap.

I use AI Gap to mean the difference between a process today and an improvement that software and AI might now make worthwhile. Reading an unusual request and finding relevant earlier work are examples of preparation AI may help with.

Some of that work can now change. The valuable part is identifying where, in your company, the new capability is reliable enough and economically worthwhile. The company still needs trustworthy records, clear responsibility and a way to handle exceptions.

A useful starting question is: what preparation has to happen before a capable person can exercise judgment?

Find the context the work depends on.

An AI-generated draft is only as useful as the information it can use and the review it receives. For the process you chose, identify which records people should trust, the history they need and the rules they use. Note which details only someone’s memory can supply.

  • What starts the work?
  • What information is needed to finish it?
  • Where does that information live, and can it be trusted?
  • What does a person have to interpret or decide?
  • How does the business know the outcome actually happened?

These questions are part of what I call the Business Nervous System: the records, instructions and software that help people notice a request, share details, prepare a decision and check what happened. A missing record or unclear approval rule may need attention before AI can help.

An example: preparing a proposal.

Illustrative example, not a client result. A customer asks for work that resembles an earlier project. Today, the owner reads the request, finds the history, checks what was promised and prepares the scope.

A possible redesign assembles the relevant records and flags missing details before drafting a proposal. The owner reviews the scope, price and commitments. The system records the approved decision and makes the next action visible.

The experiment needs to measure the total preparation and review time, the quality of the result and any rework. A draft that appears quickly but takes longer to correct has not established a useful improvement.

Measure what happens before changing it.

Collect a representative sample of the current work. Include straightforward cases and exceptions. Record active work time separately from waiting, the number of handoffs, errors or rework, and what prevents completion.

Choose the main result you want to test, such as less preparation time or fewer missed details. Define acceptable quality. We use those measurements of the current process—the baseline—to judge a build in actual use.

Time released is potential capacity. It becomes a business benefit when you use it for something valuable or avoid a real cost. Record that distinction when estimating the opportunity.

Make one decision about what comes next.

If the opportunity is credible, agree on a bounded first implementation and the evidence needed to continue. If the records are unreliable or the review burden is too high, fix the underlying constraint or choose another workflow.

The Read is my $2,500 assessment of an agreed business question. It includes a 90-minute session and a written report within two business days afterward, with one recommended first change. A build or ongoing work has a separate scope and fee.

I call this Company-Level AI when the AI is connected to the company’s records and everyday processes. We can start with one change and see whether it holds up in use.

Talk about your business

Tell me about your business.

Tell me about a task or business question you’d like help with. If a detailed assessment is useful, the $2,500 Read includes a 90-minute session and a written recommendation within two business days afterward.

Show me your business

For established businesses doing $500k+ a year, including one-person companies. Building and ongoing work are scoped separately.