That is the reaction I hope this article earns. You shouldn’t have to master a stack of new terms before you can improve one annoying task.

Picture this:

It’s Friday afternoon. You owe a client an update before the weekend.

You check your notes, search for the latest decision, look at what is still open, and try to explain it clearly. Half an hour disappears before you send a few paragraphs.

You’ve heard about agents, automations, integrations, and workflows. But you don’t need to begin with any of them. You need to get this update out the door, with less effort and without making anything up.

So let’s follow this one job and see what it actually needs.

Subscribe now

TL;DR

Start with one recurring task. Test a prompt. Save the instructions if you keep repeating them. Connect information if finding it becomes the bottleneck. Add a reminder, automation, or agent only when it solves a specific remaining problem.

Measure the whole job, including review and corrections. Stop when the result is useful enough.

What you’ll learn

• How to choose a good first task for AI

• A prompt structure you can adapt to your own work

• When to save instructions or connect information

• The difference between a scheduled workflow and an agent

• A simple way to test quality, time saved, and risk

A real result, and what it does not prove

In a 2021 engagement, Devon, a solo consultant, was spending about 15 hours a week managing communications across email, Slack, her calendar, and CRM. The process changes included email batching, response templates, CRM routines, calendar blocks, follow-up routines, and weekly prioritization. Her communication workload fell to about 11 hours a week, a reduction of roughly four hours.

That was a real result from process changes. It was not an AI result. Devon still had to maintain the routines and run the system herself. I’m including it because a useful improvement starts with a specific burden and a way to see whether it changed. The Friday client update that follows is an illustrative example, not a claim that AI will save a particular amount of time. Read the full Devon case.

Friday, 3:12 p.m.: Start with the notes

You open an AI tool and paste in this week’s notes. If they include client information, use an account and tool approved for that work.

Then you ask:

Prepare a short client update using only the notes below.

Organize it into:

• Completed

• Still open

• Decisions needed from the client

• Next steps

Do not invent missing facts, dates, or commitments. If information is unclear or conflicting, list it under “Needs my review.” Draft only. Do not send.

Notes: [paste notes]

The draft is a useful first pass. You check it, correct one date, remove a sentence that sounds too definite, and send it.

The example is hypothetical, so we won’t assume it saves time. In your own work, time the full task, including review and corrections. The result may be faster, clearer, both, or neither. That is what the test is for.

You haven’t built a system. You’ve tested one change.

Prompt: Do this task with this material.

If the result is good enough, stop here.

The next Friday: You repeat yourself

The prompt helped, but you find yourself adding the same directions again:

“Keep it short.”

“Flag unresolved commitments.”

“Separate what happened from what you recommend.”

“Don’t promise a date unless I confirmed it.”

The task itself is still simple. The repeated instructions are the new annoyance.

So save the parts that should stay the same: the structure, tone, rules, and what to do when information is missing. In some tools, reusable instructions may be called a skill. In others, you might use a saved prompt or template. The name varies. The point is to stop rebuilding the same guidance from scratch.

Keep the changing material separate. This week’s notes belong in the input. Your lasting rules belong in the reusable instructions.

Reusable instructions: This is how we do this task.

You now have a more consistent starting point. If gathering the notes is still fine, you can stop here.

A few Fridays later: Finding the information takes longer than writing

The draft is easier now. But you still spend time collecting the ingredients.

The meeting notes are in one place. A decision is buried in email. The last update is in a project folder. Open items are in your CRM.

The bottleneck has moved. You don’t need more help writing. You need less searching and copying.

This is when connecting a source may help. Depending on the tool, you may see terms such as app, connector, or integration. These connections can let an AI tool retrieve information from approved systems. They do not automatically guarantee that it has found the right record or interpreted it correctly.

Start with the one source that causes the most repeated hunting. Give access only to what the task needs. Ask the system to show the source for important details and flag anything it cannot verify. Test it with a normal week, a week with a missing note, and a week with conflicting information.

If the source is hard to search, the connection is unreliable, or the review takes longer than the search did, it has not solved the problem yet.

Information access: Give the task the sources it needs.

Share

One Friday, you nearly forget

The update is working. The instructions are saved. The relevant information is accessible.

Then Friday gets busy. At 4:40, you remember the update you meant to prepare at 3.

First ask whether a calendar reminder would solve this. If the work is simply easy to forget, a reminder may be all you need.

If the system should start gathering information and preparing a draft, you may need a scheduled workflow or an agent. These are related ideas, but they are not interchangeable. A conventional automation follows steps you define. An agent uses a model to interpret context and choose among bounded steps or tools.

For this client update, a scheduled process might:

• Start every Friday at 3 p.m.

• Gather information from approved sources

• Compare it with the previous update

• List completed work and unresolved commitments

• Flag missing or conflicting details

• Prepare a draft for your review

Set a clear boundary: it prepares the update, but does not send it. You check the facts, decide what the client should hear, and approve the message.

An agent is worth considering when the job repeats, has a clear expected output, uses connected systems, and needs some interpretation along the way. If the steps are completely fixed, a regular automation may be simpler. If the job depends on judgment you cannot describe or check, keep that judgment with a person.

OpenAI’s guide to workspace agents describes an agent in terms of a trigger, a process, and tools or systems it can use. It also recommends testing realistic cases and setting human checkpoints. The product names differ across platforms, but those are useful design questions wherever you build.

Triggered work: Start the task at the right time, with a clear stopping point.

The four questions to ask

The Friday update has changed, but you have not climbed a required ladder. You have solved one problem, noticed the next, and added a capability only when it earned its place.

Use these questions to decide what your own job needs:

The fourth answer may be a calendar reminder, a standard automation, or an agent. Choose based on the work, not the label.

Subscribe now

A small test before you trust it

Before using AI on an important recurring task, write down four things:

1. The job
What starts the task, and what finished result do you need?

2. The baseline
How long does the task take now? What errors, delays, or rework happen?

3. The review rule
What must a person check? What should the AI flag instead of guessing?

4. The test
Try a routine example, an example with missing information, and one with conflicting information. Compare the result with your normal standard.

After a few runs, compare total time and quality with your baseline. Count the review time. If you saved 15 minutes of drafting but spent 20 minutes fixing the output, you did not save time. If the update became clearer and errors fell, that may still be a worthwhile improvement.

Keep the first version narrow. Let it prepare a draft before you consider allowing it to update a record or send a message. Add permissions only when you have evidence that the next action is reliable and appropriate.

Start with one annoying job

Look at your week. Find a task that repeats, follows recognizable rules, uses information you can access, and produces an output you can check. Good first candidates are often small and boring: summarizing meeting notes, drafting a follow-up, preparing a status update, or comparing a few supplier quotes.

Try the smallest change. Keep it if it helps. When another part of the work becomes the bottleneck, decide whether a new capability would remove that friction.

That is how a prompt can become a machine: not through a grand design, but through useful improvements to work you already understand.

Prompt → Reusable instructions → Information access → Triggered work

Each step should make the job easier, more reliable, or easier to start. Stop as soon as you have what you need.

Further reading

• Workspace agents: triggers, processes, tools, testing, and human checkpoints

• Connected apps in ChatGPT: how apps connect to services and information

Grab a coffee. This one is a look back at what we built together in September, and a few things I have been thinking about since.

September was a quieter month for publishing than August, but some of my favorite work came out of it. One piece was my first experiment with voice agents. Using the xAI voice beta, I built a voice bot called Sage. Sage interviews you about your business and helps you find what is slowing it down. Then it sends you an organized summary you can use to design a tech stack that saves you time and money. You'll find it below.

Something else happened this month that I care about a lot. I submitted a proposal for a business accelerator for 18 to 24 year olds who want to join the workforce or start their own business. If it is approved, the 12-week program begins in March. Each participant will take a real business process, improve it, and apply AI to it. Along the way, they will learn to spot opportunities in the market and become fluent in AI, beyond simply being familiar with it.

I have been here before. In 2021, I designed an accelerator for solopreneurs hit hard by the COVID lockdowns. I learned from more than 100 businesses, and their stories taught me something I keep coming back to: when desperation and inspiration arrive at the same time, people discover capacities they never knew they had.

I see that same moment forming now. This time the lockdown is quieter. AI is repricing the work many of us spent decades mastering.

That thread runs through everything I wrote in September. Building has become the easy part. What makes the build worth anything is knowing what the work is, what it costs you, and which decisions stay with you.

Something I put together for a few of you

Until October 15, I am offering my paid subscription at half the price, $58.50 for a full year of premium content, AI skills and agentic hacks, plus adding a one-on-one session with me (which I only did this with the $360 plus founder subscription). We can use this time to set up my content engine for you, or to work through a project you are stuck or have been putting off. Think of it as a virtual coffee where you leave with something built. The subscription also includes more than 200 prompts and my content engine plug-in to get your content on auto-pilot.

I can only give this kind of time at this price to a small group, so I am capping this offer at 20 people. If those spots fill before October 15, I will close it early. If interested click below. You will get a link to setup our session.

Claim your spot here

Now, here are September's four pieces.

1. Sage: The Voice Agent That Helps You Find What Is Causing Your Operational Drag

September 10

Most owners already sense where the drag is. What they are missing is a way to finish the thought, so I wrote the method down and built a voice agent to walk you through it.

What you'll learn:

• How to pick one room of your business and one recurring task, using a real recent example.

• How to map who and what that task depends on, where it breaks, how often, and how many hours it costs.

• How to mark every step as a chore or a judgment call. Pricing, fit, saying yes, and hitting send stay with you.

• How to test one fix on five live items. You leave with a written picture you can hand to your team or a consultant, or use as the spec if you build the fix yourself.

2. Your Business Already Has a Product Manager. It May Be You.

September 15

AI now lets nontechnical owners build their own systems. The part you cannot hand off is deciding what to build and why, and most owners are already doing that job without the title.

What you'll learn:

• Why my newsletter agent had the research ready and then stopped, waiting for me to choose the topic.

• The four decisions to keep: the outcome that matters, the real constraint, where preparation ends and judgment starts, and what "better" means.

• The question I now ask of every system: what could the machine prepare before you arrive, and which decision should stay yours?

3. AI Made Building Easy. It Did Not Make Choosing Easy.

September 17

Turning an idea into something that works has become much cheaper. Deciding which idea deserves the work has not, which makes it easy to spend a week building something that does not matter.

What you'll learn: Five questions to ask before you build:

1. Who has the problem?

2. What happens today?

3. What does it cost?

4. What judgment must stay human?

5. What is the smallest version that could teach you something?

Then you test that version on one real invoice, one proposal, or one client meeting.

4. Your Business Should Prepare the Work Before You Arrive

September 22

Many owners are overwhelmed less by the number of decisions than by the state they arrive in. Each one shows up half-built, so they do the gathering before they can do the thinking.

What you'll learn:

• The founder-wait test and the decision-ready brief.

• How to pick one recurring decision that keeps landing on your desk unfinished, and describe what a decision-ready package would contain. That description becomes the start of a spec for a system.

• A simple scoreboard to measure it: preparation time, turnaround, corrections, and conversion.

The system gathers and prepares. You still decide fit, price, promises, and risk.

In 2021, I watched more than 100 owners rebuild their businesses with nothing but pressure and a willingness to try. Many of them did not have a plan. They had one process they were willing to fix, and the courage to fix it before they felt ready.

Every piece this month comes back to that same idea. The machines can now do the gathering, the drafting, and the building. What they cannot do is decide what matters to you, what you will charge for it, and which promises you are willing to keep. That part is still yours, and it is worth more today than it was a year ago.

So here is my invitation. Pick one thing this week. One task that drags, one decision that keeps arriving unfinished, one idea you have been circling. Run it through one of the pieces above and see what you learn.

If you want company while you do it you can take my 50% off paid subscription offer. You will get more than 20 prompts, my content engine plug-in and a we will have a session together to work on the project of your choice. You can claim your spot here.

Talk soon,

Juan

Share

The expensive part of a new offer may be discovering too late that you were wrong about the buyer, the problem, or what they would pay to receive.

AI can produce a convincing name, landing page, sample, and sales emails before any of those questions has been answered. I recommend a five-step Market Check: write down what must be true, investigate the problem, show a small concept, ask for a meaningful commitment, and decide what the evidence earns next.

You will see the method through an illustrative case: an experienced consultant who almost builds a paid AI newsletter for small-business owners. Her conversations change both the buyer and the offer.

Free readers get the method, interview questions, sample-size guidance, recruiting math, and a two-week plan here. The planned paid Field Kit will add copyable templates, an evidence tracker, an AI analysis prompt, and a decision scorecard.

I sold my second business in September 2024. Six months later, after taking courses, reading, and trying to figure out what came next, I started Build to Thrive. At first, I wrote about entrepreneurship and my own experience. Then AI changed the direction. I became convinced that learning how to use it well was one of the best investments I could make in the next chapter of my career.

A year later, I can build things with AI that I could not have imagined when I started. But there is one thing I would do differently: I would spend more time testing the market before deciding what to build. I have always believed in getting close to customers, but I also learned how easy it is to fall in love with an idea, especially now that AI can turn that idea into something polished almost overnight.

That is what this piece is about.

An owner sees an opportunity. Clients have been asking the same question for years. The entrepreneur knows how to answer it, and suspects others would pay for that answer too.

They open an AI tool. By Friday, the idea has a name, three pricing options, a landing page, a sample issue, and an email sequence. It looks like a business.

But no buyer has chosen it over another priority. No one has put money, time, data, or access to a decision-maker behind it. The owner has evidence that she can make the offer. She does not yet have evidence that people want it.

I understand the pull. Building feels productive. Asking someone why they would not buy feels uncomfortable. AI makes the comfortable part faster, so it becomes easier to postpone the question that matters.

The point is not to stop building. It is to make the next investment small enough that you can still change your mind.

Every offer mixes facts with guesses

A Short Story

Consider Maya, an experienced operations consultant. She has helped independent business owners find useful ways to apply AI. She now wants to sell a paid weekly newsletter called AI for the Owner’s Week. It will explain new tools and give subscribers one action to try.

Maya knows her material. She has heard owners say they feel behind and are unsure where AI fits into their business. Those are facts from her experience.

Almost everything else is still a hypothesis.

Who is actually most likely to pay: the owner, a manager, a professional adviser, or an association serving many businesses? What problem feels urgent enough to spend money on now? Are owners struggling to keep up with AI news, or do they already have too much information and not enough help applying it?

Is a newsletter even the right format? Would they rather have a checklist, a monthly workshop, hands-on help, or someone who helps them implement one change? How often do they need help? What outcome would make the subscription feel worthwhile?

Then there is the buying question. What are they already paying for? What would they stop doing or buying to make room for this? Is $20 a month easy, irrelevant, or still too much for something they are not sure they will use? Who makes the decision? What would have to happen for someone to subscribe today rather than say, “That sounds useful”?

And perhaps the most important question: if the newsletter is not the product, what is the problem underneath it that Maya could build around instead?

Maya could take her first answers and build a polished product around them. Instead, she gives herself two weeks to find out which assumptions survive contact with buyers.

Maya and her results are fictional and illustrative. The case shows how to make decisions with evidence; it does not claim that these conversion rates occurred in a client project.

Subscribe now

Four ideas behind a better test

This discipline has a history. I have drawn the Market Check from four strands of work:

Rita McGrath and Ian MacMillan: write down what must be true. Their discovery-driven planning makes assumptions visible as you invest. Maya writes down the beliefs carrying the newsletter.

Steve Blank: treat the offer as a set of hypotheses. His customer development approach puts the customer, problem, solution, channel, and price in contact with real buyers. Maya talks to prospects before producing a season of issues.

Saras Sarasvathy: decide what you can afford to lose. Her affordable-loss principle helps Maya risk two weeks and a small pilot instead of months of production.

Daniel Kahneman and Dan Lovallo: look beyond your own plan. Their outside-view argument prompts Maya to examine what owners already read, pay for, and ignore.

The governing question: What is the smallest, honest test that could change my decision?

1. Write down what must be true

Before Maya interviews anyone, she completes five sentences:

Maya’s first answers are:

● Buyer: An independent business owner curious about AI.

● Problem: They cannot keep up with new AI tools.

● Why now: They worry competitors will move faster.

● Desired outcome: One useful AI action each week.

● Reason to act: A short paid newsletter will save research time.

All five sound plausible. None is yet a customer decision.

Write your own answers before talking to people. Otherwise, it becomes too easy to claim afterward that you “always knew” what the market meant.

Maya also writes down what would change her mind: if owners already get enough free AI news but repeatedly ask for help applying it, she will stop treating a paid newsletter as the obvious product. That sentence matters later. Without it, she could explain away every inconvenient answer.

2. Investigate the problem before showing the offer

Maya looks for owners who have recently tried to use AI in their business, not just people who enjoy discussing it. In each conversation she asks:

● Tell me about the last time you tried to use AI for a business task.

● What were you trying to improve: revenue, margin, customer service, or your time?

● What did you try, and what happened afterward?

● What are you using now to find advice or examples?

● Have you paid for help with this? Who approved that purchase?

● What would make this problem important enough to address this month?

She does not lead with the newsletter. If she does, the conversation can turn into feedback on her idea instead of evidence about their lives.

Maya aims for 12 completed conversations in one reasonably defined buyer group. That is a working target, not a validation threshold. A systematic review by Hennink and Kaiser found that studies with narrow objectives and relatively similar participants often identified recurring themes within roughly 9–17 interviews. A commercial decision still requires its own evidence of urgency and commitment.

For planning, if 40% of invited people agree and 80% of those attend, 12 completed interviews require about 38 invitations: 12 ÷ .40 ÷ .80 = 37.5. Your rates may differ. Start with five, adjust the questions, then continue where the uncertainty remains.

In Maya’s illustrative test, the funnel looks like this:

She personally invites 38 qualified owners. Fifteen agree to talk, 13 schedule, and 12 complete a conversation.

The sequence matters. An open poll of AI enthusiasts might produce encouraging answers, but Maya needs to hear from people who run businesses and have recently tried to apply AI. The recruiting funnel also shows how many invitations a modest interview target can require.

The first five conversations alter her questions. An owner says that AI wrote a decent promotion but could not tell whether it brought anyone back. Another tried to summarize invoices but stopped when the line items were wrong. Maya had been asking, “Where do you get AI news?” She starts asking, “What happened the last time you tried to use it?” That shift moves the discussion from curiosity to a business job and its consequences. These scenes are illustrative, not reported interviews.

Here is what Maya might hear in this illustrative round:

After the 12 conversations, Maya sorts the evidence:

● Nine describe a recent AI attempt that stalled after the first experiment. The practical problem is real for this group.

● Eight already receive free AI news through email or social feeds. More news alone may not stand out.

● Seven say they need help applying an idea to their own records or workflow. The proposed delivery format may be wrong.

● Three would consider paying personally for a newsletter. Interest in AI is not the same as demand for this offer.

Maya keeps three columns in her notes: what the person actually did, what they said they want, and her interpretation. “I would read that” belongs in the second column. An owner spending Saturday correcting invoice lines belongs in the first. “They need hands-on setup” is an interpretation she must still test.

Maya was right that owners want help. She was less right about what kind of help they would buy. The interview counts do not represent a market survey or prove how common this problem is among all small businesses. They tell her which assumption deserves the next test.

3. Create the smallest honest test

She could revise the newsletter’s headline and send another survey. That would mostly test copy.

Instead, Maya writes two one-page concepts and shows them to people who described a recent problem:

Concept A: a weekly AI newsletter. Each issue offers one practical action for a monthly fee. Maya wants to learn whether owners will pay for guidance they read and apply on their own.

Concept B: a four-week working pilot. An owner brings one recurring task and leaves with a working first version and a way to measure it. Maya wants to learn whether they will invest both money and time to solve a current problem.

She keeps both small. There is no full curriculum, membership site, or automated delivery system. A test should help decide what to build; it should not quietly become the full build.

On day eight she shows the same seven people the two one-page concepts and offers a sample newsletter issue. The sample translates one AI development into a practical task. The pilot concept asks the owner to bring an actual stuck task, their current way of doing it, and one measure of improvement. She explains the time commitment and a proposed price for each, rather than hiding those details until after someone says they are interested.

The seven are the people who described an urgent, recent problem, not a random sample. Maya is learning what these prospects will consider next; she is not running a controlled experiment between two product formats.

4. Ask for commitment, not applause

