He brought the building, the one we would turn into a destination dispensary, and the job of raising the money. I brought the license, the plans, the vision, and the sweat.

The trip was a financing conference, the one everyone in our industry said we could not skip. This was the room where the money was supposed to happen.

I went anyway. I drove there alone, and the empty passenger seat should have told me something. If you have a big venture on your desk right now, a key hire, a second location, a partner who says the money is close, this is about the one number I skipped and the $300,000 it cost me.

The conference was excellent. I walked the floor in a hard hat with a QR code on it that linked to our investor deck. I met a gaggle of sharp people and learned a ton. And a financial mentor I trust told me the truth in one sentence: right now, there is no money for cannabis businesses that are not already generating revenue. Not slow money. No money.

I heard it. When I got home, I shared it with my would-be partner. It was a solid reality check.

I kept going anyway.

By then I held a seed retail license and was running a small online business selling seeds and grow kits. I started it to get my feet wet in one of the most regulated industries there is. I had applied for a microbusiness license to grow, make, and sell under one roof: cultivation, manufacturing, a dispensary, and a lounge. I found a seed supplier in Massachusetts after traveling the country. I went to bank after bank until one would hold a cannabis account. I lined up lawyers, accountants, manufacturing partners, and architects. A city council rezoned land for the manufacturing site. And I was doing the demolition on his building myself, sixty hours a week.

Every one of those was real work, and every one felt like progress. A full calendar of setup looks exactly like a business moving forward, right up until someone asks how much money has come in.

I was blinded by my own sweat equity. The more of it I put in, the harder it was to walk away from it.

He kept saying the same thing. He had someone on the hook. The money was ready to come in.

Thirteen months in, not one dollar had come in. Eventually we had a falling out and went our separate ways.

We never signed a partnership agreement. Looking back, that was the one thing I got right. It is the only reason I walked away with my shirt.

It would be easy to tell this as a story about a bad partner. It isn’t. It is a story about me. I handed the most important number in the whole project, the money, to someone else, and I never made him show it to me.

We were not running on feel. We had a business plan. We had a working P&L. Our investor deck projected $13 million a year by year five. We even had deadlines: if we cannot raise the funds by a certain date, we skip cultivation and put everything into the dispensary.

That deadline did not end anything. It changed the plan. Every time a number came up short, the project got a little smaller and kept going.

A projection tells you what the business will make if it works. It tells you nothing about when to stop paying to find out.

I now call this missing piece the Walk-Away Number: the amount of real money, in the bank, by a real date, below which you stop. Not shrink. Stop.

A deadline that only changes the plan is not a deadline. It is a negotiation, and your own vision wins it every time.

I did not have a Walk-Away Number because I believed in what I was building. I wanted to bring jobs paying $21 an hour with healthcare to a rural town like mine, and set the bar for what a cannabis business could do for a community. The warning lights were flashing. The vision was brighter.

Good intentions make it worse. When the reason is a good one, walking away feels like letting people down.

There was a second number I never wrote down, too: what the project was costing me. Our P&L had no line for the work I was not doing. Three years of not serving my regular clients, not taking on new ones, not building my own business. When I finally ran it, the lost revenue came to about $300,000.

And that is only the part I can put a dollar figure on. Two and a half years into the project, the week before the license application was due, I had a heart attack. I was in Arizona. They put a stent in my heart, I traveled back to Minnesota, and I worked the next six days straight to get the application in on time. I was awarded the license.

Read that again, because I had to. I could hit a deadline six days after a heart attack. I never set one for walking away.

The most expensive line in the whole project never showed up on the spreadsheet. It was me.

You are probably not opening a dispensary. But I would wager this is already happening somewhere in your business.

You hire a sales manager and give him two quarters to ramp. The quarters pass, the pipeline is “building,” so you give him one more. Then another.

Or you open a second location. It is not hitting its numbers, so you trim the hours and keep it open one more season.

Each time, the deadline arrives, and instead of a decision you get a smaller plan. Each of those had projections. Almost none of them had a Walk-Away Number.

Here is what I do now.

After it fell apart, I built a system for scoring every opportunity before it gets my time, mine or anyone else’s. I wrote about using it in What I’m actually listening for on the first call. I would like to tell you I built it for clients. The truth is, part of the reason was that I did not want to get burned like that again.

One of the first rules I wrote into it: first dollars matter more than projections.

So anything that wants my sweat has to answer one question first. How fast can this produce its first paying customer? Not the forecast. A real dollar, from a real customer.

That project would have failed that question on day one. The earliest possible first dollar was always one milestone away: after the license, after the funding, after the build-out.

Ask that question before you put another month into it, so you find out now whether you are building a business or funding a hope.

If you are already in, ask it the other way: how many real dollars have come in, and since when? If the answer is none, set your Walk-Away Number today, while you can still see clearly.

And stop doing two things. Stop counting promised money as money. Stop letting a missed deadline shrink the plan instead of ending it.

The vision will always ask for one more month. Decide your answer before it asks.

Richard D. Stuart
The Weekly Prescription

The client is a wilderness tour operator. Good people, real trips, years of happy guests. The site looks great to a human being. Beautiful photos, clear tours, a booking path that works.

Then the crawl came back. The site had 73 pages. About 40 of them were leftovers from the template it was built on: sign-in screens, sample pricing tables, five practice landing pages, a change log. All of them live. All of them listed in the map the site hands to search engines. Thirty-nine of them carried the same title: the name of the template.

To a machine, more than half of this tour company says it is a software company.

Yours might be saying something just as wrong. You would have no way of knowing, because you are not the one reading it.

I sat there for a minute. Nobody did anything wrong. The designer moved on, the owners never had a reason to look, and the site worked fine for every human who visited. The problem lives in the part of the website no person ever sees.

That part used to matter only a little. It is starting to matter a lot, and it matters to you.

When someone asks ChatGPT, Perplexity, or Google’s AI which outfitter to book, which firm to call, or what a service should cost, the machine answers the question itself. The buyer reads a summary first. Sometimes they never click through at all.

That changes the job your website does. It is no longer just the storefront where a buyer browses. It is the source the machine quotes from when the buyer never shows up at all.

Think of it like the post office. You can wrap a package beautifully, but nobody at the post office admires the wrapping or opens the box. The sorting machines read the label: who it is going to, where, who sent it, and whether the postage is paid. Get the label right and the package lands on the right doorstep. Leave it smudged or blank, and it sits in a bin somewhere or shows up at the wrong address.

Your website works the same way. The design, the photos, and the copy are the wrapping, built for people. Structured data is the label: plain code that states who you are, where you are, what you sell, for how much, and how long it takes. The machine skips the wrapping. It reads the label to decide what you are and who to deliver you to.

I call this the Shipping Label Problem. Most owner-operators have spent real money on the wrapping and never looked at the label.

This client’s label was blank. Not a single page carried structured data. No business name and address stated for machines, no tour prices, no durations, no seasons. So the machines guessed, and they guessed wrong. Google currently lists them at the hotel their office happens to sit inside. The package went to the wrong address.

Here is my prediction, and I am putting a date on it so you can hold me to it. By the end of 2027, more of your first impressions will happen inside an AI answer than on your homepage.

The businesses those answers name will not be the biggest ones. They will be the ones the machine can describe with confidence.

That is the good news. In the old search game, the biggest budget usually won. In this one, a small operator with clean, consistent facts can be named ahead of a large firm with a vague site. I wrote about how buyers default to the safest-looking name in The room we had no business winning. The machine has the same instinct. When it is unsure, it leaves you out.

AI search does not reward the loudest business. It rewards the clearest one.

So here is what we are doing for the tour operator, starting next week.

Cleanup comes first. We take the template leftovers out of the map and out of the index, and we give every real page its own title and description. No point writing a clean label on a box that is still covered in old labels.

Then we write the label. The business name, address, phone, and hours go on every page in plain code. All eighteen tours get marked up with price, duration, season, and what is included. The FAQ gets marked up so its answers can be quoted directly.

Then we ask the machines again and see what they say.

And here is my prescription for you. It takes about fifteen minutes.

Ask ChatGPT or Perplexity to describe your business, who you serve, and what it costs to work with you, so you see what the machine believes before your buyer does. Then type your web address followed by /sitemap.xml into your browser, so you see every page you are telling machines about. If anything in either one surprises you, ask whoever built your site where your structured data is, so you know whether anyone is minding the label.

If they cannot answer, you have found the Shipping Label Problem. The wrapping can wait. Fix the label first.

Or reply with your web address, and I will tell you what your label says.

Richard D. Stuart
The Weekly Prescription

The next morning the desk is still there. I walk past it on the way to the coffee. Most weeks, something on it is pulling at me. A build that is one session from done. A client email I could answer in four minutes. A fix I already know how to make.

That pull shows up every single week. I have kept the Sabbath for years, and it has not gone away. The world around me does not help. Everyone else runs Monday to Friday, nine to five, and then never really unplugs on the weekend either. Some weeks I catch myself wondering whether I am on the right path and keeping His commandments properly, and I take that question to Yahweh instead of Claude.

Then the day opens up. I spend most of the morning with the King James Version of the Bible, unhurried, with nowhere else I need to be. Later, Cash and I head out for a long walk at the Old Koschak Farm.

The rest of the day belongs to people. I call family and reach out to friends. If my hands want something to do, I putz in the garden. Nothing on the clock, nothing that looks like my regular work. Just my hands in the dirt and no one waiting on me.

