What a Customer Transaction Reveals Before Revenue Scales
This chapter examines the early-stage new technology-based firm at the point where a business plan still contains more intention than history. The specific question is what the plan’s descriptions of customers, financiers, partners, and people can reveal about the venture’s ability to connect with its environment. Understanding that mechanism helps a reader treat customer transaction maturity as an observable proxy for adaptive capacity—useful evidence, but not the capability itself and not a direct forecast of survival.
A young venture does not survive on an idea in isolation. It needs access to money, people, suppliers, partners, and customers, and it must revise how those resources are assembled as conditions change. The focal study calls the observable relationships created through these exchanges “transaction relations.” The term sounds more technical than it is: it refers to the strength or maturity of the venture’s actual or intended dealings with other parties, as described in its business plan.
From a network story to an observable mechanism
A generic claim that a venture has a network tells a screener very little. Almost every applicant can say that it has contacts, advisers, or potential partners. A transaction relation asks a more concrete question: what kind of exchange has been established, with whom, and at what stage? A plan that names a target market is making a different claim from one that reports market tests. A plan that says investors are interested is making a different claim from one that documents acquired capital. The difference is not the number of names on a slide; it is the maturity of the relationship that links the venture to a needed resource or a real exchange.
This is why the construct is connected to venture life cycles. In a seed phase, founders may be coordinating resources and exploring an idea. In an early start-up phase, they may be testing a first product and beginning to establish external exchanges. In a growth phase, the venture is attempting to operate at a larger scale. The relationship between the venture and its environment changes as the business model develops, and those changes can leave traces in a written plan.
The study interprets transaction relations as a proxy for dynamic capabilities. In plain language, dynamic capabilities are the capacity to create, extend, or modify a venture’s resource base as circumstances change. A venture that can sense an unmet need, act on an opportunity, and reorganize its resources may be better positioned to withstand uncertainty. But those internal capacities are difficult to observe directly, especially before a company has a long operating record. The study therefore looks for an intermediate outcome: the relationships the venture has built as a visible consequence of interacting with customers and resource providers.
That distinction matters. The customer relationship is not a transparent window into the founders’ minds, and a high maturity score does not prove that the team can adapt in every future situation. The relationship is an observable trace that may be consistent with adaptive capability. It can also reflect other forces: a favorable market, unusually helpful partners, a founder’s prior reputation, or a sector where customers commit early. The focal evidence supports an association between the coded relationship and later survival; it does not establish which hidden capability produced the relationship or whether the relationship itself caused the outcome.
The four dimensions make the mechanism more specific:
- Customer relations connect the venture to demand, market tests, early sales, and turnover.
- Financier relations describe how the venture moves from founder or family resources toward external funding and professional investment.
- Partner relations describe movement from an intention to cooperate toward developed supplier or organizational relationships.
- Human-resource relations describe movement from a single founder toward a team and then a more developed organization.
These are not interchangeable measures of general momentum. A capital-intensive venture may need financing before it can demonstrate customer turnover. A research-heavy company may depend on specialist people or institutional partners before a market exchange is possible. A software venture may test demand with a small team. The dimensions are separate because they represent different resource channels and because their relevance can depend on stage and business model.
The relationship to survival is therefore indirect. External ties can help a venture obtain resources, validate assumptions, or adjust its offering, but the presence of a tie does not guarantee that the exchange is profitable, repeatable, or defensible. A customer can express interest without paying. A partner can sign a memorandum without delivering capability. An investor can provide capital that extends the runway without solving the underlying market problem. Transaction maturity is informative partly because it narrows the distance between a plan’s story and an interaction with the outside world; it does not eliminate that distance.
The dotted links are deliberate. They mark a proposed measurement relationship, not a proven causal chain. The venture produces observable relationships through interactions with its environment; those relationships are used as an indirect proxy for adaptive capability; the study then tests their association with a later survival outcome. The diagram does not say that a score guarantees the capability, or that the proxy explains every path to survival.
How maturity turns narrative into a score
The instrument used in the study assigns each of the four dimensions a five-point scale tied to five venture stages: early seed, late seed, early start-up, late start-up, and growth. The stages are not a claim that every venture develops in exactly that order. They provide a common ladder for comparing descriptions that otherwise differ in language and detail.
For customers, the lower end begins with a defined target market. A more mature description includes market tests, then increasing turnover, and eventually considerable turnover. The progression is meaningful because it moves from an assertion about who might buy to evidence that the venture has interacted with potential customers and generated economic exchange. It still leaves important questions unanswered—how many customers, at what price, with what retention, and at what cost—but it is more informative than an untested market label.
The other dimensions use analogous progressions. Financier relations move from planning external funding, through government funds, bank credit, and angel investment, toward professional risk capital from more than one investor. Human-resource relations move from a single founder to a team that divides tasks and then to a more developed organization. Partner relations move from an intention to cooperate toward a functioning supplier network with regular transactions. The scale records a stage of relationship maturity, not a moral ranking of one type of venture over another.
For each dimension, the highest maturity mentioned in the business plan determines the value used in the analysis. This rule makes a messy document comparable, but it also creates a compression problem. Suppose a plan mentions a market test that failed, a later pilot that generated a small payment, and an ambitious projection of future turnover. A maximum-based score can preserve the highest observed stage while hiding the sequence, the failure, and the uncertainty around repeatability. It does not tell us whether the strongest relationship is current, central to the business model, or merely an isolated event.
The same issue appears across dimensions. A venture may have a sophisticated financing relationship and immature customer contact. Another may have paying customers but no stable supplier network. Taking only one maximum score per dimension can miss the pattern formed by timing and interaction. A higher customer stage may be more informative for one business model, while financing or specialist people may be the binding constraint for another. The study’s measure creates a tractable representation; it does not claim to preserve the full relational history of the venture.
There is also a difference between the presence of a relationship and the role that relationship plays in the business model. A supplier tie may be essential for delivery in one venture but replaceable in another. A customer pilot may be a genuine test of demand, or it may be a one-off demonstration arranged by an enthusiastic early adopter. A funding relationship may extend the venture’s life without improving its ability to learn from customers. The five-point scale can mark the described stage of each relationship, but it cannot by itself determine whether the tie is strategically central, economically healthy, or likely to persist.
This is the trade-off behind any common ladder. Without some compression, plans cannot be compared consistently: one founder may write several pages about a customer conversation while another reports the same stage in one sentence. With too much compression, the signal becomes vulnerable to wording, selective disclosure, and the accidental prominence of one unusually advanced relationship. A maximum score is therefore useful for asking whether a mature relationship appears at all, but insufficient for answering how reliable, repeatable, or profitable that relationship is.
The limitation also affects how the four dimensions should be combined. A venture with moderate customer maturity and strong people may be more viable than one with high customer maturity and no capacity to deliver, but the source evidence does not establish a universal rule for such combinations. The focal study’s later analysis deliberately favors the customer dimension for its predictive contribution in this sample; it does not test every interaction among relation stages. That is an important reason to keep the construct open to refinement rather than turning its four labels into a finished scorecard.
Customer relations nevertheless have a special reason to attract attention in an early survival screen. They are close to the market’s response to the venture’s assumptions. A customer interaction can reveal whether a proposed problem matters to someone outside the founding team, whether a product or service has been tested, and whether an exchange has begun. Those signals can indicate market sensing and the first steps of seizing an opportunity. They may also show that the venture is adjusting its resource use around observed demand rather than simply elaborating an internal technology story.
“Close to the market” is not the same as “more important in every venture.” The focal paper notes that financier, partner, and human-resource relationships may matter under different conditions. Their weaker predictive contribution in the reported model could reflect stage dependence, capital intensity, differences in how easily quality is captured in a standardized plan, or information already contained in the customer dimension. The absence of incremental predictive value in this sample is not evidence that the other relationships have no practical value.
Nor does a customer relationship automatically mean product-market fit. Early interest may be exploratory. A pilot may be subsidized. A first sale may be unprofitable or impossible to repeat. A large named customer may create concentration risk. The measure’s value is that it prompts a more discriminating question than “Does this plan sound promising?” It asks what external interaction has already occurred and how mature that interaction is. A decision-maker still has to verify the answer and examine its economics.
That verification concern is especially important because business plans are persuasive documents. Authors may have incentives to present relationships in the most favorable light. The focal study argues that due diligence can check claims involving customers, employees, revenue, and suppliers, and cites evidence that described transaction relations can overlap substantially with the venture’s reality. That is a reason to treat the text as usable evidence, not a reason to assume every statement is true. The relationship between plan and reality remains part of the screening risk.
The measure is thus best understood as a disciplined reduction of a narrative, not as an objective essence extracted from it. It preserves a comparable maturity signal and loses detail about timing, quality, failed exchanges, and combinations among dimensions. It offers a way to test whether a particular observable feature adds information to a survival prediction. It does not turn a business plan into a neutral record, and it does not turn dynamic capability into a directly observed variable.
The next task is to hold these distinctions together: the venture is the subject, transaction maturity is the signal, survival is the measured outcome, and adaptive capability is an interpretation that sits between them. Once those pieces are kept separate, the later comparison between customer evidence and gut-feel judgment can be read as a test of added predictive information rather than as a verdict on which kind of person or venture is inherently better.