“What do you think?” invites politeness. Maya asks what each prospect would do next.

Would they pay for the first month of the newsletter? Would they forward a sample to the person who controls the budget? Would they bring a real business task to a paid pilot and reserve time for it?

In the illustrative case, five ask to see a free sample issue. One agrees to pay for the newsletter. Three agree to pay for the working pilot and identify the task they want to tackle.

Here is the decision trail she records:

Among those seven prospects:

● Five request the free sample issue. They want to inspect the content. That is useful feedback, but weak purchase evidence.

● One accepts the paid newsletter offer. That is a purchase commitment for one person, not proof of a broad market.

● Three identify a current task and accept a paid pilot. They commit money and working time to a specific outcome, a stronger signal for the pilot among this group.

● Two take neither next step. Maya keeps them in the record and asks why, rather than removing them from the story.

The categories can overlap: someone may read the sample and also choose a pilot. They are not seven exclusive votes to add together. Maya records names and actions rather than presenting the totals as a conversion rate.

That does not prove a larger pilot business will succeed. It does tell Maya more than five compliments would. The proposed format affects whether people act.

Commitments have different strength. A second meeting costs time. An introduction risks some reputation. A deposit or payment costs money. No single action is proof on its own, and the appropriate request depends on how developed the offer is. What matters is whether the customer does more than approve the idea in conversation.

5. Decide what the evidence earns next

Maya has not learned that “newsletters don’t work.” She has learned something narrower: among the owners she interviewed, free AI news was plentiful, while hands-on help with one stuck task prompted stronger commitments.

Her decision is revise and pilot. She delivers the three working pilots manually, records the time each one takes, and asks whether the promised outcome actually appears. Only then does she decide whether a repeatable offer is worth building. The newsletter may become a free channel that helps the right owners recognize the problem, rather than the paid product itself.

The two-week Market Check ends with a decision to run those pilots; their delivery happens afterward. For each, she records the starting task, hours spent before, the first working output, the owner’s review, and any correction or follow-up time. If the work takes her ten hours to save the owner one, the offer needs another revision even though someone paid for it.

She has learned something concrete, with limits:

Maya compares each original belief with what happened:

● “Owners lack AI news.” Eight already get it free. She will not build a paid content library yet.

● “A weekly action is enough.” Seven want help applying an idea to their own work. She will test delivery support.

● “Owners will pay for this newsletter.” One accepts it, while three accept a paid working pilot. She will pilot the stronger commitment and keep observing.

● “I can build a repeatable offer now.” Delivery cost and outcomes remain unknown. She will deliver manually before systematizing.

You can make the same decision using this table:

Your Market Check can end in one of four decisions:

● Build when the problem repeats, the buyer is clear, and customers make commitments that fit the offer.

● Revise when the problem is real but the buyer, promise, price, or format is off.

● Keep testing when signals are promising but inconsistent or come from different buyer groups.

● Stop when urgency is low and qualified customers will not take a meaningful next step.

Stopping an idea at this stage is useful. It is cheaper than discovering the same thing after building months of material.

Where AI helps, and where it can mislead

AI can prepare an interview guide, organize notes, surface repeated phrases, compare the findings with the original assumptions, draft the one-page concepts, and identify contradictions Maya should check herself.

It can also turn weak evidence into a persuasive story. If Maya asks it to write a case for the newsletter using only enthusiastic comments, she may get a very convincing answer to the wrong question.

Keep each quote and action tied to a real source. Label what someone said, what they did, what you infer, and what remains unknown. AI finds and prepares. Human judgment chooses. The market proves.

Share

If you only remember one thing

A finished-looking offer is no longer expensive to make. That makes it easier to invest in the wrong buyer, promise, or format before anyone has had a reason to say yes.

Let a small amount of market evidence earn the next investment.

Run your Market Check in two weeks

Day 1: Write the five assumptions and the decision you need to make. You leave with an Assumption Card.

Days 2–3: Identify a narrow buyer group and invite qualified people. You leave with a recruitment list and invitations.

Days 4–6: Conduct an initial five conversations, improve the questions, and continue. Keep notes tied to real incidents.

Day 7: Compare what people do with what you assumed. Revise your view of the buyer, problem, and urgency.

Day 8: Create one or two small, honest concepts. Keep each to one page.

Day 9: Ask for a commitment appropriate to the offer: a meeting, introduction, pilot reservation, deposit, or payment.

Day 10: Decide whether to build, revise, keep testing, or stop. Record the evidence and what remains unknown.

This article gives free subscribers the complete method, questions, sample-size guidance, recruiting calculation, and schedule.

You can begin without another tool. Write down the five assumptions from step one and circle the answer that would be most costly to get wrong. Then invite five people who have faced that problem recently to tell you what happened. Listen before you show them the offer.

That first round may save you from building the wrong thing. It may also give you a better reason to build.

If you want the copyable materials for running the full check, the planned Field Kit begins below.

The Market Check Field Kit

The paid companion includes an Assumption Card, a five-minute questionnaire, invitation and follow-up templates, a recruitment calculator, an evidence tracker, a one-page concept template, a commitment-test menu, an AI analysis prompt, a decision scorecard, and the worked Maya example.

Read more

TL;DR

Many owners are not overwhelmed because they have too many decisions.

They are overwhelmed because every decision arrives unfinished.

The information is scattered. The history has to be reconstructed. Someone needs to find the email, compare the numbers, review the notes, and explain what changed.

Only then can the owner think.

AI can prepare that work before the owner arrives.

The goal is not to remove human judgment. It is to make sure human judgment is used where it matters.

Here is what you will learn

• Why owners become the hidden queue inside a growing business

• The difference between preparing work and making decisions

• What a decision-ready business looks like

• Five questions for finding work that should stop waiting for you

• Examples of work AI can prepare without taking control

• How to identify the first machine worth building

Most work does not arrive ready for a decision

A proposal lands in your inbox.

Before approving it, you need to remember what the client requested, check the last conversation, compare the price with similar projects, and confirm what the team can deliver.

A purchasing question arrives.

Before answering, you need to see what was ordered last time, whether the price changed, what is already in inventory, and what the next few weeks of demand might look like.

Someone asks what the business should publish this week.

Before choosing, you need to know what customers are talking about, what competitors are covering, what performed previously, and what the business is trying to sell.

None of these decisions is necessarily difficult.

The preparation is what makes them heavy.

And that preparation often waits for the owner.

The owner becomes the hidden queue

Michael Gerber wrote about the difference between working in the business and working on the business.

Cal Newport has written extensively about the damage caused by fragmented attention.

Research from companies such as Asana and Microsoft continues to show how much work disappears into coordination, searching, switching, and communication.

Different writers use different language, but the pattern is familiar:

The owner is not only making decisions.

The owner is also gathering the material required to make them.

That creates a hidden queue.

Projects wait because the owner has not reviewed the notes.

Proposals wait because the owner needs to reconstruct the client conversation.

Content waits because the owner has not chosen the angle.

Follow-up waits because the relationship history lives in the owner’s head.

The business appears to be waiting for a decision.

In reality, it is often waiting for preparation.

New to Build to Thrive? See the different subscription plans here

What should be waiting for you?

This is the question I would ask:

What work is waiting for you that could be waiting for your decision instead?

Consider two versions of the same Monday morning.

Version one: the work waits for the owner

You open your laptop and find:

• Twenty-seven unread emails

• Three proposals requiring review

• Notes from four customer calls

• A spreadsheet that needs interpretation

• Five possible topics for the newsletter

• A message asking which lead should receive attention first

Before making progress, you have to reconstruct the week.

Version two: the work waits for a decision

You open your laptop and find:

• Three emails that actually require your response

• A proposal with the client’s goals, scope changes, price comparison, and open questions

• A summary of repeated customer concerns

• A short explanation of what changed in the spreadsheet

• Three newsletter opportunities ranked by relevance

• A lead brief showing the relationship history and recommended next step

The decisions are still yours.

But the work arrives prepared.

That is a very different business.

Preparation is not judgment

This is where many conversations about artificial intelligence go wrong. Preparing a decision is often treated as if it were the same as making the decision.

A capable system can gather information, organize notes, compare versions, identify repeated themes, expose contradictions, and draft a recommendation. Those activities reduce the distance between information and judgment.

The owner still determines which outcome matters and which constraint cannot be ignored. Decisions involving fit, price, promises, relationships, exceptions, and risk continue to require human responsibility.

This is the division of work Build to Thrive is built around. The machine finds and prepares, human judgment chooses, and the market proves whether the choice worked.

I have written about my AI Chief of Staff and how helpful it has been for me.

If you like to meet for 15-min and see what would make more sense to you, click on the link below. I’ll be happy to help you find the best approach to this. Believe me, it is night and day, your productivity will 10x.

15-min Virtual Coffee

What a decision-ready brief should answer

• What happened? The relevant facts.

• What changed? The difference from the previous situation.

• Why does it matter? The likely consequence.

• What remains uncertain? Missing or conflicting information.

• What is recommended? A proposed next step and the reasoning behind it.

• What decision is needed? The exact choice the owner must make.

A useful brief makes the facts visible without burying the owner in detail. It also separates what is known from what is inferred, recommended, or still not established.

The machine does not bury the owner in information.

It reduces the distance between information and judgment.

Six examples of work that can arrive prepared

1. Market intelligence

Instead of sending the owner twenty links, the system can:

• Monitor selected sources

• Remove duplicates

• Group developments by topic

• Explain why each development may matter

• Identify three opportunities worth reviewing

The owner decides which opportunity fits the business.

2. Content

Instead of beginning with an empty page, the system can:

• Review customer questions

• Find themes in recent conversations

• Compare them with past content

• Suggest several angles

• Prepare an outline using the business’s voice and offers

The owner chooses what is worth saying.

3. Repurposing

After an article is approved, the system can prepare:

• A LinkedIn post

• A Substack Note

• An email introduction

• Several short excerpts

• Suggested visual concepts

The owner approves what represents the brand.

4. Proposals

Before the owner reviews a proposal, the system can assemble:

• The client’s stated problem

• Desired outcome

• Relevant meeting notes

• Open questions

• Proposed scope

• Similar past work

• Pricing considerations

• Risks or unclear promises

The owner decides what to offer and what not to promise.

5. Follow-up

The system can prepare:

• The relationship history

• The last commitment made

• What has happened since

• A suggested message

• The appropriate next step

The owner decides when the relationship requires a personal touch.

6. Purchasing

Before approving a purchase, the system can show:

• Previous prices

• Current price changes

• Supplier history

• Quantities purchased

• Inventory information

• Expected demand

• Unusual cost movements

The owner decides whether to buy, wait, substitute, or renegotiate.

If you like to know more about my Chief of Staff click on this link it guides you through the plug-in I install for others after a short consultation.

The founder-wait test

Choose one piece of work currently waiting for you.

Then ask five questions.

1. What decision actually requires me?

Name the specific judgment.

If you cannot identify it, the work may be reaching you because of habit rather than necessity.

2. What information do I gather before making that decision?

List the emails, documents, numbers, history, and context you normally reconstruct.

This is the preparation layer.

3. Which parts follow a repeatable pattern?

Look for work that happens in a similar way each time:

• Searching

• Sorting

• Comparing

• Summarizing

• Drafting

• Checking for missing information

These are strong candidates for a machine.

4. Which parts require my judgment?

Protect the decisions involving:

• Fit

• Price

• Promises

• Relationships

• Exceptions

• Risk

The objective is not to remove the owner from the business.

It is to stop wasting the owner on preparation.

5. What would a decision-ready package contain?

Describe what you would want to receive.

Not “summarize the emails.”

Something more useful:

Show me the customer’s objective, what changed since our last discussion, the relevant commitments, the financial implications, the unresolved questions, and the recommended next step.

That is the beginning of a real machine specification.

Share

Start with one recurring decision

Do not begin by asking:

How can we automate the business?

That question is too broad.

Start with:

Which recurring decision keeps arriving unfinished?

Then build the smallest system that can prepare it.

For example:

Before: The owner searches through emails, notes, and spreadsheets before every proposal review.

Machine: The system collects the client context, summarizes the request, compares it with previous work, identifies missing information, and drafts the proposal.

Owner’s decision: Scope, price, promises, and whether the opportunity fits.

Scoreboard: Preparation time, proposal turnaround, corrections required, and conversion rate.

That is a machine with a purpose.

The first machine teaches you about the business

Building the first machine is not only about saving time.

It reveals how the business actually works.

You discover:

• Which decisions have never been documented

• Where essential context lives

• Which exceptions occur repeatedly

• What employees cannot access

• Where information becomes unreliable

• Which steps require experience

• Which decisions should never be delegated

This is why owners should participate in building their first AI machine.

Not because they need to become technical.

Because the first build forces the business to explain itself.

If you only remember one thing

AI should not replace the moment when your judgment matters.

It should prepare that moment.

The best machine may not make a single important decision.

It may simply make sure that when the decision reaches you, the facts are organized, the history is visible, the uncertainty is clear, and the next move is ready for consideration.

The work no longer waits for you.

It waits for your decision.

Where is your business waiting?

If work keeps stopping because it needs your memory, preparation, or rescue, that is usually not a personal productivity problem.

It may be the first machine your business needs.

I offer four free 30-minute diagnostic calls each month.

We will identify the work that keeps waiting for you, separate preparation from judgment, and find the first practical move.

A few days later, I will send you a two- or three-page report with what we uncovered and my recommended first step.

It is yours to keep, whether or not we ever work together.

Juan

AI has dramatically reduced the time and money required to turn an idea into something you can use.

A business owner can now create a workflow, internal tool, client portal, research system, or first version of an app without assembling a traditional software team.

But easier building creates a new problem. When almost anything can be built, it becomes easier to spend time building things that do not matter.

The question is no longer only, “Can we build this?”

It is, “If we build this, what becomes meaningfully better?”

A few years ago, most business owners could identify problems they wanted software to solve but could not build the solution themselves.

They needed someone to translate the problem into technical requirements. Then they needed a designer, developer, budget, and enough confidence in the idea to justify the cost.

That cost created a filter. Many ideas never made it past a notebook because testing them was too expensive.

AI is removing much of that barrier.

You can now describe a problem, create a rough version of a solution, try it on real work, and improve it as you learn. You do not need to begin with a large software project. You can begin with something that frustrated you on Tuesday afternoon.

That is a major shift for business owners.

It is also an invitation to build the wrong things faster.

Here’s what you’ll learn

• Why the old cost of building acted as a filter

• * How AI changes the order in which we develop ideas

• * Why cheaper building makes judgment more important

• * How to decide whether an idea deserves to be built

• * The five questions to answer before choosing the tool

Subscribe now

The old cost was building

For most of the software era, turning an idea into something usable required a long sequence of decisions.

You identified the problem. Someone wrote a specification. The project was scoped and priced. A designer worked through the experience. Developers built it. The team tested it, revised it, and eventually released it.

The process was slow because engineering time was expensive. Companies created planning rituals to protect that limited resource.

Josh Elman, a former product leader at LinkedIn, Twitter, and Robinhood, describes the old development loop as beginning with the idea and moving through specification, costing, scoping, design, and finally building.

AI changes the order.

Instead of fully describing the system before anything exists, you can build a rough version first. Then you play with it, learn what feels useful, see what is missing, and decide whether it deserves further investment.

The new loop looks more like this:

Idea → Build → Play → Learn → Design → Ship

Elman describes this shift in his article, “Product Management Is Still All About Telling Stories.”

A prototype gives you something a written specification cannot. It lets you experience the idea.

For a small-business owner, that prototype does not have to be software sold to thousands of people. It could be a system that prepares a proposal, reviews purchase receipts, organizes research, or shows which client relationships need attention.

The economics have changed

The cost of using AI has fallen with unusual speed.

The Stanford AI Index found that the cost of querying a model performing at approximately GPT-3.5 level fell from $20 per million tokens in November 2022 to $0.07 by October 2024.

That is a reduction of more than 280 times in about 18 months.

The figures explain why capabilities that once required a software company are appearing inside ordinary businesses.

A consultant can build a research system around past work. A restaurant owner can turn purchase receipts into information for the accountant, inventory, food-cost decisions, and tomorrow’s purchasing. An agency can prepare client updates before the weekly meeting. A real estate operator can organize property information and identify what needs attention.

The technical barrier keeps getting lower.

The cost of a bad decision has not fallen at the same rate.

You can still spend days building something nobody uses. You can automate a process that should have been eliminated. You can create a dashboard that displays information without improving a single decision.

The system may work exactly as designed and still have little value.

The new cost is distraction

When building was expensive, the obstacle was access.

When building becomes cheap, the obstacle is focus.

You can create an app for a task that takes ten minutes each month. You can build an agent to produce a report nobody reads. You can connect five tools when a shared checklist would solve the problem.

The app works. That does not mean it was worth building.

This is where many AI projects go wrong. They begin with a capability instead of a business problem.

Someone sees that AI can summarize calls, create dashboards, generate proposals, or coordinate agents. The conversation begins with what the technology can do. Nobody stops to ask which part of the business is actually costing time, margin, revenue, or customer trust.

A working prototype can create false confidence. Because the system runs, everyone assumes the project has moved forward.

But activity is not the same as progress.

The better question is:

If we build this, what becomes meaningfully better?

Can we name the hours that come back?

The delay that disappears? The decision that improves?

The customer who receives a better experience?

The margin that is protected?

If the answer is unclear, the idea is not ready.

Experience becomes part of the technology

AI gives business owners a new ability to act on what they already know.

The owner knows which part of the process breaks when the restaurant is busy. The owner knows why two clients who appear similar need different recommendations. The owner knows when an invoice is normal, when it requires attention, and when the supplier needs a call.

That information rarely appears in the official process.

It lives in experience.

A developer may understand how to build the system. AI may be able to produce the first version. A consultant may recognize patterns from other companies.

The owner understands what happens when the clean process meets the real day.

That knowledge helps answer questions the technology cannot settle on its own:

• Which problem is worth solving?

• * Which exception matters?

• * What can be standardized?

• * What must remain specific to the customer?

• * Which decisions involve money, trust, or accountability?

• * What should the system prepare?

• * What should a person still decide?

AI can help execute the answer. It cannot decide what matters to the business without being taught.

Five questions before you build

Before choosing a tool, writing a prompt, or connecting two systems, answer five questions.

1. Who is experiencing the problem?

“The business” is too broad.

Is the problem affecting the owner, an employee, a customer, the accountant, or a supplier? Different people may experience different parts of the same process.

2. What happens today?

Describe the work as it actually happens.

Where does the information begin? Who touches it? What gets copied? What is reconstructed from memory? Where does the process wait?

3. What does the problem cost?

The cost may be time, lost revenue, lower margin, a poor customer experience, or a decision made without current information.

If the cost cannot be described, it will be difficult to know whether the solution helped.

4. What judgment must remain human?

AI can collect, organize, compare, calculate, summarize, and draft.

A person should remain responsible for decisions involving fit, price, promises, relationships, risk, and accountability.

Define that boundary before automating the process.

5. What is the smallest version that could teach you something?

Do not begin by building the final system.

Run one invoice through it. Prepare one client meeting. Draft one proposal. Use one real piece of work and observe what happens.

A prototype is useful because of what it teaches you, not because it exists.

Share

Start with work that already exists

You do not need to invent an AI strategy for the entire company.

Look at the work already happening.

Find one repeated process that consumes meaningful time or money. Choose something with recognizable inputs, a visible output, and a decision that can remain with a person.

Then test the smallest useful version on live work.

If it is a proposal process, prepare one proposal.

If it is purchasing, process one set of receipts.

If it is client preparation, use it before one meeting.

You will learn more from one real run than from another week of discussing tools.

If you only remember one thing

AI has lowered the cost of turning an idea into something that works.

It has not lowered the cost of choosing the wrong idea.

The advantage will not belong to the business that builds the most systems. It will belong to the business that knows which problem deserves attention, what outcome matters, and where human judgment belongs.

This is why my work with business owners begins before we choose a tool. We identify the real constraint, define what should change, and build the smallest, useful version around the work that already exists.

The technology comes after the problem is clear.

Build assets. Create freedom. Thrive on your terms

Juan

AI has made it possible for business owners to build tools, workflows, and internal systems that once required developers. But access to building does not guarantee that we will build the right thing.

The owner still has to identify the problem, define the outcome, provide the context, and decide where human judgment belongs. That sounds a lot like product management. Whether you realize it or not, you may already be doing it.