By the time we are back from the walk, something has shifted. The deadlines that felt urgent at the desk have shrunk to their actual size. The work is still there. It is always still there. It just is not shouting anymore.

Here is what years of this have taught me. The river of work never stops flowing. It was flowing long before I waded in, and it will keep flowing after I step out. My job is not to stand in it every waking hour. My job is to decide when and where to cast.

I call this the River Rule.

The Sabbath I keep follows the moon, not the Saturday-Sunday week. So it does not always land on a weekend. Some weeks it falls on a Tuesday or a Wednesday, a day everyone else treats as a full workday.

When I started, my colleagues and I were sure that would cause problems. Missed calls. Frustrated clients. Lost work. Friends told me flat out that I could not run a business that way.

It had the opposite effect.

Not one client has ever objected. When someone asks why I am unavailable that day, I tell them. The answer is usually some version of “That’s cool” or “Sounds good, let me know when we can talk.” They do not need me any less. The week was simply built to absorb it. My days are themed, which I wrote about in Your calendar is not yours. Clients know when I am working on their business. The Sabbath is not a hole in that structure. It is the beam the rest of the structure hangs from.

It is the same pushback people get when they follow Tim Ferriss’s advice to check email only twice a day at set times. Everyone assumes the world will fall apart. The world adjusts. Most of what feels urgent is just unscheduled.

That is the pattern I see in owner-operators all the time. Not laziness. The opposite. They are always on, always reachable, standing in the river every hour it runs, and they have mistaken that for commitment.

A business that cannot survive one day a week without its owner is not a business yet. It is a job with overhead.

The ceiling those owners hit is not the market. It is that every decision in the company still routes through them, so the business can only grow as large as their waking hours. One day away is the cheapest audit you will ever run. Whatever breaks while you are gone is the next system you need to build.

I want to be honest about the order of things, though. I do not keep the Sabbath for my business. I keep it because it is His appointed time, and the relationship matters more to me than the output. The business benefits came second, and they came as a surprise.

Gary Vaynerchuk likes to remind people not to let work define their self-worth, that it is nowhere near the top of what makes you who you are. I agree with him. One day a week, I get to prove it to myself.

So here is my prescription, and it is not a productivity hack. Keep the Sabbath.

Not a day of your choosing, and not a protected block you hope to grow into one someday. The day He set. “Remember the sabbath day, to keep it holy” (Exodus 20:8) is a commandment, not a suggestion. And it comes with permission built in. You are allowed to stop. Every week. Even with a business to run.

Start by finding out when it falls. That is why I am building Remembr, an app that tracks Sabbaths, new moons, and feast days on a modern lunisolar calendar, aligned with the rhythm of heaven and earth. Then get ready the night before. Finish what you can, put the computer to sleep, and let the river run without you. Let your clients know which days you work on their business, and let that structure carry the week. When the day comes, give it to Him, and to the people you love.

The work will be there when you get back. In all my years of doing this, it always has been.

If you want to see how the calendar on your wall drifted from the original, I made a series of short videos that walk through it. And if you want the full case, I wrote it out in Who Set the Clock?

The river will keep flowing. Cast wisely.

Richard D. Stuart
The Weekly Prescription

Most believers would never consider changing who they worship. Very few stop to ask who set the calendar they worship by.

Mr. Spock would raise one eyebrow at that. If the One we worship matters, then the appointed time to meet Him deserves at least a logical review.

I keep the Sabbath by the moon. This essay lays out why, as plainly as I can. Scripture defines the Sabbath as an appointed time. The Creator assigned the lights in the sky, especially the moon, to govern appointed times. Therefore the Sabbath should be reckoned by the lunisolar calendar.

Every link in that chain can be checked in your own Bible. You don’t have to take my word for any of it. Spock wouldn’t.

I’m also not going to hang the case on one verse. Anyone can prove almost anything with a single text pulled out of context. Scripture describes a better method: “precept upon precept... line upon line... here a little, and there a little” (Isaiah 28:10). And it sets a standard of proof: “at the mouth of two witnesses, or at the mouth of three witnesses, shall the matter be established” (Deuteronomy 19:15). So each premise below gets more than one witness.

Premise One: The Creator Set the Clock

Genesis 1:14 says the lights in the heavens are “for signs, and for seasons, and for days, and years.” The English word “seasons” translates the Hebrew mo’adim (Strong’s H4150). It means appointed times, set meetings, or fixed feasts.

Psalm 104:19 makes the assignment specific: “He appointed the moon for seasons.” Same word, mo’adim.

So timekeeping was not left to committees. It was built into the sky on day four, before a single human existed to argue about it. A clock visible to every person on earth, needing no batteries, no software updates, and no royal decree. Spock would call that efficient design.

Premise Two: The Sabbath Is an Appointed Time

Leviticus 23 opens with a heading: “Concerning the feasts of the LORD... even these are my feasts.” The word for feasts is again mo’adim. Then verse 3 names the first item on the list: the weekly Sabbath.

That placement matters. The Sabbath is not a separate category standing outside the appointed times. It leads them.

The word itself tells you what kind of time this is. The same mo’ed shows up in the name of the tent where Moses met with God, “the Tabernacle of the congregation” (Exodus 33:7), more literally the tent of meeting. An appointed time is not a rule on a chart. It is a meeting.

Think of it like a standing date night. You and your spouse pick one evening a week, just the two of you. Now picture showing up faithfully every week, flowers in hand, on the wrong night. Your heart is right. Your effort is real. But you’re working from a different calendar than the one who set the date. That is the question this essay is really asking.

Put it in logical form. If the Sabbath belongs to the mo’adim, and the mo’adim are governed by the heavenly lights, then the Sabbath is governed by the heavenly lights. The weekly Sabbath is the first appointed time named in Leviticus 23, and the moon was appointed to keep the appointed times. A calendar that ignores the moon cannot keep the first of them.

Premise Three: The Text Ties Sabbaths to the Month

The feasts are anchored to numbered days of a lunar month. Passover falls on the 14th of the first month (Exodus 12:6). Unleavened Bread begins on the 15th (Leviticus 23:6). Tabernacles begins on the 15th of the seventh month (Leviticus 23:34).

Lunisolar Sabbath keepers point to a pattern. Leviticus 23:39 calls both the 15th and the 22nd of the seventh month a sabbath. Many also read Exodus 16 as placing a Sabbath on the 22nd of the second month: the people arrive in the wilderness on the 15th, gather manna for six days, and rest on the seventh.

On this reading, weekly Sabbaths fall on the 8th, 15th, 22nd, and 29th of every month. The new moon day stands apart from the work week. Advocates point to Ezekiel 46:1, where the gate is “shut the six working days” but opened “on the sabbath” and “in the day of the new moon,” as treating the two separately.

Here is the test. On a continuous week, those month dates land on different weekdays every month. Only a month-anchored week keeps them lined up. The pattern is either a remarkable coincidence or a design feature, and Vulcans are suspicious of remarkable coincidences.

How the Clock Was Reset

If the lunisolar calendar is so precise, why did it fade? The record shows a gradual shift from watching the sky to calculating on paper.

In 45 BC, Rome adopted the Julian calendar, a fixed solar system built for taxes, contracts, and armies. In AD 325, the Council of Nicaea set Easter by its own rule, separating Christian observance from Jewish reckoning of Passover. Around AD 359, Hillel II published a calculated Hebrew calendar, since persecution had scattered the witnesses who once confirmed the new month. In 1582, Pope Gregory XIII corrected the Julian drift, and trade carried his calendar around the world.

Here is the part Spock would find most interesting. Even after Nicaea, the church never fully cut the moon out. Easter is still set by the moon to this day, which is why it lands on a different Sunday every year. Passover and First Fruits, the days Yahushua was crucified and rose, have no fixed date on the Gregorian calendar at all. You need a lunisolar calendar just to find them.

Notice what is missing from that list: a prophet. Each change came from councils, emperors, and administrators. A calendar’s authority is only as strong as its source.

If you’d rather see the drift than read about it, I made a series of short videos that walk through each step, from the sky-watched month to the calendar on your wall. They’re on the Remembr YouTube channel.

Objections, Answered Honestly

A sound argument has to survive its best counterargument. Spock never won a debate by ignoring the data, and neither should we.

“I worship every day. Isn’t that enough?” Daily prayer and devotion are good, and Scripture asks for them. But the commandment asks for something different: “Six days shalt thou labour, and do all thy work: But the seventh day is the sabbath” (Exodus 20:9-10). It’s not either/or. Most of us would never tell our spouse that thinking about them every day means we can skip date night.

“Aren’t these the Jewish feasts?” Read how Leviticus 23:2 introduces them: “Concerning the feasts of the LORD... even these are my feasts.” Not Israel’s feasts. His. The invitation comes from the host, and it was never limited to one guest list.

Philo and the continuous week. This is the strongest objection, and it deserves careful study. Philo of Alexandria, writing in Yahushua’s own lifetime, contrasted states that “keep the holy festival only once in the month, counting from the new moon” with “the nation of the Jews,” who “keep every seventh day regularly, after each interval of six days” (On the Decalogue 96). He also lists the Sabbath and the new moon as separate festivals (Special Laws 2.41).

Lunisolar advocates answer with the 1906 Jewish Encyclopedia. Its article on the week says “the week of seven days was connected with the lunar month,” and it reads the command in Leviticus 23:15 that the weeks to Pentecost be “complete” as a sign that weeks were once counted in a way that could break that rule. The same article also says, “At an early date, however, this intimate connection between the week and the moon must have been dissolved.” Quote it as written. Some websites insert “[359 A.D.]” into that sentence. It is not in the original.

