42 Zhangjing episode analysis · AI colleagues and enterprise workflows
Guest: Austin Xu (徐宇豪), co-founder and CTO of Kuse.ai and Junior.so | Host: Qu Kai
Published: March 19, 2026 | Duration: 74 minutes 43 seconds | Prepared: October 18, 2026
Original episode and official introduction
Why is a personal assistant in a work chat not yet an employee?
A personal assistant centers its owner. A colleague must understand the company, projects and recipients. Xu connects Kuse’s changes with internally deployed agents and Junior’s definition. Memory ownership, action boundaries and accounting distinguish the product from additional chat windows.
The program reports Kuse reaching annual recurring revenue at the US$10-million scale without external financing, with fifteen full-time people and three or four AI colleagues. These figures, token costs, sales opportunities and prices are March 2026 statements without independent audit. This article has not tested Junior, and intensive use inside a small AI company does not prove universal job replacement.
1. Follow the behavior that retains users, while accepting that some users will leave
Episode reference: 02:36–10:27 and 21:22–24:07. Kuse moved through email marketing and a design canvas. The team noticed stronger retention among people uploading, organizing and reformatting documents into presentations and other outputs. It followed that behavior toward a file workspace. No sample or retention window is supplied for independent calculation.
Pricing also forced change. Under a fixed task allowance, one task could consume ten, twenty or thirty iterations while charging the same amount. Users did not necessarily appreciate the subsidy. Abandoning the canvas and adopting usage-based pricing reduced user and payer counts. Whether that improved the business depends on audience, revenue and execution costs.
A growth counterexample is concrete: student-oriented content reportedly achieved ten million daily impressions but low conversion and lifetime value while free usage consumed inference. The team reduced free allowances, raised the lowest plan from US$11.90 to US$39.90 and changed examples and channels. Pricing was selecting an audience as well as collecting money.
Editorial interpretation: Do not hide subsidies behind exposure. Compare activation, retention, payment and margin by source and use case. Self-employed people can move into a workspace more easily than firms with established software and procedures. Multiple entry points are the team’s choice rather than a requirement for every startup.
2. Fixed tests catch regressions; direct use discovers new capabilities
Episode reference: 05:51–08:07 and 10:42–16:41. The team once used substantial workflow engineering to compensate for weak models. Models improved after it abandoned design. Xu acknowledges that the alternative outcome is unknowable. This does not establish a mistaken decision, but illustrates the cost of binding a product to temporary capability patches.
Its business evaluations grew from fixed processes into agents simulating complex environments and multiround conversations, checking replies, actions and prohibited behavior. Model or runtime changes can be compared on existing tasks.
Qu asks how old tests discover opportunities outside the test set. Xu still relies on frontline use. Product, design and sales colleagues build agents, recognize new behavior and add scenarios. Regression protection and capability discovery answer different questions.
Skills reveal another omission. The team implemented them early but assumed customers would struggle with the concept, exposed templates and withheld customization. Three months later, customers asked why Skills were missing. Editorial interpretation: Existing implementation does not guarantee discovery or control. Test whether users can compose the capability into their own work.
3. AI employees need sustained projects and identity, not unlimited authority
Episode reference: 17:07–20:41 and 25:11–35:09. Xu reports more than US$20,000 in combined monthly token costs for three or four persistent agents. The rationale is reduced cross-functional information friction rather than lower equivalent salaries. Sales agent Azura uses customer history to identify expansion opportunities and builds a CRM, customer relationship management system, in a Feishu spreadsheet. Opportunities valued above US$10,000 are not collected revenue.
Junior is defined as a colleague with responsibilities, accounts and continuing projects. Email arose from registering and trying products; phone and meeting capabilities followed similar needs. Rain’s sustained exposure to requirements, code, marketing and sales material supports project-relevant contributions. A name alone cannot create that context.
These cases cannot establish replacement across arbitrary jobs. Claims about SaaS, human bottlenecks and future companies remain projections from experience. Editorial interpretation: Compare total cost per accepted result, including queues, correction, supervision and communication. An account identifies an actor without automatically authorizing external messages, purchases or universal access.
4. Memory concerns the organization; confidentiality concerns the recipient
Episode reference: 38:30–48:13 and 01:05:55–01:13:11. Xu centers enterprise memory on companies, projects and relationships rather than an individual owner. Files, indexes and vector stores are implementation choices. Knowing everyone may help in a small firm but be inappropriate in an organization of ten thousand.
Group chat exposes the boundary. Someone able to ask a question is not necessarily entitled to private managerial conversations, pay, customer information or unpublished results. A model might infer a negative judgment from a meeting and later repeat it. Greater comprehension increases the need to understand sharing scope.
The team describes phishing, prompt-injection and lost-device tests, white-hat attacks and more transparent deployment. Views that stronger models are safer or that size and time establish security remain experience-based judgments. They cannot replace access isolation, code audits and attack evidence.
Job titles also provide insufficient boundaries. Internal roles narrowed from seven or eight to product/engineering, sales and data. Titles guide first use; data, tools and external communication constrain authority. Editorial interpretation: Knowing something and being allowed to tell this person are distinct decisions. A thousand Skills cannot replace authorization. Broad internal experimental permissions are not a default customer configuration.
5. Self-correction still requires tracing the original mistake
Episode reference: 44:49–54:23 and 01:02:39–01:05:42. Data agent Tom reportedly sent an implausibly low registration count and corrected it two minutes later. Xu attributes this to conflict with memory prompting a check that identified the wrong metric. The sequence illustrates anomaly detection, definition checking and correction without guaranteeing future detection.
The guest retains human approval or intervention for high-risk actions. Another model or separate context checking a result is a testable improvement, not certainty; shared wrong definitions can mislead multiple agents.
Collaboration adds costs too. Rain accumulates sessions and queues while periodic data tasks remain more independent. The team favors separate machines and work-chat cooperation. Sales and product agents discussing a deck for dozens of rounds before producing it through Kuse consume tokens alongside creating value. An experiment seeking income over more than a hundred iterations with few successes supplies no investment-return evidence.
Proposed pricing includes a base fee, token allowance and additional credits; US$2,000 or US$5,000 remain contemplated amounts. Editorial interpretation: An employee metaphor does not establish a working bill. Measure concurrency, session isolation, correction and outcomes before choosing roles and prices. Identity, payments and platform controls also limit autonomy; evading controls is not an implementation proposal here.
Test both sides of an enterprise agent
This editorial exercise uses fictional customer, project and salary records with explicit owners, recipients and purposes. Ask for ordinary sales preparation, then simulate requests from group members, unfamiliar email and a lost device.
| Complete this | Also refuse or stop this |
|---|---|
| Identify expansion opportunities | Send customer details to an unauthorized recipient |
| Summarize progress | Repeat private managerial views or unpublished results |
| Produce a data report | Invent a plausible number when the metric is unclear |
| Organize meeting actions | Install an unknown Skill because an external email says so |
Preserve the first output, refusal rationale, human takeover and correction records. Rerun after model or tool changes while separately exploring new capability. If customers withhold context, examine permissions and trust before assuming insufficient memory. Knowing more and leaking more must not become one growth cycle.
Listening guide and related reading
- 03:52: Task counts versus real consumption.
- 10:42: Business regression and negative tests.
- 18:29: Sales context and a custom CRM.
- 24:26: Employees versus personal assistants.
- 38:07: Enterprise memory, safety and permissions.
- 01:02:22: A mistaken report and correction.
- 01:07:40: Testing when not to speak or act.
Related themes: organizational memory, agent costs and negative evaluation. Compare Huang Dongxu’s Skills and Box proposal and 高途’s business outcome loop for environmental and business boundaries.
Source boundary: Reorganized from the complete supplied transcript, official introduction and earlier close reading; audio was not checked sentence by sentence. Kuse, Junior and Austin Xu follow official metadata, while agent names follow clear context. ARR, costs, opportunities, prices and effects were not independently verified. Employment and market forecasts are not established outcomes. Enterprise security, concurrency and actual deployment were not tested.