A few months ago, I started building an AI agent for my newsletter. It could read the research I had collected, review articles I had published, identify recurring themes, organize sources, and prepare material for a new edition.

Then it stopped.

The technology had not failed. The agent was waiting for me to choose what I wanted to write about. The research was available, the tools were working, and the agent was ready. But the decision was still mine.

That experience changed how I think about building with AI. The limitation was no longer whether I could build the system. It was whether I could tell the system what mattered.

The old barrier was building

For most of the history of software, an idea had to survive a long journey before anyone could use it. Someone identified a need. A product manager translated that need into requirements. Designers created the experience, engineers built it, and the team tested and revised it before releasing it.

The process required specialists, money, and time. That made building inaccessible to most small-business owners. You might have known exactly what you needed, but knowing was not enough. You still needed someone who could translate the idea into software.

That barrier is falling.

Josh Elman, a former product leader at Twitter, LinkedIn, and Robinhood, recently described how AI is changing the traditional product-development loop. The old process was largely: specify, scope, build. The emerging process looks more like: build, play, design, ship.

Instead of describing an entire system before anything exists, people can create a rough version, try it, learn from it, and improve it. You can read more about that shift in Josh Elman’s a16z article.

This matters beyond technology companies. It changes what is possible for someone running a consulting practice, restaurant, agency, real estate company, or professional service business.

You no longer need to begin with a software project. You can begin with a problem from Tuesday afternoon.

Product management without the title

A good product manager does not simply tell engineers what to build. The job begins by answering a series of questions:

• What problem are we trying to solve?

• Who experiences it?

• What happens today?

• What should happen instead?

• Which decisions can the system make?

• Which decisions require a person?

• How will we know whether the new process works?

Business owners answer versions of these questions every day. When a client inquiry arrives, you decide what information your team needs before responding. When a proposal takes four hours to prepare, you decide what can be standardized and what must remain specific to the client.

When inventory keeps running short, you determine which information would help you order more accurately. When follow-ups disappear, you decide when a relationship needs attention and what should happen next.

You may not call this product management. You call it running the business. But the underlying skill is the same: understanding a problem well enough to design a better way through it.

AI gives proximity a new value

A developer may know how to build the system. A consultant may recognize useful patterns. AI may be able to produce the first version. But the owner knows what happens when the restaurant is busy, the client changes the scope, an invoice arrives late, or an exception does not fit the documented process.

That proximity tells you where a process looks clean on paper but breaks in practice. It helps you recognize which client question signals a real opportunity, which recommendation is technically correct but commercially foolish, and when an exception is noise versus evidence that the process itself was designed incorrectly.

As AI becomes more capable, that knowledge does not become less important. It becomes the ingredient that makes the technology useful.

A Harvard Business School study involving 640 entrepreneurs in Kenya found that access to an AI business adviser produced different results depending on the person using it. Higher-performing businesses improved, while lower-performing businesses experienced declines in revenue and profit.

The researchers suggested that AI could produce advice that sounded reasonable without understanding whether it addressed the owner’s underlying problem. The owners still needed the judgment to evaluate and apply it.

The lesson is not that AI only works for successful people. The lesson is that access to an answer is different from knowing whether it is the right answer.

Your advantage is not technical

When I tell business owners they can build with AI, many imagine they need to become programmers. They do not. They need to become better at describing the work.

Take a proposal process. The owner does not need to understand the code behind the system. But the owner does need to explain:

• Where the information comes from

• What must be included

• What changes from client to client

• What language should never be used

• Who approves the price

• When the proposal is ready

• What the system must never send automatically

Those are business decisions. Once they are clear, AI can organize the inputs, retrieve relevant material, prepare the first draft, identify what is missing, and present the proposal for review.

The owner keeps the decisions about fit, price, the promise, and whether the proposal goes out.

The machine prepares. The owner decides.

That is not handing the business to AI. It is designing the business so your judgment is used where it creates the most value.

Subscribe now

Four decisions the owner must keep

1. Decide what outcome matters

“Use AI for proposals” is not an outcome. “Reduce proposal preparation from four hours to 45 minutes without weakening the client-specific recommendation” is an outcome.

The first statement names a tool. The second describes what should change in the business and what must be protected while it changes. The clearer the outcome, the easier it becomes to design the machine.

2. Find the real constraint

The loudest complaint is not always the real problem. A founder may complain about email, but the deeper issue may be that nobody knows which messages require a decision.

A restaurant owner may complain about inventory, but the deeper problem may be that purchasing decisions are based on memory instead of current sales and cost information.

If you solve the complaint without finding the constraint, you may automate the wrong process. That only helps the wrong work move faster.

3. Separate preparation from judgment

AI can collect, organize, compare, calculate, summarize, and draft. The owner should identify the decisions that affect trust, money, positioning, or accountability.

Those decisions need a person. The boundary between preparation and judgment should be designed before the workflow is automated.

4. Define what better means

A machine needs a scoreboard. Did it give time back? Did it protect margin? Did it improve the customer experience? Did it increase capacity without another hire?

If the business cannot describe what should improve, it cannot know whether the machine is working.

Share

Start with one machine

You do not need to automate the company. Look for one repeated piece of work that happens often, consumes meaningful time or money, and follows a recognizable pattern.

Then ask:

What could the machine prepare before I arrive, and which decision should remain mine?

That question might lead to a market-intelligence system that prepares the week’s relevant developments, a content system that turns your knowledge into publishable ideas, or a proposal system that retrieves the right information and prepares a draft.

It might lead to a follow-up system that shows which relationships need attention, a repurposing workflow that adapts one article into several formats, or a purchasing report that gives an owner better information before placing an order.

None of these requires a giant collection of autonomous agents. A useful machine can be surprisingly simple. It combines a repeatable process, the context of the business, a few tools, human judgment, and a way to measure the result.

The owner as builder

I believe business owners should participate in building their first AI machine. Not because they need another responsibility or should spend their evenings becoming software developers. They should participate because building reveals the business.

You discover which decisions were never documented and where important information lives only in someone’s memory. You see how often a process depends on an exception. You learn which parts can move without you and which parts still deserve your attention.

Most importantly, you stop seeing AI as something being done to your business. You begin to see it as a material you can shape.

This is why I created Build My Machine. Across two working sessions, I train you to work with Claude Cowork and give you the plug-ins needed to begin applying it to specific areas of your business.

The real outcome is not installing a plug-in. It is understanding how a business machine is put together.

The larger system I use with clients is called ThriveOS. It helps us connect the technology to the way the business actually operates. You provide the context, see how the instructions shape the result, and identify where your judgment belongs.

You leave understanding what you built and how to use it. The goal is not to make you dependent on me. It is to help you become capable of building with AI.

If you only remember one thing

You do not need to become a product manager or software developer. You need to recognize that your experience is now part of the building technology.

AI can help create the system, but you know the customers, the exceptions, what the business can promise, and what good looks like. That knowledge is what turns an AI workflow into a business machine.

Once you learn to build one, you begin seeing possibilities throughout the company.

Build assets. Create freedom. Thrive on your terms.

Juan

I’ve spent most of my career building businesses, advising founders, and trying to figure out the same thing most entrepreneurs eventually run into:

How do you build something that grows without requiring more and more of you? AI has changed what’s possible. One person can now research, create, sell, serve clients, and operate with capabilities that used to require a much larger team.

But that’s also created a new problem. There are thousands of AI tools, prompts, agents, workflows, and opinions about what you should automate next.

I don’t think the answer is more AI. AI isn’t the destination. A better business is.

Most entrepreneurs start the same way: they are good at the craft, so they open the shop, and for a while that is enough. Then loving the work and running the company turn out to be different jobs, and the week fills with fires, so the time to think about growth shrinks to almost nothing.

Before AI, a shared inbox and a good checklist could only take you so far. By 3pm you were still hunting the same email, re-explaining the same scope, walking the same task from person to person by hand.

That tension, between the craft you love and the company you now have to run, isn’t new. What’s new is a way to close part of that gap without hiring your way out of it. Done right, AI doesn’t replace your judgment, it buys back the hours the fires were eating, and often the money too, so the growth you’ve been meaning to get to actually earns a slot on the calendar.

The fires don’t stop on their own, and you can’t out-work a business that has no clear picture of where the time is actually going. If you are still trapped in the fires with no room to think about growth, this piece walks through the method, one room at a time, then shows you how Sage runs that diagnosis with you tonight.

You already sense the drag. You need a method, not a hunch.

Most business owners already sense where the drag is. It’s the task you dread. It’s the thing you do the exact same way every single week and think, “there has to be a better way.” The mistake isn’t a lack of awareness; it’s a lack of structure around that awareness. You need a method, not a hunch. Here it is, and you can run this yourself with nothing but a notebook.

1. Name the room. Not the whole business, one department or function. If your answer sounds like a slogan, or doesn’t match where your actual hours went last week, rename it and say why in one sentence.

2. Get specific about the task. Not “customer service is slow,” the exact recurring task. Walk through one real, recent example step by step: what triggered it, what you actually did, what happened.

3. Map the dependencies. Most bottlenecks aren’t one broken task, they’re a handful of parts that are supposed to talk to each other and don’t. List the systems, people, and information sources involved. For each one, does it connect automatically, or does a person manually bridge the gap every time?

4. Find where it breaks, and how often. Not “sometimes,” a real frequency. This is usually where the actual leak lives, not the task itself, the specific point where the handoff fails.

5. See the loop. Ask what happens after it breaks. Does it change how you or your team behaves going forward, extra double-checking, a workaround that’s become permanent. That’s the difference between a one-off annoyance and a pattern that quietly keeps costing you.

6. Cost the leak. Hours per week the task consumes, times what that time is worth. One sentence: “this job costs about $X a week.” That number is your ceiling, and here’s a concrete rule of thumb whenever you work with an AI advisor. Never pay more than 20% of the annual savings that you will get for the AI system. This is a rule of thumb and the way I price my work. Put another way, you should be making at least five times in annual savings compared to what you are getting charged.

7. Split chore from judgment. Go through your step map and mark each one CHORE or JUDGMENT. Hard rule, no exceptions: price, fit, the yes, relationship language, blame, and the send are always JUDGMENT. Never hand those to a system, no matter how tempting the automation looks.

8. Define done. One outcome, by when, one number. Not “make it better,” a finish line you’d actually know if you hit.

9. Pick one fix, prove it. One chore step, run on five real live items. You still decide. You still send. No new tools, no second room, not yet.

Where This Falls Apart Alone

Here’s the honest part. Steps 3 and 7 are where most people quietly cheat, not out of laziness, but because the brain fills gaps faster than it admits them. You already half-know your dependencies, so instead of naming them specifically, you say “it’s kind of a mess over there,” which sounds like an answer but isn’t one. And judgment steps get relabeled as chores because “just automate it” feels like progress, even when the step in question was the send, or the yes, or the price, the exact things that were never supposed to move.

That’s the real reason most business owners get as far as “I know something’s wrong over there” and stop. Not a lack of insight, a lack of something holding them to finishing the thought.

Talk to Sage

Most bottlenecks aren't one broken task, they're a handful of interdependent moving parts, and untangling that on your own, while you're also running the business is often times very challenging. One way that has helped me and my clients think clearly is by having a conversation that can guide them through diagnosing and defining the system or function that needs to be intervened. To do this systematically I created Sage. Sage is my Voice agent, and her job is to walk you through this exact method in a real, ten-minute conversation and won’t let “kind of a mess” stand as an answer. If a response is too vague, it’ll ask the same question a different way until you land on something specific. It pushes for the one real recent example, maps the dependencies with you, and holds the same hard rule on judgment steps that the method does.

One thing it deliberately doesn’t do: pitch you anything. No tool names, no recommended platform, no “here’s your fix” mid-conversation. Its only job is to get the diagnosis right. It’ll only attach a number to the problem, hours per week, and a dollar figure if you name a rate, if you actually say it out loud yourself. It never invents one.

The Report You Get Back

Before the call ends, Sage reads the whole picture back to you in your own words and asks you to confirm or correct it. Nothing moves forward until you say it’s right.

What comes back isn’t a transcript, it’s a structured report:

• The problem, in your own words. The room, the task, the specific example, how often it breaks, hours a week, exactly as you said them.

• Where the dependency actually breaks, named specifically, not a vague “communication issue.”

• What has to stay judgment, in your words, so nothing gets automated you never agreed to hand off.

• What done looks like, based on the finish line you set.

• The real cost, using only the numbers you confirmed. No invented dollar figures, nothing rounded up to sound worse than it is.

• What’s still open. If something never got specific enough, even after a few tries at asking differently, the report says so instead of quietly filling the gap.

That report is the actual deliverable. Take it to an AI consultant, hand it to your own team to implement, or use it as your build spec if you’re doing this yourself. If you’d like me to review your report and recommend specific tools and solutions, I’m offering a free fifteen-minute assessment. Your report comes with a link you can use to set up that call.

Just Start the Conversation

You don’t need an AI strategy document or a six-month roadmap to get moving. You need one honest look at what’s actually costing you time and money, walked all the way through instead of half-thought. Name the room, cost the leak, split chore from judgment, and prove one fix, whether you run that with a notebook or let Sage hold you to it.

If you’ve got a task that’s been bugging you for months, that’s the one to start with. Talk to Sage, and get the picture in front of you, finally, complete. The fires won’t ever fully go out, but every hour you win back from one is an hour that belongs to the growth you started this for in the first place.

Build smart. Build with purpose. Build to Thrive.

Juan

Subscribe

August was professionally intermittent and family bundled. Soccer with the kids (I still play, believe it or not). Beach in Connecticut. Niantic is nice, if you haven’t been there. Movies, escape rooms, etc. Quality time with my wife and the kids. Feeling blessed.

Somehow, in the middle of all that, Build to Thrive hit #26 Rising in Business on Substack. That one is on you. Your comments, replies, shares, and the constant feedback on what I should dig into next. Thank you. Keep it coming.

I also had three new people join Experience to Authority, the program I started back in March.

That one came from a bunch of conversations with people in corporate and academia who kept telling me some version of the same thing:

I know I can do the work. I just don’t know how to turn what I know into a business.

That’s really the problem we’re solving. What’s the offer? Who is it for? How do you become visible to those people? How do you build authority before you need the sale? And how do you use AI so you’re not creating another job for yourself?

Five weeks. We build the machine together. Then you drive it.

If that sounds like you, check it out here: learn.buildtothrive.co/build-authority

Anyway, I did manage to write in August. 🙂

Nine articles.

Some are about getting your time back. Some about positioning and visibility. Some about building with AI without handing the machine your judgment.

Here they are.

Join me on a journey to scale your business. The Build the Machine subscription gets you started on your pathway to build your AI-Powered Business

Subscribe now

1. Your Business Remembers Nothing

If every new AI conversation feels like starting over, read this one.

Your AI probably doesn’t sound generic because the model is bad. It sounds generic because it has never been handed your business.

Who you serve. What you charge. Why you dropped that service. What you believe. The decisions you already made.

Most of that is still sitting in your head.

Put the important stuff on one page and give it to the machine. Suddenly a new session, a new hire, or a follow-up doesn’t have to start from zero, or from you.

Take it with you: Before asking AI to understand your business, give your business a memory.

Tools: The Business Memory Page. The Quiet Deal Finder. The Repeat Work Audit..

2. Why Building With AI Is Slower Than I Expected

If AI made production faster but somehow the work still isn’t moving, this might be why.

I kept running into a strange contradiction.

The machine could draft something in minutes, yet the project still felt slow.

Eventually I realized the bottleneck had moved.

Old work could hide unfinished decisions inside a six-week build. AI removes a lot of that production time, so suddenly all those decisions are sitting in front of you.

The machine can draft the page.

It cannot decide what you actually want the page to say.

Take it with you: You may not be behind on production. You may be behind on decisions.

Tools: The Decision Debt Audit. Paid subscribers also get the Loop Audit.

Subscribe now

3. Building a Foundational Brain

If your AI is brilliant at 9 a.m. and confused by 3 p.m., read this one.

The problem isn’t necessarily that the model got dumber.

The problem is that nothing in a long conversation is really the boss.

An early wrong turn gets carried forward. Instructions compete. Context piles up. The answers begin to drift.

My fix is surprisingly low-tech: put the important rules outside the chat.

One page. The things that should remain true. Bring it into every session.

Take it with you: The goal isn’t one brilliant AI answer. It’s getting the same good judgment twice.

Tools: The Four-Answer Memory Page. The Session Handoff. The One Sentence. Plus the free Operator Second Brain starter pack

4. How a $379 Bill Survived the AI That Should Have Killed It

If you’re paying a vendor every month because leaving feels scarier than the bill, this one is for you.

I thought this was a story about a $379 monthly charge.

It wasn’t.

It was about what that $379 was buying: the ability to keep operating without discovering who actually owned the domain, customer list, bookings, and other pieces underneath the business.

AI has made rebuilding things dramatically cheaper.

It has not made leaving a vendor safe.

First find the keys. Then decide whether to stay.

Take it with you: Don’t negotiate from fear. Know what you own first.

Tools: The free Keys and Accounts Inventory. Paid subscribers get the Vendor Negotiation Pack.

5. Build a Company of One

If your AI org chart is starting to look like a Fortune 500 company, stop.

Agents are seductive.

Sales agent. Marketing agent. Research agent. Operations agent. Another agent to coordinate the agents.

Pretty soon you’ve recreated the organization you were trying to avoid.

My conclusion: don’t build a swarm.

Start with one seat. Give it a short, testable job. Give it an off switch. Make sure it can actually do the work reliably.

Only then earn the next box on the org chart.

Take it with you: Don’t build the AI company. Fill one useful seat.

Tools: The Agent Org Chart. The Orchestrator Brief. The Agent Job Description.

Credit: Greg Isenberg

6. The Consultant Communication Overhead Trap

If you’re a consultant spending half the week talking about the work instead of doing the work, this one has numbers.

Meet Devon.

Fifteen hours a week disappeared into email, Slack, calendar, and CRM.

Templates helped. Better habits helped. But they still required Devon to operate them.

So I redesigned the problem.

Instead of helping her process communication faster, the system brings her only the three to five calls that actually require her judgment.

She spends about 30 minutes deciding.

The machine handles the rest.

Before: 15 hours a week.

After: 8 hours.

Recovered: 7 hours a week. At $175 an hour, that’s 364 hours a year, or $63,700 in reclaimed billable capacity.

And if some of those hours go into business development, there may be another $38,000 to $63,000 sitting on the table.

She still decides.

She just doesn’t have to sit in every chair.

Take it with you: Don’t automate your judgment. Automate everything that keeps your judgment from getting to the right place.

7. The Problem With AI Is Often That It Answers Too Soon

If AI keeps giving you perfectly reasonable solutions to the wrong problem, read this one.

Tell AI you spend too much time on follow-up and it will happily automate follow-up.

But what if follow-up isn’t the problem?

What if the offer is?

A good mechanic doesn’t replace the tires just because you pointed at them.

So I built a sequence that makes the model earn the right to recommend:

Outcome → Current state → Constraint → Working hypothesis → Economics → Solution

Diagnosis first. Prescription second.

Take it with you: Stop asking AI for solutions before it understands the problem.

Tools: The diagnostic sequence is free. Paid subscribers get the full instruction set.

8. Are you hesitating to leave the corporate world?

If you know you can do the work but don’t know whether anyone will buy it, this one is for you.

That’s the fear I keep hearing from people thinking about leaving corporate or academia.

Usually they aren’t questioning their craft.

They’re questioning the market.

And those are two very different problems.

An offer without a market is still a hope.

So research the buyer while you still have the job. Publish to them. Watch what they respond to. Test the angles. See what gets ignored.

Then make the decision with evidence.

Take it with you: Don’t leave with a vision. Leave with proof that somebody wants what you know.

Tools: Start with the assessment of your background and what is actually marketable. If there’s something there, we build the content and market-intelligence system around it.

Build the Machine members gets my AI content, repurposing and market intelligence agent

Subscribe now

9. The Consultant Proposal Prison

If a good sales call ends and then you lose most of a day writing the proposal, meet Nathan.

Nathan isn’t short of leads.

The problem starts after a good call when somebody says:

Send me a proposal.

In the old version, most of a billable day disappeared into the file. Research. Restating what the prospect already said. Writing. Formatting. Pricing.

