The hottest Product Substack posts right now

And their main takeaways
Category
Top Design Topics

TBM 401: Solving Problems the Hard Way

The Beautiful Mess • 528 implied HN points • 16 Jan 26
đź’Ľ Business Product
  1. Break work into a small set (3–5) of clear but flexible lanes with a one- or two-line intent; make them stable enough to get a groove but easy to reshape or retire as reality changes.
  2. Put real ownership on each lane (one to three people) and run simple routines—copy lanes forward and review weekly or biweekly—to surface what moved, what stalled, and where to course-correct.
  3. Work small and think big: focus on near-term actions you can influence while keeping longer-term direction soft, and treat lanes as a collaborative, iterative learning practice rather than a rigid framework.

Staying Relevant in a Post-AI World

Let's talk games & AI. • 15 implied HN points • 17 Mar 26
đź•ą Technology Product
  1. Surface-level polish can hide core flaws and create false positives. Always put a bare prototype in front of users first and make evaluation an explicit, scheduled step before you add polish.
  2. AI speeds up production but not judgment, so faster generation shouldn’t force faster review. Don’t let generation volume set your review pace—deliberate discernment must be preserved.
  3. As AI and automated testing scale, volume and measurement can replace human taste, making distribution the real advantage. Build and nurture an audience now because reach will matter more once creation commoditizes.

How Duolingo reignited user growth

Lenny's Newsletter • 9571 implied HN points • 28 Feb 23
đź’Ľ Business Product
  1. Duolingo achieved 4.5x user growth over four years through innovative strategies like leaderboards and push notifications.
  2. Their focus on improving retention over new user acquisition led to significant improvements in engagement metrics.
  3. Using data and models, like Zynga and MyFitnessPal did, helped Duolingo identify North Star metrics and drive growth effectively.

Vibe Coding and the Maker Movement

Technically • 94 implied HN points • 26 Feb 26
đź•ą Technology Product
  1. Vibe coding skipped the slow, playful "scenius" phase of earlier maker cultures and went straight into production, so people can build fast but often lack the practical judgment that comes from long, messy practice.
  2. Think of vibe coding as consuming a surplus of machine intelligence: spent well it produces taste, attention, reputation, or gift-like social capital, but spent badly it’s just addictive, disposable output.
  3. Long-term value tends to accumulate in the model and infrastructure layers unless creators intentionally capture the byproduct signal as datasets, documentation, or curated taste, and framing the work as consumption can help avoid burnout.

The case for wasteful agents

Generating Conversation • 116 implied HN points • 19 Feb 26
đź•ą Technology Product
  1. When the cost of trying things becomes tiny, run lots of quick experiments in parallel. Most will fail, but this approach finds the right solution much faster.
  2. Cheap AI prototypes and low-cost automation change how teams spend time: product people should build many rough, working prototypes while engineers focus on hardening and scaling, and experience matters more for taste than for avoiding every mistake.
  3. Build agents to be 'wasteful' by trying multiple speculative paths and presenting options for incremental user feedback. This beam-search–like behavior will likely become the standard and yields better results than single-shot attempts.
Get a weekly roundup of the best Substack posts, by hacker news affinity:

2026 Scheming

Erik Torenberg's Thoughts • 442 implied HN points • 02 Jan 26
đź’Ľ Business Product
  1. Working inside a large venture firm to productize venture work, hire broadly, and launch ambitious projects like a new fellowship, a rolling dinner series, and a podcast used to explore ideas.
  2. Committed to building and funding community programs — reviving Turpentine, supporting the Art of Accomplishment retreat, backing matchmaking as a business, and bringing back relationship-focused podcasts and group chats.
  3. Prioritizing personal health and life: getting more serious about sleep and wellness, playing in a recreational basketball league and planning events, and sharing favorite books, movies, and TV while asking for more recommendations.

UX Roundup: GUI Heroes | Great AI Videos | AI Won’t Kill Software | Bing GEO | AI Capability Growth | Google AI UX | One-Shot Video | GPT 5.4 Writing

