For much of the past decade, the dominant delivery model in China's enterprise software market was project-based: vendors built custom solutions around a single client's requirements, revenue came mainly from one-time licenses plus subsequent implementation fees, and the customer relationship fluctuated with the project cycle. That model made reasonable commercial sense when the customer base was small and requirements highly fragmented, but it inherently limited a vendor's ability to scale — each new customer amounted to starting the build over again.
The industry is now moving toward the other end of the spectrum: standardized products paired with subscription pricing, where customers shift from owning software outright to paying continuously for service and updates. This shift is not simply a commercial-model choice; it requires vendors to redesign product architecture so a single product can serve a large customer base within a limited scope of customization.
- 01Custom project delivery
- 02Semi-standardized modules
- 03Standard product plus implementation
- 04Subscription product
- 05Platform extension and ecosystem
Custom project delivery: 1; Semi-standardized modules: 2; Standard product plus implementation: 3; Subscription product: 4; Platform extension and ecosystem: 5
Illustrative framework describing the sector's overall direction; individual companies progress at different paces
Mid-market depth versus large-account customization
Vendors face an ongoing resource-allocation choice between two paths.
Mid-market depth
Serving a large number of mid-sized customers, where per-customer revenue is lower but replicability is strong. The product must cover most customers' core needs within a limited scope of customization, testing product design and implementation efficiency.
Large-account customization
Serving a small number of large customers, where per-customer revenue is high but delivery cost rises with the degree of customization. A careful balance is needed between the revenue stability and the bargaining position that come with customer concentration.
The core variables in retention economics
The value of subscription revenue depends on retention and renewal terms, not the size of the first-year contract.
Renewal rate and net revenue retention
Whether a customer renews, and whether their purchase expands or contracts upon renewal, directly determines the long-run compounding effect of subscription revenue — a more important indicator than the number of newly signed customers.
Implementation cycle and the churn window
The longer the implementation cycle and the longer a customer waits before actually using the product, the higher the risk of early churn. Implementation efficiency therefore has a direct bearing on retention performance.
Alignment between price and perceived value
Whether the subscription fee matches the efficiency gain a customer actually realizes determines the room for future price increases, and whether the customer treats this spending as a priority cut when budgets tighten.
Localization dynamics
Enterprise software products from international vendors typically require substantial localization to match domestic tax and accounting rules, supply-chain conventions and organizational management practices in China. That process is time-consuming and costly, and it leaves competitive room for domestic vendors.
That localization advantage narrows over time, because customer needs keep evolving too. Domestic vendors need continued R&D investment to keep pace with how customer organizations themselves change, rather than relying on existing localization work for permanent protection.
The Havrion Capital Perspective
Within enterprise software, Havrion Capital gives priority to companies that have already built a replicable product and implementation system for the mid-market, judged by net revenue retention and implementation cycle time rather than the growth curve of total signed customers. The sector actively steers away from companies still heavily dependent on custom project delivery that have not completed the transition to a productized model — such companies may show meaningful revenue scale, but rarely build an operating advantage that reinforces itself over time.
This industry has a natural division of labor with two related industry pages: cybersecurity focuses on the distinct dynamics of security products as a specific category, while software infrastructure within financial services serves heavily regulated customers such as banks, with different procurement cycles and compliance requirements, and is discussed there separately.