AI created another problem: a beautiful finished-looking proposal with a price nobody had actually approved.

So the new system produces two drafts after the call.

One is the honest internal read. No invented price.

The other is the short client-facing page.

Anything the machine doesn’t know stays blank.

Nathan keeps three seats:

The sentence. The price. The send.

Before: Most of a billable day per proposal. Two or three a week. Leftover names waited, and some went cold.

After: About 15 minutes of judgment. Two or three files can be out by late morning.

Take it with you: The machine can write the proposal. It shouldn’t make the promise.

Nine very different problems.

But there’s a thread running through most of them.

The point isn’t to hand your business to AI.

It’s to get clearer about what matters, become easier to find and trust, remove the work that shouldn’t require you, and keep your judgment where it creates the most value.

In the words of Dan Koe, the renaissance is already here.

The people who get crushed will be the ones who treat AI as a religion or as a replacement for their own judgment.

The people who get their time back will keep the craft and let a system run the rest.

Taste. Direction. The yes.

That’s the lab.

Build to Thrive is about helping non-tech entrepreneurs build AI-powered businesses that earn more, serve clients better, and give them more of their time back.

Thank you for reading.

Quick question: What should I write about next?

Juan

Two of my best moments in August. My two son’s goals! Sign them up!

A word on why I write it. I have started four companies, and I am building my fifth: this one, a media company I run almost entirely solo, on a fleet of about thirty AI agents that draft this newsletter, scan my inboxes, prep my client work, and write my morning brief. I am not reporting on this shift from the sidelines. I am living it, and I share what works and what breaks, openly, as I go.

Subscribe now

Contents

• Why advice fails and systems win

• What this Build Sprint Series is

• What consultants and operators should expect

• Mini case: the consultant proposal prison

• 2021 vs 2026

• The machine

• The time impact

• How the Build Sprints work

• Build the Machine

Why advice fails and systems win

Most operators I have sat with do not fail for lack of a good idea, but because the week eats the idea.

You leave a coaching program clear. Six weeks later the clarity is a PDF in a folder. The hairdresser understands cash flow and still cannot build a forecast because every hour is a chair. The baker knows she needs marketing and spends sixty hours at the oven. The consultant knows what matters, but Tuesday is already booked.

In 2021 I founded a business accelerator for solopreneurs and small operators. Hairdressers, plumbers, consultants, photographers, bakers, therapists, service shops, etc. I had the opportunity to work with more than 100 businesses and graduate 47 of them in a 16-week program. We diagnosed. We designed. We handed over frameworks. The advice was sound. However, execution sat around 60 percent. By week six, life got busy. The framework got shelved.

Teaching my first Business Accelerator Cohort. 2021.

“Before the program, I was overwhelmed, too many priorities, constant second-guessing. Within two sessions, I had a clear roadmap… and the confidence to act on it. This wasn’t just guidance. It was a reset.”
Monica G., Creative Agency Founder

During the 90-Day Sprint, we landed two new clients and restructured our core offer. Juan helped us zoom in on what was already working and scale it. I’ve tried other programs. This one actually moved the needle.”
David L., Food Distribution Business

Advice without a system does not stick.

It was in April of 2025 when I decided to start my 5th company, Build to Thrive to work on productizing a system that will help solopreneurs and small businesses see long lasting and scalable results to my coaching and advisory. I had sold my real estate and hospitality business for $35M and thanks to AI the timing was right to build this system.

What this Build Sprint Series is

Last week I described how I helped a Consultant who saw how every client added more communication burden. She couldn’t scale her practice without drowning in coordination overhead. The solution, an AI Chief of staff that helped her prioritize and managed client communications and delivery. You can read it here

This time I am writing about Nathan. Same kind of shop. Different ceiling.

The cases in this series are actual weeks from 2021 or 2026. When the week happened in 2021, the 2026 cut is what that same problem looks like with an AI system installed. When the week is from 2026, the 2021 cut is what the old advice would have delivered. The gap is the series.

If you wer a consultant prior to 2022, you have noticed the big shift. As AI has brought the value and speed of execution and coordination charging by the hour is, for the most part I non-starter. Your client can do much of what you used to do, you now have to charge for the outcome. You judgement has brought you where you are, your ability to deliver long lasting results becomes the value.I addressed this shift in this article How senior operators are charging $3,000 per 48-hour AI project

Meet Nathan: the consultant proposal prison

Meet Nathan

Nathan runs a solo strategy practice. Sharp. Credentialed. Clients like the work.

He is not short of leads. After a good call they ask for the proposal. The call already named the week. The file is supposed to document it. He still loses most of a day writing it.

Two or three leave in a week. Other names who already called wait. Some go cold.

The writing became the ceiling. Not the work.

The week

He hung up. They had said yes to a next step. He opened the notes, then the company site, then last quarter’s proposal that was close enough.

Tuesday went into restating what they had already told him. Objectives he had heard out loud. A timeline he was guessing in the gaps. A price he already knew and still had to type into a clean page.

The PDF left after dinner. One name done. Two more were cooling.

He did this again on Thursday. Friday he chose the file over a call that would have filled next month.

The leftover names did not get a better proposal. They got silence.

2021: the advice

I had seen this shop before. In 2021 we handed operators a template. Six parts. A checklist. A review pass.

The file got clearer. Nathan still wrote every page.

The template improved how he wrote. It still needed him to write.

Advice without a system does not stick. I learned that in the accelerator. We diagnosed. We designed. We handed over frameworks. Execution sat around 60 percent. By week six the framework was a PDF in a folder.

Teaching my first Business Accelerator Cohort. 2021.

What he tried first

Nathan did what most people do now. He put the call into a chat and asked for a proposal.

The page that came back looked finished. Then the afternoon started.

The model wrote a rate nobody had said. It added a workstream he had never offered. He spent the rest of the day checking the draft against what he actually remembered from the call.

So he had a file. In practice he had a first draft to police. That is the old Tuesday with extra steps.

A neat recap of the call is not enough for this. The recap keeps the vibe and drops the commitments. The proposal is built out of the commitments.

2026: what I applied

Same week. We stopped asking the model to invent a document and started asking it to wait for him.

After the call, two drafts are sitting there. Not one.

The first is for Nathan. The honest read. What they said they needed. What they did not say. What is still open. Who in the room can actually say yes. No price on that page. Price on an internal page is how a guessed number leaks.

The second is for the client. Short. Their words for the problem. What is in. What is out. What happens after they approve.

Anything the call did not settle stays blank. A blank is useful. A confident guess is how you send a rate you never quoted.

Nathan does not send either file from the chat. He takes about 15 minutes on three things I will not let a model own.

The sentence. Is this the week they named? The price. He types the number he already had, or the file waits. The send. What they do on Monday if they say yes.

He cuts the extra workstream. He leaves every blank that is still a blank. Then the drafts land in the CRM he already uses, on that client, with links he can open. He sends the client page himself.

Two or three files can leave by late morning. The leftover names get a file the same week. The rest of the day is the work he actually sells.

The system does not replace Nathan. It removes the writing around a file the call already agreed.

I have watched models answer before the week was named. That is the failure mode if those three seats go out unsupervised. The machine writes. He still owns the sentence.

The savings

2021: most of a day per file. Two or three a week. Leftover names go cold.

2026: 15 minutes of judgment on the seats that are actually his.

Recovered: a billable day per proposal, plus the names that used to wait.

Devon’s scoreboard was a rate we could multiply. Nathan’s is the day, and the file.

Send this to the person who has the calls and still spends a day on the proposal.

Share

Build the System. Drive the Machine.

This series is the public half of the work. The Founder membership is how you sit closer to the machine while it is being built.

It is called Build the Machine. $360 a year. It works as a membership into the Build to Thrive ecosystem, which includes: the Vault (more than 200 skills, GPTs, and tools, plus a new one each week), it also includes my content, repurposing and market intelligence system. Then two hours with me to design and give you the tools you need to start driving.

If you feel conducting business is taking too much time, depending on too many manual processes, or losing leverage through scattered workflows. Take the AI Leverage Assessment. It will shed some light into the issues and we can then chat during an initial 15-min to give you some pointers. Click below:

My Time Back

If you prefer to contact me directly, you can message me or schedule a 15-minute conversation. Listen to what’s keeping you up at night, then get one idea, tool, or workflow you can implement this week. No need to go through the assessment.

If it can’t give you a quick solution in 15 minutes, I will get back to you with the answer.

The only ask: If it works, let’s continue the conversation.

Let's connect

Read my Hotel Turnaround Story. At the New Haven Village Suites. Former Residence Inn. 2015

Visit: juansalasromer.com for more information about my programs and assessments.

Share

For years, maybe a decade, you’ve thrived inside a system designed to amplify that excellence. There’s structure. There’s support. There’s a team, clear KPIs, defined roles, and a paycheck that doesn’t require you to figure out the entire business side of things. The corporation handles marketing, sales, pricing, operations. You handle your craft.

And it’s worked beautifully until it hasn’t. Until you started thinking: What if I did this for myself? What if I built something independent? A consulting practice. An agency. A program or course. Something that was mine.

The vision is real. The capability is real.

But somewhere between the vision and the leap, something stops you cold. Not fear exactly, or maybe it is, but it’s a specific kind of fear. It’s not “Can I do this work?” You know you can. It’s deeper than that.

It’s: “Will anyone actually buy it?”

Daniel’s Story

I worked with someone, call him Daniel, who had exactly this problem.

Daniel was brilliant at his craft. He’d spent years building expertise inside a contained environment. And he had big ambitions. He wanted to launch a program. A real offering. Something substantial that could generate income and impact.

We sat down to map it out. I asked him the questions you have to ask: Who’s your buyer? What’s their situation? What keeps them up at night? What uncertainty do they have that you could remove?

He paused.

“I... haven’t really thought about that,” he admitted. “I know my program is valuable. I know I’m valuable. But who exactly am I building this for, and what problem are they actually trying to solve? I’m not totally sure.”

And there it was. The gap. The thing that stops most people cold.

He had an offer. He didn’t have a market.

The Real Problem

This is where most transitions fail.

A specialist leaves corporate with confidence. They have expertise. They have credentials. They have years of proof that they’re good at what they do. So they assume: People will recognize that value and buy from me.

Except that’s not how markets work.

Your expertise doesn’t have inherent value in the market until someone who has a problem recognizes that you solve their problem. And you can’t know that you can’t assume that without testing it.

So what happens? They leave their job. They build something. They invest time, money, and emotional energy. And six months in, they realize: Nobody’s actually buying this. The market wasn’t ready. The positioning was wrong. They were solving the wrong problem, or solving it for the wrong person.

Then they’re scrambling. Back to contract work. Back to looking for another corporate gig. The independence dream stalls.

All because they never validated the offer while they still had a safety net.

Some related articles and videos

How senior operators are charging $3,000 per 48-hour AI project

How Experienced Professionals Are Converting Career Capital Into Independent Income Before AI Reprices Their Expertise

The Fractional Chief Marketing Officer

Going Fractional Series: Portfolio Careers in the age of AI. w/Alen Randall Kittredge, Juan Salas-Romer and Katie Barnes

Going fractional series: AI at work. Rethinking the value of your experience

The Death of the High-Performer: Why Your Mastery is No Longer Your Security

The Case for going Fractional Series - The Fractional CFO

Here’s What Actually Works

What if you could test the market before you quit?

Not in theory. In practice.

Here’s the framework I used with Daniel, and it works:

First, research your buyer. Who are they? What’s their situation? What’s keeping them stuck? Where do they hang out? What language do they use? This isn’t guesswork, it’s research. You ask. You listen. You observe.

Second, build a content machine. This is where it gets interesting. You create a system powered by AI, guided by your thinking that generates weekly content options for you. These aren’t random posts. They’re targeted at your buyer, addressing the uncertainties they have, the problems they face.

Third, publish and listen. You put that content out there. LinkedIn. Newsletter. Substack. Wherever your buyer lives. And you pay attention: Which angles get engagement? Which resonates? Which falls flat? You also ask directly new subscribers and engaged readers: ”What do you want to know more about?”

Fourth, iterate. Based on what the market tells you, you adjust. You explore different angles. Different value propositions. Different ways of framing what you do. You’re not guessing anymore. You’re learning.

The result? You build a body of knowledge. You discover what your market actually wants. You position yourself based on data, not assumption. And all of this happens while you’re still employed. One hour a day. Low friction. Zero risk.

This Chart shows the complete content, repurposing and market intelligence system. With your Founder’s “Build the Machine” Subscription I set this up for you including 2 hours of my time. Click below for more information.

Subscribe now

What Changes

This isn’t just about visibility. It’s not just about “building authority.”

It’s about moving from assumption to validation.

Before: You think your offer is X. You hope the market will want it. You’re anxious about leaving because you’re not totally sure.

After: You know what the market wants because they’ve told you. You’ve tested it. You’ve seen what resonates. You have data, not hope.

And that changes everything.

Daniel went through this. He published content. He watched what landed. He asked his audience directly what they needed. Within weeks, he had clarity. Not just on what to offer, but on who to offer it to and why they’d care.

That clarity is worth its weight in gold. Because now when he does leave corporate, he’s not betting on an assumption. He’s betting on validation.

The Offer

You don’t have to figure this out alone.

This is exactly the work I do in the Experience to Authority Program, I help you move from “I think I have something valuable” to “I know the market wants this, here’s the proof.”

It starts with an assessment. You tell me about your expertise, your ambitions, and where you are today. Then I, along with a few of my buddies, a.k.a. agents, dig into your background to figure out what you know, what people might pay for, and where the strongest opportunity is. You get a report back.

From there, we can work together in a few ways:

1. DIY Route: You get the framework and specs. You build it yourself.

2. Guided Route: I teach you. You implement with my support. I install the content, repurposing and market intelligence system together and you run it.

3. Done-With-You Route: I am deeply involved. I make sure the system works. You feel confident and supported throughout.

All of it is designed to do one thing: Get you market validation while you’re still employed.

The Experience to Authority Program

Your Next Step

Before you commit to anything, take this assessment. It takes less than 5 minutes. You’ll answer questions about your background, your expertise, your ambitions. You’ll get back a clarity report that shows you what’s actually marketable in your experience—and what you might be missing.

Value Clarity Assessment

After the assessment, if it resonates, we can talk. A quick 15-minute call to see if this is the right next step for you.

The goal isn’t to pressure you. It’s to get you data. So you can make a smarter decision about your path forward.

Because hesitating isn’t the problem. Making the jump without validation…that’s the problem.

Let’s get you clarity first.

Juan

Share

Running one of my entrepreneurial cohorts

For more programs, assessments and tools, visit juansalasromer.com

A little more about me…

A word on why I write it. I have started four companies, and I am building my fifth: this one, a media company I run almost entirely solo, on a fleet of about thirty AI agents that draft this newsletter, scan my inboxes, prep my client work, and write my morning brief. I am not reporting on this shift from the sidelines. I am living it, and I share what works and what breaks, openly, as I go.

Subscribe now

There is a strange thing that happens when you ask AI for business advice.

It is almost too helpful.

Tell it, “I spend too much time following up with leads,” and within seconds you have a proposed CRM workflow, three automated sequences, an AI qualification agent, and a list of software you should connect.

It feels productive.

But there is a problem.

Nobody stopped to ask whether follow-up was actually the reason you were losing sales.

Maybe you do not have enough qualified leads. Maybe the leads are good but the offer is wrong. Maybe prospects are interested but there is no clear next step. Maybe your CRM is perfectly capable and nobody uses it consistently.

You complained about follow-up.

AI heard: automate follow-up.

That is the difference between answering a question and diagnosing a problem.

And I think it explains a lot of disappointing AI implementations.

The mechanic who replaces whatever you point at

Imagine taking your car to a mechanic because it shakes at 60 mph.

You say, “I think I need new tires.”

A bad mechanic says, “Absolutely,” and starts replacing them.

A good mechanic asks questions.

When did it start? Does it happen while braking? Is it in the steering wheel or the whole car? Did you hit anything recently?

Then he inspects the car.

Because the customer’s proposed solution is not the same thing as the diagnosis.

We understand this instinctively with doctors, mechanics, accountants, and good consultants.

Yet with AI, we routinely do the opposite.

We tell it:

Help me automate client onboarding.

Or:

Build me an AI sales system.

Or:

I need a better content strategy.

And the machine obliges.

The better the model becomes, the more convincing the answer sounds.

That can actually make the problem worse.

A sophisticated answer to the wrong problem is still the wrong answer.

I realized I was optimizing the prompt instead of the thinking

For a long time, the conventional advice was to write better prompts.

Give AI a role. Provide context. Specify the output. Add examples. Tell it to think carefully.

All useful.

But I became interested in something slightly different:

What if I could change what AI is required to do before it is allowed to give me an answer?

Instead of trying to make the answer better, could I improve the process that produces the answer?

Think about hiring a senior operator.

You would not value her because she can produce longer reports than a junior employee.

You value her because she knows when not to answer yet.

She asks the uncomfortable question.

She notices that the problem you described is probably a symptom.

She wants to know what you have already tried.

She asks what success actually means.

And occasionally she says:

I don’t think that’s the problem we should solve.

That is much closer to how I want AI to work with me.

So I gave AI a process

The framework I ended up with looks roughly like this:

Outcome → Current State → Constraint → Working Hypothesis → Economics → Solution → Measurement

The order matters.

Start with the outcome

“I want to automate sales” is not an outcome.

Do you want more qualified conversations? Higher conversion? Faster follow-up? More revenue? Less founder time?

Those can lead to completely different systems.

Understand what happens today

Before redesigning something, AI should understand what already exists.

What works? Where does the process stop? What requires judgment? What is repetitive? Where are people waiting? Where are they hunting for information?

Otherwise, AI tends to design the business it imagines rather than improve the business you actually have.

Find the constraint

This may be the most important part.

Suppose you have 30 qualified prospects each month but only 12 ever reach a sales conversation.

You could spend months doubling your audience.

Or you could ask why 18 people who were already qualified disappeared.

It is like adding water pressure to a hose with a kink in it.

More water isn’t necessarily the answer.

Find the kink.

Then I added one rule that changed everything

Before recommending a solution, I require AI to state a working hypothesis.

Not a conclusion.

A hypothesis.

For example:

Working hypothesis: The primary revenue constraint is not lead generation. It is inconsistent movement of qualified prospects from initial interest to a sales conversation.

Then it has to answer two more questions:

Why do I think this?

And, more importantly:

What would prove me wrong?

That second question matters.

Without it, AI is remarkably good at constructing an argument for whatever it has already decided.

Humans are pretty good at that too.

Requiring disconfirming evidence changes the conversation from:

“Give me a convincing recommendation.”

to:

“Give me an explanation we can test.”

That is a much higher standard.

Only then do we talk about AI

Here is another rule I built into the system:

Do not assume automation is the solution.

Sometimes the best automation is deleting the task.

Sometimes the process needs to be standardized.

Sometimes the same decision is being made 40 times when it could be made once as a rule.

Sometimes information is scattered across five places.

Sometimes the work simply belongs to someone else.

Only after those possibilities have been considered should we ask what AI can do.

My preferred sequence is closer to:

Eliminate → Simplify → Standardize → Clarify ownership → Automate → Add AI → Build custom technology

It is the business equivalent of not buying a robotic lawn mower before checking whether you actually need to mow that part of the yard.

And building it isn’t enough

This is another place where I think businesses will get AI wrong.

An automation runs successfully.

Everyone celebrates.

But “it ran” tells you almost nothing.

Imagine hiring a salesperson and measuring performance by the number of emails they sent.

That is activity, not value.

The same distinction applies to AI.

I now think about four different states:

BUILT → RUNNING → WORKING → CREATING VALUE

Those are not synonyms.

An AI follow-up system might be built and running perfectly while annoying good prospects and reducing conversion.

A client-onboarding agent might process every client while creating more work for the team fixing its mistakes.

So before building, the system should define what working means.

Maybe follow-up falls from 48 hours to 8.

Maybe founder administration falls from six hours a week to two.

Maybe qualified-lead conversion moves from 12% to 17%.

Now we have something to test.

This is becoming my default way of working with AI

I don’t want AI to agree with me faster.

I want it to make it harder for me to solve the wrong problem.

I want it to challenge assumptions, distinguish facts from hypotheses, look at economics, identify what should remain human, consider how a system could fail, and tell me what evidence would change its recommendation.