Rome and the day of Saturn. Cassius Dio, describing Pompey’s capture of Jerusalem in 63 BC, says the Jews dedicated to their God “the day called the day of Saturn” (Roman History 37.16). Critics read this as proof the Sabbath already fell on a fixed weekday. Advocates note that Dio wrote more than two centuries after the event, through the lens of the planetary week of his own day. Dio himself says the custom of naming days after the planets was “comparatively recent” (37.18).

Leviticus 23:39. Critics point out that the word used for the 15th and 22nd of the seventh month is shabbaton, a solemn rest that Scripture also applies to annual feast days. That is a fair point. Advocates answer that the annual rests and the weekly pattern land on the same dates, which is the very alignment a continuous week cannot produce year after year.

Colossians 2:16. “Let no man therefore judge you... in respect of an holyday, or of the new moon, or of the sabbath days.” Many read this as freedom from observance. Advocates note that Paul names the new moon and the Sabbath together, which assumes a moon-linked calendar, and read the verse as telling believers not to let outsiders shame them for keeping it.

Romans 14:5. “One man esteemeth one day above another: another esteemeth every day alike.” The context concerns disputed matters among believers, such as food and fasting. Advocates argue that a commanded Sabbath is not a disputable matter.

Logic does not require objections to vanish. It requires that they be answered honestly.

One more thing, because it matters. Scripture is generous with people who simply didn’t know. Paul told the Athenians, “the times of this ignorance God winked at” (Acts 17:30). If you’ve kept Saturday or Sunday your whole life with a sincere heart, nothing here is an accusation. The faith of the people who raised you, and your own, was real. This isn’t about anyone’s past. It’s about what you do with what you find.

Conclusion: Test the Hypothesis

Yahushua said, “If ye love me, keep my commandments” (John 14:15). Keeping His appointed times is not about winning a calendar argument. It is a way of loving Him on His schedule instead of ours.

So run the experiment. Open Blue Letter Bible and look up H4150 for yourself. Then pull up the U.S. Naval Observatory’s moon phase data and find the next conjunction, the moment the moon passes between the earth and the sun. That begins the month. (Some keepers count from the first visible crescent instead. I count from the conjunction.) Count to the 8th day and rest.

To make that count easier, I’m building an app. Remembr tracks Sabbaths, new moons, and feast days on a modern lunisolar calendar, aligned with the rhythm of heaven and earth. Use it as a shortcut, but check it against the USNO data yourself. That’s the point of this whole essay.

The believers in Berea were commended for exactly this. They heard Paul out, then “searched the scriptures daily, whether those things were so” (Acts 17:11). That’s all I’m asking.

Spock would approve of the method: a published, measurable source anyone can check, instead of a decree you’re asked to trust. Decide with your own eyes and your own Bible whether the clock in the heavens still keeps time.

Fascinating. Live long, and rest well.

Sources

• Emil G. Hirsch, “Week,” Jewish Encyclopedia (1906)

• Philo, On the Decalogue 96, C. D. Yonge translation

• Philo, On the Special Laws 2.41-56, C. D. Yonge translation

• Cassius Dio, Roman History 37.16-18, Loeb translation via LacusCurtius

• U.S. Naval Observatory, Phases of the Moon

• Remembr, lunisolar calendar app and video shorts

• Blue Letter Bible, Strong’s H4150

Most were small and useful. Add this partner. Link to that report. This step needs clearer wording. Two were praise. And a few were bigger asks tucked inside a casual sentence. Could we add a loan calculator? Could real estate agents post their own listings? Shouldn’t we be aiming more at existing businesses?

Those are not work orders. They are a feature, a platform decision, and a change of strategy, and each deserves a conversation about scope and cost before anyone builds anything. My AI agent, the software that does the building, would have built all of it if I had handed it the pile. Cheerfully.

That is the problem with speed.

The question on my AI Mastermind call this week was how to speed up delivery with AI without creating operational chaos at machine speed. The speed is not the hard part. The hard part is what the speed lands on.

AI is an amplifier. It does not fix a process. It runs the process you already have, faster and at a volume you have never seen. If the process is sound, you get more of a good thing. If it is loose, you get more of the looseness before you have had time to notice.

I call this the Amplifier Rule. AI multiplies whatever is already there.

When building was slow, the slowness did some of your sorting for you. A person had to read the request, think about it, and do the work, and somewhere in that effort a little judgment leaked in. When building is fast, you have to sort on purpose.

So I never let the agent build straight from a note. In the first version of this feedback board, I told my agent to review every note marked New, ask me clarifying questions about each one, and only then write a ticket, which is just a written work order. The next session starts the same way. The agent reads the project board, the project files, and the product requirements document, the plain-English description of what we are building. Then it drafts the prompt for that day’s batch of work and asks what it is unsure about before anything begins.

The feedback tool is the front door, and the easier it is to use, the more you get. Tuesday night I soft launched that client’s new website at their board meeting. During the walk-through a member asked whether there was a final version of a report labeled draft. I captured it on the spot, in front of everyone, and told the room that this is exactly the kind of note I want from them.

Once the board worked, I turned it into a skill in Claude Code, a saved set of instructions I can call up on any project. When a build reaches its test version, I invoke it, and every project’s feedback shows up on my Feedback Hub. A system you can package is a system worth amplifying.

None of that works without everything behind the door. Opportunity evaluation before I say yes. Wireframes, which are rough sketches of each page, before anything gets built. A design system so the pieces match. Written requirements. Tickets on a board, with a rule that nothing gets built unless it is a ticket. None of it is exciting, and none of it is AI. All of it is what the AI is amplifying.

So what do I actually do about this. Slow down once, so you can speed up for good, and show your work.

Remember the teacher who asked you up to the board to show the class how you solved the algebra problem? The answer was not enough. You had to show your work. AI hands you the answer in seconds. Your job is to be able to show the work behind it: the steps, the rules, and the decisions.

Start with a sketch. I keep a yellow legal pad on my desk for exactly this. Break down the steps a request takes, from the moment someone asks for it to the moment it is done. A flow diagram, boxes and arrows, a simple list. It does not need to be pretty. That sketch is the work you show.

It will take a few hours, and it will feel like the wrong direction. You are trying to move faster and I am telling you to sit down with a legal pad. Do it anyway.

AI does not know when it is wrong. It works out the most likely answer and keeps moving, and every wrong guess becomes what the next one builds on. A mistake at human speed is an irritation. At machine speed it is a runaway freight train headed for town. By the time you notice, you are not fixing a mistake. You are cleaning up the wreckage.

AI will amplify whatever you give it. Make sure it is something worth amplifying.

Richard D. Stuart
The Weekly Prescription

P.S. If you suspect your process is looser than it looks, that is a good thing to find out before you add AI to it, not after. A free 20-minute working call, not a pitch: yourwebguy.org/become-a-client

I hurt my back last week. Staying seated at my desk long enough to get through any of it has become its own daily fight.

I was wired and behind before yesterday afternoon even happened.

That’s when Claude Code, running the newest model, went rogue. It started writing code before there was a ticket for it, before I had told it what it was allowed to build.

I have a rule for exactly this. Never build what isn’t a ticket. Move the ticket to In Progress on the board before a single line of code gets written. My own AI broke my own rule, and the only reason it got caught is that I happened to still be watching.

The new model was also slow. Tasks that should take five minutes were taking twenty to thirty. I sat there, back aching, watching the fastest tool I own move slower than usual, on a day I had none to spare.

Here’s the part that stings a little. AI did not get rid of the bottleneck in my business. It moved it.

The actual writing of code, once the hardest, slowest, most expensive part of any build, is now the cheap part. I hand Claude a well-written task and get working code back in minutes. That’s real. That is not hype.

What didn’t get cheap is the judgment. Deciding what a task should actually say. Noticing an AI is about to build the wrong thing before it builds it. Catching the moment a newer model starts making different choices than the version that built the rest of the project. Keeping every work session short enough that the AI stops remembering and starts guessing. None of that is code. All of it is still entirely mine.

I call this Judgment Doesn’t Scale. Two years ago the constraint on my business was my own two hands. I could only build so much, so I automated the building. Now the constraint is my own attention. I can only supervise so much, and there is no version of Claude I can hire to supervise Claude for me.

AI did not remove the bottleneck. It moved it from the code to the judgment, and judgment still only comes in one unit.

Right now that one unit is stretched across four fronts, and I am the only one who can move any of them.

So what do I actually do about this. Not work faster. I tried that yesterday, and a rogue build in the middle of four projects is what faster gets you.

The fix has to be the same one I would hand a client with this exact problem.

Stop trying to personally move quicker. Shrink the list of things that require you specifically.

I am turning the parts of my process that used to live only in my head, how I read a set of requirements, how I break it into the right pieces, the same categories of mistakes I catch every time, into an actual written standard operating procedures. Not to remove my judgment. So the judgment that has to stay mine takes less of me every time I use it.

If you are the bottleneck in your own business, the fix was never speed. It is writing down the thing you do automatically in your head so it stops living only there.

I did not build myself a team. I built myself a faster way of doing it alone.

Richard D. Stuart
The Weekly Prescription

P.S. If your business runs on the same single point of judgment mine does, yours or an employee’s, the fix is rarely “find more hours.” It’s turning what only lives in your head into something repeatable. That’s a free 20-minute working call, not a pitch: yourwebguy.org/become-a-client.

