We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Muse: trust as a launch gate, agent swarms in place of dashboards
Mona Sarantakos is head of product for Muse and VP of product at Meta Superintelligence Labs. The project started when she ran OpenClaw on a Raspberry Pi with access to her email and calendar, and by Monday it had pulled together her kids' school week. The team then spent seven months making it "safe and simple enough for everyone." Lenny Rachitsky calls Muse the fastest-growing AI consumer product ever .
Takeaways from the interview that PMs can use:
- Hold launch on quality. The end-to-end product worked by spring. Most of the remaining time went to reliability, safety and security, measured against an eval bar the team wrote itself because industry benchmarks felt insufficient for an agent that holds personal context and can buy things . Each new feature, such as the browser, opened new security vectors . Instead of one launch, they let in larger and larger groups of internal dogfooders and external alpha testers .
- Let usage revise the roadmap. An external UX research panel ran from March, and stories from it went to leadership almost weekly . Shopping, which Sarantakos didn't predict, became a top use case and got its own evals. Home automation turned out smaller than expected .
- Agent swarms over dashboards. The team had little production data for long, multi-turn conversations outside coding. Swarms of agents reviewed conversations and data, generated synthetic data for evals, and checked whether a suspected issue was real . They return specifics, such as "10 people… got blocked" shopping on a site, not just metric movements. Sarantakos makes all her PMs use them to build empathy .
- Rank your evals. Priority evals such as safety and prompt injection must always pass. Capability, behavioral and use-case evals can trade off slightly, and feature-level evals belong to individual teams . People must review all the data, and the system prompt and behavioral spec must be written by hand, not by AI .
- Activation is still unsolved. The strongest lever is word of mouth from someone the user relates to. Advertising messages didn't land . The second lever is getting past the frozen first prompt, which the Ideas tab's starter packs address . Later cohorts ask how Muse differs from chatbots they already use, so the team is moving to tiered onboarding. Sarantakos says "I don't think we figured it out" .
- The PM bar is now taste. Prototypes let the team argue over working versions instead of specs and sunk costs . With product-minded engineers on the team, the PM's job is to speak for the customer and hold a quality bar, because "AI slop is very easy to put out." Taste is the first thing she looks for when hiring . Four PMs built the product. Early zero-to-one work often needed a builder more than a PM, and PMs mattered most once work moved toward integration and launch .
David Cancel makes a related point about agents in general: building the agent is easy, keeping it doing the job a month later is the real work, and "whoever owns that owns the customer" .
Deciding to cut ad spend after two weeks
A team that has shipped 15+ apps replayed two years of ad spend and made a keep-or-stop call on each week using only what was known two weeks in. Flagged weeks returned $0.55 per dollar by day 90; kept weeks returned $1.51 . The signal was new paying customers above the app's normal level, valued at what they actually paid, and compared with earlier weeks at the same age . None of the 27 flagged weeks broke even by day 90, against 33 of the 36 kept weeks . The result is less clean at one year: 3 of the 15 flagged weeks old enough to check had paid back, and the flagged group returned $0.84 against $1.89 . Slow weeks got a "behind" call rather than a cut, and all six paid back by day 90 .
Do PMs feel safe?
Many in an r/ProductManagement thread reported layoffs or reorgs. The more useful comments were about where PM value holds. One PM sees sales leads and company owners skipping the PM to vibe-code features for a single client . Another says they'll worry when AI can turn customer feedback into valid requirements and unspoken needs . A health IT PM says their organization grew its PM team about 25% and trimmed engineering for an AI-based development lifecycle, because "faster code won't do any good" if PM and QA remain the bottleneck . Immad Akhund, whose post Hiten Shah endorsed, says small startups now have people managing agents that do ops, sales and support .
Briefly
- Users before investors: Paul Graham says users are "the ultimate gatekeepers." If users don't like the product, impressing investors won't save it .
- Interview follow-ups: For any feature you propose, name one primary metric and one guardrail. Commit to a single priority, and state the riskiest assumption and a cheap way to test it . When a metric drops, first check whether the drop is real, how it's measured and which segment it affects .
- Validating B2B demand: Find out who controls the budget and ask for a small paid pilot. That's a stronger signal than "sounds interesting" .
- Muse treated reliability, safety, and security as launch gates: standard benchmarks were not enough for an agent with personal context and the ability to act, and adding a browser introduced new security vectors. The team red-teamed, dogfooded internally, and expanded external alpha testing, guided by its principle that trust is a must.
- Product discovery and evaluation drew on an early external research panel, internal feedback, and agent swarms analyzing usage and conversations; the swarms helped fill a gap in long-running, multi-turn, non-coding examples and investigate whether reported issues were widespread. Use-case priorities shifted with the evidence: shopping became a top use case despite not being expected, while home automation was less important than anticipated. Evals also covered priority safety, capabilities, behavior, and use cases; people reviewed the data, and the system prompt and behavioral spec were required to be handwritten.
- For activation, the team found relatable word-of-mouth stories more effective than simply describing the product; starter packs in the Ideas tab helped users get past the blank first prompt. It also moved toward tiered onboarding because later users needed to understand how Muse differed from a chatbot, unlike early adopters.
- Product principles shaped the interface: the team kept Jolly and user-customizable avatars rather than a corporate logo so a personal agent would feel like it belonged to the user. It chose chat bubbles as a familiar way to communicate, while recognizing the resulting tradeoffs for long answers and other content.
- AI-enabled prototyping and internal tools let the team discuss concrete working versions and iterate faster than with abstract specs; with product-minded engineers, the PM’s distinctive contribution was taste, customer empathy, and holding a quality bar against easy-to-ship AI slop. The core team began at about 10 people and was mostly engineers; the team found PMs were less necessary for some early zero-to-one prototyping and more important as work moved toward product integration and launch.
- Muse treated trust as a launch gate: after reaching a working end-to-end product, the team spent substantial time on reliability, safety, and security, set its own evaluation bar, and red-teamed; adding a browser introduced new security risks. It expanded internal dogfooding and external alpha testing to build confidence before launch.
- Frame an agent around helping users achieve their goals, not merely completing tasks; that shift led Muse to explore proactive help and add a Goals tab. Use observed behavior to revise roadmap assumptions: shopping became a top use case despite not being an initial bet, while home automation was less important than expected, prompting shopping-specific evals.
- Make real user evidence a regular input to product decisions: Muse started an external research panel early, gathered internal feedback, and reviewed user stories with leaders weekly.
- For a multi-turn agent where relevant production data is scarce, Muse used agent swarms to analyze conversations, metrics, and user feedback, generate data for evals, and surface specific friction—such as users being blocked while shopping—beyond what dashboards show. The team said these examples also helped PMs empathize with users.
- Structure AI evals across non-negotiable safety checks, capabilities, behavior, use cases, and feature-level tests. Agents can help create evals, but people should review the data; Muse required its system prompt and behavioral spec to be written by people.
- Give capable engineers room to prototype from a small idea; Muse found some early zero-to-one work needed a builder more than a PM, with PM coverage becoming more important as ideas moved toward product integration and launch. Rapid prototypes and internal tools make discussions concrete and faster, while PMs add customer empathy, product taste, and a quality bar.
- For AI-assistant activation, Muse found relatable word-of-mouth stories more effective than general promotion; its Ideas tab and starter packs addressed users freezing on the first prompt. Because later cohorts were less familiar with agents than early adopters, the team moved toward tiered onboarding and noted the problem was not fully solved.
- AI makes design iterations and proof-of-concept coding faster, but commenters argue that production-ready, scalable products still need product, design, and engineering skills. One PM warns that stakeholders may vibe-code a feature for one customer without considering other users, leaving engineers to handle quality problems and support .
- Commenters identify customer understanding, translating feedback and unspoken needs into requirements, evidence-based prioritization, and deciding what not to ship as important PM contributions. A rollout plan still calls for feature flags, customer validation, and statistical significance; balanced product, technical, and design expertise helps connect these decisions .
- One commenter in HIT reports their organization grew its PM team by about 25% while cutting engineering somewhat during an AI-PDLC shift, arguing that faster code does not remove PM/QE input-output bottlenecks .
- Job-security accounts are mixed: some commenters report layoffs or being moved out of product during reorganizations, while those who feel relatively secure point to niche industry experience, customer knowledge, and strong relationships with leadership. These are individual accounts, not evidence of a general employment trend .
- Muse’s origin story began when Mona Sarantakos, unable to find a Mac Mini, set up OpenClaw on a Raspberry Pi with access to her email and calendar; by Monday it had assembled her children’s school activities for the week, convincing her of the product’s potential. The team then spent seven months building a safer, simpler product before launch; the post describes Muse as the fastest-growing AI consumer product ever.
- The interview teaser flags two activation levers for AI agents, using “agent swarms” more than dashboards, and product taste as a key PM skill. It does not specify the activation levers or explain the practices, so these are discussion topics rather than detailed recommendations.
- The founder has 150+ registered contributors but has not confirmed researcher need or willingness to pay; a commenter frames the contributor pool as supply, not demand, and recommends focusing on buyer conversations.
- For discovery, target PhD students and postdocs who work with datasets, as well as first authors of relevant papers, rather than relying on cold pitches to professors. Ask about specific pain and current alternatives or spending, not just whether the product sounds useful. Dataset issue threads are another suggested way to find people discussing unmet needs.
- Test a small, labeled sample for one narrow research task, then track replies, downloads, and calls and ask what would make the data usable. Also identify who controls the budget and seek a small paid trial as a stronger demand signal than polite interest. For wearable data, a commenter recommends surfacing consent and licensing details up front, citing concerns about publication and review-board approval.
- For paid acquisition, evaluate performance by app-week rather than individual ad; compare new paying customers above the app’s normal level at the same cohort age, value them by what they actually paid, and track returns at days 14, 30 and 90 using only information available at the decision point. The replay froze its decision rule in advance and separated slow “behind” weeks from cuts; all six “behind” weeks paid back by day 90.
- In the founder’s two-year ad-spend replay, 27 of 63 weeks flagged after two weeks returned $0.55 per $1 spent by day 90, versus $1.51 for kept weeks; these totals were spend-weighted and before app-store fees. None of the 27 flagged weeks reached break-even by day 90, compared with 33 of 36 kept weeks; even counting every new customer as ad-driven, the flagged weeks returned $0.99 per dollar versus $1.73 for the rest, across 10 ad runs in four apps. The longer-term result was less absolute: 3 of the 15 flagged weeks old enough to assess had paid back by a year, while the flagged group returned $0.84 per dollar versus $1.89 for kept weeks.
Muse’s team spent seven months building a product they considered safe and simple enough for everyone before launch. In an early trial, Mona Sarantakos gave an AI agent access to her email and calendar; by Monday it had assembled her children’s school activities for the week, though her husband had questioned the setup’s safety. The interview also highlights the team’s reliance on “agent swarms” more than dashboards and presents taste as an increasingly important PM skill.
An aspiring PM transitioning from data science and research asks whether PM hiring values a side project for identifying a genuine user problem or for achieving commercial success; their project targets academia and graduate students, where they expect paying customers and revenue to be limited, and they want to build PM experience without having to become a founder .
- Mandate clarity was central to one newly promoted PM’s career decision: their team’s current scope was moving elsewhere, proposed new work had no formal mandate or funding and could leave the team as support-only, while an external Senior PM offer included ownership of a familiar commercial product.
- A commenter suggested testing the ambiguity directly: ask current leadership what the mandate is and by when, since promising work without a named owner and budget may not materialize; for the PE-owned employer, ask about recent layoffs, revenue growth, and the reporting line, treating evasive answers as a warning.
- PE-backed experience was mixed: one PM described annual reorganizations as growth opportunities but also a source of constant stress and job insecurity; another commenter argued that stability depends on the company’s stage, leadership, and a new hire proving effective, while warning that a Senior PM may be expected to operate without much mentorship.
A Senior PM at a relatively small global trading app says they managed 30+ local and global fiat and crypto payments and that the business handles about $1 billion in annual payment volume. They are targeting larger consumer-payments companies to gain experience at greater scale after their learning curve flattened, while worrying that their smaller-company background and lack of connections may make those roles harder to land. Their self-reported outreach approach is to send directors artifacts describing product problems or gaps and contact PMs at target companies for referrals; they ask whether this works and what skills, timelines, and hiring experiences matter, so the approach is presented as a question, not validated advice.
Hiten Shah endorsed the view that AI-agent tools could extend Claude Code-like automation beyond engineering into operations, sales, and support; the quoted post says some small startups are already shifting from doing those tasks manually to managing agents, and predicts more work will center on training and overseeing them . Shah also included Claude Duet and Muse among the tools in this category .
For agent products, building the agent is the easy part; the harder product challenge is keeping it doing its job a month later. Whoever owns that ongoing performance owns the customer.
A PM interview-prep checklist based on the author’s experience in Amazon, Microsoft, and AI-startup interview loops: define one primary success metric and a guardrail before designing; when asked to ship one thing this quarter, choose it and explain why alternatives can wait; distinguish your own contribution from the team’s in behavioral stories; and name the riskiest assumption plus a cheap way to test it. For an overnight 10% metric drop, first check whether the change is real, how it is measured, which segment is affected, and whether the cause is internal or external before proposing explanations. The author recommends practicing aloud with someone who pushes back rather than relying on reading frameworks alone.
A PM trying to follow PM and AI trends says their AI chief-of-staff/Perplexity weekly newsletter and custom trend podcast are not yet satisfactory . A commenter recommends the Lenny and Product Moat newsletters for perspectives from product practitioners, including their experiences with AI .
- The poster’s guidance is that overseas PM hiring depends on scarce local talent, a company’s ability to sponsor visas, and sometimes locally specific domain knowledge (payments is one example); check sponsorship eligibility before targeting employers.
- For an international search, build a target list from your product vertical and adjacent industries, automate career-page and LinkedIn alerts, apply through company websites, contact relevant employees, and watch for roles shared only on LinkedIn or through your network.
For PM job applications, the post recommends matching the job description’s wording where accurate and using a plain, single-column resume; it says to focus on missing terms rather than third-party ATS percentage scores, which it claims do not reflect a published pass mark.
Paul Graham’s product lesson for founders: prioritize users’ opinions over investors’—users are the ultimate gatekeepers, winning them can bring investors, and investor persuasion cannot rescue a product users dislike; trying to fool investors is temporary and not worth it.
As one self-reported compensation datapoint, an early-career technical PM working remotely from India for a US B2B AI voice-agent startup says they earn about $700/month (₹67–68K) after roughly six months in the role. They report positive culture, substantial ownership, and taking a client-product project from idea to launch, while weighing a job switch, staying another year, or seeking onsite work in India.
For software in an unfamiliar B2B domain, make workflow discovery a prerequisite to coding: shadow real operators and trace a transaction end-to-end, documenting who handles each step, exceptions, and common failure points, since undocumented workarounds and the reasons behind processes can encode business rules the software must capture . Turn the most common breakdowns into initial test cases, check financial models against actual figures, and use AI afterward to surface gaps in your workflow notes—not as a substitute for operator knowledge .
- Product management is less a linear path from user research to launch than a cycle of conflicting user and sales requests, technical constraints, scope cuts, stakeholder escalation, and ambiguous results; discovery, strategy, stakeholder management, and maintaining perspective are central to the work.
- To manage incoming requests, research them before adding them to the backlog, communicate decisions transparently, and explain rejections with evidence; keep other ideas outside the backlog for later review, while avoiding a reputation for rejecting everything.
r/ProductManagement comment by u/BuckeyeSRQ
Product managers do you feel your job is safe??
Just curious how safe y’all think your job js
Laid off in 2024 and forced out in a reorganization a few weeks back. Looking at getting out of tech because of its toxicity. Doesn’t matter how well you do your job you have zero security anymore.
- AI makes design iterations and proof-of-concept coding faster, but commenters argue that production-ready, scalable products still need product, design, and engineering skills. One PM warns that stakeholders may vibe-code a feature for one customer without considering other users, leaving engineers to handle quality problems and support .
- Commenters identify customer understanding, translating feedback and unspoken needs into requirements, evidence-based prioritization, and deciding what not to ship as important PM contributions. A rollout plan still calls for feature flags, customer validation, and statistical significance; balanced product, technical, and design expertise helps connect these decisions .
- One commenter in HIT reports their organization grew its PM team by about 25% while cutting engineering somewhat during an AI-PDLC shift, arguing that faster code does not remove PM/QE input-output bottlenecks .
- Job-security accounts are mixed: some commenters report layoffs or being moved out of product during reorganizations, while those who feel relatively secure point to niche industry experience, customer knowledge, and strong relationships with leadership. These are individual accounts, not evidence of a general employment trend .