In other words, I don’t just want a better answer.

I want a better thinking process before the answer.

So I turned all of this into a reusable set of AI instructions.

It forces the model to begin with three high-value questions, diagnose before recommending, state a falsifiable working hypothesis, test the economics, choose the simplest intervention, separate human judgment from automation, define failure conditions, and establish how we will know whether the result actually worked.

That’s the what.

For paid subscribers, the rest of this article is the how.

🔒 PAID: Install the AI Thinking System

Below is the complete instruction set I use, ready to copy into your AI.

I’ll also show you:

• how to install it

• how to bypass the three questions when you want an immediate answer

• how to make AI interrogate the problem further when necessary

• how to use it to diagnose a real business problem

• and the complete master instruction set

The goal isn’t to make AI give you more answers.

It’s to make it earn the right to give you one.

Subscribe now

🔒 PAID: Install the AI Thinking System

If you made it this far, the useful part is not just understanding the framework.

It is making your AI behave this way by default.

The goal is to create a reasoning layer that sits between your question and the answer.

Instead of:

Prompt → Answer

you get:

Prompt → Clarify → Diagnose → Form hypothesis → Test economics → Recommend → Measure

That changes the interaction completely.

Read more

A word on why I write it. I have started four companies, and I am building my fifth: this one, a media company I run almost entirely solo, on a fleet of about thirty AI agents that draft this newsletter, scan my inboxes, prep my client work, and write my morning brief. I am not reporting on this shift from the sidelines. I am living it, and I share what works and what breaks, openly, as I go.

Contents

Why Advice Fails and Systems Win

What this Build Sprint Series is

What Consultants and Operators should expect

Mini Case Study: The Solo Consultant Communication Crisis

• 2021 vs 2026 Consulting Approach

• The Machine that I build

• AI Impact

How the Build Sprints Work

Why Advice Fails and Systems Win

Most entrepreneurs suffer from a failure of the human operating system. You finish a high-level coaching program feeling energized, only to watch that momentum dissolve into systemic entropy within weeks. The talented hairdresser understands cash flow perfectly yet remains too busy cutting hair to build a forecast. The baker knows she needs marketing but spends sixty hours a week at the oven. You do not lack knowledge. You lack the functional capacity to execute that knowledge while surviving the daily grind.

For 25 years, I’ve launched, developed, grown, failed, and sold businesses across Finance, Real Estate, Hospitality, and Business Education. The most important and painful lesson I learned is this: building systems that automate repetitive tasks is everything. Knowledge without infrastructure is just noise.

In 2021, I founded a business accelerator program designed to help solopreneurs and small business operators—hairdressers, plumbers, consultants, photographers, bakers, service providers—break through the ceiling trapping them. We advised over 100 businesses that year.

Teaching my first Business Accelerator Cohort. 2021

The pattern was identical across every single one: exceptional at their craft but drowning in everything else. These weren’t people who lacked knowledge or ambition. They lacked the systems to stabilize and grow. A consultant knew exactly what to prioritize but couldn’t find the bandwidth to do it. A photographer had great ideas but no system to execute them. A salesperson could close deals but had no follow-up infrastructure. Everyone was building the plane while flying it.

We diagnosed problems, designed solutions, handed over frameworks. The advice was sound. Execution? 60% at best. By week six, life got busy, frameworks got shelved.

The lesson stuck: Advice without implementation infrastructure doesn’t stick.

I stepped back. Built, grew, and exited a business for $35M. Took a year to ask the real question: what if I didn’t have to accept that 60%? What if infrastructure could be built, not just recommended?

In October 2025, I started working with some of the same operators from 2021. This time, I brought AI. The impact was immediate and profound. The problems were identical: time starvation, coordination chaos, growth ceiling. But the solutions were fundamentally different. Instead of frameworks that required discipline and personal bandwidth, we built machines that executed independent of personal effort.

The operators stayed time-strapped. But now they controlled systems that gave them time back.

This is the shift: AI has moved us from “learning what to do” to “building machines that do it for you.” Strategy is no longer something you learn and implement. It’s hard-coded into your business infrastructure. The goal isn’t to become a better manager. It’s to build an independent system that functions regardless of your personal discipline.

What This Build Sprints Series Is

The cases that follow are actual engagements from either 2021 or 2026. When an engagement happened in 2021, the 2026 approach represents what that same problem would look like solved today with AI infrastructure. When an engagement is from 2026, the 2021 approach shows what the old methodology would have delivered. This illustrates the real gap between advice and infrastructure.

If you’re a consultant: AI has fundamentally changed what you can deliver. It’s no longer an hourly charge. It’s outcome-based. Execution time has shrunk dramatically, both for you and your clients. They now expect a machine built that they can take and drive. That changes your pricing, your accountability, and your competitive advantage.

If you’re a business operator: Here are real ideas from operators like you, using AI infrastructure that actually works. These solve business problems that are incredibly common: time loss, cash recovery, customer consistency, demand generation. These aren’t theoretical. They’re from the last eight months of actual work.

Case Study:

Meet Devon: The Solo Consultant Communication Crisis

Devon runs a solo strategy and operations consulting practice. She’s sharp, credentialed, and her clients love her work.

But she’s stuck. She spends about 3 hours a day roughly 15 hours a week across email, Slack, calendar, and CRM managing communication instead of doing client work, sales, or business development.

The real problem: Every new client adds more communication burden. She can’t scale her practice without drowning in coordination overhead. The constant switching, prioritizing, remembering, and following up has become the ceiling on her growth.

2021: The Advice-Based Approach

The solution focused on helping Devon manage communication more efficiently:

• Email batching

• Response templates

• CRM discipline

• Calendar blocking

• Follow-up routines

• Weekly prioritization

The system worked. Communication workload dropped from 15 hours a week to 11 hours. Devon recovered roughly 4 hours a week.

But Devon still had to operate the system herself. She had to keep the CRM current, maintain the routines, remember follow-ups, and decide what needed attention.

The system improved how Devon worked. It still depended on her to keep it running.

2026: The AI System-Based Approach

Same problem. Completely different solution.

An AI Communication System was developed, built around the tools Devon already uses: Gmail + Slack + Calendar + HubSpot integrated into a lightweight AI infrastructure powered by Claude Cowork.

The architecture:

A Chief of Staff Agent handles the coordination work: organizing communication, tracking commitments, preparing context, drafting routine responses, keeping important information current.

Instead of opening multiple tools and figuring out where to start, Devon begins with a prioritized view of what needs a decision, response, meeting preparation, or follow-up.

How Devon operates it:

Each morning, a priority brief surfaces the 3-5 things requiring her attention, ranked by impact. Client status. Pipeline updates. Meeting prep. Everything else is organized and tracked. Devon spends 30 minutes reviewing context and making decisions. The system runs the rest.

Communication workload drops from 15 hours a week to 8 hours. Devon recovers roughly 7 hours a week.

The system does not replace Devon. It removes more of the coordination work around her, plus helps her prioritize her actions to optimize the time she dedicate to achieve her goals.

The Shift: Before and After

All communication flows through one system. Devon is decision-maker only. System manages the coordination. Time: 15 hours/week managing communication → 8 hours/week. 7 hours recovered.

The Time & Money Impact

Devon charges $175/hour.

Time Savings:

• Pre-AI: 15 hours/week in communication management

• Post-AI: 8 hours/week in communication management

• Time recovered: 7 hours/week

Annual Value:

• 7 hours/week × 52 weeks = 364 hours/year

• 364 hours × $175/hour = $63,700/year in reclaimed billable capacity

Potential: If recovered time gets deployed for business development, add $38,000–$63,000+ in new revenue annually. Most operators recover time but don’t have a plan to deploy it strategically.

How This Works: The Build Sprint Methodology

Every engagement follows a five-stage process called the Build Sprint. It’s simple, repeatable, and designed to move from diagnosis to a running system in weeks, not months.

Phase 1: Design + Define + Diagnose

Diagnose. Real listening. We map the actual workflow—not the one you think you have—and trace visible problems back to their root. A solo consultant spending 15 hours a week in email isn’t the problem. The problem is scattered communication across five tools with no priority system. Visible problems are usually symptoms of invisible system failures.

Define. Once we understand what’s broken, we agree on what success looks like. Measurable success. How many hours per week should this reclaim? What’s the financial impact? What would change in your business if this problem disappeared?

Design. We design the system. What agents do we need? Which tools integrate? How does data flow? This is architecture work. The design phase produces a blueprint everyone agrees on before a single line of code is written.

If you decide to Build it, you will get all spec, the design for you to install and drive the machine.

If you decide to build it together, we work on a new engagement for another $999.

If you decide to have me build it including training and setup, we will work on a proposal.

Phase 2: Delivery + Drive

Deliver. We build the system, test it, install it, and train you to operate it. This is execution. The system gets built, not handed off as a framework to implement. You don’t have to figure out how to use it. You don’t have to maintain it yourself. You open it, it works, you make decisions on what it surfaces. This phase typically takes two to four weeks depending on complexity. When it’s done, you have a running machine, not a homework assignment.

Drive. You operate the system forward. This is the part that’s different from 2021. You’re not struggling to implement something new. You’re running something that already works. The system adapts as your business grows. New tools integrate when you need them. Rules evolve based on what you learn. The operator owns the outcomes, and the system runs the coordination work.

This five-stage approach works because it separates the thinking from the doing. It separates the strategy from the infrastructure. It separates what you have to do from what the machine does for you.

Let’s Connect

Schedule a 15-minute conversation. Listen to what’s keeping you up at night, then get one idea, tool, or workflow you can implement this week.

If it can’t give you a quick solution in 15 minutes, I will get back to you with the answer.

The only ask: If it works, let’s continue the conversation.

Let's connect

Read my Hotel Turnaround Story. At the New Haven Village Suites. Former Residence Inn. 2015

Visit: juansalasromer.com for more information about my programs and assessments.

A word on why I write it. I have started four companies, and I am building my fifth: this one, a media company I run almost entirely solo, on a fleet of about thirty AI agents that draft this newsletter, scan my inboxes, prep my client work, and write my morning brief. I am not reporting on this shift from the sidelines. I am living it, and I share what works and what breaks, openly, as I go.

If you want the right AI solution for your business, not just another list? Book a 15-minute call. I will assess your bottleneck and point you to the right system or app that fits. If it needs more digging, I will come back with the answer on a follow-up call.

Let's connect

Editorial

For most of this year I have not been using AI. I have been managing it. There is a real difference, and it took me a while to see it. A tool is something you pick up when you need it. What I run now is closer to a small staff. Something scans the market before I wake up. Something drafts from my own notes. Something checks the numbers and flags what moved. I sit at the top of it, deciding and approving, the way you would with people. I wrote about the first version of this in how I build my AI chief of staff. This issue is the org chart underneath it, and how you build your own, even if the whole company is just you.

Here is the shape, because the shape is the whole idea.

Three findings from the last eight weeks changed how I would build this, and two of them cut against what is being sold. Competence at individual jobs does not add up to a working system. The agent-to-agent coordination layer everyone is selling has the thinnest evidence behind it of any part of the stack. And in the sectors AI touches most, people have stopped starting companies that intend to hire.

Read together they say something specific. Do not build a swarm. Build one coordinator that routes to you, keep every seat short and testable, and accept that you are the part that cannot be automated. Pick the one seat your business needs most this week, and fill only that one.

Juan

26.8 percent, against 6.4 percent down. In sectors most exposed to AI, solo-type business applications rose 26.8 percent from Q1 2024 to Q1 2026 while a construction-and-wholesale comparison group sat flat at negative 0.4 percent. Over the same window, applications in those AI-exposed sectors carrying markers of intent to hire fell 6.4 percent. The growth came entirely from filings with no employer intent. (Mercatus Center, 17 July 2026, on Census Business Formation Statistics and CPS microdata)

Six clusters, twenty-seven papers. An Oxford synthesis across nineteen benchmarks found that failure compounds non-linearly with task length, that sub-skill competence does not reliably compose into end-to-end success, and that adding scaffolding does not uniformly improve reliability. (University of Oxford, July 2026 preprint, not peer reviewed)

Seven of ten. Recent multi-agent coordination architectures whose headline improvement is smaller than the measured run-to-run noise of the same model on the same benchmark. The clean paired contrast came to five percentage points, with a confidence interval crossing zero. (UT Austin and Uber, 15 June 2026 preprint, not peer reviewed)

Zero. How many of the four confident claims my own system handed me last month survived a check. All four traced to real files. All four were wrong. Nothing was invented, which is the harder failure to catch, and it is why an evaluation step is infrastructure and not a nicety.

79 percent. The share of multi-agent failures blamed on specification and coordination rather than the models, quoted all summer as this year’s finding. It comes from a paper published in March 2025. The work is solid and I would have used it, except seventeen months is not recent, and a new date on an old number is not a new number.

Story 1: Your Agents Can Each Pass and the Company Can Still Fail

What is happening. Researchers at Oxford pulled twenty-seven benchmark, taxonomy and audit papers spanning nineteen benchmarks into six failure clusters (July 2026 preprint). Three conclusions matter more than the taxonomy. Failure compounds non-linearly as tasks get longer. Competence at the sub-skills does not reliably compose into end-to-end success. Adding more scaffolding does not uniformly improve reliability. They are careful about where agents have genuinely improved: single-turn tool selection, short web navigation, narrowly scoped coding.

What it means for you. Notice the shape. Agents are good at short, bounded jobs and degrade as the job gets longer and more connected. That is not an argument against an agent organization. It is an argument for how to draw one: short seats with clear edges, not one agent asked to run a whole function. It also kills the common fix. When your setup is flaky the instinct is another layer, another tool, another wrapper. The synthesis says that does not dependably help. Smaller seats do.

The uncomfortable part if you are buying: each piece can demo perfectly and the assembled thing can still fail, because composition is where it breaks. A vendor demo is a sub-skill test.

What I would do this week. Draw the chart above for your own business. Then ask one question of every box: can this be finished in a few steps with a clear end? If not, split it. Do not automate anything yet. Getting the boxes the right size is most of the work.

Story 2: The Coordination Layer Is the Least Proven Part of the Stack

What is happening. Two researchers, one at UT Austin and one at Uber, asked what the multi-agent field had skipped: before you claim your coordination architecture beat another, how much do two identical setups differ by chance? They measured that floor on one model against a retail benchmark, then held the published claims against it. Seven of ten recent coordination architectures report gains below that floor (15 June 2026 preprint). Their own clean contrast came to five percentage points with a confidence interval crossing zero, which means not significant.

What it means for you. Be careful what this says. It does not say coordination is worthless. It says the evidence that elaborate agent-to-agent schemes work is thinner than the marketing, and some of it may be noise. The practical read: the least proven thing you could build right now is agents negotiating with each other, and it is what is being sold hardest.

Which is why the orchestrator in the chart is drawn the way it is. Its job is not to let agents talk. Its job is to take what came back, decide what needs you, and put it in front of you. The value sits in the escalation, and the escalation ends at a human. I have watched my own system hand me four confident wrong answers in a month. No amount of agents conferring would have caught that. I caught it.

What I would do this week. Build one coordinating routine with exactly one job: gather what happened, sort by what needs your decision, hand you a short brief. Do not let anything act on another agent’s output without you in between. Not yet.

Story 3: AI Is Changing What Kind of Company People Start

What is happening. A Mercatus study published 17 July 2026 compared business formation in sectors most exposed to generative AI against construction and wholesale as a control. From Q1 2024 to Q1 2026, solo-type applications in the exposed group rose 26.8 percent while the comparison group sat flat at negative 0.4 percent. Then the finding that reframes it: applications carrying markers of intent to hire fell 6.4 percent in those same sectors, even as total applications rose. Census Business Formation Statistics and Current Population Survey microdata agree.

What it means for you. The story is not that more people are going solo. It is that where AI reaches, the kind of company people choose to start has changed. Fewer are built to hire. More are built to stay one person. That lands on you directly: if your growth plan never included headcount, your org chart is not a metaphor. It is the staffing plan, and the seats get filled with agents or they stay empty.

That is also the honest limit. This is early evidence of a correlation in exposed sectors, not proof AI caused it, and the authors say so. What it does establish is that you are not unusual for planning a company that runs without employees.

What I would do this week. Take your chart and pick the single function that eats the most of your week and needs your judgment the least. Recurring admin, first-draft content, lead follow-up. That is the first seat. One. The point is not a full company by Friday. It is proof that one box can run without you.

Move 1: Draw the chart, then size the boxes. Your functions, an orchestrator, you at the top. Split any box that cannot be finished in a few clear steps. Long connected jobs are where agents fail, so the sizing is the work.

Move 2: Fill the orchestrator seat, and point it at yourself. One routine that gathers, sorts by what needs your decision, and briefs you. Not agents conferring. The escalation to a human is the part with evidence behind it.

Move 3: Stand up one specialist, the highest-drag lowest-judgment one. Give it a job, the access it needs and no more, a place its output lands, and an off switch. If you cannot write those four things down, it is not ready.

Move 4: Put a test on it that can fail. Not “does this look right,” which the system will always say yes to. A number that clears a bar or does not. Resist adding a wrapper when something is flaky. Check what stays in your hands against the six things that should stay human.

None of these needs a developer, and none starts with buying an agent.

PROMPTS

The Agent Org Chart. Walks away with their business drawn as an org chart of functions, an orchestrator, and a human accountability layer, every box sized against the short-and-testable rule and the safest one marked to fill first.

GO TO PROMPT

The Orchestrator Brief. Walks away with the spec for one coordinating routine: what it gathers, how it sorts by what needs a decision, and what it escalates to a human.

GO TO PROMPT

The Agent Job Description. Walks away with one specialist defined before it is built: job, access, output, off switch, and the test that has to pass. If they cannot fill it in, the agent is not ready, and that is the useful answer.

GO TO PROMPT

Run in order they produce three documents: a map, a spec, and one job description. This is the thinking that happens before anything gets built, and it is the part most people skip on their way to a mess.

If you run a business and want to know which seat is costing you most, the free Diagnostic takes fifteen minutes and names your biggest constraint and what it costs. learn.buildtothrive.co/diagnostic. When you want the org chart mapped rather than guessed, Find the Operational Drag is the $999 assessment that walks your operation function by function and tells you which seat to fill in what order.

If you would rather build it with someone, take fifteen minutes with me and we will draw your agent org chart together and pick the first seat.

Let's connect

Check out my Builder’s Store (Work in progress)

…and remember

Build assets. Create freedom. Thrive on your terms.

Juan

Oh…I almost forgot.

Want more free resources? Fifty operators shared the prompts behind the first six months of our AIBlueprint Edition. 50 Creators share their rockstar prompts →

Liked, downloaded and shared by more than 1000 people…you can’t go wrong!

Subscribe now

A word on why I write it. I have started four companies, and I am building my fifth: this one, a media company I run almost entirely solo, on a fleet of about thirty AI agents that draft this newsletter, scan my inboxes, prep my client work, and write my morning brief. I am not reporting on this shift from the sidelines. I am living it, and I share what works and what breaks, openly, as I go.

TLDR

A recurring bill is easy to see and easy to argue about. What the bill is buying is usually invisible, and the expensive part is almost never the amount. It is whether you could leave. The AI make or buy decision.

Last summer I went through my own AI spend line by line, expecting to find one expensive tool I could cut. That is not what I found. The cost was spread across a dozen small automatic things that were each too minor to question on their own. I cut the bill roughly in half without changing any of the work.

What stayed with me was not the savings. It was that I had been paying that bill every month for months and could not have told you what most of it was for. Not because I am careless with money. Because a subscription is designed to stop being a decision.

I thought about that this week reading a thread I have not been able to stop turning over.

The thread

A man in a small town runs a mobile auto-detailing business. He has been paying $379 a month for six years for what he was told is a custom booking system. His nephew opened the developer tools on the site.

The custom booking system is a single script that embeds Square. The service-area map is a screenshot. There is no custom backend at all.

The provider has now quoted him $2,400 for a platform upgrade, after which the monthly goes to $469. Changing the price of a wash package costs $95.

The internet did what the internet does. Ninety-three upvotes and a hundred and sixteen comments, most of them arguing about whether $379 is too much.

What most of the room got right, and why it still misses

The obvious answer is that he is being overcharged, and plenty of people said so. One version of it sat at eighty-two upvotes.

Then something more interesting happened. The top comment of the entire thread, at two hundred and forty-six upvotes, told the nephew not to touch it.