We got talking about the Kekekabic Trail, the stretch that runs closest to town. It put me right back at that same trailhead a few weeks earlier, where I’d driven twenty miles out of Ely to pick up a young man I taught fifteen years ago on a wilderness expedition. He’d just walked roughly thirty-nine hundred miles from Vermont, something like eight million steps, to reach that exact spot. At the time he had one trail left to finish, this one.

He’s since finished it. He is now the ninth person ever to complete all eleven National Scenic Trails in this country, every mile on foot.

That stopped me for a second, standing under that tent. Eight million steps is not a plan. It is not a campaign. It is not a launch. It is eight million individual decisions to take one more step, most of them made somewhere nobody was watching, most of them not feeling like progress at all.

That is the part owner-operators get backwards. We aim at the big result directly, the finished trail, the thriving business, the sold-out season. It is never reachable directly. It only shows up as the sum of deposits nobody saw you make.

An old friend of mine used to put it plainer than any business book ever has: no deposit, no return. He was talking about a bottle, the five-cent kind you used to get back at the counter. The wisdom never stayed on the bottle. You don’t get a return on anything, a full pipeline, a business that runs without you standing over it every day, that you didn’t first put a deposit toward. And the deposit, almost always, looks too small to matter in the moment you make it.

I see this in real numbers with the businesses I work with. A law firm here in town sits at fifty-six Google reviews now, five stars, because the owner started asking every satisfied client for one, consistently, for months, long after it stopped feeling like it was doing anything. No single ask built that number. The fifty-sixth review didn’t either. The deposits did, made on weeks nobody was checking.

A cabin-linen client of mine added one thing to the order form two summers ago, a premium towel set offered at the exact moment a guest was already deciding to book. It still sells at full price today, no discount required, because the value was legible right when the decision got made. One deposit, made once, still returning.

The most striking example of this I know isn’t even a business story. Oseola McCarty spent her working life as a washerwoman in Hattiesburg, Mississippi, taking in other people’s laundry for whatever they could pay. She’d quit school in the sixth grade to care for a sick aunt and never went back. Nobody would have called any single week of that work remarkable. But she set something aside out of nearly every one of those weeks, for decades, in savings accounts scattered around town. In 1995, at eighty-seven years old, she used it to set up an irrevocable trust worth an estimated $150,000, most of it endowing scholarships at the University of Southern Mississippi for students who couldn’t otherwise afford to go.

Harvard gave her an honorary doctorate the following year. Not one of those weekly deposits looked, on its own, like it would ever pay for anyone’s education. It was never one deposit. It was thousands of them, made by someone nobody was watching, for longer than most people stick with anything.

If you are waiting for the one big move before you start compounding, you are standing at the trailhead waiting for the whole trail to appear at once. It won’t. Take the step you can see. Then the next one.

If you recognize your own business somewhere in that, waiting on the big move instead of banking the small ones, the honest audit is a free twenty-minute working call at yourwebguy.org/become-a-client. No pitch.

Richard D. Stuart
The Weekly Prescription

I wanted to just tell him to build it. That would have been the easy, generous thing to say.

Instead I ran the brief through the same system I run every opportunity through, mine or anyone else’s. Nine categories, scored out of five apiece: how clear the customer is, how painful the problem really is, whether there’s a real lever for revenue, whether distribution exists or has to be invented from nothing, and so on. Forty-five points total, plus one more score only the founder can give himself, would he actually stay obsessed with this for two years.

The brief scored well. Customer clarity, four out of five. Recurring revenue potential, four out of five. The brand and the name, genuinely the strongest part of the whole package.

Distribution scored a two.

There are over five thousand apps in the App Store’s Food and Drink category alone. Most of them are dead. I told him flat out: the App Store is a cemetery. A good idea and a good name are not enough to survive it.

Final score: 28 out of 50. Needs Validation, not Strong. Not because the idea was bad. Because nobody, including him, had a real answer for how the first hundred users would find this thing that didn’t amount to hoping the App Store noticed.

That’s the part of a first call nobody sees from the outside. People assume I’m listening for whether an idea is good. Good ideas are common. I’m listening for whether this one has earned the right to be built yet, or whether it still only deserves to be tested.

Here’s close to word for word what I wrote back to him: before you think about a tech stack, answer one question. Who are your first hundred users, and how do you reach them personally today? Not through the App Store. Not through ads. Personally.

Then I gave him something concrete to chase instead of a launch date. There’s a cooking channel on YouTube with four point six million subscribers, built entirely around people who love food but still don’t know what to make. More Americans watch cooking shows than actually cook, and that gap is the whole business. Helpful, honest comments in the communities where those people already ask “what’s for dinner” every single night are a zero-cost way to find the first thousand users before a single screen gets built.

Validate first. Build second. The idea deserves to be tested. It doesn’t yet deserve to be built.

I told a friend, essentially, not yet, on an idea I genuinely liked. That’s an uncomfortable thing to put in writing. It’s also the whole job.

If this sounds like the diagnosis in “The Last 20%,” it’s the same problem. That post named it. This is what it looks like running live, on someone I like, where the easy thing would have cost me nothing to say.

The businesses I actually work with aren’t pitching me app ideas on a first call. They already have a real business. But the same categories apply to the next hire, the next redesign, the next product line, the next dollar you’re about to spend. Who are the first hundred people who’d actually use or buy the new thing, by name if you can manage it. Have you shown it to real people and asked them to pay today, or is “they’d love this” still a guess. Do you already own a way to reach people, a list, a following, a referral network, or are you starting from zero. And if the growth is slow for a year, will you actually still want this.

If you can’t answer the first one, the idea isn’t ready. It doesn’t matter how good the brief looks.

Richard D. Stuart
The Weekly Prescription

P.S. If something you’re building, or something you already built, has never had those four questions run against it honestly, that’s exactly what a free 20-minute working call is for. yourwebguy.org/become-a-client. No pitch, just the same four questions I ran on my friend’s app.

They flew down that hill for an hour, soaked in the last of the evening light, screaming the whole way down and racing each other back up.

An older gentleman stood next to me on the porch, watching the same thing I was. He said he’d done the exact same thing on that same hill more than sixty years ago.

He wasn’t performing nostalgia for my benefit. He said it quietly, mostly to himself, the way you talk when a moment catches you off guard.

That’s when I understood what I’d actually driven two days to get to.

I was there for the wedding of a dear friend at the Gatineau Fish and Game Club, founded in 1894 by Canadian and American sportsmen who loved the wilderness enough to spend their lives protecting it. The clubhouse itself was built by local craftsmen, by hand, with views down two lakes that haven’t changed since. I’d left early, crossed the Upper Peninsula of Michigan, cut through Ontario, and rolled into Quebec that Wednesday, four days ahead of a Sunday wedding, so I wouldn’t miss German Night on Saturday.

The day before I pointed the truck east, I’d had dinner with a former student of mine, fifteen years after I taught him on a twenty-eight day expedition course. That’s the same summer I met the groom, back when the two of us were both Outward Bound interns. Two threads from one summer, fifteen years old, both coming due in the same week.

Every Wednesday night, all summer, the club runs a standing supper club open to members and their guests. Within that tradition, my friend’s parents have hosted their own themed German Night each summer for the last fifteen years. This year, with the wedding on Sunday, they moved their night from its usual Wednesday to Saturday instead. Decked out in lederhosen and a dirndl, they hosted two hundred and thirty people out on the lawn, at long picnic tables under brightly colored tablecloths, club members, guests, and half the wedding party, one day before their son said his vows.

Fifteen years of showing up to host the same night, for a lawn that isn’t only theirs anymore.

My friend is the oldest of six kids, three boys and three girls. Their parents started by camping, off the grid, on a small platform on an island in the lake. No power, no plumbing, just a family and a piece of plywood. They kept camping there for more than a decade, every summer, even after life scattered the six kids across three countries.

That camping trip eventually became a real off-grid cabin. The family’s actual home place now, every summer, no matter where anyone lives the other eleven months.

I walked the property before the wedding. The original platform is still standing, right next to the cabin it turned into. Nobody tore it down. It’s just there, holding up nothing anymore except the proof that it held up something once.

The bride grew up in Montana. She and the groom now have a son, barely a year old, who is already the fifth generation of her family to call Montana home. Nobody camped on a plywood platform for a decade to earn that. It’s just what happens when a family stays put on the same ground long enough.

The club has its own version of that same math. Its history page says it plainly: five generations after it was founded, members and their families still meet at that same clubhouse, look at the same two lakes, and more likely than not, tell some of the same old stories.

Two different families. Two separate counts of five generations. Neither one planned to land at the same wedding, on the same lawn, in the same week. They just did.

Two things on that property never asked anyone’s permission to keep existing. The platform stood because a family kept choosing to go back to it long after camping stopped being a phase and started being a decision. The hill kept its tradition because it never depended on any one family running it. It just needed kids and cardboard, generation after generation, whoever happened to be standing there that summer.

I write a lot in this publication about the systems that let a business run without the owner holding every piece of it up personally. I’ve got a framework I use called the 8 Forms of Wealth, and two of the eight columns are Family & Social and Impact, the ones about who you’re connected to and what outlives you. I’ll be honest, those two columns get the least attention in a culture that rewards whoever posts the most this week.

Watching that hill, I finally saw why. Impact and legacy don’t show up on a quarterly report. They show up five generations later, on a porch, when someone tells you they did the exact same thing as a kid.

