From Cause to Company: The Work Between an Idea and Regular Sales
For a mission-driven venture, the path from a cause to a company is not one decision but a sequence of changing states. The founder first has to learn what the venture could be, then make that possibility tangible enough for customers, partners, and resource providers to support it. This chapter distinguishes discovery from exploitation and follows what each contributes to venture emergence. The goal is not to memorize startup activities, but to understand what kind of uncertainty each activity can reduce and what regular sales do—and do not—tell us when they finally appear.
The distinction matters because a founder can be busy without becoming more informed, and informed without becoming operational. A polished plan may leave the critical assumption untouched. A registered company may still have no repeatable customer exchange. A first sale may confirm interest without proving that the venture can continue. Treating every action as equivalent hides the transitions that mission-driven ventures must actually make.
Discovery builds an evidence-bearing model
Discovery-related startup activities concern the conceptual side of venture creation: identifying, evaluating, and developing the business idea. In the focal study, they include discussing the idea with potential customers, researching its market potential, collecting information about competitors, working on a business plan, formulating that plan, and developing a prototype. These activities differ in form, but they share a function. They can change the founder’s understanding of the problem, the proposed solution, the people involved, and the resources the venture will require.
That function is easy to miss because discovery often looks less like progress than construction. No customer may be paying yet. The founder may spend time asking questions, comparing alternatives, or changing a prototype that will never be sold. But if the activity produces evidence that removes a false assumption, it can improve the model more than an impressive early launch. For a mission-driven founder, this is particularly important because the business may be trying to introduce a practice that customers, suppliers, or institutions do not already know how to support.
A customer conversation is not automatically validation. Its value depends on what uncertainty it addresses. A person may agree that a social problem matters but not adopt the proposed product. They may use the product once but not often enough to support regular sales. They may want the outcome but lack the authority, budget, or routine needed to purchase it. The conversation becomes useful when it helps the founder distinguish those possibilities and change the model or the next test accordingly.
The same logic applies to competitor research and business planning. Competitor information can reveal that an apparently novel solution is already available, or that the real differentiation lies in delivery, trust, sourcing, or institutional access rather than in the product itself. A business plan can force the founder to make relationships among customers, costs, partners, and activities explicit. A prototype can uncover a practical barrier that an abstract discussion conceals. None of these activities guarantees a viable venture, but each can make the assumptions visible enough to challenge.
Discovery is therefore best understood as evidence-generating work, not as a ceremonial prelude to “real” execution. The source study’s categories do not measure the quality of a conversation or the truth of a market estimate. They record whether different types of activity occurred. That limitation matters: doing more discovery activities is not the same as obtaining better evidence. Still, the distinction gives us a useful question for any early-stage venture: what did this action teach the founder, and what changed because of that learning?
The answer should affect the next state of the venture. If customer research shows that the intended users recognize the problem but cannot adopt the proposed solution, the founder may change the offering or the route to delivery. If competitor information shows that the market already has a strong substitute, the venture may narrow its claim or find a different source of value. If a prototype exposes a cost or usability barrier, the founder can test an alternative before committing to facilities or staff. In each case, discovery has done its job by making a choice more informed. The result may be continuation, redesign, or abandonment; only continuation is visible as forward motion, but all three can be valuable decisions under uncertainty.
This is particularly important when the mission makes the problem emotionally or morally urgent. Urgency can make delay feel irresponsible, yet premature exploitation can spend the very resources that would have supported a better solution. A founder may need to explain to supporters why a changed design or a rejected route represents progress. The evidence standard should not be “did the activity make the venture look more real?” but “did it improve the reasons for believing that the intended value can be delivered?”
Exploitation turns a model into an operating state
Exploitation-related startup activities concern making the business idea tangible and creating demand or operations. The focal study includes such actions as starting marketing or promotion, creating a website, acquiring equipment or facilities, seeking external funding, registering the company or legal form, hiring interns or employees, and participating in a support program. These activities put the model into contact with the conditions it must survive. They require commitments of time, money, relationships, and reputation that are different from the commitments involved in exploring an idea.
Exploitation cannot replace discovery because implementation amplifies the consequences of a weak assumption. Acquiring equipment before the operating requirements are understood can lock the venture into an expensive design. Hiring before demand or roles are clear can create obligations the business cannot support. Marketing can increase attention without creating repeatable demand. Legal formation can give the venture a formal identity without giving it a working value exchange. These actions remain necessary in many ventures; the point is that they solve a different problem from learning whether the model makes sense.
The reverse is also true. Discovery cannot replace exploitation. A founder can understand customer preferences, map the stakeholders, and refine a prototype without ever acquiring the resources or building the routines needed to serve anyone. An idea becomes an operating venture only when it can perform the work it promises, obtain the inputs it needs, and create enough demand to continue. For mission-driven ventures, implementation may be especially demanding because the model can require new partnerships, responsible suppliers, unfamiliar processes, or institutions that do not yet recognize the offering.
The two types of work should therefore interact rather than form a rigid two-step staircase. Discovery may show that a proposed operation is too costly, sending the founder back to revise the model. Early implementation may reveal that customers behave differently from what interviews suggested, sending the founder back to test a new assumption. A partner may agree in principle but fail to deliver in practice. A prototype may work technically while the supply chain cannot support it. The relevant progress is not simply movement from “idea” to “execution,” but a series of updates in which the model becomes more credible—or is abandoned before more resources are committed.
This lifecycle shows why “startup activity” is too broad a phrase to carry much meaning by itself. The same number of activities can describe different situations. One founder may be learning rapidly and delaying a costly launch for good reasons. Another may be repeatedly adding operations without confronting weak demand. One venture may have regular sales but an unresolved mission-related externality. Another may still lack sales yet be producing strong evidence that its model is improving. The activity category and the state transition must be read together.
Regular sales mark an operating threshold
The focal study uses regular sales as its main measure of firm emergence rather than profit. Respondents were asked whether the business had generated returns or revenue from selling goods or services for more than six of the previous twelve months. This choice fits mission-driven ventures because profit may not be the founder’s primary objective, even though a continuing market exchange is necessary for the venture to operate. Regular sales are evidence that the venture has crossed an important threshold: it is no longer only a proposal or a collection of startup intentions.
The threshold is deliberately modest. Regular sales do not tell us whether revenue covers the full cost of operations, whether the venture can withstand competition, or whether the business has produced the social or environmental change it claims to pursue. They also do not reveal whether the sales came from a stable pattern or from a narrow set of transactions that may not repeat. The measure answers one question—has recurring market exchange begun?—while leaving the next questions open.
This is why sales should be treated as feedback, not a verdict. If regular sales appear, the founder has evidence that some part of the offer and exchange can work. They still need to learn whether the model is financially durable and whether its mission is represented in actual operations. If regular sales do not appear, the founder has not necessarily disproved the cause. They have evidence that the current route has not yet produced a recurring exchange, and that evidence should prompt a more specific diagnosis: weak demand, poor access, unsuitable price, unresolved supply constraints, inadequate resources, or a model that asks stakeholders to do more than they can sustain.
Regular sales also have a different evidentiary meaning from a mission claim. A buyer may return because the offering is convenient, affordable, or necessary, without the venture producing the social or environmental benefit the founder intended. The reverse can occur as well: an intervention may be valuable in principle but fail to find a repeatable way to reach the people or organizations who need it. The sales measure is useful precisely because it is narrower. It gives the researcher and founder a shared operating threshold while leaving impact, distribution, and durability open for later tests.
The study also treats time as relevant to emergence. It examines the distance between the first startup-related activity and the later outcome. Earlier research summarized in the article suggests that the chance of firm emergence is highest relatively early in the creation process and declines as time passes. The logic is not that fast founders are always better or that a slow venture is always doomed. A long period without regular sales can mean that the model is still being developed, but it can also mean that negative feedback has accumulated without changing the route. Time becomes informative when combined with what the founder has learned and how the venture has responded.
For mission-driven founders, this timing question is especially sensitive. The mission may justify a longer search because the venture is attempting something less established and must assemble a broader set of relationships. But the same commitment may make it easier to continue treating effort as evidence of progress. A founder who has spent another year contacting partners, refining operations, and defending the cause has invested more than money. That investment deserves respect, but it does not by itself increase the probability that customers will eventually return.
A disciplined lifecycle view holds both possibilities together. Discovery should continue when new tests can materially reduce uncertainty or reveal a better route. Exploitation should continue when implementation is producing evidence of demand and operational learning. A return to discovery is rational when implementation exposes a broken assumption. Abandonment is rational when the available evidence shows that the route cannot reach regular sales under the resources and constraints available. None of these outcomes, by itself, settles the question of long-term social impact.
The main lesson is therefore narrower and more useful than “move fast.” Mission-driven ventures need movement between states, not motion for its own sake. Discovery makes the model more knowable; exploitation makes it more testable in the world; regular sales show that an operating exchange has begun. The next question is how the focal study’s data connect missionary identity to these activities and outcomes—and how far those statistical relationships can safely be taken.