“If you don’t know the answer to this question you are not qualified to be managing it. I would charge a bit more than your current guy. Not messing with it is the least risky option.”

Another, at forty-four: “OP is out of his depth here. So fixated on a few hundred dollars a month he is about to wipe out his uncle’s business.”

Someone pointed out the six years of accumulated search history a rebuild would throw away. Someone else called the nephew “the one who can do it cheaper that the prophecies foretold.”

I want to be careful here, because that camp is right about something real. The instinct to rebuild the thing yourself, now that the tools are cheap, is the second most expensive mistake available in that situation. It is not the first.

The three comments nobody upvoted

Buried under all of it, at single-digit upvotes, three people were having a completely different conversation.

“The 379 a month isn’t really the problem, and neither is the 2400. What he’s paying for is not being able to leave.”

“The biggest issue here is not what your uncle is paying this vendor but that he doesn’t have the keys to his business.”

“The thing I’d check before touching anything is whose name the domain and the business email are actually in. Six years with one provider usually means both sit inside their account, and that is the real leverage, not the booking widget.”

Three people, arriving from three directions, at the same answer. The number is not the problem. The lock-in is the problem, and the number is what the lock-in costs.

None of them wrote down what to check.

The broader pattern

I think this shows up in a lot of operations, and almost never as a website.

It looks like the bookkeeper who has been doing your books for nine years and is the only one who understands your chart of accounts. The scheduling tool your front desk built a workaround inside of. The one spreadsheet that runs your pricing, which lives in an employee’s personal drive. The email list you cannot export in a usable form.

In each case there is a visible number and an invisible dependency, and the operator is looking at the number because the number arrives once a month with a subject line.

Here is the test I have started using on my own business. It is not about cost.

If this provider stopped answering tomorrow, what would I lose that I could not replace in a week?

If the answer is nothing, the bill is just a bill and you can negotiate it like one. If the answer is my customer list, my domain, my search history, or my ability to take a booking, then you are not buying a service. You are renting the ability to keep operating, and the price of that is whatever they decide next year.

Why this matters now

Two things changed at once and they pull in opposite directions.

The cost of rebuilding almost anything fell through the floor. That is real, and it is why the nephew’s instinct is not stupid.

But the cost of a bad migration did not fall at all. Six years of search history, a customer database you assumed was yours, a business email address printed on the side of a van. AI made the build cheap. It did nothing to make leaving safe.

Which means the gap between those two things is now the most expensive place in a small operation, and almost nobody is measuring it.

So should you just rebuild it with AI?

Everyone reading this has already had the thought, so let me take it seriously rather than waving at it.

A weekend and a decent model will get you a booking page. That was not true three years ago and it is true now. The people saying otherwise are defending something.

But look at what the rebuild accomplishes if nothing else changes. The uncle stops paying a provider he could have fired, and starts depending on a nephew he cannot. The lock-in did not go away. It moved, and it moved to the person hardest to replace. That is what the do-not-touch camp is sensing when they say he is not qualified. They are right about the risk and wrong about the reason.

And the same is true of anyone else he brings in, including someone he pays properly. The question is never who builds it. It is whose name is on it when they are finished. Set up inside the uncle’s own accounts, a nephew has done him a favor. Set up inside the nephew’s, he has quietly become the new provider at a better price and worse terms, because now the exit is a family conversation.

This is the make-or-buy call, and the reason it goes wrong is that most operators run it on the whole vendor at once, when the two halves of what they are buying have opposite answers.

The inventory sorts it, because it separates two kinds of line that look identical on an invoice.

Records are the domain, the business email, the merchant account, the customer list, the analytics history. A record is never a make-or-buy decision. You do not build one and you do not really buy one. You get your name on it. That is paperwork, and no model has ever made paperwork happen.

Surfaces are the site, the booking flow, the forms, the page that shows the service area. Those are cheap to rebuild now, genuinely, and getting cheaper. Surfaces are where make-or-buy is a real question.

Once you know it is a surface, three questions decide it

How often does it change? The man in the thread pays $95 to change the price of a wash package. If he does that twice a year it is an irritation. If he does it monthly it is the entire argument. Frequency is what turns a small fee into a structural cost, and it is the question people forget to ask because each individual fee looks survivable.

What breaks if it is wrong? A page listing your service area can be wrong for a day and nothing happens. A booking flow that takes payment cannot. The closer a surface sits to money, the higher the bar for building it yourself, and the more of that monthly bill was quietly buying you insurance.

Can you describe it completely? This is the one people skip and it is the one that decides. AI builds what you specify. If you cannot write down every rule your booking flow follows, including the ones you have never said out loud, you are not ready to make it. You will also not be able to tell whether anyone else built it correctly.

Two yeses and a low blast radius, build it. Anything else, keep buying and negotiate better.

And the sequence matters more than the answer

Own the records first. Then run make-or-buy on the surfaces, at your own pace, from a position where leaving is possible. Rebuild before your name is on the registrar and you have put a new house on land somebody else owns.

And if you bring somebody in to help, that is the thing to settle before they start. Not the price. Whose name goes on what, and what you are left holding when the work is done. Anyone good will find that an easy conversation. The reaction to being asked tells you most of what you need to know.

One more thing the invoice hides. Part of what you pay a provider is not software at all. It is somebody answering on a Saturday when the booking form breaks. If you build, that person is you. Price it before you decide, not after.

What I would do first

Not renegotiate. Not rebuild. Find out what you own.

Before you touch the invoice, sit down for one afternoon and answer a single question for each piece of your operation: whose name is on it?

Not who manages it. Not who set it up. Whose name is on the account.

For the man in the thread, the answer to one of those lines is probably worth more than the entire six years of $379 payments. And here is the part that should be encouraging rather than alarming: two commenters pointed out that his booking history and customer data sit inside Square, not with the developer. His switching cost is almost certainly far lower than it feels. He does not know that, so he is negotiating from a position of fear he may not actually be in.

That is the whole thing. You cannot negotiate a dependency you have not located, and you cannot price a risk you have not named.

The Keys and Accounts Inventory

One page. One afternoon. Whose name is on each line.

This is the procedure the thread never wrote down. It is yours, no email required.

Work through each row. For each one you need three answers: who is named on the account, who can add or remove that name, and what happens to the business if access stops tomorrow.

Here is a fillable sheet you can print and use The Keys and Account Inventory

How to score it

Mark each line OWNED, SHARED, or THEIRS.

You are not trying to get to all-owned. Plenty of THEIRS lines are fine and normal. You are trying to find the ones where THEIRS and business-stops-tomorrow are true at the same time. That intersection is usually two or three lines, and it is the entire negotiation.

The one move after the inventory

Take your THEIRS-and-critical lines and ask for one thing per line: to be added as an owner, not to take it over.

It is a small ask, it is hard to refuse without saying something revealing, and the answer tells you what kind of provider you have. A good one adds you the same week. The response is the diagnostic.

That is the whole free method. If you only do the inventory and nothing else, you are already ahead of the hundred and sixteen people arguing about the invoice.

SOFT NEXT STEP

I am still running this inside my own business, and the lines that came back THEIRS surprised me more than the ones that came back OWNED. I am sharing the parts that break because those are usually the parts other operators need help naming.

Two things tend to happen after someone fills the sheet in.

The first is that one line turns out to matter more than the other eleven, they sort it out themselves, and that is the end of it. That is the sheet doing its job. You do not owe me anything for it.

The second is that the sheet raises a question it cannot answer. You now know what you could stop paying for. You still have to work out which of those you could actually replace, in what order, and whether any of it is worth a month of your attention. That depends on how your week really runs, which parts only work because you are the one running them, and what your own time is worth against the invoice. A checklist cannot see any of that.

If that is where you have landed, let’s connect over a virtual coffee.

Here is exactly what happens in it, so you know before you book anything.

I ask you three questions. What is taking time away from you. Where could you be making more. Where are your customers being served worse than you would like. You pick the one that matters most right now, and we spend the rest of the call on that one rather than surveying all three.

Then, before we hang up, I come back to you with something. A tool, a prompt, a different way to run the thing. Not notes to action later. Something you can use that afternoon.

Sometimes that solves it and there is nothing else to discuss, which is a good outcome and a common one. Sometimes it turns out to be bigger than fifteen minutes, and then we can talk about going deeper with an AI Leverage Assessment. That is your call, at your pace, not mine.

If it is useful, take fifteen minutes with me and we will look at your week together.

Most of the time we find five hours or more sitting somewhere fairly obvious. Sometimes we do not, and I would rather say so than stretch for it.

I am doing these because seeing how other people actually run their week is how I learn what is really breaking out there. If you get something out of it, a sentence I can quote back is more helpful to me than you would guess.

---

Subscribe now

The Vendor Conversation Pack (Paid subscribers)

Six prompts for the part that happens after the inventory.

The inventory is the easy half. It is a list, and lists are calm.

The hard half starts the moment you have to open the conversation. You are asking someone you depend on to give up a piece of their leverage, usually while you still need them, often while you are not certain what you are entitled to. Most operators either send nothing, or send something that reads like an accusation and gets a defensive reply that costs them six months.

These six prompts cover that arc end to end. They assume you have done the inventory and know which two or three lines are THEIRS-and-critical.

Prompt 1: The ownership ask

Read more

I have spent the last week reading the research on where AI actually breaks, rather than where people say it breaks. Three studies, measuring the same thing from different angles, and they agree in a way I did not expect. The failure is not capability. Models are not getting worse at the work. What collapses is consistency, and it collapses in the exact conditions we all work in: long conversations, a lot of context, and a session that has to remember what we agreed twenty minutes ago. I wrote in June about why the tools kept making me busier, and last month about what happens when you stop collecting tools, both pieces This issue hands you three fixes, and none of them is a better prompt.

If your AI output feels inconsistent rather than bad, this issue gives you the one page that makes it steady. If you deliver work anyone pays for, it gives you the sentence to have ready before a client asks whether AI touched it. And if your sessions have been getting longer because everything needs to stay in one place, it gives you the two-minute habit that replaces them.

Leak One: reliability, not ability. Aptitude barely moves as a conversation runs on. Consistency falls off a cliff, and once a session takes a wrong turn it does not recover. The fix is a page, not a prompt, and it takes an hour once.

Leak Two: the window on the label is not the window you can trust. Accuracy drops well before the advertised limit, and whatever sits in the middle of a long brief is the first thing lost. The fix is where you put things, and it costs nothing.

Leak Three: your buyer already suspects. Seven in ten say they would not trust a report made with AI, and the ones who have used the tools are the more sceptical group. The fix is one sentence, written before the question arrives rather than during it.

All three run on the same idea. Nothing inside a conversation is authoritative, so nothing in there can correct a wrong turn once it happens. Reliability has to come from outside the chat, from something you wrote down while you were thinking clearly. It is not a property of the model. It is a property of what the model can check itself against.

Do one of them this week. What you are after is not smarter answers. It is the same answer twice, which is the thing you have actually been missing.

Juan

16 and 112. In over two hundred thousand simulated multi-turn conversations, leading models lost 16 percent of their aptitude and gained 112 percent more unreliability, an average 39 percent drop across six tasks. Capability held. Consistency did not. (Microsoft Research and Salesforce, ICLR 2026)

More than 30 percent. The performance drop when the thing that matters moves from the start or end of your input into the middle of it. Models have primacy and recency bias, exactly like people. (Stanford, TACL 2024)

30 to 50 percent. Accuracy loss across eighteen frontier models measured well before the stated context limit. A 200,000-token window can be unreliable at 50,000. (Chroma, named lab, not peer reviewed)

70 percent. Buyers who say they would not trust a consultancy report prepared using AI, from a survey of 3,887 companies. Among those who have actually used consultants’ AI tools, 77 percent call it a bubble, against 55 percent who have not.

20 to 30 percent. The widely quoted share of the workday knowledge workers supposedly lose searching for information. I went looking for the source and found four different figures from four vendors and one analysis calling it a myth. Directionally true, badly sourced, and I am not using it.

What is happening. Researchers at Microsoft and Salesforce took standard single-turn benchmarks and converted them into multi-turn conversations, which is how people actually work. Every leading model got worse. The average drop was 39 percent across six tasks.

Then they decomposed it, and that is the finding. Aptitude fell 16 percent. Unreliability rose 112 percent. Their conclusion: when a model takes a wrong turn early in a conversation, it does not recover, because nothing in a chat is authoritative enough to correct it.

What it means for you. If your AI output feels inconsistent rather than bad, that is measured behaviour and not your imagination. It also means the common fix is the wrong one, because sharper prompts address ability and ability is not what broke.

Sit with their explanation, because the fix is inside it. Nothing in a conversation is authoritative. Every statement in a chat carries the same weight as every other statement, including the wrong turn taken at minute four. There is nothing for the model to check itself against, so a small early error compounds instead of getting corrected.

Which tells you exactly where the fix has to live. Not in the conversation. Outside it, in something written down when you were thinking clearly, that does not drift as the session gets long. Reliability is not a property of the model. It is a property of what the model can check against.

What I would do this week. Open one document and write four things: what you sell and to whom, how you decide pricing, what makes a client a good fit, and three decisions you have already made and do not want reopened. Paste it at the top of your next session. That document is the authority the conversation does not have. One hour, and it is the highest-return hour in this issue.

What is happening. Two separate findings, same direction. Stanford measured a U-shaped curve: models use what sits at the beginning and end of what you give them and lose what sits in the middle, with more than 30 percent degradation as the important thing moves inward. And the lab Chroma tested eighteen current models and found accuracy dropping 30 to 50 percent well before the advertised context limit.

What it means for you. Two habits are quietly costing you. Running one enormous session all day instead of shorter ones with the context written down. And burying the constraint that matters in the middle of a long brief, where it is the first thing to fall out. The number on the box is a capacity figure, not a reliability figure.

What I would do this week. Put the things that must always be true at the top of the conversation, not in the middle of paragraph nine. And when a session gets long, stop and ask it to write down what has been decided so far, then start fresh with that summary. Two minutes, and it is the difference between a session that holds and one that drifts.

What is happening. Source Global Research surveyed 3,887 companies. Seventy percent said they would not trust a consultancy report prepared using AI. Almost a third said learning a firm had used AI would shake their confidence in that firm.

The part that inverts the expectation: the clients who have actually watched these tools work are the more sceptical group. Seventy-seven percent of those who have used consultants’ AI tools think the technology is a bubble, against fifty-five percent of those who have not. Familiarity lowered trust rather than raising it.

What it means for you. If you deliver work anyone pays for, the question is no longer whether to use AI. It is what you say about it, to someone better informed and less impressed than they were a year ago. Hiding it is not a strategy and confessing everything is not either. What the buyer is actually paying for is a named person who is answerable when the work is wrong.

What I would do this week. Write one sentence you would be comfortable saying out loud if a client asked directly. Not a policy. One sentence. If you cannot write it, that is the thing to fix before the question arrives.

Move 1: Write the four-answer memory page. What you sell and to whom, how you price, what makes a good client, and three settled decisions. One page, one hour, pasted into every session from now on. This is the whole fix for Leak One: the conversation has no authority in it, so you supply one.

Move 2: Move the constraint to the top. Whatever must always be true goes first, never buried mid-brief. This is free and it recovers most of that 30 percent.

Move 3: Break the marathon session. When it gets long, have it write down what has been decided, then start clean with that summary. Long sessions feel efficient and measure badly.

Move 4: Write your one sentence about AI use. Before a client asks, not during. Check it against the six things that should stay human.

None of these needs a developer and none needs a new subscription.

PROMPTS

The Four-Answer Memory Page. Walks away with a one-page description of the business that makes every future session specific instead of generic. Asks the four questions, produces the document, says where to keep it.

GO TO PROMPT

The Session Handoff. Walks away with a clean summary of everything decided in a long session, formatted so it can start the next one. Built for people whose conversations run all day and drift by afternoon.

GO TO PROMPT

The One Sentence. Walks away with a single line they can say to a client about how AI is used in their work, drafted from their own delivery process rather than a template.

GO TO PROMPT

Run in order they cover the same three leaks: what the business knows, what a session remembers, and what the buyer is told.

Operator Second Brain Starter Pack (Free Subscribers)

8 plain text files and a morning routine. That’s it. No software to install, no tool to buy, no architecture to design.

Drop these files somewhere your AI assistant can read them (ChatGPT projects, Claude projects, a local folder your AI tool has access to). Fill them in once. Update them as you go. Read them every morning with AI before you start working.

That’s the whole system. Operator Second Brain

These are notion text files. For our paid subscribers, you can access my Second Brain Prompts at the end of this edition.

Subscribe now

See how your whole business is organized. There are nine moving parts to a healthy business. One is under strain. Most operators fix symptoms instead of finding the real constraint. The Thrive Business System Assessment shows you all nine and helps you find which one matters first. Numbers & Decisions might be it. Or it might be something else. The map shows you. Start at learn.buildtothrive.co/build

Run the AI Leverage Assessment. If you already know the strain is operational drag, time leaks, or workflow bottlenecks, this is the faster path. It shows you the cost of friction and where AI actually helps. Start at learn.buildtothrive.co/mytimeback

The Thrive Business System Assessment. Run this diagnostic to see all nine moving parts of your business and surface which one is under strain. Most operators fix symptoms instead of finding the real constraint. This assessment walks you through each lever—Clarity, Opportunity, Follow-Through—and names where the bottleneck sits. Numbers & Decisions might be it. The Thrive Business System

For our paid subscribers

Read more

The strange part is that nothing broke. No tool or model failed me in a way I could point at, and I have more working parts running now than I planned to have by this point, and I am still behind the date I wrote down. For a few weeks I read that as a discipline problem, which is the read most of us reach for first, and it is usually wrong.

Here is what actually happened, and I think it happens to a lot of people building right now.

The week my own system refused to work

Three weeks running, one of my agents produced nothing.

It is the one that drafts the weekly newsletter. It fires, it reads the research, it checks the inventory, and then it stops and writes a short note that says it is waiting on me to choose the topic. I built it that way on purpose, back in July, after I caught myself reviewing finished editions I had never asked for and rejecting them. So I locked it, on the rule that it does not draft anything until I have chosen the topic myself.

The lock worked exactly as designed. Every week it read the research, found no decision from me, and halted.

What I had built was not a writing bottleneck. It was a mirror. The agent could do the work in minutes. It could not do the one thing the work depended on, which was me deciding what the week was about. Three weeks of a machine sitting still, waiting, while I told myself I was behind on production.

I was not behind on production. I was behind on decisions, and I had never noticed because until this year, my slow execution had been quietly absorbing them.

What speed actually exposed

For twenty five years across five businesses, the gap between deciding something and seeing the result of it was long enough to hide a lot of vagueness. I could say “we should go after that market” and spend six weeks building toward it, and somewhere in week four the decision would finish making itself. The work did the thinking. I did not have to be precise up front, because the time it took to execute gave me room to get precise on the way.

That room is gone. When execution collapses from six weeks to an afternoon, every decision I was half making now has to be whole before anything moves. The vagueness that used to dissolve inside the build has nowhere to go. It sits at the front and blocks the queue.

This is why the build feels slower even while everything measurable about it got faster. I am not producing less. I am hitting the unresolved decision sooner, and hitting it more often, and there is no longer a four week buffer where it quietly resolves itself.

You have probably seen a version of this number: roughly 95 percent of corporate AI pilots produce no measurable return. It comes from an MIT-linked report in August 2025, it has been argued with since, and I would not build a case on it. I mention it because when I read past the headline, most of those stalls are not the model underperforming. They are organizations that automated a process nobody had decided the shape of, so the tool arrived on schedule and the judgment about what it was supposed to do never got made.

I wrote something related last year about what happens to high performers when output stops being the scarce thing. I was looking at it from the employee side then. Running my own build, the same shift showed up from the owner’s chair, and it was less comfortable.

Three signs this is what is happening to you

Not every slow build is this. Sometimes a build is slow because the thing is genuinely hard. A few weeks ago I wrote about how to tell which broken thing in your business is worth fixing first. What follows is the answer I kept getting wrong in my own, for months, with that general version already written down. These are the signals that say the delay is sitting somewhere else.

One. Your output went up and your finished work did not. You are generating more drafts, more versions, more options than you were a year ago, and fewer of them are crossing the line. The pile in the middle is growing. That middle is where undecided things go to wait.

