Early hands-on work can reveal what customers value, what delivery costs, and what is worth repeating.
“That doesn’t scale” can be a good reason to change how you work. It can also end a useful conversation before you understand what the work might teach you.
An early customer needs more help than expected. A prospective partner sees an opportunity outside your current plan. A buyer asks for something you could deliver manually, but haven’t built into the product.
Each could become a distraction. Each could also reveal something important about the business. The judgment is in deciding which efforts will help you discover something worth repeating and which will become expensive habits.
Having worked for and with multiple founders before becoming one myself, I’ve developed a strong respect for instinct and experimentation. Some worthwhile decisions begin with a sense that there’s more to an opportunity than the current plan allows. You still have to find out whether that sense holds up.
That’s part of the art of building a business. Frameworks help you make deliberate choices, but they can’t tell you in advance which customer request deserves another hour or which unexpected conversation might change your direction.
“That doesn’t scale” can end the conversation too early
A company that needs its founder involved in every sale, every implementation, and every customer issue will eventually run into a wall. You need a way for the business to grow beyond the capacity of the people who started it.
But early on, you’re often still figuring out what deserves to become a process.
Consider a software company whose first few customers need substantial help getting started. The team could decide that onboarding needs to be automated immediately. It could also spend time alongside those customers and learn why they need so much help.
Perhaps the setup is confusing. Perhaps the person who bought the product doesn’t control the data needed to use it. Or perhaps customers keep asking for help with a small part of the product that the company barely mentions in its sales pitch.
Those discoveries lead to very different decisions. One calls for a better interface. Another changes who needs to be involved before the sale closes. The third might change the offer itself.
Working through those situations personally takes time. It also gives you a chance to understand what’s happening before you commit resources to making it happen faster.
Gut instinct still has to answer to reality
This is where experience earns its keep. Sometimes you sense that a customer’s hesitation matters more than their enthusiastic feedback. Or that a prospective partner sees an opportunity your current plan doesn’t account for. You may struggle to explain why you want to keep pulling on that thread.
That instinct can be useful. Experience gives you patterns to draw on, including ones you haven’t consciously put into words. It can also make an unfamiliar situation look more like a familiar one than it really is.
I’d give the instinct room, then look for a way to test it.
If you think a different buyer would care more about the product, have a few conversations with that buyer. If you suspect a partner could open a new market, work through one specific customer opportunity together. If you think a customer will pay for an outcome, try delivering a defined version manually before building the full system around it.
There will be some wasted effort. You may discover that your idea doesn’t hold up. But you’ll have made a smaller commitment to find out, and you’ll have something better than your own conviction to guide the next decision.
Be careful what the first sale proves
There’s a trap in this approach, and founders are particularly good at falling into it.
You care deeply about the product. You know how everything works. You can make exceptions, solve problems across departments, and put in hours that never appear in the cost of delivery. With enough personal effort, you may be able to make an early customer successful.
That’s an achievement. It also leaves a question: what, exactly, did the customer buy?
Did they buy a product that solves a recurring problem? Did they buy your expertise? Did they buy a custom project at a price that only works because your time is effectively free?
Any of those can point toward a viable business, provided you recognize which one you’re building and price it accordingly. The trouble starts when you use one to prove the economics of another.
The first sale tells you someone was willing to buy under those conditions. The next few should help you understand which conditions can repeat and what it will cost to support them.
Watch what becomes easier
Some of these activities will never scale in their original form. You won’t personally sit beside every customer or spend weeks shaping every partner proposal.
What should carry forward is what you learn.
After working closely with a few customers, you should have a better sense of the questions to ask before they buy. You may know which setup decisions need guidance and which can safely become defaults. You may discover that a certain type of customer consistently needs more support than their contract can justify.
The next customer should benefit from that understanding. A colleague should be able to handle more of the work. Your estimate of the effort involved should become more accurate.
If the fifth engagement requires the same improvisation as the first, I’d want to understand why. You may be serving very different needs, making promises the product can’t yet support, or delivering something customers value without charging enough for it.
More volume won’t resolve those questions. It will make them more expensive.
Give exploration room and limits
I don’t think the answer is to turn every instinct into a formal exercise. There has to be room for curiosity, generosity, and conversations whose value isn’t immediately clear. Relationships would be fairly miserable if every interaction needed a business case.
You can’t schedule a lucky break. You can develop a relationship before there’s a deal to discuss or spend enough time with customers to notice a need they haven’t quite articulated. The return is uncertain, but that doesn’t make the effort wasted.
When an interesting possibility starts consuming meaningful company resources, though, it needs a clearer purpose. What could this effort help us decide? What are we willing to commit? What would make us stop?
I’d also look for commitment on the other side. A customer who supplies data, brings the right colleague into the conversation, or pays for a limited engagement gives you more to work with than one who simply says the idea sounds interesting. A potential partner willing to pursue a real opportunity with you is helping test the proposition.
Especially in a bootstrapped business, you need to preserve enough capacity to act on what you discover. An experiment that consumes all your time and cash can leave you with a useful answer and no ability to do anything with it.
There will always be decisions you have to make before the evidence feels complete. You prepare, pay attention, make a considered bet, and stay willing to change your mind.
Before asking how to scale an activity, give yourself a chance to understand what doing it well might teach you. Then use what you learn to change how the next one gets done.
Levrist helps emerging and growth-stage technology companies turn strong products into businesses that can grow through commercialization strategy, go-to-market execution, pricing, and strategic partnerships.
If you’re working through where to experiment and where to build more structure, I’d welcome a conversation. Visit levrist.com to get in touch.
If you found this compelling, please share it with a founder or colleague weighing what to keep doing personally and what to build into a repeatable process.
Make moves that matter.