Marco has been a licensed plumber for twelve years. He runs a small operation in a mid-sized city — three vans, four employees including himself, and a reputation built entirely on word of mouth. He is not looking to build an empire. He is looking to build something that solves a problem he has been living with since his first year on the job.
The problem is a specific type of pipe fitting access tool. The existing options on the market work adequately in standard configurations. In tight residential spaces — the kind Marco works in constantly — they are awkward, slow, and occasionally damaging to surrounding surfaces. Over the years Marco has modified his own tools repeatedly, improvising solutions that work better than anything he can buy. His employees use his modified versions by default. When a supplier rep visited the shop last year and saw the tools, he said, without prompting, that he had never seen anything like them.
That conversation stayed with Marco. Six months later, sitting at his kitchen table on a Sunday evening, he decided to find out whether the idea in his toolbox was actually a business.
Starting With the Right Question
Marco's first instinct was to call a manufacturer and ask about production costs. This is a common starting point and almost always the wrong one. Production costs are a later question. The first question is whether the problem is real and widespread enough to support a product business.
Marco had twelve years of evidence that the problem was real for him. What he did not know was whether other plumbers in other markets experienced the same frustration with the same intensity, or whether his specific working conditions — older housing stock, particular pipe configurations common to his region — made his situation unusual.
He spent two weeks doing something that felt uncomfortable for someone more accustomed to fixing things than talking about them. He called plumbers. Not suppliers, not manufacturers — plumbers. He found them through trade association directories, through social media groups, through the loose network of contacts accumulated over a career. He called fifteen of them in cities he had never worked in.
Eleven of the fifteen described a version of the same problem without being prompted. Three of those eleven asked, before the conversation ended, whether he was selling something.
That was his validation signal. Not a market research report. Not a focus group. Eleven out of fifteen plumbers recognizing the problem unprompted, and three of them already wanting to buy a solution that did not yet exist.
Building the Case Before Building the Product
Marco resisted the urge to move directly to prototyping. Instead he spent a week writing down the argument for why the product made sense to pursue. Not for a bank. Not for an investor. For himself, because he had seen colleagues pour money into ideas that felt obvious and arrive somewhere expensive and confusing.
The exercise forced questions he had not fully answered.
How would the product actually make money? Marco's instinct was to sell directly to plumbers through trade supply distributors. When he examined this more carefully he realized that distributor margins would compress his pricing significantly, and that plumbers — practical people with limited time — were unlikely to seek out an unfamiliar product through a new channel without a strong referral. The distribution assumption needed work.
What would it actually cost to bring to market? Marco had a rough number in his head. When he itemized it — tooling, prototyping, testing, certification requirements for professional trade tools, packaging, initial inventory, and the time he would spend managing the process while still running his plumbing business — the number was nearly three times his initial estimate. Not a reason to stop. A reason to plan properly.
Why was he the right person to build this? This question felt almost insulting at first. He had invented the thing. Of course he was the right person. But the question was asking something more specific. His advantage was not just the invention. It was twelve years of working knowledge about how the tool needed to perform under real conditions, a network of plumbers who trusted his professional judgment, and the credibility of being a practicing tradesperson rather than an outside inventor trying to sell into a trade he did not understand. Those were durable advantages. He wrote them down.
The Risks He Almost Missed
Marco was not particularly worried about competition. His tool was genuinely novel and he had filed a provisional patent application on the core mechanism. He was not worried about manufacturing — he had already identified a local machine shop with relevant experience. He was not worried about demand — the validation calls had given him confidence.
What he was worried about, in the background, was time. He was running a business. He had employees who depended on consistent work. He had customers who expected him to answer his phone.
When he examined his risk picture honestly, the time constraint was not just a personal worry. It was a project risk with a specific shape. The most dangerous scenario was not that the product would fail in the market. It was that the product development process would consume enough of his attention to degrade the plumbing business that funded everything else, at exactly the moment when the product was not yet generating any revenue to compensate.
This realization changed his plan. Instead of trying to manage product development personally while running the business, he identified a specific person — a recently retired manufacturing operations manager he knew through a trade association — who could manage the production side of the project on a part-time consulting basis. The cost was real. The risk it mitigated was larger.
He also named two other assumptions he had been treating as facts. The first was that professional tool certification requirements in his target markets were manageable within his budget and timeline. A single conversation with a certification consultant revealed that the process was longer and more expensive than he had assumed, and that it varied significantly by market. The US market, which he had been mentally including in his revenue projections, required a separate certification process that would delay his American launch by at least eight months.
The second was that his key supplier relationship — the machine shop he had identified — would be available and willing to prioritize his relatively small initial production run. It turned out the shop had a twelve-week backlog. His timeline needed to shift.
Neither of these discoveries killed the project. Both of them would have been expensive to discover after commitments had been made.
What the Plan Actually Looked Like
Marco's finished project plan was not a complex document. It was four pages. It covered the major milestones in plain language: finalize the design and complete the prototype, complete domestic certification, establish the distribution channel, produce the initial inventory run, and launch to the trade market with a targeted outreach campaign to the plumber network he had been building since his validation calls.
The timeline was fourteen months to first sale in his domestic market, with the US market following approximately eight months later. The financial picture was clear: total investment before revenue of approximately forty-two thousand dollars, funded from business savings and a small business line of credit, with a break-even point at roughly four hundred units sold in the first year.
The definition of success was specific. In twelve months from first sale: four hundred units sold, distribution relationships established with at least three regional trade suppliers, and a product reputation strong enough to generate inbound inquiries without active outreach.
Not a billion-dollar vision. A real plan for a real product built by a real person with real constraints and a genuine advantage.
What This Story Is Actually About
Marco is fictional. The pattern he followed is not.
The moves that made his planning process effective were not complicated or expensive. He validated with direct conversations before committing. He built a business case that forced the hard questions into the open. He examined his assumptions honestly and found the ones that needed testing. He built a plan around his actual constraints rather than an idealized version of them.
None of this required a business degree or a consulting engagement. It required a willingness to slow down before committing, and a structured way of thinking through the territory before walking into it.
The tool that helped Marco think through each of these steps is the same one you are reading this on.
If you have an idea sitting in your own toolbox, the questions Marco asked are the right place to start.