I’m naming the test right now. Not whether you built something. Whether what you built is still standing, and still running, after you personally stop being the one holding it up.

The platform passed. It’s still there, empty, a monument to a decade of showing up. The hill passed a long time before any of us were born. The club has been passing it for five generations, and it re-takes the test every single summer. The annual German Night is still being tested. Fifteen years in, it’s theirs to keep proving.

I don’t know a business owner who wouldn’t want the same test applied to what they’ve built. Most of what I get called in to fix is the opposite problem: a business that cannot run for a single week without the person who started it standing underneath every piece of it.

Before I left, I told the property caretaker I’d see him again for my friend’s son’s wedding, sometime in the 2040s. The boy is barely a year old, already the fifth generation of his mother’s family to call Montana home, at a wedding hosted by a club now five generations deep into its own history. I meant it.

Richard D. Stuart
The Weekly Prescription

P.S. If it feels like this connects to the piece I wrote last week about the young man who just finished walking all ten major long trails in America, it does. Same expedition, same summer, fifteen years ago, two threads finally crossing in the same month. If you want an honest read on whether what you’ve built would pass the same test, that’s a free 20-minute working call at yourwebguy.org/become-a-client. No pitch.

He’s thirty-one now. He’s finished all ten major long trails in America. Every mile of every one, on foot, no skipped sections.

Last week I picked him up at the western terminus of the Kekekabic Trail. It had rained steadily all night and straight through the day. He’d just walked roughly 3,900 miles from Vermont, somewhere north of eight million steps to that trailhead, give or take. We drove the twenty miles back into town for a pot of hot coffee and a hot lunch before I brought him out to my cabin.

The timing lined up with something else. My mom has been visiting Minnesota for the last nine weeks, and that was her last night in the cool air before flying back to Arizona.

My co-instructor from that expedition still lives in Ely. That evening he broke bread with him in town and caught up on fifteen years, while I cooked dinner for my mom.

After dinner I picked him up to spend the night on my couch and meet my 88-year-old mother. She was curious. The two of them talked well into breakfast the next morning, and she gave him a big hug before I drove him the twenty miles back out to the exact spot on the Kek where I’d picked him up the day before.

He wouldn’t take the shorter option. Nobody would have known if he had. Nobody was checking.

Before he started walking west again, at least another month left to finish the North Country Trail, we hugged it out. And he told me the one thing he still carries from that expedition fifteen years ago isn’t the wilderness skills or the twenty-eight days. It’s integrity. What it actually means, day to day, when nobody’s grading you on it.

That’s the whole post.

Integrity isn’t what you do when someone’s watching. It’s the twenty miles you drive back to the precise point you stopped, because you told yourself you would, and you’re the only one who’d ever know the difference.

Most of us cut that corner constantly. In small ways. The status update we call “done” when it’s 90%. The invoice we don’t double check. The commitment we quietly shrink because nobody’s tracking it but us.

He’s got one month of walking left. I’ll let you know when he closes the loop.

Richard D. Stuart
The Weekly Prescription

P.S. If you liked this, I wrote about a different kind of number a while back, the one that forces you to actually decide something. His eight million steps is that idea in boots. And if you recognized your own version of that twenty-mile drive somewhere in your business, the honest audit is a free 20-minute working call at yourwebguy.org/become-a-client. No pitch.

Twelve issues in, every one landed on schedule. Then the thirteenth didn’t. No diagnosis went out. No prescription. Just quiet, the kind that makes a guy who’s published every week for three months start composing the “sorry I went dark” email in his head before anyone’s even asked for one.

Here’s what I was actually doing instead.

Friday morning, the first installment of a weekly column I write for The Ely Echo, “Ask Your Ely Web Guy,” ran in print. That day and then on Saturday I spent my time standing up richardstuart.me from nothing: domain, DNS, business email, a live site, all of it, in under 48 hours.

Three real things. A newsletter. A newspaper column. A website. Built over years, one weekend, and one Wednesday’s silence, none of them talking to each other.

That’s when it hit me. I’ve spent three years telling clients their reputation is scattered across a POS system, a Facebook page, and word of mouth, with no single place a stranger can land and see the whole picture. I had the exact same problem. My own credibility was scattered across a Substack subdomain, a newspaper’s website, and two separate company domains, with no page anywhere that said “here is all of it, here is who did all of it.”

I call this the Front Door Problem. It’s what happens when a person or a business has real, credible work happening in more than one place, and nobody visiting any single one of those places can find their way to the rest. Each piece is legitimate. Together they read as nothing, because nobody can see them together.

Here’s the plain version. A stranger who can’t find their way from any one thing you’ve built to everything else you’ve built doesn’t experience you as three credible things. They experience you as one thing they’ve never heard of.

So instead of writing issue thirteen on schedule, I built the front door. richardstuart.me is now the one place that ties the newsletter, the column, and both businesses back to the person doing the work. It went live over the weekend.

I skipped a week of showing up in your inbox to fix the reason showing up here wasn’t compounding into anything bigger. That’s not a contradiction. It’s the same math I’d run for any client: sometimes the fix that matters isn’t the next piece of content. It’s the thing that makes every piece of content before it finally add up to something.

If you’ve got more than one real place where your credibility lives, and you’ve never once checked whether a stranger can find their way from one to the others, that’s worth twenty minutes before you write your next post, your next flyer, your next anything. You don’t have a marketing problem yet. You have a front door problem, and content poured into a house with no front door just piles up in the yard.

Richard D. Stuart
The Weekly Prescription

P.S. If your work lives in more than one place and there’s no single page that ties it together, that’s the twenty-minute conversation worth having before the next dollar goes into more content. Free working call: yourwebguy.org/become-a-client.

A firm I work with, a professional practice whose entire business is reputation and being the people others call when something important is on the line, had its website caught in a coordinated wave of attacks that swept through a whole category of sites at once. Theirs was one of thousands. I saw it, and I shut the site down the same day.

To hold the line I bolted on two-factor login. The team felt the friction the next morning. One more hurdle, one more thing to explain, one more piece of machinery standing between them and their own website.

And standing there, having just fixed it, I realized the fix was the problem.

That two-factor login was maybe the tenth thing bolted onto a site that was built years ago, for a smaller, simpler version of the business. A plugin here to handle a form. A plugin there for security. Another to make the calendar behave. Each one solved a real problem the day it went in. Together they had turned a clean foundation into a patchwork nobody could see the shape of anymore.

The site still looked fine. That is the trap. It looked fine.

I see some version of this in nearly every established business I get called into. The website was built at one point in the company’s life, usually five or more years back, when the business was younger and did less. Since then the business grew. Added services. Added people. Added a whole reputation. The website did not grow with it. It got added to.

And adding to a foundation is not the same as building one.

I call this Foundation Debt. It is the accumulating cost of running a growing business on infrastructure built for an earlier, smaller version of it.

Every patch feels like progress, because it fixes today’s problem. But you are not paying the debt down. You are paying interest on it, and the interest comes due in leads you never see. The prospect who could not find what they needed and quietly left. The form that broke on a phone. The page that loaded slow enough that someone hit back before it finished.

Here is the plain version, the one worth writing on a sticky note. A website you keep patching was finished a long time ago. You have just been paying interest on it ever since.

The reason capable owners miss this is the same reason they are capable. They are resourceful. When something breaks, they fix it, or they have someone fix it, and the fix works. Problem solved, move on. That instinct built the business. It is also what keeps them adding a fourteenth patch to a foundation that needed replacing at the fifth.

Because no single patch is ever the thing worth stopping for. The security plugin is not a crisis. The slow page is not a crisis. Each one is small. The debt is the sum of them, and nobody ever gets a bill that reads “Foundation Debt, total due.” You just notice, if you notice at all, that the website has quietly become something you work around instead of something that works for you.

This is the part I most want the capable owner to hear. What you have is not a website problem. It is a platform problem. The site, the security, the way you publish, the way anything you make reaches the people who should see it, all of it is fighting the tools instead of the tools doing the work. You cannot patch your way out of that. You can only rebuild the foundation underneath it.

That sounds expensive. What is actually expensive is the third straight year of leads you lost without ever learning their names.

So here is the prescription, and it costs you nothing but honesty.

Do not audit your website. Audit your patches. Write down the last five things you added, changed, or fixed on your site. The plugin, the workaround, the “can you just make this one thing work.” Then ask one question of the list. Is this a foundation being improved, or a foundation being propped up?

You will know the difference by how the list feels. Improvements feel like building. Propping up feels like keeping something from tipping over. Nobody props up a foundation they trust.

If the honest answer is propped up, then more pages will not fix it. A fresh coat of design will not fix it. The thing under the pages is what aged, and that is what has to be rebuilt.

Your business is not the five-year-old version of itself anymore. The foundation carrying it should not be either.

Richard D. Stuart
The Weekly Prescription

P.S. If your website has quietly become something you work around instead of something you work from, it is worth twenty minutes before you spend a dollar on a redesign that just sits on the same old foundation. Start with a free working call at yourwebguy.org/become-a-client. No pitch. Just an honest read on whether you have a website problem or a foundation problem.

Guests show up to fresh linens already delivered and waiting at the cabin, softer than anything they own at home, enough for every bed in the place including the pull-out couches and the kids’ bunks, and they never think about laundry once. It’s a good business built on a simple promise: travel light, sleep well, we handle the rest.

We were looking at the online shop, and I asked a question I ask a lot of owner-operators. What else does the person buying this already wish they had?

