Episode 013: Knowing What Deserves a Yes

Building a Better Business is now also on Substack. The full series will continue to live here at JW Designs, but if you’d rather have new episodes delivered by email, you can follow along at https://bigjeffw.substack.com/.

In the last episode, I wrote about one of the stranger problems that comes with building a product. You can do the engineering, get the manufacturing right, build something people genuinely like, put it on a website, and still have almost nobody know it exists. That pushed JW Designs into search, social media, reptile communities, shows, creators, retailers, and partnerships. Some of those efforts have produced measurable results. Some created useful conversations. Some looked promising and then went almost nowhere.

Eventually, though, getting attention creates a different problem. People start bringing you ideas. A retailer might want to carry the product. A creator might want to test one. A customer asks for a size you do not make yet. Someone has an enclosure that could use a completely different lid. A builder sees a way to include your product in something larger. A conversation at a show turns into a possible partnership or a completely new direction.

At that point, the problem is no longer getting somebody to notice the business. The problem is figuring out which of those possibilities deserve time, money, engineering effort, production capacity, or even another conversation. That has turned out to be a much bigger part of building JW Designs than I expected.

Attention creates options

The reptile shows we did in August made this obvious very quickly. We went into that weekend mainly wanting people to see the EncloSure products in person. By the time it was over, we had placed several strategic samples, generated warm leads, opened a possible retail path, found people interested in testing products, and learned considerably more about where the product seemed to fit in the market. People who knew the reptile industry were handling the lids, looking at the fit and finish, operating the locking mechanisms, and reacting to them as manufactured products rather than just another 3D printed accessory.

That was great information, but it also created a lot of possible directions at once. Someone likes the product, so maybe they should become a retailer. Someone has an audience, so maybe we should send them a sample. Someone builds vivariums, so perhaps we should design around what they are doing. Someone mentions wholesale, so maybe we need to build a wholesale program. Someone has an unusual enclosure, so maybe that should become the next product.

When you are trying to grow a company, it is easy to interpret all of that as momentum. Sometimes it is. Other times it is simply a growing collection of choices, and every one of those choices competes for the same limited resources. Engineering time spent developing a speculative product is time not spent finishing something already in front of us. A sample sent to somebody who never uses it costs more than the filament and acrylic. There is production time, packaging, shipping, follow-up, and the mental space taken up by waiting to see whether anything comes of it.

The same thing happens with relationships. A possible retailer can consume hours of discussion without ever placing an order. A creator can genuinely love a product without producing a single sale. A customer can request a new size without there being enough demand to justify developing it. None of those things make the original conversation worthless, but they do mean Business Development cannot simply be the part of the business that finds interesting things. It also has to help decide which interesting things deserve to become real work.

Not every idea is an opportunity

One thing I have had to get better at is not calling everything an opportunity too early. A customer saying, “You should make one of these,” is not automatically an opportunity. Someone liking a product at a show is not automatically an opportunity. A product category that looks interesting during research is not automatically an opportunity. Sometimes those things are simply ideas or signals that deserve to be captured and nothing more.

That distinction matters because an idea is cheap. Acting on it is not.

Business Development gives me a place to let an idea earn its way forward. At the earliest stage, something may be nothing more than an interesting thought. Then maybe a second customer asks about it. Maybe search behavior suggests people are looking for a solution. Maybe competitors are already selling something similar. Maybe a builder explains why the current options do not work very well. At that point, there may be enough signal to justify spending some time understanding the problem, but that still does not make it a project.

This is where research becomes valuable. Before Engineering starts designing anything, I can look at whether there is a real customer problem, who is already trying to solve it, what people are paying, how crowded the market is, what materials or manufacturing methods might be required, whether the economics make sense, and whether the idea fits what JW Designs is already good at doing. Sometimes an idea becomes more interesting the deeper we look. Sometimes ten minutes of research kills it, and that is useful too.

I have started thinking about these possibilities as moving through stages. First there is an idea: something might be interesting. Then there may be a signal that a real problem or market exists. If that signal is strong enough, it becomes worth researching. Only after the research supports a plausible customer, economics, technical path, and strategic fit does it start looking like a vetted opportunity. Even then, it does not automatically become an active project. We still have to decide whether it deserves resources now.