Jakob Nielsen on UX • 29 implied HN points • 09 Mar 26
đź•ą Technology Product
  1. AI is improving fast across images, video, and language. New models make much better visuals and one-shot instructional videos, GPT 5.4 writes more compellingly, and capability metrics show AI handling longer expert tasks.
  2. AI won’t kill software — it will make building software cheaper and open much larger markets, though legacy vendors that don’t adapt may be disrupted while AI-native firms and new business models grow.
  3. Website visibility now requires Generative Engine Optimization (GEO) instead of just SEO; tools like Bing’s AI Performance help measure AI citations, which are often highly concentrated, so focus on your top pages and track the AI grounding queries that drive citations.

Your keyboard is the real bottleneck | Wispr’s Sahaj Garg

Dev Interrupted • 51 implied HN points • 24 Feb 26
đź•ą Technology Product
  1. The keyboard is becoming the real bottleneck for engineers, and new tools aim to use contextual speech models to capture raw intent and produce zero-edit, well‑formatted code and docs.
  2. Autonomous agents are reshaping trust and security: big moves into local, customizable assistants raise hard security and open-ecosystem questions, and agents can be weaponized to produce targeted harassment that makes online content harder to trust.
  3. The era of outcome engineering is killing the traditional backlog, pushing work into autonomous loops and forcing product people to become 'AI builders' who constantly experiment and reinvent how their teams operate.

The Ultimate Positioning Guide (+ Worksheet)

Startup Business Tips 🚀 • 25 implied HN points • 01 Mar 26
đź’Ľ Business Product
  1. Make a clear positioning bet now instead of waiting for perfect data; deciding what you are, who it’s for, and who you compete with creates the data you need to test and improve.
  2. Follow the 3-step framework: pick a primary anchor (Activity, Use Case, Product Category, or Competitive Alternative), add one or two differentiators, then combine them into a single positioning statement. This structure makes messaging, targeting, and comparisons much easier.
  3. Choose the right level of specificity so you’re not too vague or too niche, and pick only real, defensible differentiators. Use a decision tree and worksheet to map your ICP, use case, alternatives, and to create clear internal and external positioning statements.

What Moltbot tells us about the ideal UX for AI

Generating Conversation • 186 implied HN points • 29 Jan 26
đź•ą Technology Product
  1. AI should be present in the tools and workflows you already use, integrating deeply so it can act where and when you need it.
  2. Trust is earned by making the AI's work visible and giving users control to inspect, accept, or correct steps and decisions.
  3. Design AI like a teammate: it should do real work on your behalf, learn from feedback, and fit into your team's existing practices rather than forcing new ones.

16 Lessons on Selling (and Life) from My 5-Year-Old

Not Boring by Packy McCormick • 211 implied HN points • 18 Jan 26
đź’Ľ Business Product
  1. Start selling early and learn by doing — every no is useful feedback, so write down what you hear and iterate on the product.
  2. Know who the buyer really is and price to match them — the kids wanted the toy but the parents had the money, so meet the payer where they are and be willing to adjust price.
  3. Small, practical details matter: pick the right time and place, use social proof, have cash/payment options, be friendly, and sometimes a kid’s pitch works better than an adult’s.

This Is a Good Year to Build Something Small

Tiny Empires • 159 implied HN points • 23 Jan 26
đź’Ľ Business Product
  1. AI has made building products much cheaper and faster, so attention — not development cost — is the scarce resource, making clarity and specificity more valuable than big ambitions.
  2. Small, narrowly scoped products convert and reach viability faster because they’re easier to explain, fit into communities, and don’t require massive scale to matter.
  3. Solo founders and tiny teams win early by iterating quickly and avoiding communication overhead, which reduces burnout and makes small, focused businesses more resilient and profitable.

One-on-one coaching moment for paid subscribers

Ageling on Agile • 39 implied HN points • 09 Oct 24
đź’Ľ Business Product
  1. One-on-one coaching sessions are available for paid subscribers. These sessions allow for personal engagement on topics like Agile, Product Management, and Leadership.
  2. Each subscriber can have six half-hour coaching moments a year. These moments can help clarify work-related issues and provide guidance.
  3. Feedback from subscribers shows that the coaching is valuable. Many find the insights helpful for understanding their challenges and finding solutions.

