We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Big Ideas
The agent moat is moving from initial build to accountable operation. Businesses want ordinary mess removed—email triage, call memory, CRM hygiene, invoices, search, lead routing, and reporting—but value appears when an agent holds context across systems and carries work forward. The PM problem is therefore operating design: define what the agent can see and use, when it may act, how output is checked, and what happens under uncertainty.
Platforms are already absorbing bespoke agent work into native surfaces, so horizontal “we make AI agents” offers are exposed. More durable bets sit in vertical workflows, cross-system integration, private/local deployments, evaluation-heavy systems, and high-cost-of-error operations; maintenance is part of the product because an agent can stay online while silently degrading. Roadmaps should budget for evaluation, monitoring, correction, permissions review, and redesign—not just launch.
Tactical Playbook
Make the prototype the shared decision object. One PM reports that rough, unbranded wireframes improved collaboration with designers and engineers, sped alignment, and enabled collective ideation; the tradeoff was that written requirements became more painful and agreements moved into concept-building. Use low-fidelity prototypes early, label assumptions and roughness explicitly, then capture final decisions once the concept stabilizes so speed does not erase traceability.
Case Studies & Lessons
A freemium test rejected forced conversion. A student productivity app split new users among the existing free plan, a 14-day Premium trial followed by read-only access, and an 80-hour usage paywall. The normal/free experience performed best, so the founder kept the core app free and shifted to contextual Premium prompts after repeated use of a relevant feature, alongside multiple price points and regional pricing.
The results are directional, not proof of causal lift: registered users rose from 3,080 to 5,561, monthly active users reached about 1,500, trials rose from 2 to 59, five converted—roughly 8.5% of a small sample—and revenue reached about €185. Most growth came organically through Google, while infrastructure costs came under control. The PM lesson is to test whether the problem is gating, value, or positioning before degrading the free product. A useful diagnostic is a non-leading question such as “What’s the biggest value you get?” Answers about free features suggest a premium-value problem; answers about premium features suggest a positioning problem.
Career Corner
High-talent hiring is a targeting problem, not a volume problem. Cursor’s head of talent calls the conventional 100-outreach/20-replies funnel “remainder” hiring. His alternative: define “great” by stack-ranking skills and experiences, explain the role’s impact and success criteria, map a finite target list—50 is his example—and pursue it. Use referral questions tied to a specific trait, such as collaboration with designers, rather than “who’s the best?”
For PM candidates, build a work sample that demonstrates judgment and execution, not just polished artifacts. The interview cites work samples as the strongest predictor of success, and Cursor uses project-based, side-by-side on-sites because removing work trials weakened its signal.
Tools & Resources
Simplify AI harnesses as models improve. Aakash Gupta’s Claude Code note argues for “outcomes > steps”: specify the desired outcome, format, quality bar, examples, and guardrails rather than a large procedural prompt; move context into skills and libraries, and maintain the harness because 1–2% gains on each task compound. The note also links a free harness-upgrade skill. For PM workflows, keep the brief outcome-led, put reusable context in a maintained skill, and evaluate outputs against a small explicit quality bar.
Talent market & roles
- Adam Ward — co-founder of Growth by Design, acquired by Cursor, where he is now head of talent — calls today's hiring market an 11 out of 10, comparable to the early mobile talent scramble but compressed from two-year cycles to days/weeks, and bifurcated: record offers to new-grad PhDs coexist with blue-chip layoffs. He expects a resettlement of talent and labor .
- Most in demand: the forward deployed engineer — deeply technical, product-literate, able to partner with sales/executives to deploy complex products (e.g., help customers move from token-maxing to optimization) . Waning: narrow deep specialists, as engineering/product/design converge toward design engineers and product-sense engineers, and inexperienced new grads where AI tools can cover some of the work . The power IC is rising: taste, decision-making, problem-solving, and curiosity are prized again .
High-talent-density hiring
- Reject the funnel of doom: reaching out to 100 people and hiring the 20 who reply is, by definition, the remainder, not the top 20%. Instead, get clarity on what top means, market-map ~50 target people, and relentlessly activate them — executive-search discipline applied to every hire .
- Scoping works through specific questions (e.g., who is most collaborative with designers? or who can translate a framework into a product better than anyone?) rather than who is the best engineer?; targeted questions triangulate the same names .
- Treat the person as the atomic unit, not the job spec: expect decision-tree-like, bespoke processes; invest weeks/months planting seeds, then move fast when a candidate is ready (e.g., hiring-manager conversation within the hour) .
- Candidate experience is two-way: use work-sample/project on-sites because work samples are the highest predictor of success; curate who greets, lunches with, and interviews the candidate; every candidate should leave as a net promoter .
- If talent is #1, measure it like uptime or revenue and keep accountability with hiring managers; recruiters are a confidence engine, not a decision engine .
- Closing is a team sport: per-candidate stand-ups and Slack channels, personal touches (e.g., a custom instrument for a violinist), and continuous touchpoints over months/years .
- Early-stage hiring mistake: hiring a silver-bullet first recruiting lead who must both fill 5–15 open roles and build the system; decouple those two jobs .
- Talent density is collective: a 10X person can't exist on a bad team; optimize for compounding team effects rather than individual heroes .
Career & negotiation
- Offer negotiation: candidates should put their asks on a line of logic — be consistent and clear about the few things that matter rather than piling on random demands .
- Recommended reads: Emotional Intelligence (Goleman), especially relevant in the AI age, and The High-Growth Handbook (Elad Gil) for jump-to-chapter answers .
Emerging trends
- Offer reneges are increasing; run a second motion between accept and join — community dinners, laptops, touchpoints — to protect delivery and speed ramp .
- Talent engineer trend: recruiting functions should build their own tools instead of begging for engineering time .
- Cursor's head of talent Adam Ward calls the standard recruiting funnel the "funnel of doom": reaching out to 100 people and expecting 20% to reply isn't finding the top 20%, it's just catching people on a bad day; weeding out stage by stage produces "remainder" hires and regresses to the mean. Instead, use the "pillar of excellence" approach: identify the top 50 people for a role, validate with assessment, and pursue them with exec-search rigor.
- To hire elite talent, define "great" before talking to anyone: objectively stack-rank the skills and experiences you need, articulate why the role matters and what success looks like, and avoid "I'll know it when I see it" or copying another company's definition. Don't default to resume logos.
- Ask specific referral questions, not "who's the best?": instead of "who's the best product engineer you know?", ask "who's the most collaborative with designers?" or "who can translate a framework into a product better than anyone?" — specific questions map back to your scoping and surface names you can triangulate on.
- Relentless pursuit means planting seeds and staying in touch: ask top candidates only for a "next conversation," keep weekly touchpoints, and accept timelines of weeks, months, or years. "Caring is free" — the #1 candidate satisfaction driver is feeling the company genuinely wanted them; don't lose the human element to funnel numbers.
- Role demand trends: forward deployed engineers (technical people who partner with sales and customers to deploy complex products) are in acute demand; narrow, over-specialized roles are waning, and new grads are squeezed because AI tools can do entry-level work. Companies increasingly want design engineers, engineers with product sense, and "power ICs" with taste, judgment, problem-solving, and curiosity.
- Systems thinking is a top attribute: anchor on the fundamental problem you're trying to solve, break it into small pieces, and remove blockers tactic by tactic.
- Work samples/on-site projects are the strongest hiring signal: research shows work samples predict success best, and Cursor runs project-based on-sites where candidates work side-by-side with the team. They design the experience two-way (curated interviewers, meals, greeters) to feed candidate self-selection. When they removed work trials, signal tanked and they brought them back.
- Hiring managers own the hiring decision: recruiters are a "confidence engine," not a decision-making engine; the hiring manager and team feel the pain or joy of a good or bad hire, so holding a recruiting org accountable is a conflict. At Cursor there are no hiring committees — the hiring manager leads, with team input.
- Sell throughout, not at the close: understand the candidate's motivations up front and hit them in every touchpoint; focus on intrinsic factors and mitigate comp as the reason to join. Comp often isn't the deciding factor — people who chase the largest number often regret it six months in. Closing is a team sport: daily stand-ups, a per-candidate Slack channel, and personalized gestures (e.g., a gift tied to a candidate's passion).
- Candidate offer negotiation: have a line of logic. Be clear and consistent about the few things that matter to you, and ground each ask in a rationale; scattergun asks read as random excuses for more income.
- Talent density is a team property, not a single 10Xer: a brilliant person on a bad team is throttled; aim to build complementary teams.
- Post-acceptance, run a "second motion" against reneges: after an offer is accepted, do pre-boarding — dinners with other acceptees, staying connected, sending hardware (e.g., a laptop) — which increases show-up rate and speeds ramp.
- Rise of the talent engineer: a growing role on recruiting teams, often a former engineer who builds tools with AI. Warm take: every recruiter should be a talent engineer, since they can now build what previously required begging for engineering time.
- A first-time founder (this is their first SaaS ) spent ~1 year building a compliance guardrail for AI agents (checks AI outputs against privacy/financial/sanctions rules), began selling only afterward, and after 3 months of cold outreach to federal contractors/partners, LinkedIn, daily posting, and a leak-demonstration field test had warm conversations but zero paying customers or pilots .
- The core mistake identified: building for a year without talking to a potential customer; validate demand with customer conversations before building .
- Faster validation pattern: sell before you build — landing page describing the problem plus waiting list or book-a-call, optionally with a weekend demo prototype .
- In B2B compliance/regtech, 3 months without a deal isn't necessarily a bad signal: federal contractor cycles run roughly 6–18 months; the metric that matters is whether any prospect said "I would pay for this" .
- A proven way to customer #1 is doing the diagnostic work unsolicited: run your compliance check on a prospect's actual AI agent and send them the violation report — evidence of a problem sells before a control does .
- Segment hard and sell to multiple roles: the real need is in highly regulated enterprises (ideally with in-house compliance teams), and sub-segments (bank chatbot vs insurer) need different processes/pitches — sales scripts don't transfer across markets; expect to resell to legal/GRC roles over ~6 months .
- Lead conversations with problem questions, not the demo; cut tech jargon and double down on pain; prepare a one-sentence rebuttal to "OpenAI/Anthropic will build this in" (e.g., model providers can't audit every jurisdiction; regulators require independent third-party audit) .
- In regulated/government channels, certifications are purchase prerequisites: vendor minimum certifications (FedRAMP High for federal agencies), benchmark/cert requirements from partners, and at least visibly in-progress SOC 2; validate gov demand via RFPs (government doesn't buy without one), which appear under "AI governance"/"responsible AI"/"model risk" language rather than exact product keywords .
- Category risk is real: the AI compliance space is crowded and well-funded (direct competitor raised $10M from a16z; another shipped runtime enforcement; hundreds of millions in research funding), and buyers may see guardrails as a built-in feature of chat-agent vendors — differentiation and pain proof are essential .
- A PM with 20+ years in the game lists pricing, P&L, business cases, end-of-life, and build/buy/partner as the five topics that create the most "flop sweat" . Pricing drew the most agreement as hardest: "Pricing feels like vibes" , one PM spent 6+ months pricing a single offering , and pricing untested or innovative features is an "endless back-and-forth" or a "black box" .
- Practical pricing tactics shared: calculate minimum selling price from cost + expected unit economics, validate willingness to pay, and build a calculator to optimize price against goals ; use The Pricing Roadmap for a product-centered pricing approach ; know the difference between Conjoint Analysis and Van Westendorp Price Sensitivity .
- Build/buy/partner decisions often get derailed by politics, not analysis — e.g., an acquisition-era push to outsource a "bread and butter" function triggered a huge fight despite better candidates ; a customer VP with more political capital than the PM VP killed a service-replacement plan . The call forces balancing cost, control, and stakeholder priorities ; a quick heuristic: estimate costs, get a quote, and ask if it's core and easily changed later .
- End-of-life: the decision is easy, execution is not — "literally an archaeological dig of random corner cases" that never ends, with hidden deals and hidden work surfacing and TPMs bearing the brunt .
- P&L/planning realities: asking about CAC and break-even reveals whether a team understands unit economics ; a commercial-insurance PM describes bottom-up forecasts being overwritten by a CEO's arbitrary 3.5%→12% growth mandate, then evenly spread because it's unrealistic, with strong years ratcheting future targets . AI products add a cost problem: marginal user cost can rise exponentially and has "no ceiling," unlike SaaS .
- Career bar: defending business cases with ROI timelines is a baseline PM expectation , yet many PMs — especially those from technical backgrounds — can't execute these skills .
- Hiten Shah argues AI agents are following the website adoption curve, and the service market forms in the gap between seeing an agent work and trusting it with real work; a proposal's monthly maintenance line is the most important reveal of where durable business will be, because buyers pay for someone to own the outcome after the build .
- The recurring business demand for agents is ordinary work: email triage, call memory, CRM hygiene, invoices, internal search, lead routing, reporting . Turning a demo into a working system is what creates the service market .
- Building agent systems is 'operating design': deciding what the agent can see, which tools it can use, when it may act, how output is checked, and what happens when uncertain; systems need memory, permissions, escalation paths, and a way to learn from failure without quietly repeating it . Because an agent can stay online while becoming less reliable, maintenance becomes trust preservation: evaluate, monitor, correct, and periodically redesign as models, tools, data, and business change .
- Market evidence: Fiverr reported an 18,347% increase in searches for AI agent freelancers over six months in 2025; Microsoft's 2026 Work Trend Index found organizational factors (culture, manager support, talent practices) accounted for more than twice the reported AI impact of individual effort; Salesforce Agentforce reached $800M ARR and 29,000 deals by early 2026; Shopify turns natural-language requests into Flow automations and custom admin apps via Sidekick .
- Strategy for agent products: horizontal 'we make AI agents' offers will age quickly; durability rises with cost of error and specificity of context — strongest opportunities are vertical workflows, cross-system integration, private/local environments, evaluation-heavy systems, and operations where a plausible mistake is expensive. Platforms can standardize actions, but accountability takes longer to standardize .
- Related post: unlike a website, an agent can keep running while quietly becoming less reliable; that turns maintenance into trust preservation, and the durable agent business begins after the initial build .
On r/startups, a founder of an AI dev tool saving token costs/time reports prospects agree the problem is real yet keep using manual workarounds, with low conversion despite cold outreach . Takeaways for PMs:
- A workaround existing can mean the problem is 'solved enough': ask whether it is a real outstanding problem and what makes your solution worth the effort/cost of switching — 'most workarounds are good enough for most people' .
- Switching is a value-vs-inertia tradeoff: buyers weigh cost, frequency, and how much they hate the current process, and the product must be 'exciting enough' to overcome resistance to change . A commenter with two SaaS exits and F500 buying experience says the 'new, unknown startup' excuse is usually wrong — 'It's the product; a lot of people just use that as an excuse. Not all but most.'
- Position against the gap between workaround and tool, not the category label: 'The most successful mop ever wasn't sold because it cleaned floors, but because it made wringing out easier' — e.g., sell the specific recurring pain (re-typing your stack and past decisions on every new session), not 'it's an AI product' .
- Cost savings is a requirement, not a reason to buy: 'no one buys a tool because it saves them money. They buy a tool that solves a problem they are having right now and are then happy it saves them money' — even enterprises; 'money saving is a harder sell than making life measurably easier'; 'people will pay for convenience' .
- Selling on token savings in AI dev tools is especially weak: the space moves too fast and users expect the 'foundation labs' to ship the capability in the next release, plus they will ask 'is it something that I can build in 30 minutes?' — quantify the actual money/time saved .
- Without urgency you are a nice-to-have fighting 'if it ain't broke'; developers add a 'build vs. buy' blocker. Tactic: recruit a few specific target users as design partners/beta testers, map their adoption/usage, and reframe the value proposition in terms other users identify with .
- Target whoever actually bears the pain: e.g., seniors 'have zero problems' — the put-upon family IT person is the one with the problem; find the person carrying the cost of the workaround .
Hiten Shah (@hnshah) frames ChatGPT's current state as a "ux transition phase" whose resolution is still unknown — "we are in a ux transition phase of chatgpt and us as users don’t have a clue yet because the answer is yet to come" . He amplified a critique by @signulll arguing the split between chat and work modes has fragmented the product: chat feels "constrained & legacy" with no way to choose the desired intelligence level, while work mode turns simple questions into slow, tool-using "expeditions"; with "no good default" users must constantly switch modes, and the lack of mobile/desktop sync plus unclear local-vs-cloud chat distinction add further confusion — ChatGPT "went from the most usable simple consumer experience to confusing af" .
In "Agents Are the New Website," Hiten Shah argues agents will follow the website adoption curve at much higher speed: the buyer's real decision is whether to become their own integrator or pay someone who has already found the sharp edges — the same decision that created website service markets in the late 1990s . The recurring demand he sees is removing ordinary business mess — email triage, call memory, CRM hygiene, invoices, internal search, lead routing, reporting — where an agent becomes valuable by holding context across those places and reliably carrying work forward .
Market signals: Fiverr reported an 18,347% increase in searches for AI agent freelancers over six months in 2025, and Microsoft's 2026 Work Trend Index found organizational factors such as culture, manager support, and talent practices accounted for more than twice the reported AI impact of individual effort — people learn faster than companies change, and that gap is becoming a market .
Platform pressure is real: Shopify turns natural-language requests into Flow automations and generates custom admin apps via Sidekick; Salesforce says Agentforce reached $800M ARR and 29,000 deals by early 2026 . Horizontal "we make AI agents" offers will age quickly; durability rises with the cost of error and specificity of context — so strongest opportunities sit in vertical workflows, cross-system integration, private/local environments, evaluation-heavy systems, and operations where a plausible mistake is expensive .
Maintenance becomes trust preservation: an agent can stay online while silently becoming less reliable, so it needs evaluation, monitoring, correction, and periodic redesign as models, tools, data, and business change; buyers will pay for someone to own the outcome, which is why the monthly maintenance line in proposals reveals where the durable business will be .
- Engineers moving into PM are best positioned to transition internally at their current company; external applications are hard without PM experience because recruiters prefer on-the-job PM experience .
- Build PM evidence outside work: volunteer with organizations such as Taproot Foundation, join hackathons, or prototype solutions to real problems using existing dev skills; employers look for visible thought process and understanding of product/project principles .
- Learn the differences between project, program, and product management — knowing the fundamentals of each lets you lean into one as your career progresses .
- PMI offers project/program management certifications, but they require experience; unconventional work can qualify (e.g., planning a wedding was accepted as a project) .
- For PMs with accessibility needs: remote/hybrid work can help; large companies often pack schedules with meetings, though many are accommodating, while mid-size companies (200–1,000 employees) tend to have fewer meetings .
- Open-source PM opportunities are rare; internal moves are the recommended way in .
- Hiten Shah argues that for AI agent products, retention metrics based on activity mislead: a user can remain active — agents still running, usage looking healthy — while their relationship with the product shrinks, as they stop adding workflows, keep important work elsewhere, and experiment with another system. Real churn happens months before usage disappears; "trust left first" .
- Suggested alternative metric: how much additional responsibility the user handed over — added another workflow, connected another source of context, granted another permission, moved more consequential work in, or let an agent run longer without supervision. In this category, trust determines how much of the user's work the product gets to touch .
- Reliability is how trust compounds: uneventful ("boring") updates teach users they can delegate more; broken updates teach them to hold back. His own experience: repeated breaking updates made "openclaw update" a dreaded command — he stopped wanting to add workflows, became hesitant to update anything working, and looked for alternatives; with Hermes Agent, updates kept memory, skills, and workflows intact, producing zero update anxiety, so he kept building and granting more responsibility .
- Takeaway: "Retention tells you whether I stayed. Responsibility tells you whether I trust you. For agents, the second matters more."
- PMs recommend learning AI by building — automate a repeatable work task with Claude Code/Codex or build a knowledge-base voicebot to cover LLM fundamentals, RAG/grounding/vectordb, prompt engineering, fine-tuning, evals, and cost-quality-speed trade-offs . A step-by-step path: learn RAG, build a RAG pipeline, understand MCP servers, build a skill, automate with cloud routines/loops, and write golden-set evals .
- One commenter's framework: learn AI fundamentals to join architecture/build-vs-buy decisions, build small AI apps, and follow Anthropic/OpenAI engineering blogs; avoid 'AI PM' courses costing >$50 — generic and obsolete in 6–12 months . Free resources: Anthropic 'Claude Code in Action' , DeepLearning.AI/Coursera fundamentals , Matt Wolfe weekly update, Matt Pocock technical YouTube, Karpathy's LLM explainers , TLDR newsletter . Evaluations with golden sets are the hardest part — 'just precise guessing in large prompts' .
- Counterpoint: most self-described 'good at AI' PMs merely write basic prompts ; PMs need conversational fluency, not data-science depth — 'AI is one more tool in our toolbox' . One commenter distinguishes four AI PM archetypes (general productivity, AI features, internal efficacy, infra/lab) to calibrate depth .
On AI agents and product discovery: Hiten Shah frames agents as drivers — given an exact address they can run for hours without asking, but when asked to help choose where to go they need to check in along the way; long agent runs work when the destination is clear, while discovery needs shorter loops . Quoting @trevin, he argues long-horizon agents don't work (at least today) because they assume requirements all exist upfront, are fundamentally against human-in-the-loop, and lack true judgment for what humans like .
From a /r/startups thread on spending a $200k+ marketing budget for a small fitness app:
- A commenter argues the founder overestimates product-market fit: PMF "feels like runaway growth" — if it existed, the question would be about keeping up with growth, and assuming PMF before it exists "will kill your startup" .
- Before PMF, spend as little as possible on many experiments to find something repeatable; brand marketing before knowing what people want is "flushing money down the toilet" . Avoid big splashy campaigns; instead focus on ongoing visibility to a specific niche .
- To choose channels, talk to a good sample of customers and ask where they go online and in the real world; that's where to spend money .
- Growth lesson from experience: start small and data-driven; it takes time to learn whether paid customers spend and retain like organic ones; don't over-trust early growth — one founder's big-company CMO "went too hard" and "cost us a ton of money" .
- For a non-gaming consumer app, the only realistic ROI-positive direct-response channel is Instagram/Facebook: test creative/message variants at $10–30k per campaign group, then iterate on winners; with $200k, allocate $20–80k to creative production/brand assets and the rest to three rounds of testing and media fees. The budget itself likely won't be ROI-positive but can reveal a path to scale. Unless per-customer LTV is unusually high, paid media probably can't scale user growth, so the alternative is a long, slow grind: evangelism, social/local events, DIY PR, and tending users to slow churn .
A startup making mobile games for children with speech delay/autism reports very low sales; only one app has IAP/subscriptions and low revenue forced ads into the other three games, which the founders oppose for a kids product . Its only acquisition channel is the co-founder's Instagram following (~32k), with no paid ads .
Commenters give go-to-market advice:
- Before scaling traffic, analyze the conversion funnel: from Instagram clicks → store page → installs → repeat usage → payment, and identify the biggest drop-off; 32k followers with low sales suggests auditing the funnel before spending on ads . ~150 daily visitors (Android) on the biggest app is enough traffic to justify deep funnel analysis before increasing traffic .
- Target the parents (buyers), not the kids, since children won't seek out brain-development games on their own .
- Trust matters more than for a normal mobile game, so involve speech therapists, clinics, and schools as channels and authority signals . Partnerships with institutions working with children can serve as acquisition channels and lend credibility; consider the education space ; the founder confirms they are pursuing business partnerships and the edu space . Similar organizations (e.g., e-sports programs for developmentally challenged kids) may also serve as distribution channels .
- Paid ads can be tested cheaply with a clear conversion model to ensure ad spend yields profit; parents of autistic children are described as an easy cohort to target .
- Chris Hlad (@chrishlad) says that as his company scales, his most important job is to inject (1) energy, (2) clarity, and (3) urgency into everything — every email, Slack thread, and meeting — and that they "will live and die by maniacal urgency."
- Hiten Shah (@hnshah) replies that he would add "appropriately" before "inject," because "maniacal urgency" is often misunderstood as "go go go," which misses the point.
B2B SaaS practitioners report that repeated customer conversations reshaped product positioning: messaging shifted from explaining what the product does to focusing on the operational problem it solves and the outcome the customer gets , and the feedback also made the product easier to explain in demos and marketing content . One practitioner concludes that customer feedback doesn't just improve the product — it can also change how it is positioned and communicated .
Another account describes still talking about the solution and what the product does, but using customer conversations to decide which problem to lead with: after hearing similar challenges across different customers, product capabilities were positioned as solutions to those specific problems, with the product itself changing less than the framing of its value .
A positioning-services provider adds caveats: feedback only helps repositioning when the customer matches the ICP, knows what they want rather than guessing, and volume is weighed cautiously — 30-40 people naming an issue isn't always a problem; they advise monitoring TAM when positioning and researching the core problem proactively, since feedback-driven repositioning cases are few .
- In a student productivity app, an A/B test of three monetization experiences — normal free plan, 14-day Premium trial then read-only, and usage-based paywall after 80 tracked hours — found the normal/free version performed best; the founder decided not to hard-paywall the core app, concluding that aggressive paywalls made things worse.
- Post-experiment monetization improvements: contextual Premium prompts shown when users repeatedly use features where Premium helps, new pricing tiers (Premium €3.99/mo, Exam Pass €9.99 for 3 months, Lifetime €49.99, Friends Plan €9.99/mo for 3 people, 7-day trial with no card), and regional pricing that helped trials. Metrics: 5,561 registered users, ~1,500 MAU, 59 trials (up from 2), 5 conversions (~8.5% trial-to-paid), total revenue ~€185; acquisition now mostly organic via Google SEO.
- Diagnostic framework for freemium conversion: survey premium users with non-leading questions (e.g., "What's the biggest value you get out of using this product?"); if they cite free features, it's a premium value problem; if they cite premium features, it's a positioning problem (users see free as good enough). One commenter used this after finding 80% of users valued premium features, so now advertises only premium and gives an immediate premium trial.
- When free users don't upgrade, the root cause is often that the free version provides enough value; the solution is to add more desired features (some free, some premium) rather than degrading the free tier or forcing paywalls, which shrinks the user base.
- The founder counters that the issue is communicating value ("people don't really know what premium would do"), not pricing, since competitors charge more.
A PM reports better collaboration with UX designers and engineers by bringing rough, unbranded wireframe prototypes instead of relying on written specs; being candid about the prototype's rough quality is part of why it works, and it speeds alignment and collective ideation. The trade-off: writing specs feels more painful, and requirements effectively get agreed while building concepts . One commenter simply agreed: "Yes" .
Builder-founder report: 10-year designer launched the same product three times, earning only 20 then 8 upvotes, and concluded the real failure is distribution, not product: 'the building was never the bottleneck,' yet he had always treated distribution as a formality after the build .
Community guidance for this problem:
- Validate before building: get people to care before building anything; don't build until you know there is a customer base and the product solves a real problem for them .
- Set concrete validation volume, e.g., reach out to 1,000 customers; low hundreds is too little. If stats don't look good, fail fast and start something new .
- For distribution, the repeatable channel is never the launch; it's 'the narrow place you keep showing up after the launch is forgotten' .
Practitioners connecting campaign messaging to product adoption do so manually: campaigns are tagged with UTMs, then campaign cohorts are compared in Mixpanel against product usage, with data pulled into Sheets and reviewed using Claude/GPT . One B2B SaaS PMM reports this costs about half a day per month and that they have not found a tool that automates it .