Why service ventures face a different survival test
For the Portuguese new ventures examined in the service-survival study, the immediate question is not simply whether the firm has a good idea or a committed owner. It is whether the firm can produce a dependable customer experience when production happens in real time, depends on people, and cannot be stored for later. Understanding that operating problem helps explain both the study’s higher failure hazard for service ventures and the later finding that employee scale and family ownership matter differently within services.
A service venture is not just a small manufacturer with a different label. A manufacturer can often make an item before a customer arrives, inspect it against a specification, store it, and sell it later. A service venture may have to establish value before the customer can fully evaluate it, coordinate the customer’s participation while delivering the service, and deal with an outcome that varies from one encounter to the next. The difference is a chain of dependencies. If one link is weak, the problem can reach the customer immediately.
From an intangible promise to a repeatable customer experience
The first difficulty is that a service is often intangible at the moment a customer decides whether to buy. A physical product can provide visible clues about its size, materials, or finish. A service may instead be represented by a description, a price, a brand, a review, or the provider’s assurance. These signals help, but they are not the service itself. The customer must decide whether to trust a promise before seeing the full result.
That gap matters especially for a young venture. A new firm has not yet accumulated a long history of reliable encounters, recognizable reputation, or a large base of customer testimony. It may know what it intends to deliver, but prospective customers cannot directly inspect the future experience. If the first encounter falls short of the promise, dissatisfaction can spread beyond the single transaction. Negative word of mouth can make the next customer harder to acquire, while a disappointed customer is less likely to return. The venture therefore has to manage both delivery and the credibility of its description of delivery.
This does not mean that marketing can solve an operating problem. Clear communication can reduce uncertainty about what the service includes and what the customer should expect. It cannot compensate indefinitely for inconsistent performance. If a venture repeatedly promises more than its processes can deliver, the very messages meant to build trust can become evidence against it. The service-survival study consequently treats intangibility as part of a larger system in which value communication, customer expectations, actual experience, and retention are connected.
The second difficulty is that the customer often participates in producing the outcome. A service is not always handed over as a finished object. The customer may supply information, make choices, arrive prepared or unprepared, follow instructions, or interact directly with the employee delivering the service. That participation can improve the result, but it also introduces variation that the venture does not fully control. Two customers may receive the same formal offering while contributing different inputs or having different expectations.
This is why a final inspection is not enough. A product firm can inspect an item after production and remove defects before sale. A service firm may discover the defect only while the customer is present, when the interaction is already shaping the customer’s judgment. The relevant control system must therefore operate before and during the encounter: defining the promise, preparing the employee, gathering the right customer information, setting boundaries, and creating a way to recover when the interaction goes wrong.
The third difficulty is human variability. Service employees differ in skill, motivation, communication, judgment, and ability to respond under pressure. Even when they follow the same broad policy, their behavior can produce different experiences. A new venture may depend heavily on one or two people whose knowledge is not written down. If one person is absent, overloaded, or leaves, the venture may lose not only labor capacity but also the tacit method by which customers were served.
This dependence creates a two-way risk. Inconsistent encounters can weaken customer trust and retention. At the same time, the pressure to keep every encounter acceptable can exhaust the employees who carry the service system. The venture’s brand then becomes difficult to separate from the individual who happens to be present. A business that appears to offer a stable service may in practice be offering a series of personal performances with no reliable bridge between them.
The service study describes variability in delivery as a defining challenge rather than an occasional defect. When production and consumption occur together, each encounter is a small test of the venture’s operating model. A customer does not experience the firm’s intention, its business plan, or its ownership structure directly. The customer experiences a sequence of interactions. Survival is affected when those interactions are too inconsistent to support repeat demand, referrals, and a reputation for reliability.
The sequence is therefore cumulative. An intangible promise creates uncertainty before purchase. Customer participation and employee behavior shape the live encounter. The encounter produces a judgment about quality. That judgment affects trust, word of mouth, and the likelihood of returning. The outcome of one interaction becomes part of the conditions under which the next interaction must be sold.
The diagram does not imply that every encounter follows a perfectly linear path. Its purpose is to show where a service venture’s reliability is produced. The venture process can support the employee with training, information, and quality controls, but the customer remains part of the encounter and the employee remains part of the output. Feedback then changes the venture’s future demand. A weak routine can therefore reproduce the same problem, while a useful feedback loop can make the operation more dependable.
Perishability, demand swings, and the liabilities of being new and small
Services add another pressure because unused capacity cannot usually be stored as inventory. An empty appointment, an idle employee hour, or an unfilled place at a scheduled service time cannot simply be placed on a shelf and sold next week. Low demand can leave labor and facilities underused, reducing revenue without reducing all of the associated costs. High demand creates the opposite problem: if the venture accepts more work than its people and routines can handle, service quality may fall precisely when customers are most numerous.
This makes demand management part of survival. Forecasting, scheduling, capacity allocation, and, where appropriate, pricing for different demand periods can help the venture avoid both underuse and overload. Digital booking or communication tools may improve coordination, but technology is not a substitute for a realistic capacity model. If the venture promises a response time or level of personal attention that its available people cannot sustain, a fuller order book can increase rather than reduce failure pressure.
Perishability also makes timing important. A product venture may accumulate stock during a slow period and sell it when demand returns. A service venture has fewer ways to carry unused production capacity forward. That exposure can be especially severe for a young firm whose demand is uncertain and whose fixed resources are limited. Early revenue weakness may reduce the funds available for training, marketing, technology, and process improvement—the very investments that could make the next customer encounter more reliable.
The service-survival study connects these operating conditions to the broader liabilities of smallness. Small organizations typically have fewer financial, human, and technological resources. They may not be able to assign separate people to sales, scheduling, quality control, customer support, and delivery. One person may perform several roles, so a problem in one part of the operation quickly affects the others. Small ventures may also struggle to establish legitimacy, build networks, obtain favorable terms, and attract specialized employees.
These are not merely disadvantages of having fewer employees in an abstract statistical sense. They are weaknesses in the venture’s ability to absorb variation. If one employee is unavailable, there may be no substitute. If demand peaks unexpectedly, there may be no second team to take the work. If a customer complains, the person who must fix the problem may also be the person responsible for the next scheduled service. If a new competitor appears, the venture may lack the marketing budget or specialized expertise needed to respond.
Newness adds a related problem. A young venture has fewer established routines, networks, and stakeholder relationships. It may not yet know which customer information predicts a difficult encounter, which tasks need a checklist, how long the service really takes, or which quality failures are early warnings rather than isolated events. Experience is accumulated through operation, but each experiment also exposes the venture to the cost of getting an encounter wrong.
Service characteristics can intensify that exposure because the venture cannot separate learning from delivery as neatly as a firm that tests a physical production process before releasing the product. The service is often being learned while customers are receiving it. That does not make learning impossible; it makes feedback design and recovery capacity more important. A young service venture needs ways to turn individual encounters into shared knowledge before the same failure is repeated.
The empirical result is consistent with this mechanism. In the study’s near-census-style sample of Portuguese new ventures with certified financial information, service ventures were reported to have a higher failure hazard than non-service ventures. The service estimate in the first Weibull model was reported as β = 1.348 with p < 0.01. The descriptive comparison also placed non-family service ventures at the highest failure rate, 18.9 percent, while non-service family ventures had the lowest, 9 percent. These figures describe the study’s groups and model; they are not the probability that any particular service startup will fail.
The result should also be read with its qualification. The researchers tested whether the distinction was being driven by whether ventures actually had service revenue. In two selection-correction specifications, the service coefficient was not significant, and the authors concluded that service revenues alone do not necessarily produce failure. That finding is not evidence that service operating conditions are irrelevant. It indicates that a broad industry classification and a revenue mix are not identical constructs. A venture may sell services without facing the same level of customer interaction, perishability, or delivery variability as another venture, and service categories may contain substantial internal differences.
For the same reason, the evidence does not support a claim that service ventures are doomed to fail or that non-service ventures are automatically safer. It supports a more useful conclusion: service ventures face a distinctive baseline operating problem, and that problem must be managed through reliable encounters, demand and capacity coordination, employee capability, and repeatable routines. The study did not directly observe customer perceptions, service quality, or the precise routines through which a venture coped with these pressures. The mechanisms explain why the result is plausible, but the statistical association does not identify each mechanism separately.
The practical question is therefore how a venture can reduce dependence on improvisation without losing the responsiveness that customers value. A written procedure may improve consistency, but an overly rigid script can fail when customers bring different needs. More employees may create coverage and skill diversity, but they also create more handoffs to coordinate. Technology may improve scheduling and communication, but it cannot decide what level of service is feasible or repair a relationship after a poor encounter. Each solution changes the coordination problem rather than eliminating it.
That is why service survival cannot be reduced to customer acquisition or revenue growth. A venture can attract demand and still be weakened by the cost of delivering it inconsistently. It can have loyal employees and still lack enough capacity to handle peaks. It can be small and agile while remaining dangerously dependent on one person’s memory. The central capability is a dependable operating loop: promise an intelligible service, prepare for the customer’s participation, support the employee during delivery, learn from the outcome, and adjust capacity before the next wave of demand.
Once the problem is stated this way, ownership and employee scale become easier to interpret. A family member who is close to customers may help a small venture notice failures and protect relationships. A larger workforce may spread tasks and create routines that make reliability less dependent on one individual. Neither is automatically a solution. The next question is how family proximity and employee capacity work together when a service venture has limited resources—and why that combination can be especially valuable before growth changes the organization.