TBM 396: So You Want To Define “The Problem”?

The Beautiful Mess • 489 implied HN points • 18 Dec 25
đź’Ľ Business Product
  1. Don't hunt for a single, perfect problem statement. Use multiple layers to see the customer's story, other actors' views, and the wider system shaping behavior.
  2. Listen to how customers describe the issue and collect perspectives from everyone involved, while treating history and past attempts as useful data.
  3. Turn the integrated understanding into small, testable interventions your product can realistically influence, and be clear about what capabilities or constraints will expand or limit your impact.

The best growth tactics of 2025

Kyle Poyar’s Growth Unhinged • 465 implied HN points • 17 Dec 25
đź’Ľ Business Product
  1. Outbound/ABM, partner/ecosystem plays, and events/community were the biggest growth channels in 2025 — they generated the most pipeline despite the AI hype.
  2. AI-driven content and discovery plus product-led tactics also paid off, with wins from AEO/LLM work (JSON-LD, custom GPTs) and freemium/mini tools that captured high-intent leads.
  3. Execution mattered most: tried-and-true tactics succeeded when done exceptionally — examples include automated intent-based outbound, "give-to-get" partner programs, and intimate in-person or virtual events.

What's a Forward Deployed Engineer?

Technically • 26 implied HN points • 05 Mar 26
đź•ą Technology Product
  1. A Forward Deployed Engineer (FDE) is a highly technical, customer-facing engineer who embeds with customers to build custom solutions and then generalizes those learnings into the core product.
  2. The FDE model is exploding because deploying AI and other complex systems is uncertain and rapidly changing, so companies want real experts to clear the fog and make things work in production.
  3. Enterprise sales are slow and messy—security, procurement, legacy systems, and institutional inertia mean white‑glove support is often needed, so FDEs can help win big deals but they’re costly and not right for every startup.

Codex Built My Startup In A Weekend

Sudo Apps • 32 implied HN points • 27 Feb 26
đź•ą Technology Product
  1. Writing code is no longer the main bottleneck — modern coding models can build working products and CLIs in days, making implementation much cheaper.
  2. Different models have different strengths: Codex follows explicit direction and executes quickly, while models like Opus infer missing details and act more like a senior engineer.
  3. The human role shifts to architecture and judgment — engineers must plan systems end-to-end, define clear acceptance criteria, manage failure modes, and focus on product tradeoffs.

Claude Cowork nukes every startup playbook

Enterprise AI Trends • 189 implied HN points • 13 Jan 26
đź•ą Technology Product
  1. Vibe coding lets well-resourced incumbents build and ship complex apps extremely quickly, eroding the startup advantage of speed.
  2. Fast build plus large distribution amplifies incumbents' power, making it harder for single startups to capture and grow a market share.
  3. Startups need to rethink their playbooks now—velocity alone won’t protect them, so they should pursue alternative defensibilities like unique data, deep integrations, or niche specialization.

Creating value in the AI age

A Bit Gamey • 13 implied HN points • 08 Mar 26
đź’Ľ Business Product
  1. Judgment — With information and execution becoming cheap, the scarce value is knowing what truly matters and making better decisions.
  2. Curation — As content and options multiply, people pay for clear filters that surface the useful signal from the noise.
  3. Direction — Speed alone creates faster confusion, so helping others choose the right path and save time is where durable value lives.

Insights from 15+ GTM audits

Startup Business Tips 🚀 • 108 implied HN points • 18 Jan 26
đź’Ľ Business Product
  1. Make your ICP a hard constraint across everything — homepage, CRM, demos, outbound lists and content — and enforce disqualification criteria so you focus on buyers who actually convert.
  2. Choose a clear product category or primary use case before you try to differentiate. Name the main alternative you replace so buyers immediately know what to compare you against.
  3. Treat GTM as an end-to-end system: design structured demos, a simple sales process with stage exit criteria, aligned buyer-facing assets, and a content strategy that targets high-intent buyers. Doing fewer, consistent things beats many disconnected activities.

10 Quick GTM Fixes You Can Ship This Week

