Guest: Wang Hua, partner at 创新工场, his role at the time
Host: Qu Kai
Originally published: August 11, 2024 | Duration: 45 minutes 16 seconds
Edited: October 18, 2026 | Official episode
AI startup discussions often collapse three questions into one: will language change software interfaces, can machines independently finish complex work, and when will artificial general intelligence arrive? A single model launch can then change someone's view of the whole industry.
Wang Hua's useful contribution in this 2024 conversation is to separate those questions. Different capabilities require different evidence, and different applications face different cost constraints. Mobile internet offers comparisons, but cannot supply AI's answers. This distinction makes a long term belief more useful for deciding what to build, observe, and afford today.
1. Three stages describe conditions, not a guaranteed timetable
Listen: 09:18–17:25. Wang's first layer covers language and multimodal interfaces, together with simple tasks that still involve people. Users can express needs through text, voice, or images without learning every menu. People remain responsible for judgment, handoffs, and completion. Wang compares this change to mobile internet and expresses strong confidence in it.
The second layer is general automation of complex, extended workflows: a machine accepts a goal and handles multiple stages with less human involvement. This requires stronger models and engineering systems that organize execution reliably. He compares it to the steam engine and expresses considerably less certainty. The third layer is artificial general intelligence, whose boundaries and route remain more uncertain. His references to “100 percent” and “50 percent” are personal judgments, not calibrated probabilities or industry statistics.
The distinction changes a product argument. Drafting an email that a person checks and sends can demonstrate useful interaction and local productivity. It does not demonstrate autonomous coordination of an entire project across departments. That would also require maintained state, exception handling, permission checks, and an acceptable cost of failure.
Editorial inference: “The model can do it” should become “under which inputs, with whom completing which steps, and how are mistakes discovered?” Using a first layer demo to support a second layer commercial promise skips the gap between capability and responsibility.
2. Opportunities will not arrive in every industry at once
Listen: 01:28–08:58 and 18:50–20:57. Wang recalls several mistakes from mobile internet: projecting expensive devices and data plans indefinitely; importing the old carrier value added services model; and concluding that a new platform has no independent opportunities because its earliest products failed. Short video did not simply copy the form of early PC video products.
But AI differs in a crucial respect. Mobile internet added usage settings, camera entry points, and connected users on top of comparatively stable network technology. AI's technical stack and capability boundaries are still evolving, and it may not receive a comparable dividend from new hardware adoption. The order in which yesterday's apps succeeded cannot determine today's opportunities.
Wang's proposed sequence starts with valuable business productivity tasks that can cover inference costs, followed by tools with large audiences, image and text social entertainment, and eventually more expensive multimedia and deeper business restructuring. This is conditional reasoning. An infrequent but valuable task may tolerate a high cost per execution. Long entertainment sessions or extensive video generation may be constrained by recurring usage bills.
Cost is not the only variable. A cheap output that repeatedly needs repair can still be expensive. A costly invocation that removes substantial manual coordination may make economic sense. The relevant comparison is the total cost of completing the same job, rather than the price of one model request.
3. Early advantages must survive change; incumbent advantages have limits
Listen: 21:23–28:32 and 35:43–41:32. When a new capability merely changes the interface for an existing need, established companies can use their users, distribution, and operating workflows. Customers already complete the task there, so an intelligent entry point can capture demand. Calling a startup “AI native” does not automatically confer an advantage.
New companies may find more room when the new form changes revenue sources, requires organizational restructuring, or conflicts with the old business. This does not mean incumbents must respond slowly. An established company divides resources among protecting existing revenue, fighting its largest battles, and exploring marginal needs. A neglected market may offer an opening without removing copyright, operational, or delivery burdens.
Wang also avoids concluding that entering earlier is always better. Technology may change enough that today's form is not the eventual form. Teams must adapt. Whether users, data, capital, and accumulated capabilities support that transition determines what the early investment leaves behind.
Editorial inference: Ask, “If we must rebuild the interface in six months, which three assets remain ours?” Old interface code alone is a thin answer. Continuing customer relationships, feedback that can legally be used, and reliable delivery capabilities may transfer. Data rights cannot be assumed to include every piece of user content; permission and permitted uses need separate checks.
4. Open or closed models require a complete operating calculation
Listen: 28:43–34:34. Wang predicted that by the first half of 2025, using GPT-4 level capabilities might cost only a few renminbi cents per daily active user. His discussion used assumptions about token consumption. Tokens measure the text processed by a model, but the conversation did not standardize input versus output, quality, latency, or retries.
This is a forecast made in 2024, not a current procurement quote or a promise that every product will become profitable. Lower unit prices can coexist with higher total bills as usage frequency, context length, tool calls, and human review expand.
His discussion of open and closed models likewise emphasizes stages. A small team might use hosted APIs or third party services to reduce maintenance. A capable medium sized team might consider its own deployment. Very large applications might mix and customize models to manage costs and differentiation. This matches organizational capability to economics; it is not a rigid classification by headcount.
Operating an open model is not free. Maintenance, scaling, incident response, licensing, and data requirements belong in the calculation. Hosted services do not remove the product team's responsibility to decide what may be sent and how failures are recorded. The objective is reliable task completion, rather than membership of a particular camp.
5. Start from the user's final intent, and allow time for validation
Listen: 32:46–45:05. Wang describes search as a shared intermediate step across many tasks. People ultimately want to complete research or handle an actual matter; searching gathers some of the necessary information. If AI organizes services around that final intent, future products need not merely add a chat entry point to each old app button.
Understanding intent still differs from completing a service. Producing a plan, finding information, receiving consent, invoking a service, and confirming completion cannot be hidden inside a fluent answer. The earlier capability distinction returns: interaction may change before delivery becomes automated.
The later discussion concerns capital and cognition. Wang argues that venture investment has small samples and slow feedback. Capital that demands predictable short term profit can reduce support for uncertain exploration. This describes a tension in an investment mechanism; it does not establish that an entire category of funds has disappeared, nor offer personal investment advice.
Product teams can borrow the lesson about pace. Do not rewrite every assumption after each launch, but do not invoke patience to avoid looking at users. Long horizon beliefs and short experiments can coexist: the former guide exploration, while the latter determine which route deserves more resources.
Exercise: separate three kinds of evidence in an AI proposal
Choose an existing project and write its entire process, from a user's request to confirmed completion. Then fill in the following distinctions:
| Claim | Minimum evidence needed | What it does not yet establish |
|---|---|---|
| Users express needs more easily | Less effort understanding and operating real tasks | Independent execution of every task |
| One step can be automated | Representative inputs, failures, and human takeover records | Reliable operation across an extended workflow |
| A complete workflow can be delivered | State, permissions, recovery, cost, and completion confirmation | Unlimited extension into any industry |
| Early investment retains value | Transferable customer relationships, lawful feedback, and capabilities | Inevitable victory over later entrants |
Add two lines: which cost assumption supports the current economics, and what scope would shrink if that assumption arrived a year late. This is more actionable than arguing only about whether AI still deserves belief.
Source boundary
This reading uses the episode's official introduction and transcript. Industry trajectories, falling costs, and capital assessments are views expressed in 2024; their subsequent fulfillment has not been independently verified. A passage around minute 18 contains a negative that conflicts with its context, so no precise conclusion is drawn from it. Uncertain device prices and model measurements are also omitted. Editorial inferences and the exercise are not presented as the guest's words.
Listening navigation
- 01:28–08:58: Early mobile internet mistakes and differences from AI.
- 09:18–17:25: Three capability layers and their conditions.
- 18:50–23:23: Opportunity sequence and incumbent strengths.
- 23:51–28:32: Founder adaptability and early investment.
- 28:43–34:34: Historical cost forecasts, model choices, and final intent.
- 35:43–45:05: Incumbent limits, capital mechanisms, and feedback cycles.
Related themes: AI industry stages, product economics, startup timing. Further listening: Do not sprint just after starting and Grasp and agent execution environments.