<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The Weekly Prescription]]></title><description><![CDATA[The bottleneck isn't execution. It's the architecture of your decisions. One diagnosis per week from a solopreneur thirty years in -- on business, faith, technology, and what it takes to finish what you started.]]></description><link>https://theweeklyprescription.com</link><image><url>https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png</url><title>The Weekly Prescription</title><link>https://theweeklyprescription.com</link></image><generator>Substack</generator><lastBuildDate>Thu, 30 Jul 2026 14:11:04 GMT</lastBuildDate><atom:link href="https://theweeklyprescription.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Richard D Stuart]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[weeklyprescription@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[weeklyprescription@substack.com]]></itunes:email><itunes:name><![CDATA[Your Web Guy]]></itunes:name></itunes:owner><itunes:author><![CDATA[Your Web Guy]]></itunes:author><googleplay:owner><![CDATA[weeklyprescription@substack.com]]></googleplay:owner><googleplay:email><![CDATA[weeklyprescription@substack.com]]></googleplay:email><googleplay:author><![CDATA[Your Web Guy]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[The pricing problem that isn't about price]]></title><description><![CDATA[They're not saying no to your rate. They're saying no to an offer they can't quite see.]]></description><link>https://theweeklyprescription.com/p/the-pricing-problem-that-isnt-about</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-pricing-problem-that-isnt-about</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Tue, 21 Jul 2026 19:42:13 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A client of mine here in Ely runs a linen service that delivers fresh, hotel-quality bedding to the vacation cabins that fill up around the Boundary Waters all summer.</p><p>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&#8217; bunks, and they never think about laundry once. It&#8217;s a good business built on a simple promise: travel light, sleep well, we handle the rest.</p><p>We were looking at the online shop, and I asked a question I ask a lot of owner-operators. <em>What else does the person buying this already wish they had?</em></p><p>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.</p><p>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.</p><p>Here&#8217;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.</p><p>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.</p><p>Nobody haggled over the towel price. They could see exactly what it did for them.</p><p>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&#8217;re starting to wonder if they should lower the rate. And almost every time, the rate is not the problem.</p><p>Per Sj&#246;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.</p><p>Buyers look irrational when they reject a fair price, but they&#8217;re actually predictable. They are not weighing your rate against your competitor&#8217;s rate. They are weighing your rate against what they can clearly see they&#8217;re getting. When they can&#8217;t see it clearly, price becomes the only thing left to measure, so price is what they push on.</p><p>I call this the Legibility Gap. It&#8217;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&#8217;s the only number the buyer can actually read.</p><p>Here&#8217;s the plain version: when a buyer can&#8217;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.</p><p>The capable owner-operator makes this harder on themselves than anyone. They&#8217;re close to the work, so the value is obvious to them. Of course it&#8217;s worth it. They can see the whole picture.</p><p>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.</p><p>The towel set worked because it closed the gap at the point of decision. The value was legible exactly when it needed to be.</p><p>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&#8217;t make the value clearer. It just teaches the buyer that even you weren&#8217;t sure it was worth the first number.</p><p>So here&#8217;s the prescription, and it costs you nothing but an honest afternoon. Write down what your client&#8217;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.</p><p>If you can&#8217;t write that sentence, your buyer can&#8217;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.</p><p>You don&#8217;t have a pricing problem. You have a problem nobody can see. Fix what they can see, and the price takes care of itself.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><p>P.S. If deals in your business keep stalling on price and you&#8217;re starting to wonder whether the number is wrong, it&#8217;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&#8217;s your price or your Legibility Gap.</p>]]></content:encoded></item><item><title><![CDATA[The everything week]]></title><description><![CDATA[Work isn't the only thing that will take your calendar. Sometimes the sky does it too.]]></description><link>https://theweeklyprescription.com/p/the-everything-week</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-everything-week</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Fri, 17 Jul 2026 14:09:53 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>We left Phoenix at 114 degrees. My mother is 88, and I flew her out of that heat so she could spend the rest of the summer at my cabin in northern Minnesota, somewhere she could actually breathe.</p><p>We landed at the Hibbing airport, birthplace of Bob Dylan, and stepped off the plane into 99 degrees.</p><p>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&#8217;ve seen.</p><p>We stepped out of the pan and into the fire. Literally.</p><p>Here&#8217;s the part I didn&#8217;t expect. My calendar didn&#8217;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&#8217;t quit, in a town I&#8217;d just landed in, with air quality warnings hitting my phone every twenty minutes. The issue didn&#8217;t get written. I let it slip.</p><p>I&#8217;ve written before about the calendar, in issue 004, &#8220;<a href="https://theweeklyprescription.com/p/your-calendar-is-not-yours">Your calendar is not yours.</a>&#8221; The diagnosis there was that work will fill any open hour you don&#8217;t claim first. Theme your days, block your priorities in advance, and work stops deciding your week for you.</p><p>That diagnosis still holds. But it assumes the thing competing for your attention is work. This week it wasn&#8217;t. It was my 88-year-old mother&#8217;s health, a wildfire complex bigger than most counties, and an air quality reading that made &#8220;go outside&#8221; a real medical question. None of those things emailed me first. None of them cared what day I&#8217;d themed for them.</p><p>I call this the Everything Week. It&#8217;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.</p><p><strong>Here&#8217;s the plain version of it:</strong> <em>a calendar that only survives a good week isn&#8217;t a system. It&#8217;s a guess. It only proves itself the week everything hits at once.</em></p><p>My structure held better than it would have five years ago, but it didn&#8217;t hold perfectly. The writing slipped two days. My mother did not. That&#8217;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.</p><p>A friend told me a line this week that&#8217;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&#8217;m not throwing out the griddle over it. I&#8217;m cooking the next one better, starting with this issue, two days late and still on the plate.</p><p>The prescription is not &#8220;protect your calendar better.&#8221; 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&#8217;t have a system. You have a system that has never been tested.</p><p>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.</p><p>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.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><p>P.S. If your business currently runs because you personally hold every plate in the air, that&#8217;s worth a conversation before your own everything week arrives. Start with a free 20-minute working call at <a href="https://www.yourwebguy.org/become-a-client">yourwebguy.org/become-a-client</a>. No pitch. Just an honest read on what would actually break first.</p>]]></content:encoded></item><item><title><![CDATA[The name nobody picked]]></title><description><![CDATA[Somewhere between the paperwork and the first invoice, you settled for whatever nobody argued against.]]></description><link>https://theweeklyprescription.com/p/the-name-nobody-picked</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-name-nobody-picked</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Wed, 08 Jul 2026 23:10:55 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In the fall of 2003, my dining room had no furniture in it. Just a sliding glass door covered floor to ceiling in small yellow Post-it notes, a folding table, and three guys with no jobs.</p><p>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.</p><p>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.</p><p>We didn&#8217;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&#8217;s in the right place, vote, take a break, vote again. We went through hundreds of names that afternoon.</p><p>The one that stuck wasn&#8217;t clever. It was obvious the second we saw it. We were, literally, a collective of professionals who met for lunch. Lunchbox Collective.</p><p>We had the name before we had anything else. That week I&#8217;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&#8217;t feel real yet. It became real the next day, when we landed our first paying client.</p><p>We&#8217;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&#8217;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.</p><p>Most businesses skip that afternoon entirely. They pick a name the way we almost picked that office, whatever doesn&#8217;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&#8217;s too tired to object.</p><p>I call it the Default Name. Nobody chose it. It&#8217;s just the one nobody objected to.</p><p>There&#8217;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&#8217;s secretly built from Latin and Italian roots meaning &#8220;wonder&#8221; and &#8220;purpose,&#8221; 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.</p><p>A name is not a description of your services. It&#8217;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.</p><p>I still run the same exercise today that put &#8220;Lunchbox Collective&#8221; on a folding table in my dining room in 2003, refined by twenty more years of doing it for clients. I&#8217;m not going to walk through the whole process here, because the process isn&#8217;t the point of this issue. The point is simpler: your name is either doing work for you right now, or it&#8217;s just the thing nobody objected to. Only one of those pays you back for the next twenty years.</p><p>If you&#8217;ve never actually run the exercise, that&#8217;s the first thing worth doing before you spend another dollar on a logo or a website. Ask yourself honestly which one you&#8217;re running on.</p><p>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.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><p>P.S. If your business name has never actually been tested against what it&#8217;s supposed to do for you, that&#8217;s worth twenty minutes. Start with a free working call at <a href="https://www.yourwebguy.org/become-a-client">yourwebguy.org/become-a-client</a>. No pitch. Just an honest read on whether your name is working or just surviving.</p>]]></content:encoded></item><item><title><![CDATA[The room we had no business winning]]></title><description><![CDATA[Three people, a speakerphone, and two dozen warm cookies against the biggest agencies on Madison Avenue.]]></description><link>https://theweeklyprescription.com/p/the-room-we-had-no-business-winning</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-room-we-had-no-business-winning</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Wed, 01 Jul 2026 18:04:13 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>The biggest pitch our young agency had ever been invited to, and I was not in the room. I was not even in the right state.</p><p>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.</p><p>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.</p><p>They had capital, momentum, and a shortlist of the biggest agencies on Madison Avenue.</p><p>And I could not get myself to the pitch.</p><p>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.</p><p>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.</p><p>Reschedule was the safe move. Reschedule was also how you go last, get measured against everyone who went before you, and lose.</p><p>So I did the thing that made no sense on paper. From Phoenix, I called the concierge at the W, where James was staying.</p><p>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.</p><p>He had no idea what he was walking into. Then I dialed in and ran the meeting from another state.</p><p>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.</p><p>We showed up with cookies, a speakerphone, and a plan we actually believed in.</p><p>I did not pretend to be bigger than we were. I did the opposite.</p><p>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.</p><p>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.</p><p><em>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.</em></p><p>We were wrong.</p><p>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.</p><p>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.</p><p>And this was exactly the kind of thinking he was looking for.</p><p>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.</p><p>A $360,000 contract. Three people. We beat firms that had more employees than our company had chairs.</p><p>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.</p><h2>Here is what actually happened in that room.</h2><p>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.</p><p>The lesson is that every other firm in that room was selling the same thing.</p><p>They were all capable. They all had case studies. They all promised to build the platform, hit the timeline, and manage the account.</p><p>Sit through four pitches like that and they blur together. The buyer stops hearing differences and starts looking for a reason to choose.</p><p>When nothing stands out, the safest reason wins. And safe almost always means biggest.</p><p>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.</p><p>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. <em>They choose the one they cannot forget.</em></p><p>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.</p><p>The speakerphone told him what he was actually buying. Direct access to the people doing the work, with nothing lost in translation.</p><p>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.</p><p>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.</p><p>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.</p><p>The move is not to look more impressive. It is to become impossible to line up next to anyone else.</p><p>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.</p><p>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.</p><p>If you have been reading a while, you already know this client. Two issues ago I told you how it ended.</p><p>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.</p><p>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.</p><p>Stop trying to be the biggest name in the room. You will never win that fight, and you do not need to.</p><p>Be the one they cannot forget.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p>]]></content:encoded></item><item><title><![CDATA[The last 20%]]></title><description><![CDATA[Every tool I ever bought got me most of the way there. Not one of them got me a paying customer.]]></description><link>https://theweeklyprescription.com/p/the-last-20</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-last-20</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Thu, 25 Jun 2026 03:42:02 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A while back I followed a free video series that promised to walk a beginner through building a complete application from end to end. I did the work. Every screen, every step. By the end I had a finished app.</p><p>Then I realized I had built something that could not actually run as a business.</p><p>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.</p><p>So it sat on a shelf.</p><p>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.</p><p>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.</p><p>It was a thirty minute conversation.</p><p>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.</p><p>The build took years of false starts. The business took thirty minutes in a room with someone willing to pay.</p><div><hr></div><p>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.</p><p>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.</p><p>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.</p><p>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.</p><p>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.</p><p>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.</p><p>A working app is not a business. It is a very convincing way to feel productive while avoiding the only question that matters.</p><div><hr></div><p>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.</p><p>I told him to put the stack down.</p><p>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.</p><p>Validate first. Build second. The idea deserves to be tested. It does not yet deserve to be built.</p><p>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.</p><p>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.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><p>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 <a href="https://www.yourwebguy.org/become-a-client">yourwebguy.org/become-a-client</a>. No pitch. Just a clear read on where the last twenty percent actually is.</p>]]></content:encoded></item><item><title><![CDATA[What I mean by "capable but stuck"]]></title><description><![CDATA[The people I write for haven't lost their edge. They've lost their confidence in it.]]></description><link>https://theweeklyprescription.com/p/what-i-mean-by-capable-but-stuck</link><guid isPermaLink="false">https://theweeklyprescription.com/p/what-i-mean-by-capable-but-stuck</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Wed, 17 Jun 2026 23:32:40 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It was April Fools Day, 2004. My car had stopped running earlier in the week. I had not taken in any money in six months. I gave blood that morning.</p><p>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.</p><p><strong>Then I looked up.</strong></p><p>There was a new steel and glass building on the corner I had never noticed. I thought: now that is an office.</p><p>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.</p><p>Someone I knew from years earlier walked by and stopped short. He looked at me and said: you&#8217;ll never get in here.</p><p>I asked if there was a leasing agent. He pointed to a door at the end of the gallery and walked away.</p><p>I knocked. A woman named Deb was heading out to an art event on the nearby campus. She mentioned the artist&#8217;s name. I stopped her.</p><p>I had known Laurie and Dan since my undergrad years. Spent summers with them in Telluride during grad school.</p><p>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.</p><p>I walked back. I was sweating through my shirt. I stepped into the locker room bathroom, washed my face, and cooled my neck.</p><p>She showed me the office. Half the size of the others. No door to the patio.</p><p>I said I&#8217;ll take it.</p><p>She asked if I wanted to know the price and the lease terms.</p><p>I said I trust you. We&#8217;re internet people and we&#8217;ll need time to get set up. Can we start May first and I&#8217;ll pay first, last, and deposit then?</p><p>She said yes.</p><p>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&#8217;t afford this. We don&#8217;t even have any clients yet.</p><p>I said rent is not due until May first. We have a month to figure it out.</p><p>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?</p><p>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&#8217;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.</p><p>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.</p><p>When we were done he looked around and said: well, it looks like you guys know what the hell you&#8217;re doing.</p><p>I looked him in the eye and said what would it take to get started?</p><p>He opened his leather attach&#233; and wrote a check for ten thousand dollars.</p><p>I walked back to where my partners had their ears pressed to the office door. I said are you guys hungry?</p><p>Then I showed them the check.</p><p>We walked down to the bank to open a business checking account. Lunch was on me.</p><div><hr></div><p>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.</p><p>I do not tell this story to impress you. I tell it because the people I write for did something like this once.</p><p>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.</p><p><strong>That is how the business got built.</strong></p><p>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.</p><p>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.</p><p>I call this the <em>Founder&#8217;s Ceiling</em>: 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.</p><p>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.</p><p>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.</p><p>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.</p><p>If you read this story and recognized yourself in it, you are in the right place.</p><p>The version of you that pressed that elevator button is not gone.</p><p>The question is whether the business you have built is running on systems, or on you.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><p>P.S. If you want an honest read on where the gap actually is, start with a free 20-minute working call at <a href="https://www.yourwebguy.org/become-a-client">yourwebguy.org/become-a-client</a>. No pitch. Just clarity on what is in the way.</p>]]></content:encoded></item><item><title><![CDATA[The foundation problem]]></title><description><![CDATA[Your business isn't losing customers because they can't find you. It's losing them because of what they find when they do.]]></description><link>https://theweeklyprescription.com/p/the-foundation-problem</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-foundation-problem</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Wed, 10 Jun 2026 17:20:03 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Eighteen years ago I was on Sabbatical at Youth Leadership Camps Canada. He was a student. I was already working online, building things on the web while most of his peers were still figuring out what they wanted to do with their lives.</p><p>We kept in touch the way people do when the connection is real.</p><p>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.</p><p>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.</p><p>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.</p><p>I was glad to.</p><p>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.</p><p>But before booking a call, they went looking for a number. Just a ballpark. Something to confirm the conversation made sense.</p><p>They could not find one.</p><p>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.</p><p>When I read it, I sat with that for a minute. Because I had built the exact foundation problem I diagnose in other people&#8217;s businesses. And it had almost cost me a real conversation with people I had known for nearly two decades.</p><p>So I fixed it. That same morning.</p><p><strong>DIAGNOSIS: The Foundation Fallacy</strong></p><p>Owner-operated businesses that plateau between $1M and $3M almost always have a foundation problem, not a traffic problem.</p><p>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.</p><p>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.</p><p>More traffic finding a misaligned foundation doesn&#8217;t produce more leads. It produces more people leaving.</p><p>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.</p><p>The owner notices the gap during sales conversations. By then, the prospect has already made most of their decision.</p><p>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.</p><p><strong>PRESCRIPTION</strong></p><p>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?</p><p><em>Not a friend. Not a colleague. Someone with no context.</em></p><p>What they cannot answer is the real problem.</p><p>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.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><p>P.S. If you want a clear read on where your foundation stands, start with a free 20-minute working call at <a href="https://www.yourwebguy.org/become-a-client">yourwebguy.org/become-a-client</a>. No pitch. Just clarity on what is actually in the way.</p>]]></content:encoded></item><item><title><![CDATA[Your calendar is not yours]]></title><description><![CDATA[Work doesn't take over your calendar. You hand it the keys.]]></description><link>https://theweeklyprescription.com/p/your-calendar-is-not-yours</link><guid isPermaLink="false">https://theweeklyprescription.com/p/your-calendar-is-not-yours</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Thu, 04 Jun 2026 00:37:53 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>A few years after the dot-com bubble burst, my friend Gordon resigned from the agency he had cofounded.<br><br>Rhino Internet was the 800-pound gorilla in Phoenix full-stack web development. Forty-plus staff. Gordon was the COO. When he walked, news spread fast.<br><br>About a month later he rented an auditorium in downtown Phoenix and invited a hundred or so of his former colleagues, friends, and professional associates. My fellow attendee that night was Jeff, Gordon&#8217;s cofounder. Neither of us knew what we were walking into.</p><p>What we walked into was Robin Sharma.</p><p>Gordon&#8217;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.<br><br>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.</p><p>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: <em>I get it</em>.</p><p>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.</p><p>The idea that changed how I run my week came out of that work.</p><p><strong>DIAGNOSIS: </strong><em><strong>Work will fill the void</strong></em></p><p>Robin&#8217;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.</p><p>Robin laid the original foundation. What I use today is my version of it, shaped by fifteen years of running it against real life.</p><p>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.</p><p>Here is where the calendar comes in.</p><p>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.<br><br><em>Because work will fill the open space. Every time.</em></p><p>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.</p><p>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.</p><p><a href="https://rememberthesabbathday.org">The Sabbath</a> 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.</p><p>I put the framework into a one-page worksheet you can download and fill in, below.</p><p><strong>The prescription:</strong> 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.</p><p>The wheel that rolls is the one you balanced on purpose.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p><div class="file-embed-wrapper" data-component-name="FileToDOM"><div class="file-embed-container-reader"><div class="file-embed-container-top"><image class="file-embed-thumbnail-default" src="https://substackcdn.com/image/fetch/$s_!0Cy0!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack.com%2Fimg%2Fattachment_icon.svg"></image><div class="file-embed-details"><div class="file-embed-details-h1">8 Forms Of Wealth</div><div class="file-embed-details-h2">5.65KB &#8729; PDF file</div></div><a class="file-embed-button wide" href="https://theweeklyprescription.com/api/v1/file/2e851f81-bc5f-4d75-91f8-906cc39569ac.pdf"><span class="file-embed-button-text">Download</span></a></div><a class="file-embed-button narrow" href="https://theweeklyprescription.com/api/v1/file/2e851f81-bc5f-4d75-91f8-906cc39569ac.pdf"><span class="file-embed-button-text">Download</span></a></div></div><p>P.S. Be sure to add your themes as non-negotiables to your Instructions for Claude and your Cowork Global instructions.</p>]]></content:encoded></item><item><title><![CDATA[The Accommodation]]></title><description><![CDATA[I restructured a client's payment schedule as a courtesy, and the bankruptcy court used that decision as evidence I knew they were in financial trouble.]]></description><link>https://theweeklyprescription.com/p/the-accommodation</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-accommodation</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Wed, 27 May 2026 15:52:56 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In 2006 my agency was brought in to build the digital backbone of one of the most ambitious mobile startups in the country.</p><p>The client was one of the original MVNOs. If the acronym means nothing to you, here is the short version: before the iPhone existed, this company was already trying to build what the iPhone would eventually become. A mobile virtual network operator. A company that did not own towers but leased them, then built products on top of the network. They were moving fast and had the capital to prove it.</p><p>We landed the project through a pitch I will save for another issue. What I will say is that it involved chocolate chip cookies, cold milk, and a COO who declared we had quite a set of cojones. We walked away with a $360,000 contract to design and build their complete online ordering, activation, and account management platform. The system had to serve both customers managing their devices and the company managing their media plans. It was a serious build.</p><p>Two weeks later my core team and I were in Hollywood.</p><p>The company had taken over the studio where the hit television show &#8220;24&#8221; was filmed. Their offices were actual sets. We set up for our kickoff meeting in the fictional Situation Room where Jack Bauer spent four seasons planning operations. One of my team members discovered the hard way that the wall outlets were props. Several laptops stopped working before we figured out why.</p><p>Two long rows of over 100 live call agents were processing customer orders in real time. This was not a company behaving like it was in trouble. This was a company that looked like it was already winning.</p><p>The contract was structured as six installments of $60,000. A clean, predictable payment schedule. Easy to plan around. We had signed it, started work, and everything was on track.</p><p>Then the request came in.</p><p>The internal team was growing so fast that accounting could not keep up. They were onboarding a new CFO to get ahead of the curve. In the meantime, could we split the remaining installments to help manage their cash flow? Same total. Same scope. Same timeline. Smaller payments, more frequent. Just a different cadence for the money already committed.</p><p>It seemed like a reasonable ask. I was not giving anything up. I was helping a good client navigate a temporary internal issue. The kind of accommodation you make when you trust the people across the table.</p><p>I added a clause to our memo of understanding. If a bi-weekly payment was missed, work would stop immediately and resume only upon receipt of payment. I thought that protected me.</p><p>The first installment arrived. Roughly $18,000. I paid my subcontractors. I paid my core team. Work continued.</p><p>The second installment did not arrive.</p><p>I stopped work as agreed. The client champion reached out. Growing fast, new CFO settling in, moving in the right direction. He believed what he was telling me, or at least he seemed to. A few of my trusted associates were in the middle of critical path work. I did not want to pull them off the project if this was a two-week delay. I kept them working.</p><p>Two weeks later I received a different kind of call.</p><p>The company had filed for bankruptcy in Delaware. The one with 100 agents processing orders in real time, the one that had taken over a television studio, the one that was going to change mobile media, was done. It turned out that even the client champion had not been told the full picture.</p><p>I had collected roughly $120,000 on a $360,000 project that was about one-third complete. I had associates who had done the work in good faith. I made every one of them whole plus a little extra for the disruption. That was not negotiable.</p><p>Over the next six months the Delaware bankruptcy court worked through the case. Larger agencies with secured creditor positions were made whole. Some took possession of hard assets, including company vehicles. I watched that process from the unsecured creditor line.</p><p>Then came the ruling I had not anticipated.</p><p>The court determined that by modifying my payment terms mid-project, I had demonstrated knowledge of my client&#8217;s financial distress. The accommodation I had made to be helpful was treated as evidence that I knew they were struggling and had renegotiated terms to extract money before the collapse. They ordered me to return one-third of what I had already collected.</p><p>I had lost the $240,000 still owed for work not yet paid. I was now also returning $40,000 I had already earned, deposited, and used to pay my team. The total damage was roughly $280,000. For a small agency, that is not a bad quarter. That is an existential hit.</p><h2>Here is what I know now that I did not know then.</h2><p>Your payment terms are not just a collection mechanism. They are a legal record of what you understood about your client&#8217;s financial condition at the time you signed them. When those terms change, you have created a document that a bankruptcy court can read as evidence of what you knew and when you knew it.</p><p>A company with healthy cash flow does not ask its vendors to restructure installments. A company that cannot meet the payment schedule it agreed to is telling you something, even when the people inside it do not fully understand what they are telling you.</p><p>Do not change your payment terms mid-project. Not for cash flow. Not as a courtesy. Not because the client is a good partner and you trust them. If the situation has changed enough to require new terms, the situation has changed enough to require a new decision about whether to continue at all.</p><p>I also learned something about contracts. I had a master services agreement. A legal team dissected it and turned it into a document that argued against me. A small agency cannot afford that fight. I now use plain English agreements. A stated prescription. Deliverables. A timeline. A payment schedule. Clear enough that a bankruptcy judge can read it and understand exactly what both parties agreed to.</p><p>The terms I sign are the terms I keep.</p><p>If I had walked away from that project the moment the second installment did not arrive, I would have been out one missed payment. Instead I stayed, trusted, and kept working.</p><p>That $280,000 lesson has a one-sentence prescription.</p><p><strong>Never change your terms.</strong><br><br>Richard D. Stuart<br><em>The Weekly Prescription</em></p>]]></content:encoded></item><item><title><![CDATA[The system that lied to me]]></title><description><![CDATA[I built a filter to protect me from bad bets. I never checked if it worked.]]></description><link>https://theweeklyprescription.com/p/the-system-that-lied-to-me</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-system-that-lied-to-me</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Wed, 20 May 2026 19:06:25 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I spent sixteen weeks delivering what I still believe was some of the best work I have done recently. The client walked at week eleven.<br><br><strong>DIAGNOSIS: </strong><em><strong>The system that confirms what you already want to hear</strong></em></p><p>The final five weeks were where everything was set to compound. The systems were built, the foundation was laid, and the returns were coming. And then there was no client left to receive them.</p><p>I spent a long time after that going over the work. Looking for the failure. Every decision held up. Every deliverable was sound. I had been delivering real value from week one and I could not find what I had done wrong.</p><p>It turns out I had not done anything wrong. I had just done the wrong engagement.</p><p>Let me back up.</p><p>Every client engagement I take begins with a twenty-minute call. Before the call, I give Claude context on the prospect and ask for four or five questions I should look to have them answer while I give them my complete, undivided attention. I record the call. After, the transcript goes into an Opportunity Evaluation System, a structured scoring rubric I built to run every prospect through before I commit to anything. Ten categories. A score out of fifty. A recommendation at the end: proceed or pass.</p><p>The number is supposed to tell the truth.</p><p>Except for a period, I was running a version of this system that I had built in another tool. And that version had hardcoded scores baked into its logic. What that means in practice: no matter what the transcript said, the system was returning the same outputs. It was not reading anything. It was confirming whatever I already wanted to believe.</p><p>It told me to proceed.</p><p>I proceeded. Ran the Trust Call to go deeper on the problem. Then the Prescription Call, where I laid out the defined approach, the timeline, and the value-based cost. I committed to a sixteen-week engagement.</p><p>Week eleven, the client walked.</p><p>I asked Claude to audit the system I had been trusting.</p><p>The response came back fast: you know this doesn&#8217;t actually work, right?</p><p>Claude rebuilt it. I fed the original intake transcript through the new version. The first twenty-minute call. Before any commitment, before any proposal.</p><p>It came back with a blinking red funding signal.</p><p>The client did not have the minimum budget required to maintain engagement momentum. The number was $312 per week. A figure the transcript had been carrying all along, sitting there in plain sight, waiting for a system that was actually reading it.</p><p>The recommendation: pass.</p><p>I felt relief.</p><p>Not because it absolved me of having made a mistake. Because it explained the shape of the mistake clearly. I had not failed to deliver. I had failed to verify the tool I was using to make a real decision.</p><p>I ran an after-action review with that clarity in hand. The work was right. The foundation was sound. Had the client finished the engagement, the results would have been exceptional. None of that was in question. The only thing that broke was the filter that should have caught this before it started.</p><p>The prescription: before you trust a system with a real decision, audit the logic. Not the output. The logic. Ask someone to look at how it actually works. A system that always says proceed is not evaluating anything. It is confirming what you already wanted to hear.</p><p>There is a small line of text at the bottom of every Claude session: &#8220;Claude is AI and can make mistakes. Please double-check responses.&#8221; I used to scroll past it. Now I read it as a feature, not a warning. The tool that admits its limits is safer than the one that appears to have none.</p><p>Last week I wrote about finding your 37. The number that forces real decisions.</p><p>This week: make sure the thing calculating your 37 is actually doing the math.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p>]]></content:encoded></item><item><title><![CDATA[The number that forces decisions]]></title><description><![CDATA[Vague goals create activity. A number creates decisions.]]></description><link>https://theweeklyprescription.com/p/the-number-that-forces-decisions</link><guid isPermaLink="false">https://theweeklyprescription.com/p/the-number-that-forces-decisions</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Tue, 19 May 2026 16:41:01 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Three months ago I started working with a seasonal lodge owner. Eight cabins. Fourteen weeks of peak season. A warm list of 1,500 people who already knew and trusted the place.</p><p><strong>DIAGNOSIS: </strong><em><strong>The goal that lets you keep moving without going anywhere</strong></em><br><br>The problem he brought me was vague: he wanted to grow awareness and get more bookings. When I asked how many bookings, he did not have a number. When I asked what a full season looked like, he said better than last year.</p><p>That is not a goal. That is a direction.</p><p>The first thing we did was count. He had 26 weeks already booked heading into his booking season. Peak season runs 112 available cabin-weeks. A large returning family had just cancelled their July block. The math told us what success had to mean: 37 additional bookings by a specific date.</p><p>That number changed everything.</p><p>Not because it was ambitious. Because it was honest. You cannot hide from 37. You cannot write a blog post and call it progress toward 37. You cannot boost a social post and feel good about 37. The number forced every decision: what we built, what we skipped, what we refused to rush.</p><p>The plan that came out of that number was concrete. A segmented email list. Targeted landing pages for three distinct guest types. Automated nurturing sequences. Each piece traceable back to one question: does this move the number?</p><p>This is the thing I see break capable business owners most consistently. Not the technology. Not the market. The goal.</p><p>They set goals you cannot count. More visibility. Better positioning. Stronger presence. These are directions, not destinations. And a destination you cannot see is just permission to stay busy.</p><p>The prescription is simple, not easy: before you build anything, before you write a single email, before you redesign anything &#8212; find your 37. The number that would force you to make real decisions if it were written on a whiteboard above your desk.</p><p>Not a percentage. Not a trend line. Not a feeling. A number.</p><p>Everything else is just activity.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p>]]></content:encoded></item><item><title><![CDATA[What I'm building and why I'm writing it down]]></title><description><![CDATA[Thirty years online. Still not a computer guy. Here's why that's the point.]]></description><link>https://theweeklyprescription.com/p/what-im-building-and-why-im-writing</link><guid isPermaLink="false">https://theweeklyprescription.com/p/what-im-building-and-why-im-writing</guid><dc:creator><![CDATA[Your Web Guy]]></dc:creator><pubDate>Tue, 19 May 2026 02:25:01 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!bo_t!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd5beda5-05e1-4ef6-9249-9de7578aa028_1280x1280.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I have been working online for thirty years. I started before Google existed, before social media was a concept, before most people had a reason to care about the internet at all.<br><br>I have helped hundreds of businesses build real solutions, and I have been blessed to work alongside some of the most talented designers, and technologists over these last 30 years.</p><p><em>And I still do not consider myself a computer guy.</em></p><p>That is not false modesty. It is the point.</p><p>The people I build for are not computer people either. They are the owner running a $2M wilderness lodge who knows their guests by name but has no idea why their website stopped generating leads. The attorney who built a practice worth trusting but cannot figure out why no one can find it. The biochemist laid off after twenty years who is rebuilding from scratch at 55 and does not know where to start.</p><p>These are capable people who have stopped believing it. That is the problem I keep showing up to solve.</p><p>Right now I am running three businesses, <a href="https://distillio.io/">building and shipping real apps</a>, hosting a weekly <a href="https://meet.google.com/ric-zopz-wbt">AI Mastermind</a>, and <a href="https://www.instagram.com/restassuredproject">walking alongside a friend</a> through something that matters deeply to him.<br><br>I work six days a week and honor <a href="https://rememberthesabbathday.org/">the Luni-Solar Sabbath on the seventh</a>. That rhythm is not background detail. It is the source. My faith does not sit alongside this work. It runs through it, and if you read long enough, you will see it.</p><p>I am not writing this publication to teach anyone. I am writing it because I keep seeing the same patterns break the same capable people, and I have found that naming them out loud is more useful than staying quiet about it.</p><p>Every week I will write one diagnosis. One thing that is breaking, why it is breaking, and what I would do about it. No trends. No listicles. One idea, fully realized.</p><p>If you are already capable and have half-convinced yourself otherwise, you are in the right place.</p><p>Richard D. Stuart<br><em>The Weekly Prescription</em></p>]]></content:encoded></item></channel></rss>