Startup Business Tips 🚀 • 34 implied HN points • 15 Feb 26
đź’Ľ Business Product
  1. Know exactly who to sell to — document a five‑point ICP and a list of disqualifiers (ANTI‑ICP) and enforce it so your pipeline stops getting noisy.
  2. Pick one clear positioning anchor (product category or use case) and make it consistent across homepage, LinkedIn, demos, and sales materials; pause weak channels and focus deeply on the strongest one.
  3. Tighten execution with simple processes and metrics — add source attribution, track lost reasons, set hard open/close deal criteria, review demo recordings, and actively use case studies and referrals.

How to Build an AI Agent Company in 2026: Lessons from Glean’s $7.2B Playbook

Market Curve • 100 implied HN points • 26 Jan 26
đź•ą Technology Product
  1. Make AI agents easy and reliable by hiding RAG and knowledge-graph complexity, connecting across apps, and grounding answers in company data so the system retrieves facts and says “I don’t know” instead of hallucinating.
  2. Get early customers by solving a real internal pain with long free trials and usage-first metrics, use high-touch onboarding and customer advocates to expand pilots into large enterprise deals.
  3. Start in a language-heavy vertical, build deep integrations and reusable agent templates (amplified by influencers), then scale with sales-led motions, bundling features while making security, permissions, and governance core.

MicroTimes Interviews T/Maker’s Heidi Roizen and Royal Farros (1994)

Computer Ads from the Past • 256 implied HN points • 08 Dec 25
đź’Ľ Business Product
  1. They pivoted from selling a Mac word processor to focusing on content like ClickArt and multimedia ZoomBooks, and that shift unlocked rapid growth and consistent profits.
  2. They took VC money, bought other art libraries, and brought in experienced managers to redesign products and packaging so they could win retail shelves and sell at multiple price points.
  3. They invested in technical know-how (CD-ROM, multi-platform formats, a reusable ZoomBooks interface) and used joint ventures with TV networks and publishers to share costs and reach much bigger audiences.

Cursor's Unfair UX Advantage

Generating Conversation • 46 implied HN points • 12 Feb 26
đź•ą Technology Product
  1. Make tasks tiny: small, incremental units of work let users catch mistakes early, build trust, and produce dense feedback that powers a strong data advantage.
  2. A low‑stakes autocomplete/IDE UX makes it easy to accept or reject suggestions, so even imperfect prompts save time and generate lots of useful training signals.
  3. Design agents for fast iteration and cumulative correctness rather than one‑shot perfection — cheap inference and quick feedback loops let users get to the right answer over a few tries and move much faster.

On Joining OpenAI

Artificial Ignorance • 138 implied HN points • 09 Jan 26
đź•ą Technology Product
  1. Joined OpenAI to work on Developer Experience, helping developers learn and build with OpenAI’s technology.
  2. Public news roundups are ending, and the newsletter will shift toward longer deep dives with more engineering-specific, practical content for builders.
  3. Experimenting with Substack Chat for paid subscribers (office hours and topic threads) while explicitly avoiding confidential or leaked information and keeping the writing practical and grounded.

#45 - Thought Experiment - Your "flexible" is hiding operational debt

OSS.fund Newsletter • 94 implied HN points • 22 Jan 26
đź’Ľ Business Product
  1. What you call flexibility may be hiding operational debt: manual workarounds, spreadsheets, and institutional memory erode margins and create single points of failure.
  2. AI can encode client-specific rules and handle exceptions at scale, letting you deliver personalized experiences without increasing marginal human effort.
  3. Audit recent special deals, map their hidden workflows, and encode repeatable rules so agents handle predictable exceptions while humans focus only on true edge cases.

The Defiant Way to Build an AI-First Brand (Stop Playing Safe)

Crypto Good • 9 implied HN points • 10 Mar 26
đź’Ľ Business Product
  1. Use AI to be defiant, not just efficient — make visuals that demand attention instead of blending in.
  2. Use bold images paired with fearless quotes. Pull inspiration from songs, books, or found objects and learn the AI skills to remix and superimpose text into unique visuals.
  3. Build with AI every day and combine multiple models and workflows to keep your brand voice unmistakable. Share your process, iterate publicly, and use practical tools to accelerate your mission.

