Is a SaaS without an interface actually more valuable?

API-native SaaS is reshaping the valuation logic. Yes, you read it right. It's the SaaS that people are reluctant to talk about these days.

Neuters has captured a quietly emerging and highly disruptive "new species" in the enterprise service field. They actively abandon the competition for front-end interaction, completely strip away the well-known graphical user interface (GUI), and choose to exist at the bottom of the giants' ecosystem in the form of pure underlying code and interfaces.

The industry is used to calling them "API-native SaaS (API-First SaaS)" or "atomized capability engines". Remarkably, while traditional SaaS is facing a cold spell in financing and a correction in valuation, these seemingly "incomplete" invisible software products are showing extremely high valuation premiums in the investment circles in Silicon Valley and China, and are becoming the core targets for top-tier capital to reshape the enterprise service landscape.

Who will buy software without an interface?

To understand this new species, we must break the fixed perception of "enterprise software" in the past two decades - forget about login boxes, dashboards, multi-level menus, and data reports.

The core product philosophy of API-native SaaS is absolute decoupling: completely abandon the software's UI and pour all R & D resources into building an extremely powerful business logic engine, data processing capabilities, and standardized data interfaces.

Traditional enterprise service practitioners will inevitably have doubts: How can customers operate a system without a basic interface? Who on earth will buy this system?

This is exactly the core of this species' dimensionality reduction strike: The primary service target of API-native SaaS is no longer "human operators", but AI.

In the traditional system architecture, in order to meet the extremely picky visual interaction experience of humans, SaaS vendors bear a heavy burden of front-end R & D and implementation and delivery. In the new ecosystem dominated by large models, the front-end interaction entrance has gradually converged to the "natural language dialog box" of super platforms. These new species have extremely keenly adapted to this trend: they don't need to write any front-end code, but seamlessly embed pure and non-redundant interfaces into the call resource library of general large models, and complete extremely complex business processes invisibly.

Reconstruction of capital logic: The real valuation myth and the underlying business ledger

Business deduction must not be separated from real transaction data. In fact, capital's preference for "stripping the UI and focusing on the underlying interfaces" is not a blind product of the large model era. Its extremely high valuation premium has long been supported by solid cases and is being magnified exponentially in the current AI wave:

The classic API valuation myth: In the previous wave, Stripe (payment engine), without a complicated financial management interface, only by providing a few lines of payment interface code, once had a valuation exceeding $95 billion; Twilio (communication engine), without developing call center client software, only focusing on the underlying interfaces for sending text messages and voice calls, also reached a peak market value of tens of billions of dollars. They have already proven the great commercial value of "pure interface delivery".

The popular unicorns in the AI era: Looking at the present, Sierra, a startup founded by the former co-CEO of Salesforce, is essentially a "conversational intelligent agent brain" that strips away the complex work order interface of traditional customer service SaaS. It has been established for just over a year, but its valuation has exceeded $4 billion, and its popularity in the capital market far exceeds that of many established customer service software.

The reason why top VCs are willing to give sky-high valuations to such projects is that API-native SaaS has completely reconstructed the extremely poor cost structure of enterprise-level software:

The first value: Break free from the quagmire of "heavy delivery" and achieve a structural leap in gross profit margin. Traditional SaaS million-level orders often require a large amount of manpower for several months of on-site implementation and training. However, API-native SaaS completely eliminates these links. The enterprise IT department or third-party platform only needs to complete the key docking in a very short time, and the business can run smoothly. This enables it to truly have the software characteristics of approaching zero marginal cost.

The second value: Cross the death trap of customer acquisition cost (CAC) and take advantage of ecological distribution. They directly target super platforms and large model ecosystems. As long as their APIs are built into the standard capabilities in the underlying resource library of giants, the massive user instructions at the front end will naturally be converted into back-end calls for this component. The most difficult "customer acquisition link" is very cleverly transferred to the super entrance with huge traffic.

The third value: A healthy cash flow based on usage-based pricing. Traditional SaaS relies on annual account subscription fees, and the pressure to renew subscriptions is huge. However, API-native SaaS adopts a high-frequency micro-transaction model: every risk control verification and every operational calculation will trigger billing. Under the extremely high-frequency calls of AI, this pay-as-you-go model similar to "water, electricity, and gas" brings extremely healthy and hard-to-lose cash flow.

The practical scenarios of the new species: The "invisible engine" in the deep water area

In Neuters' in-depth research in the industrial front line, we have seen a large number of "API-native" projects quietly exerting their strength in the deep water area of business:

Scenario 1: The "compliance and payroll computing core" hidden behind the collaboration platform

An API-native vendor focusing on payroll and tax compliance has a core asset - an underlying engine that has run through the social security bases, individual tax deductions, and payroll betting algorithms across the country. It fully opens up its capabilities in the form of interfaces. When enterprise decision-makers issue instructions at the front end, this engine completes the cross-comparison of massive rules in milliseconds and returns absolutely accurate figures. It doesn't have any front-end customer interface, but the core payroll data of countless enterprises are operating in its underlying closed loop.

Scenario 2: The supply chain decision-making black box focusing on "dynamic routing"

Another innovative enterprise in the supply chain field focuses on a dynamic operational research scheduling engine based on large models. In the face of sudden logistics disruptions, this "decision-making engine" is awakened in the background, instantly connects multiple logistics APIs, calculates hundreds of alternative plans, and directly outputs the optimal cost transportation capacity allocation instructions to the front end. What it delivers is no longer "software functions", but the "deterministic decision-making results" that are hard to buy with money.

The industry's endgame: From "closed integration" to "ecological componentization"

The outbreak of API-native SaaS is forming a silent "ecological deconstruction" of the traditional large monolithic software system.

Traditional integrated SaaS is facing severe structural challenges: Upward, super entrance platforms are constantly weakening the presence of traditional interfaces with the advantage of natural language interaction; Downward, API-native SaaS is replacing its underlying core business modules in a lighter and more specialized form.

What has a more far-reaching impact is that large language models and ecological giants have shown great welcome to these "invisible engines". Since they don't compete for brand exposure and don't seize user entrances, they perfectly fit the strategic requirements of giants to build a "boundless ecosystem". In the future enterprise software procurement list, customers are very likely to only buy a unified super entrance and mount the "atomized engines" in various sub-fields in the background as needed.

Conclusion: Capabilities live forever, reshaping the moat

The rise of the new enterprise service species is not only an iteration of the technical architecture but also a profound inquiry into the essence of enterprise service business.

In the past development cycle, the industry has devoted too much energy to the encapsulation of front-end workflows and the design of interaction interfaces. However, in the era of large models, enterprise customers' desire for "agile empowerment" is completely overwhelming their infatuation with "large systems". They are no longer willing to pay for redundant interfaces but only for the "core capabilities" that can directly solve business pain points.

The reason why API-native SaaS can reshape the valuation logic is that they have shed all irrelevant disguises and restored enterprise-level services to the purest essence of providing irreplaceable data and decision-making. For all enterprise service practitioners, letting go of the obsession with front-end interfaces and refining the most core industry experience into irreplaceable data and algorithm barriers is the only ticket to the new ecosystem.

This article is from the WeChat official account "Neuters" (ID: Neuters). The author is Neuters. It is published by 36Kr with authorization.