That last part is important because a fully researched opportunity can still get a no. The market may be real but too small. The margins may be wrong. The engineering burden may be too high. The timing may be terrible. It may rely on customer behavior that we cannot verify. It may simply pull JW Designs in a direction that does not fit the company we are building.

The goal of research is not to prove that an idea is good. It is to understand what makes the idea work, and just as importantly, what could make it fail.

That changed the way I started using AI for Business Development too. I am not particularly interested in asking it to generate endless lists of things the company could make or markets we could enter. There are already more ideas than I have time to pursue. The useful part is taking a real idea that came out of the business and attacking it from several directions. Who actually needs this? What do they use now? What would they pay? Who else is doing it? What would it cost us to make? What assumptions are we making? What would have to be true for this to become repeatable?

If the idea still looks good after that, then it has earned the right to become a more serious conversation.

Not every opportunity has the same value

Even after something survives that process, the value of the opportunity is not always sitting in the immediate transaction.

We have one local relationship that has probably demonstrated that better than anything else. It is not really a conventional wholesale account. It has become part trade relationship, part real-world test bench, part source of product requests, and part validation channel. Products have gone into actual customer environments through that relationship, new enclosure sizes have surfaced because of customer needs, and some products have deliberately been supplied as development support rather than treated as ordinary sales.

That matters because there are limits to what I can learn inside my own shop. I can test fit, stiffness, assembly, print quality, hardware, packaging, and all kinds of other things before a product leaves here, but I cannot completely reproduce what happens after somebody else starts using it. A store employee notices something I missed. A keeper handles the product differently. An enclosure gets opened and closed repeatedly. A customer asks for something that never occurred to me because I do not own that particular enclosure or use it the same way.

That kind of outside use has value, even when there is not a normal purchase order attached to it. It also forced me to stop judging every opportunity by exactly the same measure. Some relationships generate revenue. Some generate product evidence. Some provide access to customers I otherwise would not see. Some create credibility or useful market information. The important part is understanding which kind of value I expect before I start investing time and product into the relationship.

The opposite lesson has been just as useful. We have also had opportunities that looked legitimate but were not worth actively chasing. One potential customer had a clear possible use for what we make and had been exposed to earlier products, but the relationship had historically been inconsistent and very price sensitive. Instead of continuing to pursue it, the position became simple: if they come back with meaningful volume and a clear commitment, we can have the conversation. Until then, the opportunity can sit where it is.

Another retailer gave us valuable information by essentially telling us that his own customer base was not a particularly good fit. He recognized the quality of the product, but his customers were largely shopping on price. That did not make him wrong, and it did not make the product wrong. It meant forcing the relationship would probably require JW Designs to compete in a direction that does not make much sense for us.

That distinction sounds obvious after the fact, but it is easy to miss when you are trying to grow. There is a natural temptation to turn every interested person into a prospect and every conversation into a follow-up. Sometimes walking away from an opportunity is not giving up on growth. It is protecting the business from spending resources in the wrong place.

There is also a large middle ground between pursuing something and rejecting it. A retailer relationship can exist without being proven. The products can be available, the basic economics can be established, and the infrastructure can all be working correctly. Until customers actually start buying through that channel, though, that is still infrastructure rather than proof that the channel works.

I have started thinking about a lot of opportunities that way. Something can be interesting without being promising, promising without being vetted, and fully vetted without being the right thing to do today. The correct response does not always have to be expansion. Sometimes it is watching. Sometimes it is research. Sometimes it is a small experiment. Sometimes it is simply keeping the relationship warm until there is more evidence.

Giving the future somewhere to live

Before I built a Business Development function into the Business OS, future opportunities had a tendency to compete with current work almost immediately. A customer request could start turning into an Engineering project before I had really decided whether we should build it. A possible retailer could become a Sales task because somebody showed interest. A product idea could send me into an hour of research late at night when I was supposed to be finishing something that already mattered.

A lot of that came from a very simple problem: if I did not act on the idea while I was thinking about it, I worried that I would lose it. Once there was a reliable place to put those opportunities, that pressure changed. The idea could be captured without becoming a project. The signal could be preserved without being treated as proof. Research could happen when there was a reason to do it, and the decision could wait until the business actually had the time or evidence to make one.

That made “not now” considerably more useful. It no longer meant an idea disappeared into a notebook or the bottom of an email thread. It simply meant the opportunity had not earned the right to interrupt the work already in front of us.