Homepage Teardowns: What 6 Top SaaS Companies Get Right (and Wrong)

Startup Business Tips 🚀 • 43 implied HN points • 01 Feb 26
đź’Ľ Business Product
  1. Make your homepage instantly clear about who the product is for and what it does, use contextual social proof and realistic product visuals, and guide visitors to deeper pages with CTAs and FAQs instead of dumping too much detail.
  2. A sales-led motion can work below €10k ACV if you meet the right metrics: fast CAC payback (ideally under 6–12 months), enough ARR per AE, win rates above ~20%, short sales cycles, and mostly inbound-driven demos.
  3. Use early sales as a learning channel: document a simple visual sales process with clear CTAs, qualification rules, and next steps so you can learn how customers buy, improve positioning, and scale repeatably.

($) Forward Deployed Engineer: the Job that Makes AI Real

Interconnected • 169 implied HN points • 03 Dec 25
đź•ą Technology Product
  1. Forward deployed engineers (FDEs) are the on-the-ground builders who turn AI models into working systems inside large enterprises and governments, handling integration, customization, and deployment.
  2. FDEs are scarce and highly sought after, so companies are rapidly expanding FDE teams and partnering with global system integrators to scale capacity and meet enterprise demand.
  3. The FDE function originated in firms like Palantir and has become a core, strategic role that many AI labs now prioritize to drive real-world adoption of their technology.

Recent Learnings from Silicon Valley.

The Future Does Not Fit In The Containers Of The Past • 42 implied HN points • 25 Jan 26
đź’Ľ Business Product
  1. Mission-driven leaders win long term: people and companies led by purpose rather than short-term profit are more likely to endure setbacks, attract talent, and create outsized impact.
  2. Culture and stakeholdering are active choices: strong, widely shared beliefs about behavior and cross-functional relationship-building beat directives, so leaders must build belonging and bridge silos to enable reinvention.
  3. Embrace AI and reinvent now: a fusion workforce of humans and agents, plus advances in AI-driven medicine and interfaces, will reshape products, go-to-market models, and the skills needed, so organizations must learn, unlearn, and redesign their work today.

Manufacturing Epistemic Density

Abstraction • 24 implied HN points • 16 Feb 26
đź•ą Technology Product
  1. Being near people who already understand and topic (high epistemic density) makes short, frequent conversations possible, and those conversations turn into real progress and friendships.
  2. Removing coordination friction with simple tools (like an easy coffee scheduler) makes casual local meetings happen more often, and that consistency helps relationships form.
  3. AI has compressed the time to build small apps, so problems that once felt too small now merit quick, imperfect projects you can ship in hours or days.

The first principle behind "first principles"

Building the Builders • 11 implied HN points • 25 Feb 26
đź’Ľ Business Product
  1. First-principles thinking means digging down to the most fundamental truths of a problem and reasoning up from there. This uncovers causal forces and opportunities that surface-level assumptions miss.
  2. Ask basic, high-leverage questions about core needs or essential components instead of accepting proxies or industry norms. Those questions steer you toward different and often better solutions.
  3. Thinking from first principles is hard and risky and requires building your own observations and trusting your judgment. But it’s the path to original breakthroughs rather than just incremental tweaks.

Announcing GreatGamesNetwork

Let's talk games & AI. • 6 implied HN points • 09 Mar 26
đź’Ľ Business Product
  1. A new games company is focusing on evergreen casual puzzle games aimed at older women, betting these titles drive long-term engagement without a constant content treadmill.
  2. The business uses a syndication model: build one game library and publish the same games across many destinations (daily challenges, SEO-optimized sites, saga-style apps), so small revenue streams aggregate at low marginal cost.
  3. The flagship product is an ad-free daily puzzle subscription with a few games live now, and growth will rely on paid user acquisition, iterative product improvement, repeatable tooling, and public metrics to guide progress.

How to Package Agents