The answer was sitting right there in the use case. Someone renting a cabin on a lake for a week is going to be in and out of the water, tracking sand across the floor, reaching for a towel a dozen times a day.

So we added one. An eighteen-piece Turkish cotton set: six beach towels, six bath towels, six washcloths. Ultra-soft, absorbent, and the part that actually matters at a lake, you shake them out at the door and the sand stays outside instead of tracked across a cabin floor you did not come on vacation to sweep every day. You stay dry and wrapped in something that feels like a spa instead of a gas-station beach towel.

Here’s the part worth sitting with. That towel set is not cheap. It is a premium add-on at a premium price, sitting next to a linen service people were already paying for.

And it sells. Not because we discounted it. Because at the exact moment someone is booking clean sheets for a lake cabin, a plush, sand-resistant towel set is the most obvious thing in the world. The value explains itself, right when the decision is being made.

Nobody haggled over the towel price. They could see exactly what it did for them.

Now hold that against the conversation I have almost every week with a capable owner who is convinced they have a pricing problem. They tell me prospects balk at the number. Deals stall on cost. They’re starting to wonder if they should lower the rate. And almost every time, the rate is not the problem.

Per Sjöfors, who wrote The Price Whisperer and has spent a career studying why businesses underprice, puts it in five words: the perception of value is value.

Buyers look irrational when they reject a fair price, but they’re actually predictable. They are not weighing your rate against your competitor’s rate. They are weighing your rate against what they can clearly see they’re getting. When they can’t see it clearly, price becomes the only thing left to measure, so price is what they push on.

I call this the Legibility Gap. It’s the distance between how valuable your work actually is and how clearly the buyer can see that value before they decide. When the gap is narrow, like a sand-resistant towel next to a lake-cabin booking, price barely comes up. When the gap is wide, price is the whole conversation, because it’s the only number the buyer can actually read.

Here’s the plain version: when a buyer can’t see what changes for them, price becomes the only thing left to judge. What looks like a pricing objection is almost always a clarity failure wearing a price tag.

The capable owner-operator makes this harder on themselves than anyone. They’re close to the work, so the value is obvious to them. Of course it’s worth it. They can see the whole picture.

But they describe the offer in the language of what they do, the deliverables, the features, the process, and they never translate it into what changes for the person paying. The buyer is left holding a list of activities and a number. With nothing else legible, they judge the number.

The towel set worked because it closed the gap at the point of decision. The value was legible exactly when it needed to be.

Most owner-operators are doing the opposite. They assume the rate is scaring people off, so they cut it, or they pile on more features to justify it, and both moves make the gap wider instead of closing it. A lower price doesn’t make the value clearer. It just teaches the buyer that even you weren’t sure it was worth the first number.

So here’s the prescription, and it costs you nothing but an honest afternoon. Write down what your client’s situation looks like ninety days after they work with you. Not what you deliver. What is different in their business, in plain language a stranger could repeat back.

If you can’t write that sentence, your buyer can’t see it either, and you cannot price with confidence something you cannot describe. Get the after-state legible first. The rate stops being an argument the moment the value is one the buyer can see for themselves.

You don’t have a pricing problem. You have a problem nobody can see. Fix what they can see, and the price takes care of itself.

Richard D. Stuart
The Weekly Prescription

P.S. If deals in your business keep stalling on price and you’re starting to wonder whether the number is wrong, it’s worth twenty minutes before you touch the number. Start with a free working call at yourwebguy.org/become-a-client. No pitch. Just an honest read on whether it’s your price or your Legibility Gap.

We landed at the Hibbing airport, birthplace of Bob Dylan, and stepped off the plane into 99 degrees.

Four days before we landed, a violent lightning storm rolled through the Superior National Forest, the wilderness I live inside of. It sparked fourteen wildfires in and around the Boundary Waters. By the time our plane touched down, that number was seventeen. Tens of thousands of acres gone. These fires are burning hot enough to go three and a half feet into the ground, and nothing puts that kind of fire out but snow. The air quality is off any chart I’ve seen.

We stepped out of the pan and into the fire. Literally.

Here’s the part I didn’t expect. My calendar didn’t ask permission before it got rewritten. Wednesday is my writing day for this publication, the day I draft, edit, and publish one issue, start to finish. This past Wednesday I was getting my mother settled into a house that smelled like a campfire that wouldn’t quit, in a town I’d just landed in, with air quality warnings hitting my phone every twenty minutes. The issue didn’t get written. I let it slip.

I’ve written before about the calendar, in issue 004, “Your calendar is not yours.” The diagnosis there was that work will fill any open hour you don’t claim first. Theme your days, block your priorities in advance, and work stops deciding your week for you.

That diagnosis still holds. But it assumes the thing competing for your attention is work. This week it wasn’t. It was my 88-year-old mother’s health, a wildfire complex bigger than most counties, and an air quality reading that made “go outside” a real medical question. None of those things emailed me first. None of them cared what day I’d themed for them.

I call this the Everything Week. It’s the week every category of your life, family, health, weather, business, and the feed on your phone that wants a reaction from you about all of it, files a claim on the same seventy-two hours at once. A normal week tests whether you have a schedule. An everything week tests whether you have a system.

Here’s the plain version of it: a calendar that only survives a good week isn’t a system. It’s a guess. It only proves itself the week everything hits at once.

My structure held better than it would have five years ago, but it didn’t hold perfectly. The writing slipped two days. My mother did not. That’s the actual test of a themed week, not whether every box gets checked, but whether you can tell, under real pressure, which commitments were load-bearing and which ones were just habit.

A friend told me a line this week that’s been rattling around in my head since. Your first attempt at anything is like cooking pancakes, you always throw the first one out. This is my first everything week running this particular structure against this particular kind of disaster. The first pancake was ugly. I’m not throwing out the griddle over it. I’m cooking the next one better, starting with this issue, two days late and still on the plate.

The prescription is not “protect your calendar better.” You already know that. The prescription is to stress-test the calendar you built for a normal week against the week you hope never comes. A family emergency. A health scare. A literal fire. If your themed days, your priorities, your whole decision-in-advance structure would collapse the moment two of those things landed in the same week, you don’t have a system. You have a system that has never been tested.

Test it on paper before life tests it for you. Ask which commitments would survive if three things broke at once, and which ones were only ever surviving because nothing had pushed on them yet.

The wheel that rolls is the one you balanced on purpose. Just make sure you built it to survive more than one direction of wind.

Richard D. Stuart
The Weekly Prescription

P.S. If your business currently runs because you personally hold every plate in the air, that’s worth a conversation before your own everything week arrives. Start with a free 20-minute working call at yourwebguy.org/become-a-client. No pitch. Just an honest read on what would actually break first.

Michael, Martin, and I had worked together at Rhino Internet Solutions in Tempe. The dot-com crash hit the company twice. The first round cut the staff in half and somehow left the three of us standing. The second round, about eighteen months later, took Michael and Martin. I stayed on, the project manager they still needed, watching two of my closest friends walk out the door.

We had eaten lunch together almost every day for two years by then. After the layoffs, neither of them worked for six months. They spent that time asking me, over and over, to leave Rhino and start something with them. Three people who had collectively worked about one full year out of the last three, sitting down to name a company.

We didn’t just brainstorm. We ran an actual exercise, the same one I still use today, just in low fidelity. Small Post-its for names, large sheets for four categories: functional, invented, experiential, evocative. Write a name, stick it under the category you think it fits, argue about whether it’s in the right place, vote, take a break, vote again. We went through hundreds of names that afternoon.

The one that stuck wasn’t clever. It was obvious the second we saw it. We were, literally, a collective of professionals who met for lunch. Lunchbox Collective.

We had the name before we had anything else. That week I’d given blood for cash. What was left between the three of us covered a bus fare and the LLC filing fee, and nothing past that. We signed a lease on a small office with no furniture and no clients, on the strength of a name and not one dollar more. The company didn’t feel real yet. It became real the next day, when we landed our first paying client.

We’d already decided who we were before anyone paid us to be it. That name went on to do actual work for us for the next twenty years. When we finished a project, we didn’t just email a final invoice. We burned the files to a CD and a thumb drive, built a foam cutout to hold them, and shipped it inside a real lunchbox. Some of our original clients still have that lunchbox sitting on a shelf in their office today, more than twenty years later. Clients and friends started handing us lunchboxes too, just because it was ours now. We kept every one of them on a shelf in the office.

Most businesses skip that afternoon entirely. They pick a name the way we almost picked that office, whatever doesn’t require an argument. Somebody incorporates between two client calls and types whatever fits in the filing box. A partner throws something out at the end of a long meeting and everyone’s too tired to object.

I call it the Default Name. Nobody chose it. It’s just the one nobody objected to.

There’s a version that fails the opposite way. Naming circles have a term for it: the Happy Idiot. An agency invents a word that means nothing, hires someone with a linguistics degree to explain how it’s secretly built from Latin and Italian roots meaning “wonder” and “purpose,” and hands it to a client who feels smart for approving it. The client leaves happy. The name means nothing to a single person who will ever hear it. One name plays it safe. The other plays dress-up. Neither one was actually chosen.

A name is not a description of your services. It’s a promise about what changes for the person who hires you. Ours made that promise before we had a dollar to back it up, and it got tested the very next day.

I still run the same exercise today that put “Lunchbox Collective” on a folding table in my dining room in 2003, refined by twenty more years of doing it for clients. I’m not going to walk through the whole process here, because the process isn’t the point of this issue. The point is simpler: your name is either doing work for you right now, or it’s just the thing nobody objected to. Only one of those pays you back for the next twenty years.