Two. Your tools are waiting on you more than you are waiting on them. Count the number of times this week you opened something, looked at it, and closed it without moving it. If the answer is more than a couple, the constraint is not capacity.

Three. You keep rebuilding instead of finishing. Going back to improve something already built feels like progress and asks nothing of you. Finishing requires a decision you have been avoiding. Rebuilding is the more comfortable of the two, and it is very easy to do for a month without noticing.

If two of those three are true, more speed will not help you. I tried that first. I added capacity to a system whose actual constraint was one person’s unmade decisions, which is a fast way to build a larger queue.

The thing I got wrong for about six weeks was assuming the delay was a capacity problem, so I kept adding capacity. What finally moved the build was going the other direction, and the specific change I made is small enough to describe in a paragraph.

The Decision Debt Audit

This is the exercise, and it takes under an hour. I run it Friday afternoons now.

Step one. List everything currently built and not running. Any process, agent, page, offer, sequence, or asset that exists and is not live. Do not judge it yet. Just get the list.

Step two. For each one, write the sentence that starts “This is waiting on.” Be specific and name a person. “This is waiting on me to decide whether we are still selling the thing” is a real answer. “This is waiting on more time” is not, and if that is what you wrote, you have not found the real blocker yet.

Step three. Sort into four piles.

• My call, and I can make it in five minutes. Make them now, in the session. Most of my eleven were here. This pile is where the build gets unstuck.

• My call, and I need information first. Write down the one piece of information and where it comes from. Not a research project, one specific thing. If you cannot name it in a sentence, the decision is probably in pile one and you are avoiding it.

• Not my call. Send it to whoever it belongs to today, before you close the session.

• No longer needed. Kill it. Some of what is waiting on you is waiting because it stopped mattering and nobody said so. Killing these is the fastest capacity you will find all week.

Step four. Count pile one. That number is your decision debt. Mine was seven the first time I ran it. It is usually one or two now, and the build moves at a pace I recognize.

What paid subscribers get in this piece

The rest of this is the part I could not have written six weeks ago, because I had not fixed it yet.

• The one change that unblocked the build, written out step by step so you can run it this week

• A worked example from inside Build to Thrive, including the three-week halt, what it cost me, and the two decisions that were actually behind it

• Where this goes wrong, the two failure patterns I hit while fixing it

• How to tell a real capacity problem from a decision problem, so you do not apply this to a build that genuinely just needs more hours

• The Loop Audit. Is the exercise I use to walk a single process end to end and find where it stalls. It pairs with this piece directly.

Paid subscribers also have access to my library of more than 200 tools and prompts.

It runs $80 a year, and you can add two hours of my time on an AI project of your choice by subscribing as a Founder.

The change that moved it

I stopped adding to the system and spent one session writing down every place it was waiting on me.

Not every task. Every decision. There is a difference, and the difference is the whole thing. A task is work I have not done. A decision is a judgment nobody else can make, which some piece of already built work is currently parked behind.

I found eleven. I had assumed there were two or three.

Read more

I have spent this year putting AI into my own business one area at a time, keeping track of which areas paid off and which wasted my time. The wins came from three ordinary parts of the business where I had been carrying everything in my head, and where writing it down once helped my scale my business in multiple levels. This is a topic I keep coming back as it has several benefits and it is foundational to any succesful AI operation. Two related pieces you might want to read talk about why the tools kept making me busier, and the value of loops and how I built the daily brief that runs my mornings where I tell that story of my Chief of Staff and how it made me so much more productive. In this particular issue I am going to walk your through three areas where AI pays off first.

Area One: your business remembers nothing. Positioning, pricing logic, how you handle a difficult client, why you dropped a service. Most of it lives in your head, and when it lives there, AI gives you generic output because it is working with nothing about you. New team members restart from zero. So do you, every time you sit down.

Area Two: follow-up runs on mood. Leads go quiet, proposals stall, past clients disappear. Not because anyone decided to drop them, but because following up depends on remembering, and remembering competes with everything else in your week. The fastest place to find money you already earned.

Area Three: the invisible work eats the week. Copying between tools, rewriting the same email, rebuilding a document you have built forty times. It never appears on a plan and it takes most of the day.

The three connect. What lives only in your head cannot be handed to anyone, human or otherwise, which is why the business still runs through you.

This edition will give you the right tips to make AI compound your memory. I hope you enjoy it.

Juan

68 to 77 percent. Small business AI adoption between April 2025 and January 2026, per Intuit’s 2026 AI Impact Report, with generative AI use climbing 40 to 58 percent. It went up, not down.

42 to 28 percent. The decline everyone is still quoting, from a survey fielded April 2025. Fourteen months old as a description of now.

$201.9 billion. Gartner’s 2026 figure for money going into AI that acts on its own, up 141 percent in a year. Spending runs well ahead of anyone checking what it produced.

1 to 15 people. The size of business this issue is written for. Most AI coverage assumes an IT department, which is why so little of it is usable.

95 percent. Big-company AI pilots that stall before going live, per MIT NANDA. Company, not evidence: August 2025, disputed, not peer reviewed.

If you like to know where your business is dragging and its costs, try my AI Leverage Assessment. It will help you diagnose how much it is costing you. If you like to chat afterwards about how to implement a solution, I help you get started with the right direction and tools. You can do it on your own (free), with me by subscribing to Build to Thrive’s founder subscription, or I can do it for you.

Subscribe now

Story 1: Your Business Remembers Nothing, So Your AI Sounds Like Everyone Else’s

What is happening. The most common complaint I hear about AI is that the output is generic. People assume they need a better tool or better wording. Usually the business has never written anything down. Your positioning, how you price, what makes a good client, why you stopped offering that one service. Real knowledge, all in one head.

What it means for you. AI can only work with what you give it. Handed nothing about your business, it returns the average of the internet, which is what generic means. This is also why the business cannot run without you. Knowledge that was never written down cannot be handed to a new hire, a contractor, or software.

What I would do this week. Open one document. Write four things: what you sell and to whom, what makes a client a good fit, how you decide pricing, and three lessons you would tell someone taking over tomorrow. One hour. Paste it at the top of your next AI conversation and watch the output stop sounding like a brochure. Highest-return hour in this issue.

Story 2: Follow-Up Is Where Your Money Is Already Sitting

What is happening. Leads go quiet. Proposals stall. Clients from two years ago, who liked you, have not heard from you since. Nobody decided to let those go. They went because follow-up depends on remembering, and remembering loses to whatever is on fire today.

What it means for you. This is money you already paid to earn. You ran the ads, had the conversations, did the work that made those people trust you. Letting it lapse means paying for the same lead twice. It is the cheapest revenue a small business has and the easiest to lose, because nothing breaks when you drop it. It just quietly does not happen. A warm relationship is also the shortest path to a paid short engagement.

What I would do this week. Put every open relationship in one list with three columns: who, what the next step is, and when. I run mine in three tracks by how warm they are, so the hot ones get worked first and nobody sits in an undifferentiated pile. Then have AI draft the follow-ups from your own notes and send them yourself. The drafting was never the hard part. The remembering was.

Story 3: The Number Telling You to Give Up Is Fourteen Months Old

What is happening. The stat circulating says small business AI use fell from 42 percent to 28 percent in a year. James Presbitero surfaced it in When To Not Build Your Own AI, which sent me to check where it came from. It traces to a survey fielded April 2025. Intuit’s report, running through January 2026, has adoption moving the other way: 68 to 77 percent.

What it means for you. If you tried AI, it did not stick, and you concluded the market was turning against it, the evidence you are using describes a window that closed over a year ago. Adoption did not reverse. The newer numbers suggest most people who quit were doing it alone, with nobody to tell them which part to start with. Different problem, different fix.

What I would do this week. Stop trying to fix everything at once. Pick the one area above where the pain is loudest and give it a single hour. Attempting all nine is how people conclude AI does not work for them. One area, finished, is how it starts paying.

THE PLAYBOOK

Move 1: Write the four-answer memory page. What you sell and to whom, what makes a good client, how you price, and three lessons you would hand your successor. One page, one hour. Paste it into every AI conversation from now on.

Move 2: Put every open relationship in one list. Name, next step, date. Sort by how warm they are. You will find revenue in the first ten minutes, because at least one person went quiet who was ready to buy.

Move 3: Name the task you have rebuilt forty times. The document, the email, the report you make from scratch every month. Write down how you do it, step by step, as if explaining to a new assistant. That written version is what AI can finally take over. Check it against the six things that should stay human before you hand any of it over.

Move 4: Do one area, not nine. Finish one before starting the next. The people who conclude AI does not work for their business are usually the ones who tried everything at once.

Not one of these needs a developer, and none of them need a new subscription.

HELPFUL PROMPTS

The Business Memory Page. Walks away with a one-page description of your business that makes every future AI conversation specific instead of generic. Answers four questions, produces the document, and tells them where to keep it. Open the prompt

The Quiet Deal Finder. Walks away with a list of every relationship that went quiet, ranked by how close it was to money, with a first follow-up line drafted for each. Built for people whose pipeline lives in their inbox and their memory. Open the prompt

The Repeat Work Audit. Walks away with the three tasks you rebuild most often written down as steps, so the work can be handed off. Names which of the three to hand over first and why. Open the prompt

Run in order they cover the same three areas: what your business knows, who it owes a reply, and what it keeps redoing by hand.

Share

HELPFUL TOOLS

• Scattered knowledge? Build memory. Start with the Memory Gap Audit.

• Get it →

• Inconsistent execution? Build workflows. Start with the Operations to Automation Map. 🔒Get it →

• Stalled decisions? Build decision support. Start with the Decide and Deliver prompt. Get it →

• Weak marketing? Build an authority flywheel. Start with the Authority Flywheel Audit. 🔒 Get it →

• Lost revenue? Build follow-up tracking. Start with the Warm Lead Re-engagement prompt. Get it →

• Inconsistent delivery? Build delivery support. Start with the Company Health Diagnostic. Get it →

• Founder dependency? Build a Chief of Staff layer. Start with the Morning Checkin 🔒. Get it →

To unluck the rest of the resources and access our full library of more than 200 prompts, skills and loops

Become a paid subscriber

Build to Thrive just hit #26 Rising in Business on Substack last week