Good Better Best • 2 implied HN points • 06 Mar 26
đź’Ľ Business Product
  1. SaaS companies are mainly packaging AI agents two ways: as paid add-ons with clear per-unit (credit) pricing, or bundled into higher-tier plans to drive upgrades.
  2. Credits and usage-based models are becoming the standard metric, often paired with gated business access and generous trial windows to prove value.
  3. The right packaging depends on fit: flexible, multi-agent needs favor add-ons, while purpose-built solutions like support automation are better bundled into core plans, and the market playbook is still forming.

A bear case on Google :)

Enterprise AI Trends • 168 implied HN points • 23 Nov 25
đź•ą Technology Product
  1. Google’s Gemini offerings are fragmented and inconsistently messaged across apps and tools, which creates user confusion and slows adoption.
  2. Google is missing obvious product opportunities — like low‑latency real‑time voice APIs, text‑to‑music, and basic chatbot memory/agent features — that would win enterprise and creator customers.
  3. Google under‑promotes shipped capabilities and developer tools (e.g., Chrome summarization, Gemini CLI) and needs stronger marketing and dev‑rel to capture mindshare.

The Enshittification of Google Docs

How the Hell • 184 implied HN points • 18 Nov 25
đź•ą Technology Product
  1. Google put its AI buttons right on top of the document, creating a persistent distraction that breaks writers' focus and wastes ideas.
  2. The AI features are poorly integrated: suggestions appear as pop-ups you can’t easily compare, get pasted into docs messily (even breaking formatting), and the experience has become more intrusive instead of better.
  3. A new editor called Owl Editor aims to fix this by letting you write without distractions, run a review that inserts AI feedback as track-changes you can accept or reject, and gather multiple reviewer perspectives to catch factual and reasoning errors.

One list to rule them all

The Engineering Manager • 23 implied HN points • 13 Feb 26
đź’Ľ Business Product
  1. A single, stack-ranked list of priorities forces real focus and makes trade-offs visible, so you stop pretending everything is equally important.
  2. Multiple roadmaps and competing P0s create silos, spread engineers thin, and cause decision fatigue, which leaves work perpetually unfinished.
  3. Make a list of every initiative, force a strict one-to-n ranking with no ties, and use that list to guide staffing and the hard conversations about what to stop.

AI Trends for 2026

Artificial Ignorance • 100 implied HN points • 17 Dec 25
đź•ą Technology Product
  1. Agents and harnesses are now the bottleneck, not just bigger models — layering planning, tools, state, and workflows on strong models is what’s unlocking reliable multi-step behavior in real products.
  2. The core LLM primitives (tool use, search, code sandboxes, file editing, memory, personas) have mostly settled, and the next big win is standardizing interfaces and conventions so developers can wire them together consistently.
  3. Interactions are moving beyond turn-based chat toward always-on, real-time collaboration where humans and AI co-edit and co-operate, and better UX plus streaming/agent orchestration will make that feel natural.

AI is everyone's favorite excuse to raise software prices

Enterprise AI Trends • 84 implied HN points • 17 Dec 25
đź’Ľ Business Product
  1. AI is making software more expensive right now. Many SaaS vendors raised prices in 2024–25 and are likely to keep raising them through 2026–27.
  2. Companies are bundling AI features into existing plans and hiking fees, effectively converting subscription revenue into “AI” revenue and limiting opt-outs.
  3. Structural forces beyond direct product value — like customers tolerating higher prices for high-value AI improvements and halo effects from better foundational models — are giving vendors sustained pricing power and a temporary “AI windfall.”

Uber’s 2025 Reorg: Platform Strategy Meets Conway’s Law

Gad’s Newsletter • 70 implied HN points • 29 Dec 25
đź’Ľ Business Product
  1. Uber put Mobility, Delivery, and Autonomous units under one COO to build a single platform that shares data and cross-sells services, aiming to get customers to use both apps more often.
  2. The org change follows Conway’s Law: by redesigning reporting lines they’re steering the software toward shared identity, pooled supply, and unified data so cross-platform features like Uber One and contextual offers can work.
  3. Centralizing integration can speed cooperation but risks a slow monolith and lost local excellence, so Uber needs a strong shared platform with clear delegation and should watch cross-platform adoption, Uber One penetration, and contextual attach rates.