If you’ve never actually run the exercise, that’s the first thing worth doing before you spend another dollar on a logo or a website. Ask yourself honestly which one you’re running on.

We had thirty days to get the company off the ground. It took one night. That first week in the new office, we prototyped, wrote the copy, and built the site ourselves by hand. It went live under "What's With the Name," reading exactly this: "The collective was formed through open and honest conversations about how we could remain true to ourselves and the medium in which we work...on our lunch break, of course." We weren't being clever after the fact. We said the quiet part out loud from day one.

Richard D. Stuart
The Weekly Prescription

P.S. If your business name has never actually been tested against what it’s supposed to do for you, that’s worth twenty minutes. Start with a free working call at yourwebguy.org/become-a-client. No pitch. Just an honest read on whether your name is working or just surviving.

We were Lunchbox Collective. A core team of three, me running project management, Mike as our technologist, and Martin as creative director, backed by a bench of associates we brought in as subject matter experts when a build called for it.

The client was one of the most ambitious mobile startups in the country. A mobile virtual network operator building what the iPhone would later become.

They had capital, momentum, and a shortlist of the biggest agencies on Madison Avenue.

And I could not get myself to the pitch.

James, one of our associate designers, took the red-eye out of Miami and made it to Hollywood. I was stuck in Phoenix and there was no way to fix it in time.

So I had a decision to make. Cancel, reschedule, or pitch anyway with the lead coming through a speaker in the middle of the table from another state.

Reschedule was the safe move. Reschedule was also how you go last, get measured against everyone who went before you, and lose.

So I did the thing that made no sense on paper. From Phoenix, I called the concierge at the W, where James was staying.

James had just come off the red-eye that morning, gone up to shower and put on his suit. By the time he came back down to the lobby, the concierge was waiting for him with two dozen fresh-baked cookies, cups and half gallons of cold milk, and a limousine at the curb to take him to the pitch.

He had no idea what he was walking into. Then I dialed in and ran the meeting from another state.

The firms ahead of us had walked in with polished decks and rooms full of people. Real credentials. The kind of agency you hire precisely so that if the project goes sideways, no one can accuse you of making a reckless choice.

We showed up with cookies, a speakerphone, and a plan we actually believed in.

I did not pretend to be bigger than we were. I did the opposite.

I told them exactly what a three-person team would do that a forty-person team could not. No layers. No account manager relaying messages to the people who would actually build the thing.

The people doing the work were the people in the meeting, whether in the room or on the phone, and we had already mapped how their ordering and activation platform needed to work.

We ran the entire pitch not knowing if it mattered. As far as we could tell, none of the real decision-makers were even in the room.

We were wrong.

At the end of the question and answer period, the CEO spoke up. He had been working through our cookies the whole time, and he answered with his mouth still full of them.

He said he loved chocolate chip cookies. He could not remember the last time he had sat down with warm cookies and a cold glass of milk. This, he said, was exceptional.

And this was exactly the kind of thinking he was looking for.

Then he told us we had quite a set of cojones, and awarded us the project on the spot. Before the next agency in the hallway ever walked in.

A $360,000 contract. Three people. We beat firms that had more employees than our company had chairs.

An agency called Lunchbox Collective, winning the room with warm cookies and cold milk. I did not plan the symbolism. I have never forgotten it.

Here is what actually happened in that room.

For years I told this story as a cookie story. The gutsy little move that won the day. That is the fun version, and it is not wrong. But it is not the lesson.

The lesson is that every other firm in that room was selling the same thing.

They were all capable. They all had case studies. They all promised to build the platform, hit the timeline, and manage the account.

Sit through four pitches like that and they blur together. The buyer stops hearing differences and starts looking for a reason to choose.

When nothing stands out, the safest reason wins. And safe almost always means biggest.

I call this the Forgettable Middle. It is where competent companies go to lose. Not because they are worse than the competition, but because they are indistinguishable from it, so the buyer defaults to the name that feels least risky.

Here is the claim I would put my name to. When every firm in the room sells the same capability, the buyer does not choose the most qualified one. They choose the one they cannot forget.

The cookies were not a gimmick. They were a signal. They told that CEO we had thought about the room, the moment, and the people in it, not just the scope of work.

The speakerphone told him what he was actually buying. Direct access to the people doing the work, with nothing lost in translation.

We did not win by being bigger. We won by being un-comparable. There was no one else in that process to measure us against, because we refused to show up on the same axis as everyone else.

Most owner-operators I work with are stuck in the Forgettable Middle and do not know it. They are more capable than their competitors. They have the reviews, the results, the years. And they lose deals anyway, then blame it on the other company being bigger or cheaper. The size was never the problem. The sameness was.

Look at how you show up. Your website reads like every other firm in your category. Your pitch leads with the same credentials everyone leads with. Your first impression is designed to look safe, which is another word for forgettable. You have made yourself easy to compare, and the moment a buyer can compare you, the biggest name usually wins.

The move is not to look more impressive. It is to become impossible to line up next to anyone else.

Lead with the thing only you can say. Show them you have already thought about their specific situation before they hired you to. Give them one reason to remember you that has nothing to do with your size.

That reason is usually the very thing you think makes you too small. The direct access. The owner in the room. The fact that they are hiring you and not a layer of account managers.

If you have been reading a while, you already know this client. Two issues ago I told you how it ended.

The same company that awarded us this contract over warm cookies later collapsed into a Delaware bankruptcy, and the accommodation I made cost me nearly everything I earned on the deal.

Both are true. We won a room we had no business winning, and we lost more than we made. The pitch is still the best I ever ran. Some lessons come with a receipt.

Stop trying to be the biggest name in the room. You will never win that fight, and you do not need to.

Be the one they cannot forget.

Richard D. Stuart
The Weekly Prescription

Then I realized I had built something that could not actually run as a business.

The code underneath it was sloppy. Authentication and security were thin. Payment processing and email automation were never wired up the way they needed to be. The experience was clumsy in places I could not even see, because I had not yet learned how to track where users quietly give up. I had a product that worked in a demo and failed as a business.

So it sat on a shelf.

Later I rebuilt the whole thing on a different platform, hoping the new tool would close the gap. It got me closer. It did not get me there.

The app did not become real until I stopped asking which platform would save me and rebuilt it properly on a stack I actually trusted. And even then, the thing that turned it into a business was not the code.

It was a thirty minute conversation.

I sat down with a local newspaper, showed them what I had built, and walked out with a joint venture. I launched that afternoon. Today that product, ElyWorks, connects local employers with job seekers, and twenty-one companies pay for it every month across three subscription tiers.

The build took years of false starts. The business took thirty minutes in a room with someone willing to pay.

I have been buying tools for thirty years. Platforms, frameworks, courses, marketing apps, automation systems, the next thing that was finally going to hand me the answer I was looking for. I have a graveyard of them. You probably do too.

Here is what all of them had in common. Every single one got me about eighty percent of the way to something. Not one of them carried the last twenty.

I call this the Last 20%. The first eighty percent is the build. It is the part a tool can do for you. The screens, the logic, the deployment, the polish. The last twenty percent is everything that turns a working thing into a paying thing. Distribution. Validation. An offer a stranger understands. A real human deciding you are worth their money.

And here is the trap catching capable people right now. AI has made that first eighty percent nearly free. What used to cost me months of fumbling, a sharp operator can now generate in a weekend. That feels like progress. By itself, it is not.

AI has made the first eighty percent of any product nearly free to build. It has done nothing for the last twenty percent, because the last twenty percent was never a technology problem. It is the problem of being chosen by someone willing to pay.

When building was expensive, finishing the build at least felt like an accomplishment. Now that almost anyone can reach eighty percent in a weekend, eighty percent is worth almost nothing. The market is now flooded with beautiful, functional products that nobody asked for and nobody will pay for.

A working app is not a business. It is a very convincing way to feel productive while avoiding the only question that matters.

A friend sent me an app idea recently. Good idea, strong name, in a category with thousands of competitors, most of them already dead. He wanted to talk about which tech stack to use.

I told him to put the stack down.

Before you build or buy one more thing, answer a single question. Who are your first one hundred customers, and how do you reach them personally, today. Not through ads. Not through an app store. Personally. If you cannot name them and reach them, no platform will save you, because the platform was never the thing standing between you and revenue.

Validate first. Build second. The idea deserves to be tested. It does not yet deserve to be built.

That is the whole lesson of ElyWorks. The version that mattered did not begin when the code got good. It began when I sat across from a customer and they said yes.

If you are sitting on a shelf full of eighty percent, the answer is not another tool. It is a conversation you have been avoiding.

Richard D. Stuart
The Weekly Prescription

P.S. If you have built something, bought something, or subscribed to something that was supposed to grow the business and never quite did, that gap is worth an honest look. Start with a free 20-minute working call at yourwebguy.org/become-a-client. No pitch. Just a clear read on where the last twenty percent actually is.

Forty-nine dollars. That was everything I had to my name. By the time I paid the LLC filing fee and the bus fare, it was gone. When I stepped off that bus in Tempe I had lint in my pocket.

Then I looked up.

There was a new steel and glass building on the corner I had never noticed. I thought: now that is an office.

I walked around the corner, into the parking garage, past the name plates for the law firms, and pressed the elevator button for the top floor. The doors opened onto a rooftop patio with an outdoor fireplace and oversized couches. It looked like someone had picked up a building in the Bay Area and set it down in Tempe.

