Find tasks in familiar business work
Wang Shiyi, whose real name is Wang Ruofan, described first writing internal operations tools and later connecting large models to workflows. Companies trying the tools and proposing cooperation were his reported route to external projects. Recurring business friction can suggest a venture without an enormous feature list.
The October 12 interview published on Shangguan Hao also described discussions with management and frontline staff, with agents delivered through web or mini-program interfaces. We analyze that work description; the company's registered name, full current team and acceptance records were not completely disclosed.
Turn an internal tool into a service others can discuss
Department insiders know unstated assumptions, error-prone columns and who explains exceptions. Those conditions may not transfer to another company. An initial external deliverable could map submissions, information sources, result formation and downstream use.
For a hypothetical weekly-report tool, ask an outside customer for a permitted sample and check fields, departmental definitions and purpose before promising a copy. This is our example, not an interviewed client project. Its purpose is to expose differences, not prove universal suitability.
Make business experience visible in shared material
Discuss a recent record: what is established, what requires repeated questions and who decides. Then distinguish immediately testable work from missing data, interfaces or authorization in a confirmation list, showing the customer's next contribution.
AI can organize authorized records, identify field conflicts and suggest questions. Engineers must compare records with actual processes; business owners confirm meanings. A working webpage carries this collaboration rather than replacing approvals.
Clarify responsibilities before adding temporary collaborators
The interview described connecting industry professionals. Additional expertise can help a small team while adding coordination. Establish who accesses customer material, implements technology, reviews industry judgments and communicates overall progress.
A limited trial can reveal whether partners explain uncertainty, hand over work and respond on time. Social titles and community identities introduce people but do not replace evidence of actual collaboration.
Tools still have users after the project ends
Changed forms, staff or model versions create work. State handover ownership, maintenance boundaries, separately priced changes and how customers pause tasks. Founders maintaining several projects need records others can use to take over.
The shift from internal experience to external FDE turns personal knowledge into jointly checkable commitments. We do not use reported performance, customer counts or hour comparisons as outcome proof. Other teams need specific requirements, trials and acceptance evidence to assess suitability.
Further reading: the first FDE business task; accepting delivery and maintenance. Zhangjiang Digital Nomad Community.