The dispatch spreadsheet started as a whiteboard in 2019. Migrated to a shared Google Sheet in 2020. Grew a new tab per service line in 2022. Now it has twelve tabs, thirty formulas, three broken cells nobody knows how to fix, and one person on the team who is the only one who actually understands it.
You have been asking a vendor to build the real version of that sheet for five years. Somewhere in a demo call in 2022, you gave up.
Last week Nate B Jones posted a piece called Personal software is here, and you can build yours this week. The opening story is about a commuter in Amsterdam who was tired of the ferry timetable. He built a small piece of software that pulled the live schedule, printed it on a paper-thin display, and pinned itself above his kitchen counter. The commuter is not a developer. He is a guy who was tired of standing on a dock. That is the whole story.
Here’s the thing. The Amsterdam ferry is your dispatch spreadsheet. It is the renewal-tracking sheet in the insurance office. It is the patient-callback log that lives on three staff members’ phones. It is the client-status board with twelve tabs. The wish you have been carrying for years that the market never bothered to build because the market is too small, or the shape is too specific, or the buyer never had the budget.
The wish has been sitting on your shelf because you kept waiting for someone else to make it. The wait is the choice you have been making.
The old rule was true. It is not true anymore.
For twenty-five years the rule was simple. If the software does not exist, either wait for it, buy an expensive workaround, or hire an engineering team you cannot afford. The cost of the small piece of software you actually needed was too high for the size of the problem. So you built the spreadsheet workaround. You added a tab. You wrote a formula. You promoted one person to Sheet Owner and prayed she would never leave.
That rule has quietly collapsed while you were watching it.
The cost of building the specific small tool your business needs has fallen faster than any operator I talk to is tracking. Not “AI is fast.” That is the marketing sentence. The operator sentence is this: the price of a working, custom, one-shop-only piece of software that fits your renewals, your callbacks, your dispatch, is now inside the budget you were already spending on the workaround.
The wait is no longer a rational decision. It is a habit.
The habit to break
You have been waiting for a vendor to solve a problem your business has always owned.
The vendor did not come. The vendor was never coming. Every 5-to-50-person business has at least one recurring problem the market does not want to solve. The market shape is wrong. The buyer count is too low. The problem lives inside operational particulars that no product manager three states away is ever going to write down for you.
You already knew this. You built the workaround because you knew. The habit is treating the workaround as permanent. It literally is not permanent. It is a bookmark you set when the tools could not do this yet. The bookmark has expired.
Yeah. That is the sentence.
What the discipline actually looks like
The panic move here is to open a coding tool and start building. Do not do that yet.
The wish needs a shape before it needs a builder. Any builder. Human, AI, whatever. If the wish is fuzzy in your head, the thing you build will be fuzzy in your business, and you will have spent your afternoon producing a slightly worse version of the spreadsheet you already have.
The discipline for getting a wish into a shape has a name. We call it the Prep List. It is normally the discipline for figuring out which piece of work is ready to hand off before you hand it off. The same shape works for figuring out which wish is ready to build before you build it. You do not need to walk its four columns today. You need to know the discipline exists, and that there is a plain-language version of it that fits on one page.
Nate’s seven questions are that plain-language version. Same idea, sharper wording, and any small-business operator can answer them without a developer in the room.
Who is this for. What happens now that is annoying. What should happen instead. What information could make that possible. Where should the result appear. Who should be allowed to see or change it. What would actually be bad if it failed.
That is the wish, in a shape a builder can take.
Right?
An insurance agency principal I was talking to last month had a renewal-tracking sheet that carried thirty years of institutional memory. She had priced replacing it with a proper agency management system. Forty thousand a year. “I have described this thing to eight vendors,” she said. “None of them build what I actually do.” Eight vendors. Eight demos. Eight passes.
Here is what I would have said to her if I had known then what I know now. The reason none of them built it is that none of them have to. The market you are describing is you. The buyer is you. The specification is you. And the cost of writing that specification down on one page and handing it to a small builder, human or otherwise, is now smaller than one more demo call.
Does that make sense? The wait is not caution. The wait is a spreadsheet with three broken cells and one person who cannot leave.
The scope trap and the useful boundary
Now. Somebody is going to read this and go build a rebuild of Salesforce over the weekend. Do not do that.
The scope of a piece of personal software is the small thing that annoys you every Tuesday. Not the platform. Not the suite. Not the “modernization initiative.” The thing.
If the medical practice’s patient-callback log lives on three phones, the wish is a page that shows today’s callbacks, checked off as they happen, that all three phones can see. That is one wish. That is one page of software. That is not a patient management system.
If the professional-services firm has a client-status board with twelve tabs, the wish might not even be one piece of software. The wish might be four small ones, one per service line, each doing one job well, none of them trying to be everything.
The move is one wish, one shape, one page, one builder. Then look up and see whether the second wish is still on your shelf, or whether it left the shelf on its own once the first one was gone.
The Monday Move
Run the Seven Questions On One Page.
Pick one recurring problem your business has that your current tools do not solve. The renewal-tracking sheet. The patient-callback log. The dispatch board. The client-status page. The reorder-timing rule that only lives in your head.
Do not open a coding tool. Do not open a chatbot. Do not go looking for a vendor. Get a piece of paper.
Answer seven questions.
- Who is this for.
- What happens now that is annoying.
- What should happen instead.
- What information could make that possible.
- Where should the result appear.
- Who should be allowed to see or change it.
- What would actually be bad if it failed.
Guardrail: do not skip any of the seven. If you cannot answer question two in one sentence, the problem is not yet described sharply enough to hand to any builder, human or AI. Owner of this move: you, the founder, or the person on your team who has been quietly building the workaround for the last five years and knows exactly what the software should do. Metric: one page, seven answers, in the language of the person who has to live with the result.
Next step: read the page out loud to one other person on the team. If they nod and say “yes, that would help,” the wish is in a shape a builder can take. If they ask three clarifying questions, revise the page before touching a tool.
The close
The wish has been sitting on your shelf because you kept waiting for someone else to make it. The wait is the choice you have been making.
The cost of building the thing you actually need has quietly collapsed while you were watching. What has not collapsed is the discipline of describing the wish clearly enough that a builder can take it. That discipline is the same one it has always been. It just sits closer to the shelf than it used to.
Get out the paper. Answer the seven questions. See what the shelf looks like on Monday.
Translated from Nate B Jones, “Personal software is here, and you can build yours this week” (natesnewsletter.substack.com, 2026-08-19).
~ source material · Translated from Nate B Jones, 'Personal software is here, and you can build yours this week' (natesnewsletter.substack.com, 2026-08-19). Distilled and operator-translated.