Someone I knew from years earlier walked by and stopped short. He looked at me and said: you’ll never get in here.

I asked if there was a leasing agent. He pointed to a door at the end of the gallery and walked away.

I knocked. A woman named Deb was heading out to an art event on the nearby campus. She mentioned the artist’s name. I stopped her.

I had known Laurie and Dan since my undergrad years. Spent summers with them in Telluride during grad school.

Deb said give me your name and number. I was halfway home when my StarTAC rang. There was a small office she could show me if I was still in town.

I walked back. I was sweating through my shirt. I stepped into the locker room bathroom, washed my face, and cooled my neck.

She showed me the office. Half the size of the others. No door to the patio.

I said I’ll take it.

She asked if I wanted to know the price and the lease terms.

I said I trust you. We’re internet people and we’ll need time to get set up. Can we start May first and I’ll pay first, last, and deposit then?

She said yes.

I called my two partners and told them we had filed the LLC and I had secured an office. They came down, stepped off the elevator, looked around, and said: dude, we can’t afford this. We don’t even have any clients yet.

I said rent is not due until May first. We have a month to figure it out.

By Thursday morning the phone rang. An old colleague. He had heard through the grapevine that Martin, Mike, and I had started a new firm. He had a prospect, he said, that was too small for his shop. Did I want the number?

The prospect was up from Tucson, heading to Sedona and then the Grand Canyon. I called him, listened to what he needed, and said: why don’t you swing by our office in the morning before you head up. Just park in the garage and take the elevator to the top floor.

He walked through the glass doors the next morning and I showed him into that conference room. The one with the fishbowl glass that opened to the patio. We talked for maybe thirty minutes.

When we were done he looked around and said: well, it looks like you guys know what the hell you’re doing.

I looked him in the eye and said what would it take to get started?

He opened his leather attaché and wrote a check for ten thousand dollars.

I walked back to where my partners had their ears pressed to the office door. I said are you guys hungry?

Then I showed them the check.

We walked down to the bank to open a business checking account. Lunch was on me.

That day started with me giving blood to buy bus fare. It ended with a signed LLC, a signed lease, and a ten thousand dollar check in my pocket.

I do not tell this story to impress you. I tell it because the people I write for did something like this once.

Maybe not a glass building in Tempe. But they moved through something that should have stopped them and it did not. They signed the lease they could not afford. They took the client before they were ready. They made the hire before the revenue was there to support it. They operated on a read that was not guaranteed by anything except their own judgment.

That is how the business got built.

Owner-operators who plateau between $1M and $5M almost always have the same origin story: they did something audacious early, it worked, and everything that followed got built on the back of that confidence. Then the business got heavier. The cycles got longer. The obvious moves stopped working the way they used to.

And somewhere in the grinding, the version of themselves that pressed that elevator button got buried under the weight of running the thing they built.

I call this the Founder’s Ceiling: the point where the confidence that launched the business stopped keeping pace with the infrastructure the business needed to keep growing. It looks like a market problem. It feels like a momentum problem. It is almost never either of those things.

The instinct is still sound. The read is usually right. What is missing is not the confidence. What is missing is the scaffolding that should have been built while the confidence was carrying everything.

The website still describes the company from three years ago. The revenue still runs on personal relationships. The intake still depends on the owner being in every conversation. The systems never got built because the founder was too busy being the system.

That is not a character flaw. That is what happens when the early confidence works well enough that you never have to stop and build the infrastructure underneath it.

If you read this story and recognized yourself in it, you are in the right place.

The version of you that pressed that elevator button is not gone.

The question is whether the business you have built is running on systems, or on you.

Richard D. Stuart
The Weekly Prescription

P.S. If you want an honest read on where the gap actually is, start with a free 20-minute working call at yourwebguy.org/become-a-client. No pitch. Just clarity on what is in the way.

We kept in touch the way people do when the connection is real.

A few months ago he reached out. He and his wife had made the kind of move most people talk about but few actually make. They transitioned from employees to owners of the outdoor hospitality business they had been pouring themselves into. A multi-million dollar operation. Their name on it now.

They had been with a large agency for years. The agency knew it. Calls to discuss simple changes came with an invoice attached. Small tasks sat on a list for months. Getting out from under that arrangement took real effort, and a friend who helped them migrate the whole thing to a platform they finally controlled.

He reached out to me because he trusted me to give them honest perspective on what came next. Not a pitch. Just a read on where things stood and what the gaps looked like given how search was changing.

I was glad to.

When he and his wife came back to explore working together on the bigger picture, they had done their homework. They were answering reviews. Reading about AI search changes. Thinking about next season. They were not comparison shopping. They were ready to move.

But before booking a call, they went looking for a number. Just a ballpark. Something to confirm the conversation made sense.

They could not find one.

They still reached out. Eighteen years earns that much. But the note they sent made the gap plain: they knew what the other Richard charged by the hour for the migration work. They had no idea what I charged for anything.

When I read it, I sat with that for a minute. Because I had built the exact foundation problem I diagnose in other people’s businesses. And it had almost cost me a real conversation with people I had known for nearly two decades.

So I fixed it. That same morning.

DIAGNOSIS: The Foundation Fallacy

Owner-operated businesses that plateau between $1M and $3M almost always have a foundation problem, not a traffic problem.

I call this the Foundation Fallacy: the belief that more visibility is the answer when the real issue is what visitors encounter once they arrive.

The business has grown. The owners have gotten sharper. The offer has evolved. But the website, the systems, the way the business presents itself to a stranger (all built for an earlier, smaller version of what the company actually is) have not kept pace.

More traffic finding a misaligned foundation doesn’t produce more leads. It produces more people leaving.

The signs are consistent. The website describes what the business does, not what changes for the client. The pricing is absent or buried. The next step is unclear. The credibility is earned but not visible. The story the site tells is two or three versions behind the story the owner tells on a call.

The owner notices the gap during sales conversations. By then, the prospect has already made most of their decision.

I have seen this with law firms, outfitters, professional service businesses, and e-commerce operators. The revenue is real. The reputation is real. The foundation was built when the business was smaller and never updated to match what it has become.

PRESCRIPTION

Before you spend another dollar on ads, content, or SEO, send a stranger to your website and ask them one question: in thirty seconds, can you tell what I do, who it is for, and what you would do next?

Not a friend. Not a colleague. Someone with no context.

What they cannot answer is the real problem.

Most of the time the fix is not a rebuild. It is clarity. The business is already capable. The foundation just needs to catch up to it.

Richard D. Stuart
The Weekly Prescription

P.S. If you want a clear read on where your foundation stands, start with a free 20-minute working call at yourwebguy.org/become-a-client. No pitch. Just clarity on what is actually in the way.

What we walked into was Robin Sharma.

Gordon’s Canadian in-laws had given him a thin book the previous Christmas, picked up from a small bookshop in Toronto: The Saint, the Surfer, and the CEO.

Gordon was a weekend surfer, rock climber, a practicing Buddhist, and the most grounded COO I have ever known. He read it and could not put it down. He flew to Toronto, told Robin he wanted to help grow his publishing career, and would not take no for an answer.

That night in Phoenix, they handed out free copies of the book. Jeff and I walked to the car in silence, got in, looked at each other, and said the same thing at the same time: I get it.

I read everything Robin had published after that. A few years later I bought myself a ticket to one of his weekend retreats in Toronto.

The idea that changed how I run my week came out of that work.

DIAGNOSIS: Work will fill the void

Robin’s framework is called the 8 Forms of Wealth. The premise is simple: money is one column on an eight-column ledger. The other seven are inner wealth, physical health, family and social connection, career, your circle of genius, adventure, and the impact you leave behind.

Robin laid the original foundation. What I use today is my version of it, shaped by fifteen years of running it against real life.

The exercise is to rate yourself in each column on a scale of one to ten. What Robin observed (and what I confirmed in my own life) is that most capable people are not failing across the board. They are wildly uneven. A 7, a 3, a 5, an 8. Which means they are not rolling. They are bouncing. The goal is not a perfect ten in every column. It is a wheel that rolls.

Here is where the calendar comes in.

If you want balance across eight dimensions, you have to assign time to each one. Not theoretically. On the calendar. In advance. Before the week starts and before work starts filling the open space. I did exactly this. My themed days are locked into my operating system as a non-negotiable. Not a goal. Not an intention. A rule I set once and do not renegotiate.

Because work will fill the open space. Every time.

I theme my days. Monday is for new client development. Tuesday is for existing clients. Wednesday is bookkeeping and publishing. Thursday is research and professional development. Friday is for building relationships in my community. Saturday I roll up my sleeves. Sunday I reflect, plan, and rest.

That structure is not a schedule. It is a decision made before the week starts about what matters and in what order. When a request comes in that does not fit the day, the theme already made the decision. I do not have to negotiate with myself.

The Sabbath is baked in. One day a week that belongs to something larger than work. That rhythm is not background detail. The rest of the structure grows from it.

I put the framework into a one-page worksheet you can download and fill in, below.

The prescription: rate yourself across all eight. Find the columns that are starving. Block time for each one before work claims the week. A themed calendar is not a productivity system. It is a decision made in advance about the kind of life you are building.

The wheel that rolls is the one you balanced on purpose.

Richard D. Stuart
The Weekly Prescription

8 Forms Of Wealth

5.65KB ∙ PDF file

Download

Download

P.S. Be sure to add your themes as non-negotiables to your Instructions for Claude and your Cowork Global instructions.