This is also one of the more useful places the Business OS has helped me separate thinking from action. An idea can live in Business Development while it is being understood. If the research begins exposing a real technical path, Engineering can become involved. If there is evidence of demand, Sales & Marketing can help understand the customer side. Operations can eventually evaluate whether something can be produced repeatably. But those departments do not need to absorb the work while the idea is still nothing more than a possibility.

That keeps the cost of curiosity relatively low. I can explore something without immediately turning the whole business toward it.

Knowing what kind of business we are building

The opportunities we have encountered have also helped define JW Designs by showing us what probably does not fit. The show weekend was useful for that because the strongest response came from people who saw the EncloSure products as premium manufactured products. The fit seemed much more natural with serious keepers, specialty breeders, direct customers, and higher-end enclosure or vivarium builders than with customers primarily looking for the least expensive replacement lid they could find.

That becomes important when evaluating opportunities because the biggest opportunity on paper is not automatically the best one. A potentially large account can still be a poor fit if serving it requires reducing quality, competing almost entirely on price, or creating a large amount of custom work that the rest of the business cannot support. A smaller relationship can be much more attractive if the product fits naturally into a premium build and both businesses are selling to customers who value the same things.

Product requests work the same way. A one-off custom request can be worthwhile if it teaches us something or exposes demand for a product that could become repeatable. That same request can be a distraction if it creates hours of engineering work for something that will never be built again. The question is no longer simply whether JW Designs can make it. Most of the time, if the problem is interesting enough, we probably can. The better question is whether making it moves the business in a direction we actually want to go.

That is one of the ways Business Development has become different from simple sales work. Sales is naturally concerned with converting an existing opportunity. Business Development sometimes has to stand farther back and ask whether we should be creating that opportunity at all. It has to look at the customer, the economics, the engineering burden, the evidence behind the demand, what we might learn, and what else will not get done if we say yes.

Learning to say yes deliberately

There is a version of entrepreneurship that makes growth sound like a continuous exercise in saying yes. Say yes to the customer. Say yes to the retailer. Say yes to the partnership. Say yes to the new product. Say yes to the opportunity. It sounds energetic and ambitious until the same person has to engineer the product, manufacture it, package it, answer the email, update the website, pay for the materials, and remember all of the other things that were already in progress.

In a small business, saying yes to something almost always means saying no to something else whether you acknowledge it or not. There are only so many hours, so much production capacity, and so much attention available. I would rather make that trade intentionally than discover it later when the important work has been pushed aside by something that merely looked interesting.

Some ideas should disappear during the first few minutes of research. Some signals deserve more attention but never become opportunities. Some opportunities should sit quietly until conditions change. Some deserve a small experiment. Some eventually become real projects. And every once in a while, something appears that survives the research, fits the business, solves a real problem, and makes enough sense that the answer is obvious.

That is what I increasingly think Business Development is for. It is not there to make the opportunity list longer. It is there to help possibilities earn their way forward while protecting the business from treating every interesting thing as work.

Engineering gave technical work somewhere to live. Operations gave manufacturing and fulfillment somewhere to live. Sales & Marketing gave attention and discovery somewhere to live. Business Development became the place where ideas, signals, research, and future possibilities could be understood before they became commitments.

Finding ideas is not especially difficult. There are always more products that could be built, more companies that could be contacted, more markets that could be explored, and more directions a business could take. The difficult part is understanding what actually makes an idea work, what could make it fail, what it would require from the business, and what it would displace if we decided to pursue it.

For JW Designs, that has gradually changed the question from “Can we do this?” to something much more useful:

Has this earned a yes?

That turned out to solve one problem and expose another.

Once the Business OS became better at helping me decide what deserved a yes, there was still a very real gap between deciding what should happen and actually doing it. A department could reason through the problem, research the options, weigh the tradeoffs, and reach a decision, but somebody still had to carry that decision into the website, the files, the settings, or whatever system the work actually lived in.

For most of the time I have been building the Business OS, that somebody was me. Recently, that started to change. The tools underneath the system became capable of doing more than helping me think. They could begin carrying out the work itself.

That sounded like an obvious improvement until it raised a much harder question: if the system can act, how do I make sure the part doing the work does not start making the decisions too?

That is where the next part of the story begins.