Thank you for reading my newsletter and helping me grow at a pace of 600 subscribers per month. I started this newsletter in April of last year and it is now a resource to more than 5000 entrepreneurs. I would love for you to take the next step by offering a 25% discount over my paid subscription. By becoming a paid subscriber you have access to my library of prompts, workflows and timely content to help you gain your time back, improve your income and have happier customers and stakeholders. All for the price of a latte or capucchino. (Offer valid until August 15th

Subscribe now

A word on why I write it. I have started four companies, and I am building my fifth: this one, a media company I run almost entirely solo, on a fleet of about thirty AI agents that draft this newsletter, scan my inboxes, prep my client work, and write my morning brief. I am not reporting on this shift from the sidelines. I am living it, and I share what works and what breaks, openly, as I go.

If you want the right AI solution for your business, not just another list? Book a 15-minute call. I will assess your bottleneck and point you to the right system or app that fits. If it needs more digging, I will come back with the answer on a follow-up call.

Let's connect

TL;DR

Collecting AI tools won’t change your business. Building systems will. This piece shows you what an AI-powered business actually does that a pile of apps can’t: it remembers so you stop starting from zero, turns one-off prompts into loops that run without you, prepares your decisions so you spend judgment only where it counts, mines your content for what buyers actually want, and stops revenue from leaking in forgotten follow-up. The move is simple: find the one place your business is losing time, money, or momentum, and fix that first instead of buying another tool.

It comes with 8 tools built in, one for each way a business leaks leverage, so you can go from reading to fixing the same day

How to Build you AI-Powered Business

You have ChatGPT open in a tab right now. Maybe Claude too.

You use it to write emails, summarize the occasional document, or brainstorm a post when you get stuck. All of that is useful, but it may not change how the business operates. At the end of the week, the same work is still piling up, the same opportunities are slipping through, and ChatGPT has become a faster assistant sitting on top of an unchanged business.

If that sounds like you, you are not doing it wrong. You are just early. And you are asking the question almost everyone asks first: “What tools should I use?”

Natural question. Also a small one.

An AI-powered business uses technology to improve how the company remembers information, follows through on commitments, prepares decisions, and learns from its work. Writing an occasional email with ChatGPT may save a few minutes, but the larger benefit comes when AI becomes part of the way the business operates.

1. Stop chasing tools, start looking for leverage

A better place to begin is the part of the business that repeatedly wastes time, loses money, delays decisions, or allows opportunities to stall. Adding AI before understanding that problem may only accelerate an ineffective process. Identify what is breaking first, then decide what kind of system could improve it.

2. Build a memory your business can query

Most small operations have a memory problem. Important information is scattered across email, voice notes, calendar events, meeting notes, CRM fields, proposals, documents, DMs, and the operator’s head.

The consequences appear throughout the business. Important details from a prospect may be buried in an old email, a client request may never make it out of the meeting notes, and a useful audience question may disappear in the comments. Even strategic decisions can resurface months later when nobody records why they were made.

This is not an organization problem. It is a growth problem. A business without memory keeps starting from zero.

A useful business memory should make it easy to retrieve what a client cared about, what the company promised, which objections keep appearing, and which decisions have already been made. It should also show what is still unresolved and who is responsible for the next step.

This does not mean AI makes the decisions. It means the business remembers enough for you to make better ones.

3. Stop feeding the vending machine

Many people use AI like a vending machine: enter a prompt, collect the answer, and move on. That can save time, but the process disappears as soon as the task is finished.

There are three useful levels to understand.

A prompt handles a single request. You define the goal, evaluate the answer, and continue working. It is appropriate for one-time tasks such as drafting an email or summarizing a call, but it does not create a repeatable process.

A skill preserves the instructions behind a useful prompt so the same type of work can be completed consistently. Instead of explaining the task again each time, you solve the process once and improve it as you use it.

A loop, or workflow,, connects that skill to a trigger and a follow-through process. An event occurs, the skill prepares the work, the system tracks what should happen next, and you step in when the task requires judgment.

These levels build on one another. A useful prompt can become a skill, and that skill can later operate inside a loop. The prompt is not discarded. It becomes part of a more dependable system.

Consider a simple sales loop. A prospect completes an assessment, AI summarizes the responses and identifies the likely bottleneck, and a call brief is prepared for review. You lead the conversation, while the system captures the next steps and tracks the follow-up afterward.

The value comes from the full loop, not from any single prompt.

Our paid subscribers gain access to our full library of prompts, skills and loops you can

4. Protect your judgment, do not delegate it

Many operators already have enough information. The harder problem is deciding what to do with it.

A prospect may deserve another follow-up, but the previous conversations need to be reviewed first. A new product idea may sound promising, but it still has to be compared with existing priorities. Pricing changes, workshops, client engagements, and automation decisions all require context.

AI can prepare these decisions by summarizing the situation, comparing options, retrieving previous decisions, identifying missing information, and surfacing potential risks.

Some decisions should not be delegated. The final decision still belongs to the operator.

Pricing, positioning, client diagnosis, product promises, offer strategy, and major tradeoffs carry consequences that should not be delegated automatically. AI is most useful when it handles the preparation, allowing you to spend your judgment where it matters

5. Turn content into a learning loop

Content is usually treated as a marketing activity. Publish the post, send the email, look at the results, and start again.

An AI-powered business can use content as a source of market intelligence. Comments, replies, workshop questions, email responses, and sales objections reveal where people are confused, which problems keep appearing, what they want to learn, and how they describe those problems in their own words.

Most of these signals disappear because nobody captures them consistently.

AI can help collect and organize that information before it is lost. A useful comment may suggest an article, while several related questions may point toward a workshop. Recurring objections can improve an existing offer, and patterns from client work can support a case study, service, or digital product.

Once those signals are captured and reviewed, content becomes part of the learning loop. The business listens to the market, creates something in response, observes the reaction, and uses what it learns in the next cycle.

6. Plug the revenue leak in your open loops

A considerable amount of potential revenue disappears during follow-up. The problem is usually not a lack of interest or effort. It is the absence of a reliable system for managing open loops.

A prospect asks you to circle back in two weeks. A client requests something after a call. A partner suggests reconnecting the following month, or a reader asks a question that could lead to a useful conversation. Once the day becomes busy, those commitments are easy to forget.

An AI-powered business tracks its open loops. The system should show who is waiting for a response, what was promised, when the last contact occurred, and who owns the next action. It should also distinguish an active opportunity from one that has been parked, abandoned, or left overdue.

Many viable opportunities are lost because the next step depends on someone remembering it at the right moment. The prospect may still be interested and the relationship may still be developing, but the conversation stops because the open loop has no clear owner.

7. Make every engagement compound

Client delivery has consequences beyond the work completed during a single meeting. It affects trust, future decisions, and what the business learns from the engagement.

AI can support delivery by preparing for calls, summarizing sessions, recording action items, tracking progress, and identifying patterns across the work.

Before a coaching or advisory call, the system can assemble the client’s history, previous decisions, unresolved questions, and likely priorities. Afterward, it can record what was decided, what each person agreed to do, and which issues need to carry into the next conversation.

Patterns may also emerge across several clients. A problem that appears repeatedly could lead to a guide, workshop, productized service, or digital product.

The client benefits because fewer details and commitments are lost. The business benefits because each engagement contributes to future frameworks, offers, products, and content.

An AI-powered business compounds when delivery becomes part of a learning loop rather than an isolated transaction.

8. Add a Chief of Staff layer

As the amount of information grows, another report is unlikely to solve the problem. What the operator needs is a concise daily operating brief.

A useful AI Chief of Staff should identify what deserves attention, what may be at risk, and which commitments are waiting for a response. It should separate urgent work from tasks that can wait and highlight the one to three priorities that should not be displaced.

A dashboard presents data. A Chief of Staff brief interprets that information in the context of the workday and helps the operator decide where to focus.

The purpose is not to create more activity. It is to reduce the time spent sorting through information before meaningful work can begin.

9. Find your bottleneck

One part of your business probably felt more familiar than the others.

Perhaps important information is difficult to retrieve, or follow-up still depends on memory. Your content may be disconnected from your offers, while client delivery continues to depend too heavily on you. Decisions may stall because the necessary context is scattered, or the business may keep building from internal ideas without learning enough from customer signals.

Start with the problem that creates the greatest recurring loss of time, money, or momentum. Here is a tool I give clients to help them diagnose bottlenecks AI Leverage Assessment.

Instead of asking which AI tool to adopt next, identify the part of the business that needs to become easier to manage, more consistent, or less dependent on manual effort.

Once the bottleneck is clear, select the resource that addresses that specific problem. Some resources are available to all readers, while others are included with a paid subscription.

• Scattered knowledge? Build memory. Start with the Memory Gap Audit.

• Get it →

• Inconsistent execution? Build workflows. Start with the Operations to Automation Map. 🔒Get it →

• Stalled decisions? Build decision support. Start with the Decide and Deliver prompt. Get it →

• Weak marketing? Build an authority flywheel. Start with the Authority Flywheel Audit. 🔒 Get it →

• Lost revenue? Build follow-up tracking. Start with the Warm Lead Re-engagement prompt. Get it →

• Inconsistent delivery? Build delivery support. Start with the Company Health Diagnostic. Get it →

• Founder dependency? Build a Chief of Staff layer. Start with the Morning Checkin 🔒. Get it →

To unluck the rest of the resources and access our full library of more than 200 prompts, skills and loops

Become a paid subscriber

Want the right tool for your business, not just another list? Book a 15-minute call. I will assess your bottleneck and point you to the tool or system that fits. If it needs more digging, I will come back with the answer on a follow-up call

15-min tool delivery

This is the work behind Build to Thrive

This is why I do not start with AI tools when I work with a business. I start by finding the bottleneck.

AI is not the strategy. AI multiplies the way the business already works. If the process is unclear, AI produces unclear output faster. If follow-up is broken, AI sends more messages without building trust. If the offer is weak, AI writes better copy for a weak offer. If the business has no memory, AI keeps starting from zero.

But give it clear loops, clear decisions, clear ownership, and useful memory, and AI becomes leverage.

That is the work I am building at Build to Thrive: helping operators build AI-powered businesses that create more revenue, profit, and time.

Where to start

You do not fix this with another tool. You fix it at the bottleneck. The AI Leverage Assessment tells you which part of your business is losing the most time, money, or momentum, and which one to redesign first.

Take it here: Find your bottleneck

Let me know what you think of this content, I would love your feedback in the comments section.

Thank you reading. Feel free to share it!

Share

Oh…I almost forgot.

Want more free resources? Fifty operators shared the prompts behind the first six months of our AIBlueprint Edition. 50 Creators share their rockstar prompts →

Liked, downloaded and shared by more than 1000 people…you can’t go wrong!

In this edition you will walk away with one number that tells you whether your AI is an asset or a leak: cost per outcome. You learn why 70% of agents fail in production (no stop condition) and how to fix it. You get a simple follow-up rhythm that stops opportunities from disappearing. Three prompts you can use today: an outcome cost calculator, a stop-condition builder, and a follow-up rhythm designer. You understand why “my AI made more stuff” is not the same as “my AI made me money,” and the exact moves to close that gap before you spend another dollar automating.

Free mega resource for our readers

50 Creators Shared Their Rock-Star Prompts. Here They Are

EDITORIAL

Your AI made the output faster. That does not mean it made you richer. 93% of businesses report AI improved production. 57% still cannot show ROI that beats the spend. The gap is in one number: cost per outcome. This week we show you how to measure it.

Last week, we introduced the Thrive Business System: nine parts of a healthy business grouped into three clusters. This week we go deep on one: Numbers & Decisions. It is the lever that sits between “my AI made more stuff” and “my AI made me money.”

Here is what Numbers & Decisions means: the business can see what is actually working and make better decisions about what to fix next. When it is weak, the founder operates on gut feel. When it is strong, the numbers tell the story.

If you are an operator running AI work and seeing output up but margins flat: you need Numbers & Decisions working. If you are a consultant packaging AI-leveraged offers: you need it to price by outcome, not by input. If you are a founder automating a bottleneck: you need it to tell you whether the bottleneck was designed wrong first.

Three practical questions close the gap: What did the AI work cost? When should the loop stop? Which opportunities are worth following up on?

The numbers that tell you whether your AI is an asset or a leak.

Juan

BY THE NUMBERS

The gap between AI output and AI return is measurable. Here is what that gap looks like in five numbers.

1. 93% of businesses report AI improved their output. 57% still cannot show a return that beats the spend. The gap between more output and more return is the whole game. Domino Data Lab, State of AI 2026 — verify exact figures before publish

2. Agent workflows cost 19 to 50 times more than a single model call. The variance comes from context window size, retrieval complexity, and how many steps the agent needs to take. One run might cost $0.10. The next run on the same task costs $5. Pricing off an average misses the gap entirely. Atlan

3. In cost breakdowns for AI workflows, model tokens typically represent 8 to 27% of total expense. Infrastructure, retrieval, storage, and human review make up the rest. Optimizing tokens alone leaves 73% of cost unaddressed.

4. Agent systems in production often encounter reliability issues when designed without clear stop conditions and validation gates. The problem is usually not the model. It is that the operating loop was never designed with reliability in mind.

5. Most sales opportunities are not lost to rejection. They are lost to no follow-up. A simple rhythm beats a complicated CRM nobody uses.

SIGNAL

Output and Return Are Not the Same Thing

The gap is real, and it is expensive. While most organizations report AI improved their output, fewer can demonstrate that AI improved their return. There is a measurement gap, and it is costing money.

Why it matters: Faster work does not automatically mean richer work. Your AI made the task faster. That does not mean it made you more money. The gap sits in Numbers & Decisions, the lever that shows what is actually working. Most operators never measure it.

What I am observing: The operators closing this gap first do one thing different. They price AI-leveraged work by outcome, not by input. Petri Salonen has written about this: the cost per run varies wildly depending on model load, retrieval complexity, and what the AI actually uses. Pricing off the average is how you automate yourself into a loss. The fix is not faster AI. It is outcome-based pricing.

Stop Conditions Come Before You Scale

Many AI agents fail in production. Not because the model is weak, but because the operating loop was never designed with reliability in mind.

Why it matters: An agent without a stop condition is a loop without an exit. It will run until it costs you. The real fix is not better prompts. It is better design. Two things matter: an eval gate that asks “is this output worth keeping” and a stop condition that asks “should we keep going.” Those happen before you let AI run it at scale.

What I am observing: The operators building reliable systems do this backwards from the usual AI workflow. They design the operating loop first. They test the stop conditions with small batches. Then they let AI run it. The difference between that approach and “just turn on the agent” is the difference between “output worth keeping” and “output that costs you.”

Story 3: Relationships Die in Silence, Not Rejection

Most opportunities disappear because nobody followed up. Not because the opportunity was bad.

Why it matters: An opportunity without a rhythm becomes an opportunity that gets lost. A follow-up rhythm is simpler than it sounds: who owns it, when does it happen, what is the next step. The business keeps it moving.

What I am observing: The operators who win this stop buying CRM software and start designing a rhythm. AI can help send the message, summarize the call, surface what is stale. But AI only helps after the rhythm is designed. Bolt AI onto scattered follow-up and you get faster scattered follow-up.

THE PLAYBOOK

Measure outcome cost, not input cost.

You need one number that tells you whether the AI work paid for itself. Build that number this week. It rewrites how you price and what you automate next. The number is cost per successful outcome, not cost per token or per run.

Design the stop condition before you scale the loop.

Ask: when should this agent stop running? When the output is unreliable. When we have spent enough. When the job is done. Design that exit before you let it run. Then the loop is worth multiplying. More on loops in this article: Why Your AI Is Making You Busier: The 6-Part Framework for Real Delegation

Move 3: Own the follow-up rhythm.

Pick one day a week. Pick who owns it. Pick what “next step” means. The rhythm keeps the relationship moving. Everything else is noise.

Move 4: Let the numbers decide what to fix next.

Your business has multiple moving parts working together. Most operators fix the one that screams loudest. The numbers show you which one actually holds everything back. Fix that first. That is the difference between activity and leverage.

Three prompts to measure and design what works this week.

You walk away with a spreadsheet that shows the real cost of one AI-leveraged workflow. Input: task description, model used, success rate, cost per run. Output: cost per successful outcome and the threshold for profitability. This is the number that changes your pricing.

GO TO PROMPT

You walk away with a two-part test for any agent: (1) how do we know this output is worth keeping, (2) when do we stop the loop. Without these, the loop runs until it costs you. This is how reliability gets designed in.

GO TO PROMPT

You walk away with a repeatable rhythm: cadence (weekly, bi-weekly), owner (who is responsible), next step (what moves the relationship forward), and how to surface what is stale. This is how opportunities stop dying in silence.

GO TO PROMPT

The three prompts are the three redesigns that come before you multiply with AI. Cost clarity, loop reliability, and relationship rhythm. Together, they close the gap between output and return.

B2T Prompt Vault — Own the prompts you use instead of chasing new tools. This week’s three prompts live here: outcome cost calculator, stop condition builder, follow-up rhythm designer. These prompts work inside Claude, ChatGPT, Notion, or your internal company drive. Save them. Use them. Build your library. Learn.buildtothrive.co/vault

Petri Salonen — Business Models in the AI Era. Salonen names the exact problem: the cost per run varies wildly, and pricing off averages fails. His work is the proof that Numbers & Decisions is the lever holding back ROI for operators scaling AI work. Read his latest on Business Models in the AI Era

See how your whole business is organized. There are nine moving parts to a healthy business. One is under strain. Most operators fix symptoms instead of finding the real constraint. The Thrive Business System Assessment shows you all nine and helps you find which one matters first. Numbers & Decisions might be it. Or it might be something else. The map shows you. Start at learn.buildtothrive.co/build

Run the AI Leverage Assessment. If you already know the strain is operational drag, time leaks, or workflow bottlenecks, this is the faster path. It shows you the cost of friction and where AI actually helps. Start at learn.buildtothrive.co/mytimeback

The Thrive Business System Assessment. Run this diagnostic to see all nine moving parts of your business and surface which one is under strain. Most operators fix symptoms instead of finding the real constraint. This assessment walks you through each lever—Clarity, Opportunity, Follow-Through—and names where the bottleneck sits. Numbers & Decisions might be it. The Thrive Business System

Thank you for reading.

Juan

Some news I want to share before you go.

Build to Thrive just hit #26 Rising in Business on Substack last week

Thank you for reading my newsletter and helping me grow at a pace of 600 subscribers per month. I started this newsletter in April of last year and it is now a resource to more than 5000 entrepreneurs. I would love for you to take the next step by offering a 25% discount over my paid subscription. By becoming a paid subscriber you have access to my library of prompts, workflows and timely content to help you gain your time back, improve your income and have happier customers and stakeholders. All for the price of a latte or capucchino. (Offer valid until July 31st)

Subscribe now

Thank you for reading my newsletter and helping me grow at a pace of 600 subscribers per month. I started this newsletter in April of last year and it is now a resource to more than 5000 entrepreneurs. I would love for you to take the next step by offering a 25% discount over my paid subscription. By becoming a paid subscriber you have access to my library of prompts, workflows and timely content to help you gain your time back, improve your income and have happier customers and stakeholders. All for the price of a latte or capucchino. (Offer valid until July 31st)

Subscribe now

TL;DR

Your business may feel broken because you are fixing symptoms instead of the real constraint. The Thrive Business System helps you find the weak point across 9 business levers grouped into Clarity, Opportunity, and Follow-Through. Traditional organizations add people, tools, and processes to manage complexity. AI-native businesses first redesign how workflows, then use AI to multiply what works. The goal is a business that earns more, runs smoother, and depends less on you.

Most founders do not wake up thinking, “My business model has a structural constraint.”

They wake up thinking:

Why am I still involved in everything?
Why are good opportunities not moving?
Why are clients happy with the work, but the delivery still feels messy?
Why did we buy another tool and still end up with the same problem?

That is usually how business problems show up.

Not as a clean diagnosis.
As friction.

A lead goes quiet. A proposal stalls. A client asks for an update that should have already been sent. A team member waits for the founder to make a decision. A new AI tool gets added, but the work does not really get better.

So the instinct is to fix what is loudest.

Work harder.
Hire someone.
Buy software.
Add automation.
Try another AI tool.

For a while, that feels like progress.

Then six months later, the same strain comes back in a different form.

That happens because the problem you noticed first was probably not the real problem. It was a symptom.

And this is the lesson I now lead with:

You cannot create leverage by speeding up a broken process.

Bolting speed onto chaos is not leverage

AI has made this problem more urgent.

A lot of businesses are not redesigning the work. They are just automating the work they already have.

That sounds efficient until you realize the process being automated should not exist in its current form.

If follow-up is scattered, AI can help you send messages faster. But the deeper issue may be that nobody owns the relationship pipeline.

If content feels generic, AI can help you publish more. But the deeper issue may be that the business has no clear point of view, no buyer language, and no visible proof.

If client delivery feels chaotic, AI can summarize meetings and draft updates. But the deeper issue may be that the client journey was never designed.

Speed helps only after the work is worth multiplying.

Otherwise, you do not get leverage. You get a faster mess.

The three questions I use to read a business

When I look at a business, I do not start with tools.

I start with three questions:

Clarity: Do we know what matters?
Opportunity: Can we create the right opportunities?
Follow-Through: Can we follow through consistently?

Every company is answering those questions all the time, whether the owner has named them or not.

When a business feels heavier than it should, one of those questions is usually weak.

The Thrive Business System breaks those three questions into nine parts.

Not as a checklist.
As a diagnostic map.

The point is not to label the business. The point is to find where the real strain is coming from before you spend more time, money, or energy fixing the wrong thing.

Clarity: Do we know what matters?

Clarity is where the business remembers, focuses, and decides.

Without clarity, everything downstream gets harder.

1. Business Memory

Business Memory is the shared context your company runs on: positioning, offers, clients, decisions, voice, lessons, processes, and operating knowledge.

When this is weak, everything lives in the founder’s head.

The founder repeats the same explanations. Client context gets lost. Content sounds generic. Every new project starts from scratch.

This is also why AI often disappoints. If the business has no reliable memory layer, AI has nothing specific to draw from. It produces generic output because the business gave it generic inputs.

2. Priorities and Rhythm

Priorities and Rhythm is how the business decides what matters now and keeps it moving.

When this is weak, everything feels urgent. The founder becomes the traffic controller. Important work gets buried under reactive work. Projects start, stall, restart, and then get replaced by the next urgent thing.

This is where founder dependency often lives.

Not because the founder is bad at delegation, but because the business has no rhythm that allows the right work to move without constant intervention.

3. Numbers and Decisions

Numbers and Decisions is how the business sees what is working and what is slipping.

This does not need to be complicated.

For a solo operator, it might be a simple view of leads, sales, delivery load, time leaks, and cash. For a larger business, it may include margins, financing, capacity, client experience, and capital allocation.

When this is weak, the business runs on instinct.

Revenue may be growing while margin is shrinking. Clients may be satisfied while delivery is becoming too heavy. The founder may feel busy without knowing which activity is actually creating value.

Clarity creates direction.

Without it, you may be working hard in the wrong direction.

Opportunity: Can we create the right opportunities?

Opportunity is where the business understands the market, earns trust, and makes it easy for the right people to take the next step.

4. Market and Client Insight

Market and Client Insight is how the business listens.

When this is weak, messaging runs on assumptions. Offers are built from the inside out. Content does not connect. Sales calls reveal the same confusion over and over.

The business misses what buyers are actually saying because nobody is capturing the questions, objections, language, and signals already coming from the market.

A business grows stronger when it listens carefully.

5. Reputation and Visibility

Reputation and Visibility is how the market comes to see what you know and why you are credible.

A lot of operators have real expertise that the market never sees.

They are good at the work, but invisible to the people who would value it. Referrals depend too much on personal relationships. Content is inconsistent. Buyers do not understand why they should trust them before the first conversation.

Visibility is not just posting more.

It is turning experience, proof, ideas, and perspective into public assets that make trust easier to build.

6. Offers and Next Steps

Offers and Next Steps is how the business turns interest into action.

When this is weak, people may respect you but still not know how to work with you.

Calls end without a next step. Proposals are too custom. Pricing feels improvised. Content creates attention but does not create movement.

A good offer makes the next step feel obvious and valuable.

Opportunity creates demand.

But the order matters. Visibility without clarity just broadcasts a confused message more loudly.

Follow-Through: Can we follow through consistently?

Follow-Through is where the business keeps relationships moving, delivers well, and reduces the friction behind the scenes.

7. Relationships and Follow-Up

Relationships and Follow-Up is how the business keeps important conversations alive.

When this is weak, leads go quiet. Proposals stall. Past clients are forgotten. Referrals never get followed up. Good opportunities sit in inboxes, notes, or memory with no next step.

Most opportunities are not lost because of rejection.

They are lost because no one followed up.

A simple follow-up rhythm is often more valuable than a complicated CRM nobody uses.

8. Client Experience

Client Experience is how the business delivers in a way that feels clear, professional, and trustworthy.

When this is weak, the final work may still be good, but the process feels improvised.

Onboarding is unclear. Updates are inconsistent. The client has to ask what happens next. The founder keeps stepping in to rescue the experience.

Great delivery makes clients feel guided, not managed.

9. Back Office and Admin

Back Office and Admin is the invisible work that keeps the business running.

Documents. Handoffs. Inboxes. Calendars. Internal requests. Repeatable tasks. Small administrative steps that do not look strategic until they start consuming the capacity needed for growth.

When this is weak, tools pile up. Processes go undocumented. Work gets copied manually. The business feels heavier than it should.

Many “people problems” are actually design problems.

The issue is not always the team member. Sometimes the work was never structured for delegation.

Follow-Through creates trust, delivery, and results you can repeat.

The loop matters

These nine parts are not separate boxes.

They move in a loop.

Clarity creates direction.
Opportunity creates demand.
Follow-Through creates trust, delivery, and repeatable results.

Then the loop feeds itself.

Follow-Through produces learning.
Learning improves Clarity.
Better Clarity creates better Opportunity.
Better Opportunity requires stronger Follow-Through.

That is why fixing one visible problem often fails.

A business weak in Clarity cannot always be repaired with more marketing. A business drowning in delivery issues may be carrying a weak offer, unclear priorities, or missing business memory. A business struggling with sales may not need a louder funnel. It may need better follow-up, clearer proof, or a simpler next step.

The map helps you see not only where the strain is, but where it may be coming from.

Where AI actually fits

AI is not a tenth part.

It is not the strategy. It is not the operating system.

AI is what you apply after you understand the business, find the strain, and redesign the work underneath it.

The sequence matters:

Understand the business.
Find the part under the most strain.
Redesign the work so it is worth doing.
Then use AI to improve the outcome, speed, quality, or consistency.

Run that sequence backward and you get automation without leverage.

Leverage is the mechanism. A better business and a better life for the person running it are the outcomes.

A real example

I learned this the hard way.

I inherited a management-intensive Section 8 housing portfolio. It had high friction, high founder dependency, thin margins, and too many moving parts.

The instinct would have been to work it harder.

More oversight.
More chasing.
More people solving the same recurring issues.

But the real strain was not demand.

The strain was in the operating model itself: Priorities, Follow-Through, and the way the work was structured.

So we redesigned the work and repositioned the portfolio into scalable middle-market multifamily.

Over time, that led to 134 units and a 112-key hotel repositioned, more than $8 million in investor capital raised and leveraged 4x, and 20 percent plus IRR across the portfolio. The work was later recognized by the Greater New Haven Chamber of Commerce. More on this story

I did not have this map written down at the time.

I have spent the years since turning what worked into something repeatable, so the next operator does not have to learn it one expensive mistake at a time.

How to use this map this week

You do not need a consultant to start.

Ask yourself three questions:

Do we know what matters?
Can we create the right opportunities?
Can we follow through consistently?

One will feel shakier than the others.

That is your cluster.

Then ask: which part inside that cluster is carrying the most weight?

Not the loudest problem.
Not the easiest problem to fix.
The one everything else seems to be waiting on.

That is usually the first-place worth redesigning.

Where this goes next

The Thrive Business System Assessment is the main doorway into this map.

It is built for the founder or operator who can feel that something is off but does not yet know where the real constraint sits.

It asks nine plain questions, one for each part of the system, and shows what is strong, what needs work, what is at risk, and which area deserves attention first.

If you’re open to it, I’d be happy to offer you a complimentary 15-minute virtual coffee. We can talk through your results, and I’ll recommend an AI tool you can use right away to address your specific challenge.

My only ask is this: if you find that after you apply what I said in our conversation you gain back 5 hours of your time, consider recommending me to someone who could also benefit or schedule a follow-up conversation with me to explore how I may be able to help you further.

If you already know the issue is operational drag, time leaks, manual processes, workflow bottlenecks, customer friction, or AI leverage, the AI Leverage Assessment may be the better starting point.

If you already know the issue is authority, positioning, content, offer clarity, public assets, or turning expertise into trust, the Authority or Value Clarity path may be the better starting point.

And if you already know you want to talk, book the free 15-minute call.

The Thrive Business System Assessment is the central map, not the only entrance.

However you enter, the sequence is the same.

We look at the business.
We find the part under the most strain.
We identify one useful move.
Then we decide whether there is a larger system worth building.

You cannot create leverage by speeding up a broken process.

You redesign the work first. Then you let AI multiply what is worth multiplying.

That is how you build an AI-powered business part by part, without betting everything up front.

If one cluster stood out as you read this, start there.

Or take the Thrive Business System Assessment and see your whole map.

Either way, the goal is the same: find the part that is actually holding the business back before you spend more time, money, or energy fixing the wrong thing.

Thank you for reading,

Juan

Wait…I want to leave you with something extremely valuable. A post that has more than 15,000 views and over 1300 downloads.

50 Free Resources that can take your Business to the Next Level

50 brilliant creators contributed to this.

Broken down into 9 topics:

• Leadership and Decision-Making: making the call you already have the information to make

• Content and Storytelling: shaping a piece of writing that proves the point

• Product and Building: shipping the minimum version of the thing

• Growth and Marketing: finding and moving the next customer

• Operations and Systems: turning a one-off into a repeatable process

• Research and Synthesis: making sense of what you read

• Career and Personal Brand: naming your value in a sentence a buyer can act on

• Creativity and Craft: stress-testing your own thinking

• Mindset and Operating: getting your head right to do the work at all

I really hope you can experience real progress and clarity out of these resources.

Build Leverage. Thrive on your terms.

Juan

Subscribe now