中文精读
软件的价值，藏在用户从意图走到结果的距离里
嘉宾：梦琪，invoko.ai 创始人（当期身份）｜主持：曲凯
发布：2026-05-23｜时长：68分42秒｜整理：2026-10-18
官方单集
当 AI 能很快写出类似功能，软件创业是否还有空间？梦琪的答案经历了一次反转：先因编码能力进步而焦虑，再因亲自打磨具体体验重新相信软件价值。她复盘找人 Agent、营销工具与桌面产品，最值得追踪的不是尖锐措辞，而是几次听起来自洽的决定，如何被实际使用推翻。
本篇保留2026年5月的个人经验。她对同行、市场和业务模式的批评未经独立调查，不据匿名见闻给任何公司定性，也不把一次转型扩成所有 B 端创业的结论。
一、先选赛道再找需求，容易把技术共性当成客户共性
回听：08:45–16:39。 团队最初因通用 Agent 拥挤，决定做垂直 Agent，再选 sourcing，即寻找达人、候选人、专家或客户。看起来都是“找人”，似乎可以共用搜索能力并横向扩展，但这个起点首先回答了如何避开竞争，没有先回答具体付费者最需要完成什么。
上线后，两类反馈发生冲突。创始人希望直接拿结果，不想操作；专业营销人员要求过程可审、自己定义指标并逐步确认。团队顺着专业反馈打磨，产品逐渐接近传统 SaaS，却没有老厂商积累的数据。不是专业用户反馈错了，而是尚未确定目标角色，就试图同时满足相反偏好。
她后来用面粉鸡蛋比喻：能做饼，也能做意面，不代表同一顾客会同时点两道菜。共同技术不等于自然交叉销售。团队选择向达人营销纵深推进，而不是覆盖所有找人场景。编辑推论是：扩展应沿同一用户的任务相邻性，不能仅按自己已有能力画功能树。
二、补足结果链，与延缓否定旧方向，可能同时发生
回听：12:28–20:53。 梦琪估计，原来的工具只解决客户工作中约30%的部分，真正费力的沟通往返被跳过；搜索效果又高度依赖外部 API 数据。这些比例是她对具体业务的估计，并非行业统计。把最容易由 AI 完成的一段做出来，未必抓到了最大价值。
曲凯追问为何不能先把一件事做透，并提出扩展可能是在延缓承认旧方向不够好。梦琪则认为那不是完全无效，而是价值强度不足，补齐沟通、合作等环节有意义。保留这个分歧，比简单得出“应该更聚焦”更有用：要判断扩展是否真的补了交付缺口，还是只是把市场故事讲大。
她还观察到一些公司依靠人工服务获收入，客户并不使用演示产品。本文不据此认定匿名公司欺骗；可用的问题是软件、代运营、咨询和人工兜底应如何分别计价。服务本身未必坏，但团队应诚实知道客户买的是什么、成本由谁承担、能否持续。
B 端销售周期和组织要求与她的团队偏好不合，是个人选择。高付费、高消耗用户和订阅低消耗用户也有不同成本结构，但“大 R”“健身房”只是商业比喻，不足以证明某类模式更好，更不能把让用户闲置订阅当产品目标。
三、一次按钮减少的摩擦，可能比一个新概念更有价值
回听：30:21–38:31。 转向 C 端并非一天推倒重来，团队先做浏览器插件 Clico：在多个 Tab 中找信息、引用上下文，在光标附近帮助写作。用户原本要截图、切到聊天产品、解释、再复制回来，一个预设按钮把意图与动作接近了。
梦琪起初嫌这个产品太简单，后来用户反馈改变了她的看法。价值不是“世上没人想过”，而是具体任务少走几步。功能变多后仍要克制，避免按钮与信息编排又成为新负担。这是从单功能价值走向整体体验的限制条件。
扩展到桌面后，看似简单的产品据她说做了约三个月、迭代49版，仍有 bug。这里说明的是自家适配、稳定与边缘场景的复杂性，不能推成所有软件的固定工期，也不能据自评认定优于所有竞品。能打开、能运行和顺畅解决问题，是不同验收层次。
权限又是体验的一部分。团队用漫画解释数据存储，回应用户不愿读长协议的问题。但解释容易懂，不证明真实系统安全；权限范围、实际存储、访问与撤回机制还须一致。最后这一层为编辑限制，本文没有审计产品实现。
四、用研要改变决策，内部使用也有样本边界
回听：39:07–42:46、44:59–47:48。 梦琪把产品决定拆成问题漏斗，再围绕痛点、旧办法、优先级与付费意愿到 Reddit 获取反馈。她称每个问题发约40至50帖，有些不提产品。这是其研究做法自述，不是代表性样本，也不是本文建议复制的发帖策略。
可保留的方法是：每项决定对应一个能被反馈推翻的问题。论坛自选择、社区规则、措辞与重复发布都会影响结果；更稳妥的编辑建议是透明招募目标用户，标记样本来源，把讨论与真实试用、复用和付款交叉验证。不要把论坛当自动给正确答案的资料库。
团队为自己的 C 端产品做增长，又把达人营销做成内部 Skill，每天补沟通、指标和执行细节。其结果不是复杂界面，而是一张表：合作谁、报价多少、是否值得、内容检查、沟通进度和拍摄上传日期。这个例子把“交付结果”变得具体。
完整内部上下文有利于密集改进，却不保证外售同样成立。内部的数据、权限、责任人和共同目标，可能正是外部客户缺少的条件。自动联系、议价等动作还须有企业授权，表格生成也不等于合作已经履行。后两点为编辑补充。
五、技术与团队，应该跟随当前瓶颈
回听：24:44–29:55、48:30–55:16、59:26–01:01:11。 梦琪反省早期因融资叙事、豪华团队和技术概念投入过多。增长场景有曝光、互动，逻辑上似乎天然适合奖励反馈，但训练成本、归因质量和基模进步速度，可能使自训收益不划算。这是她的事后判断，不是所有应用团队不该训练或招算法人员的通用规则。
同样，Agent、workflow、聊天框或图形界面都不能因新旧而直接排优先级。稳定工作流可能已足够解决客户大部分问题；强行加入新概念，可能只增加表达和维护成本。关键仍是任务效果、总成本和体验。
研发自动化把难点继续推到两端。团队尝试让多 Agent 接用户问题、补上下文、排优先级、分发编码任务并通知用户；简单 UI 问题可能自动验，复杂问题仍需要人甚至用户确认。她还没想清外部产品界面，因此没有急着发布平台。内部流转成立与外部产品成立，明确不是同一件事。
编辑推论是：代码产出增加后，应测“该修哪个问题”和“是否真的修好”。发送通知只是交付动作，用户验证是另一条证据。将问题、权限、修改、测试与最终回读接起来，才有完整闭环。
六、效率与情绪价值可以一起交付，但不能互相遮掩
回听：21:18–24:34、55:38–58:27、01:01:37–01:07:26。 Steam 上的番茄钟、习惯培养和桌面陪伴，让梦琪看到工具、游戏与情绪体验的边界可以模糊。用户可能既需要完成任务，也希望每天打开产品时感觉舒服。节目涉及 ADHD 为个人自述与产品场景，不构成诊疗效果证明。
她最终的表述有顺序：首先解决问题，同时关心用户是谁、当下心情如何。只提供人格、没有可靠结果，不能完成效率承诺；反过来，结果正确也不代表交互不会增加焦虑。编辑推论是让任务与感受各有证据，避免把停留时间直接当成幸福或效率。
从“证明自己厉害”到做自己愿意长期打磨的产品，是她的反思。热爱能支持维护，却不能替代用户反馈；融资、名人团队也不是充分条件。她引用软件像草坪需要持续修剪，也承认未来维护可能进一步自动化。因此当前维护困难是工作事实，未必是永久护城河。结尾的乐观来自仍有未被解决的具体问题，不是每个软件项目都会成功。
练习：复盘一次“听起来必然成立”的决定
写下决定时的原始理由，例如“这些场景都需要找人，所以可以交叉销售”。再找一个真实用户最近完成任务的过程，标出：谁使用、谁付费、哪一步最费时、哪一步要求控制、最终交付物是什么。
接着分别判断技术复用、用户复用和商业复用是否成立。若只有技术能复用，就不能宣称已有同一市场。最后列一项会让你放弃扩展的证据，以及一项能证明高价值环节确实补齐的行为。对体验改进，再比较用户从意图到结果减少了多少切换、解释和返工。该练习是编辑整理，不是融资或经营成功公式。
来源与回听
据完整转写、官方介绍及章节整理，未复听音频或测试产品。匿名行业指控未扩散为事实；稳定性、版本数、账单与用户反馈均按自述。未为未明确命名的桌面产品补名称，片尾歌词不当访谈观点。
- 08:45：从垂直分类开始的选择。
- 11:40：专业与非专业用户的冲突。
- 12:28：价值链中容易做与最费力的部分。
- 30:21：从插件到桌面体验。
- 39:07：用研与决策问题。
- 44:00：内部需求如何长出具体结果。
- 01:05:00：任务价值与对人的关注。
相关主题：用户研究、创意工具、AI 组织与陪伴体验。可对照王文锋谈 AI 管 AI、Albert 谈胜率和消费者导向，观察相似技术条件下的不同产品选择。
English edition
Software Value Lives in the Distance Between User Intent and Results
Guest: Mengqi, founder of invoko.ai, as introduced at release | Host: Qu Kai
Published: 2026-05-23 | Duration: 68:42 | Prepared: 2026-10-18
Official episode
When AI can quickly generate similar functions, is there room for software startups? Mengqi’s answer reverses: coding progress first caused anxiety, then work on specific experiences restored her confidence. Her accounts of sourcing agents, marketing tools, and desktop software are valuable for tracing how apparently coherent decisions were overturned by actual use.
This article preserves a personal account from May 2026. Criticism of peers, markets, and business models was not independently investigated. Anonymous observations do not establish wrongdoing by a company, and one pivot cannot define all enterprise entrepreneurship.
1. Choosing a category before demand can confuse shared technology with shared customers
Listen: 08:45–16:39. The team first avoided a crowded general-agent market by choosing vertical agents, then sourcing: finding creators, candidates, experts, or customers. All involve finding people and seem to share search capabilities. But that starting point answered how to avoid competitors before identifying a payer’s most important task.
After launch, two feedback streams conflicted. Founders wanted results without operating the product. Professional marketers wanted auditable processes, custom metrics, and confirmation at intermediate steps. Following professional feedback produced something resembling traditional SaaS without incumbents’ accumulated data. Professional feedback was not inherently wrong; the team had not settled the target role before trying to satisfy incompatible preferences.
Mengqi compares flour and eggs: they can make flatbread or pasta without one customer ordering both. Shared ingredients do not establish cross-selling. The team deepened creator marketing instead of covering every sourcing scenario. An editorial implication is to expand through adjacent tasks of the same user, rather than a feature tree based only on technical capabilities.
2. Completing delivery and postponing rejection of an old direction can coexist
Listen: 12:28–20:53. Mengqi estimates the original tool covered roughly 30% of customer work while omitting time-consuming communication. Search quality depended heavily on external API data. These are estimates about her business, not industry measurements. Completing the easiest AI segment may miss the largest value.
Qu asks why the team could not perfect one task and suggests expansion might postpone admitting the original direction was weak. Mengqi says it was not wholly ineffective; its value was insufficient, making communication and cooperation worth adding. Preserving the disagreement is more useful than a generic instruction to focus. Did expansion fill a delivery gap or merely enlarge the market story?
She also reports companies earning service revenue while customers do not use the demonstration product. This does not establish deception by unnamed companies. The usable question is how software, managed operations, consulting, and human fallback are priced separately. Services are not inherently bad, but teams need an honest account of what customers buy, who bears costs, and whether it persists.
Enterprise sales cycles and organization did not suit her preferences and team. That is a personal choice. High-paying heavy users and subscribers with lower consumption also create different cost structures. Her “whale” and “gym” metaphors do not establish a superior model or justify making unused subscriptions a product objective.
3. One button removing friction can matter more than a new concept
Listen: 30:21–38:31. The consumer pivot was gradual. The team first built Clico, a browser extension for locating information across tabs, citing context, and writing near the cursor. Instead of screenshots, switching to a chat tool, explaining, and copying back, a preset button shortened the path from intention to action.
Mengqi initially considered it too simple. User feedback changed her view. Value did not require an idea nobody had imagined; a task became easier. Additional functions still needed restraint so buttons and information organization did not become new burdens. A valuable feature does not automatically create a coherent experience.
The desktop expansion reportedly took about three months and forty-nine versions, with bugs remaining. This describes the team’s compatibility, stability, and edge-case work, not a universal software schedule or independently proven superiority to competitors. Opening, running, and smoothly solving a problem are different acceptance levels.
Permissions also shape experience. The team used a comic to explain data storage for users unwilling to read long agreements. Clear explanation does not prove security: permission scopes, actual storage, access, and revocation need to match. This last limitation is editorial; no implementation audit was conducted.
4. Research should change decisions; internal use has sampling limits too
Listen: 39:07–42:46; 44:59–47:48. Mengqi describes decomposing decisions into questions and seeking Reddit feedback on pain points, previous solutions, priorities, and payment. She reports forty to fifty posts per question, some without mentioning the product. This is a self-reported method, not a representative sample or a posting strategy recommended here.
The useful principle is to connect each decision to a question feedback can overturn. Self-selection, community rules, wording, and repeated posting affect results. A more defensible editorial suggestion is transparent recruitment of target users, source labeling, and comparison with actual trials, repeat use, and payments. Forums are not an automatic answer bank.
Doing growth for its consumer product led the team to rebuild creator marketing as an internal Skill, adding communication, metrics, and execution details each day. The output was a spreadsheet: collaborators, prices, value assessments, content checks, communication progress, and filming and upload dates. “Delivering a result” became concrete.
Dense internal context helps iteration without proving external sale will work equally well. Data, permissions, responsible people, and shared objectives may be precisely what outside customers lack. Contacting and negotiating also require company authorization, and generating a sheet does not mean an agreement has been fulfilled. Those two boundaries are editorial additions.
5. Technology and staffing should follow the present bottleneck
Listen: 24:44–29:55; 48:30–55:16; 59:26–01:01:11. Mengqi criticizes early decisions shaped by financing narratives, impressive teams, and technical concepts. Exposure and engagement appear to offer natural rewards for training a growth agent, yet training costs, attribution quality, and foundation-model progress may make internal training uneconomic. This is her retrospective judgment, not a rule against training or algorithm hires across all application businesses.
Agent, workflow, chat, and graphical interfaces likewise cannot be ranked by novelty alone. A stable workflow may solve most of a customer’s problem. Adding fashionable concepts can increase expression and maintenance costs. Task outcomes, total cost, and experience remain the relevant comparison.
Development automation shifts difficulty toward the ends of the process. The team experiments with multiple agents receiving user issues, adding context, prioritizing, assigning coding, and notifying users. Simple interface problems may support automatic checks; complex issues still require people or users. Mengqi has not settled the external interface and therefore avoids rushing a platform release. A working internal pipeline and a viable external product remain separate achievements.
An editorial implication is to evaluate which problem should be fixed and whether it was truly resolved as code volume rises. Sending a notification is delivery activity; user verification is another piece of evidence. Issues, permissions, changes, tests, and final readback need to connect into a complete loop.
6. Efficiency and emotional value can coexist without concealing each other
Listen: 21:18–24:34; 55:38–58:27; 01:01:37–01:07:26. Pomodoro timers, habit tools, and desktop companions on Steam showed Mengqi that productivity, games, and emotional experience can overlap. Users may want completed work and a comfortable daily experience. Mentions of ADHD concern personal experience and product scenarios, not demonstrated treatment effects.
Her final formulation has an order: solve the problem while caring about the person and their current mood. Personality without reliable results cannot fulfill an efficiency promise. A correct result does not prove the interaction avoids anxiety. An editorial approach seeks separate evidence for task outcomes and experience rather than treating time spent as happiness or productivity.
Moving from proving her ability toward a product she wants to maintain is a personal reflection. Affection can sustain work without replacing user feedback; funding and famous hires are insufficient. She compares software with a lawn needing maintenance, while acknowledging that maintenance may itself become automated. Current difficulty is a work requirement, not necessarily a permanent moat. Her optimism rests on specific unresolved problems, not a guarantee for every project.
Exercise: review one decision that seemed logically inevitable
Write the original reason, such as “all these scenarios need sourcing, so customers will cross-buy.” Examine one actual user’s recent task: who operates, who pays, which step takes the most effort, where control matters, and what is delivered?
Judge technical reuse, user reuse, and business reuse separately. Technical reuse alone does not establish one market. Specify evidence that would stop expansion and behavior demonstrating that a valuable missing step was completed. For an experience improvement, compare switching, explanation, and rework between intent and result. This editorial exercise is not a financing or business-success formula.
Sources and listening guide
Prepared from the complete transcript and official introduction and chapters, without replaying audio or testing products. Anonymous allegations are not reported as established facts. Stability, version counts, spending, and feedback retain self-report attribution. No name is invented for the unnamed desktop product; closing lyrics are excluded from interview claims.
- 08:45: Starting with a vertical category.
- 11:40: Professional and non-professional user conflict.
- 12:28: Easy segments versus costly work.
- 30:21: From extension to desktop experience.
- 39:07: Research tied to decision questions.
- 44:00: Internal demand and concrete results.
- 01:05:00: Task value and attention to people.
Related themes: user research, creative tools, AI organizations, and companionship. Compare Wang Wenfeng on AI managing AI and Albert on success probability and consumer orientation for different product choices under similar technical conditions.