Tag: zero to one B2B marketing

  • Crafting Beloved Tech Brands: My Moonshot Marketing Playbook for the Post-LLM Era

    I spend a lot of my time asking a deceptively simple question: what does excellent marketing actually look like in 2026? From the vantage point of product leadership, the answer isn’t a spreadsheet or a channel plan—it’s a feeling. Beloved tech brands earn the benefit of the doubt, create gravity around their roadmap, and make customers proud to belong. That kind of momentum is not an accident; it’s a system.

    Here’s the hard truth I’ve learned building and scaling products: giving teams different goals creates dysfunction. When brand, demand gen, product marketing, and comms run on fragmented OKRs, you manufacture internal headwinds. “Marketing is one engine – not separate pieces.” One strategy, one narrative, one set of outcomes—expressed through different craft disciplines and time horizons.

    That unity of purpose clarifies executive roles, too. The real difference between an SVP and a CMO is scope and narrative ownership. A great CMO architects the whole system—portfolio allocation, brand architecture, integrated go-to-market strategy, and the bar for creative taste—while refusing to get dragged into decisions they should never be making (for example, approving every headline or micromanaging channel tactics). Leaders should decide the outcomes, standards, and constraints; teams should control the craft.

    On portfolio design, I run marketing like a portfolio of moonshots. You need a healthy mix: proven programs that compound, emergent bets that learn fast, and a small set of true moonshots that can change the slope of the curve. The point isn’t bravado; it’s risk-balanced exploration. If everything ships safely, you’re under-investing in differentiation. If everything is a swing for the fences, you’re not building a repeatable growth engine.

    This is where taste becomes a strategic advantage. “Ubiquity is the opposite of cool.” If you want to be beloved, you cannot treat every channel, audience, and moment as equal. Early on, selective distribution, distinctive creative codes, and tight community loops create status and meaning. Later, you scale without sanding off the edges that made the product special.

    Why do a few companies build a flywheel of momentum while others stall? They align story, product, and distribution. The product earns trust, the narrative creates aspiration, and the go-to-market strategy ensures the right customers experience both at the right time. Then perception cycles kick in—the Silicon Valley clock turns—and irrational optimism or skepticism can amplify signals. The antidote is compounding proof: consistent product shipping, community advocacy, and creative that makes people care.

    Scaling taste across an organization is teachable. I codify brand principles, narrative guardrails, and examples of “right” versus “almost right.” I replace abstract feedback with decision rubrics—what we keep, kill, or revise and why. I run recurring creative reviews with a small cross-functional council, so judgment compounds. Taste can’t be fully automated, but it can be operationalized: shared references, a story bible, and a high bar for craft that’s explicit, not mystical.

    In a post-LLM world, the fundamentals haven’t changed—but the frontier has. Generative tools supercharge iteration and research, yet the artistry never really left. You still need a point of view, a tension worth resolving, and a value proposition that’s felt, not just stated. Can taste be encoded in software? Parts of it—pattern libraries, style constraints, data-driven feedback—absolutely. But the spark that makes work unforgettable remains human: judgment, risk tolerance, and the courage to ship something that might not fit the playbook.

    That’s why telling an optimistic, yet realistic story about AI matters. Over-automation drains humanity; under-automation wastes potential. The best work pairs AI Strategy with craft leadership: LLMs for rapid exploration, humans for narrative decisions and ethical judgment. Your message should show how AI expands customer agency, not just efficiency.

    The brand-versus-growth debate is a false choice. The right story accelerates pipeline, and the right demand programs reinforce the brand. Look at Apple’s discipline around product truth and design codes, or Google Chrome’s “The Web Is What You Make of It (Dear Sophie)” for proof that emotion and utility can co-exist. Notion, Pinterest, Square, HubSpot, and Harley-Davidson show how community, identity, and product-led growth interlock when the company knows exactly what it stands for.

    When it comes to launches, I’ve learned that announcement videos full of humans, lack humanity. Overproduced gloss often dilutes the truth customers seek: what problem does this solve, how quickly can I feel the value, and why does it matter now? Real users, real context, and a crisp arc from problem to promise will outperform most theatrics.

    Practically, I architect my week to protect taste and outcomes. Early-week for strategy, portfolio reviews, and cross-functional alignment; mid-week for deep creative and product marketing work; late-week for decision clears and postmortems. I time-box “disruptive energy”—space to chase non-obvious ideas—and I guard it like any critical meeting. Without protected cycles for exploration, the urgent will always suffocate the important.

    If there’s a single takeaway: playbooks are obsolete, but the fundamentals are not. The channels change; the psychology doesn’t. Run one engine. Allocate a true portfolio. Scale taste with rigor. In the AI era, make people care. That’s how beloved tech brands are built—and how they endure.


    Book a consult png image
  • Stop Drowning in Tasks: How AI Marketing Agents Restore Focus and Maximize Impact

    Stop Drowning in Tasks: How AI Marketing Agents Restore Focus and Maximize Impact

    Every week I meet marketers who are working harder than ever—more campaigns, more content, more dashboards—yet seeing less movement on metrics that matter. The surge of AI tooling has amplified activity, not necessarily impact. That’s the focus problem: we confuse motion with momentum, and our backlogs look great while our outcomes stall.

    Learn how AI agents for marketing can help you prioritize impact so you can do important work, instead of just more work.

    In my role leading product and growth teams, I’ve learned that AI only compounds value when it is pointed squarely at outcomes. If we don’t define what “good” looks like, agentic AI will simply scale busywork. The antidote is a disciplined operating model that connects strategy to execution and instruments agents with clear success criteria.

    First, anchor your program with outcomes vs output OKRs. Choose one or two measurable business outcomes—such as qualified pipeline, conversion rate, or activation—and make everything else subordinate. This provides the compass agents need to make effective trade-offs when speed and volume tempt you to do “one more thing.”

    Second, map a driver tree from the target outcome down to the controllable levers: audience segments, offers, channels, messaging, and experience friction. This traceability shows where agents can move the needle fastest—whether that’s accelerating research, sharpening positioning, or eliminating handoffs that slow experimentation.

    Third, design a small, agentic AI workforce aligned to those levers. For example: a Research Agent that synthesizes market insights and past performance; a Copy Agent that generates on-brief, on-brand variants; a Distribution Agent that adapts content to each channel and schedules posts; and an Analytics Agent that runs A/B tests, summarizes results, and flags anomalies. Keep human oversight where judgment matters most—strategy, brand voice, and high-stakes decisions.

    Fourth, instrument rigor from day one with Agent Analytics and eval-driven development. Define offline evals for brand consistency, factuality, safety, and response time; pair them with online experiments that quantify lift on your target outcomes. Set a minimum detectable effect (MDE) so you stop shipping changes that cannot plausibly move the metric.

    Fifth, operationalize your AI workflows. Standardize prompts, inputs, and handoffs; templatize briefs and acceptance criteria; and keep a change log so improvements compound rather than reset. Use short, frequent feedback loops to prune low-impact work and double down on what demonstrably advances your objectives.

    I’ve seen teams reclaim focus and momentum when they treat agents as teammates, not toys. The magic isn’t in producing more assets—it’s in consistently choosing the next best action in service of a clear outcome. When you combine outcome clarity, a driver tree, targeted agents, and tight evals, AI becomes a force multiplier for marketing impact.

    If you’re feeling overwhelmed by AI’s possibilities, start small: commit to one outcome, one driver you believe is material, and one agent designed for that job. Prove lift, codify the workflow, then scale. Velocity is only valuable when it’s pointed in the right direction.


    Inspired by this post on Amplitude – Best Practices.


    Book a consult png image
  • From Spark to Scale: My Playbook for Generating, Validating, and Executing Startup Ideas

    From Spark to Scale: My Playbook for Generating, Validating, and Executing Startup Ideas

    Building a startup is equal parts craft and discipline. In my product leadership work, I’ve honed a repeatable approach for going from raw idea to real traction—and I often cross-check that playbook against the battle-tested experience of leaders I respect. I frequently reference insights from Gagan Biyani, co-founder and CEO of Maven, a company that empowers the world’s experts to offer cohort-based courses directly to their audience.

    After being early at 3 startups that achieved over $1 million in run-rate in their first six months of going live, Gagan has learned some valuable lessons and seen a wide range of outcomes — from Udemy going on to IPO in 2021, to Sprig shutting down in 2017.

    When I’m generating startup ideas, I start with open-ended exploration and a rigorous “problem inventory.” I look for founder–market fit, persistent pain points, and market signals that indicate urgency and willingness-to-pay. I also study competition to spot under-served segments or a wedge where a differentiated product discovery approach can win. The most common mistakes I see aspiring founders make are solution-first thinking, overvaluing total addressable market over real problems, and staying in stealth too long instead of testing in the wild.

    Validation is where discipline pays off. I rely on minimum viable tests to rapidly de-risk assumptions and avoid false positives. My process mirrors the spirit of his “Minimum Viable Testing Process.” I define falsifiable hypotheses, run one-channel traction experiments, test willingness-to-pay early, and favor concierge or manual workflows before writing heavy code. These tight, timeboxed sprints force clarity on product-market fit signals while keeping burn low and learning velocity high.

    Once the signals look promising, execution becomes a game of thoughtful sequencing. I explore multiple business models in parallel (subscriptions, usage-based, hybrid) while keeping the core value proposition crisp. Early go-to-market is founder-led GTM by design; I talk to customers daily, tune messaging, and iterate on onboarding until activation and retention curves stabilize. On the product side, I prioritize outcomes over output, set clear guardrails for roadmapping and sprint planning, and instrument the product to learn from every user interaction.

    Co-founder selection and operating cadence matter as much as the idea. I look for complementary skills, shared values, and a bias for transparent conflict resolution. Before committing, we pressure-test collaboration with small, high-stakes projects, align on decision-making frameworks, and codify roles, equity, and vesting. As the company grows, I revisit these agreements to keep pace with evolving responsibilities and minimize execution drag.

    If you’re eager to hear even more on finding startup ideas from Gagan, he’s teaming up with The Hustle’s Sam Parr to run an Ideation Bootcamp on the Maven platform — learn more and sign up here by May 2nd if you’re interested.

    My takeaway: winning startups don’t depend on a eureka moment. They emerge from a disciplined loop—curious exploration, fast and falsifiable validation, and focused execution. If you apply these principles with persistence and empathy for the customer, you’ll increase your odds of finding product-market fit faster—and building something that endures.


    Inspired by this post on First Round.


    Book a consult png image
  • From $2M to $100M ARR: Inside fal’s Explosive Pivot and the Future of Generative Media

    From $2M to $100M ARR: Inside fal’s Explosive Pivot and the Future of Generative Media

    Generative media is no longer a curiosity on the edges of product roadmaps—it’s fast becoming a core capability. Watching one company sprint from uncertainty to undeniable traction reminded me how much a decisive pivot, a developer-first brand, and ruthless focus can bend a growth curve. This is a story about finding product-market fit in real time, scaling with intention, and staying lean while the category accelerates beneath your feet.

    Gorkem Yurtseven is the co-founder and CEO of fal, the generative media platform powering the next wave of image, video, and audio applications. In less than two years, fal has scaled from $2M to over $100M in ARR, serving over 2 million developers and more than 300 enterprises, including Adobe, Canva, and Shopify. In this conversation, Gorkem shares the inside story of fal’s pivot into explosive growth, the technical and cultural philosophies driving its success, and his predictions for the future of AI-generated media.

    What stood out to me first was the clarity of the pivot: “How fal pivoted from data infrastructure to generative inference.” The hardest decisions often feel like abandonment—of code, roadmap, and even identity—but the right pivot reframes everything around a higher-signal customer need. That decision, described as “The hardest decision that saved the company,” unlocked a new trajectory and set a crisp north star for the team.

    Equally important was the market intuition. As they put it, “Why ‘generative media’ is a greenfield new market.” Greenfield means pattern-breaking strategy: prioritize outcomes over parity, embrace new workflows rather than retrofit old ones, and measure value in quality, latency, and unit economics—not just features. In my experience, this is where product teams win or lose: you either build the new default or get trapped perfecting the old one.

    fal’s “explosive year” wasn’t luck; it was systems thinking applied to a developer platform. The team stayed small—”lean <50-person team” and “Staying nimble as a 45-person company”—and built a brand that feels genuinely for builders: “Building a brand that resonates with developers.” That shows up in everything from docs and SDKs to the cultural quirks that scale signal, like “Why fal has 500 Slack channels.” Velocity and clarity compound when communication is designed for ownership.

    Early traction came from sharp use cases and fast feedback loops. I loved the transition arc from “The early adopters of the first fal product” to “The transition from toy to tool.” In a new category, the fastest path to durable usage is making something delightful and then relentlessly hardening it for production: uptime targets, deterministic APIs, transparent pricing, and repeatable performance. That’s how you move from demos to dependable workflows.

    The timing call is bold and specific: “Why 2025 is the year of AI-generated video” and “Predicting AI-generated film in 2027.” If you build in gen AI, this matters. Video will force teams to optimize for cost per second, temporal coherence, and developer ergonomics across long-running jobs. The winners will combine model choice (OpenAI, Anthropic, Google DeepMind, Stability AI; “Stable Diffusion XL (SDXL)”, “Sora”, “DALL-E”, “LLaMA”) with world-class inference, smart caching, and autoscaling that feels invisible to the developer.

    On the go-to-market side, I see a masterclass in founder-led GTM and developer evangelism. “Competing in a fast-moving, fragmented market” requires sharp messaging and distinctive ideas. The story behind “GPU Rich / GPU Poor” is a perfect example: a memorable narrative that encodes a real infrastructure advantage. Pair that with “fal’s greatest optimization wins” and you get a brand promise rooted in measurable performance, not just clever copy.

    Culture and team design are the force multipliers. “How to build a world-class team” and “fal’s unique hiring philosophy” emphasize high-slope talent, ownership, and speed over headcount. The result is a product org that ships, learns, and iterates without bureaucratic drag. For technical founders, “Learning sales as a technical founder” is a reminder that the best sales motion often emerges from the same instincts as great product discovery: ask better questions, observe real workflows, and sell through outcomes.

    Here’s how I translate these lessons into a practical playbook for product leaders working in gen ai and developer platforms: double down on developer experience (time-to-first-output, clear pricing, robust SDKs), make latency and reliability your product features, sequence the roadmap from delightful demos to dependable production tools, and stay lean enough to pivot as models and use cases evolve. Above all, treat “Why generative media is a greenfield market” as a call to invent the defaults others will copy.

    Looking ahead, the path is clear: as AI-generated video normalizes in 2025 and professional-grade content follows by 2027, the products that win will combine inference excellence with a brand developers trust. If you’re building in this space, now is the moment to ship fast, optimize relentlessly, and meet creators and developers where they already work.


    Book a consult png image
  • Start With the Story: Leadership Lessons from Drift’s David Cancel I Use to Elevate Teams

    Start With the Story: Leadership Lessons from Drift’s David Cancel I Use to Elevate Teams

    “Start with the story” isn’t a slogan for me—it’s a daily operating principle. As I guide product strategy and align go-to-market with product discovery, I’ve seen how a clear narrative unlocks focus, speeds decisions, and lifts execution. That’s why David Cancel’s perspective resonates so strongly: when you build from the story, you build momentum.

    David has been a CEO and founder of multiple different companies throughout his career. He’s also been a software engineer, a serial CTO, and the Chief Product Officer at Hubspot, giving him a unique lens into company building and leadership at different levels. That combination of product, engineering, and executive leadership creates the kind of pattern recognition I rely on when coaching PMs and shaping product management leadership practices across teams.

    In my experience, the fastest way to align product, marketing, and sales is to anchor everyone in the same narrative. David’s framing around storytelling at Drift, a conversational marketing and sales platform, crystallizes this. From screenplay writing inspiration, to how storytelling training is part of their onboarding, David shares how they teach storytelling and drive narrative internally at Drift. I’ve adopted a similar approach—story-first onboarding for product creators and PMs, so every spec, roadmap, and customer interaction reinforces the same promise and positioning.

    The leadership muscle here isn’t just crafting a compelling story—it’s keeping altitude discipline. He also shares tactical advice for engaging with exec teams and getting better at zooming in and out as CEO, as well as some really tactical frameworks, including Charlie Munger’s practice of inversion, the weekly rituals Drift relies on, and how they use asynchronous video communication. I use these same moves: inversion to pressure-test roadmaps and risks, weekly rituals to reinforce priorities, and async video to scale clear, human communication without meeting sprawl.

    On my teams, inversion clarifies trade-offs: before we pursue a bet, we ask, “If this fails, what will have been the likely causes?” That simple prompt improves product discovery, sharpens founder-led GTM motions, and accelerates product-market fit lessons. When we meet, we start with a crisp narrative—who the customer is, what their struggle looks like, and why our solution is the inevitable next step. Outcomes replace output, and teams rally around impact.

    I’ve also found that storytelling is a coachable skill, not an innate talent. We run lightweight workshops where PMs deconstruct great narratives (including screenplay structures) and rebuild their own. The effect is immediate: clearer problem statements, tighter product roadmapping and sprint planning, and better executive readouts that move decisions forward instead of sideways.

    If you want to dive deeper into David’s perspective, you’ll find practical resources worth bookmarking. You can follow David on Twitter at @dcancel. He also pens a popular newsletter called “The One Thing,” and hosts a great podcast called “Seeking Wisdom.” For reference, the books he mentioned in the episode include Jon Kabat-Zinn’s work on mindful meditation, and “The Passion Paradox” by Brad Stulberg.

    To learn more about how Drift approaches storytelling, check out this article David wrote for Inc:

    https://www.inc.com/david-cancel/five-storytelling-tips-to-better-communicate-your-brand-message.html

    To learn more about Charlie Munger’s concept of inversion that David mentioned, check out this Farnam Street post: https://fs.blog/2013/10/inversion/

    If you’re leading teams, think of story as a system: a shared language for product, marketing, and sales; a filter for priorities; and a mechanism for speed. It’s a must-listen for current founders and CEOs, and anyone looking to level up their leadership skills. When we start with the story, we don’t just communicate better—we build better.


    Inspired by this post on First Round.


    Book a consult png image
  • Win-Win Partnerships: Stripe & Notion Lessons to Negotiate Smarter and Scale Faster

    Win-Win Partnerships: Stripe & Notion Lessons to Negotiate Smarter and Scale Faster

    I’m always searching for practical, battle-tested strategies to build platform ecosystems and business development motions that actually move the needle. Cristina Cordova, Notion’s Head of Platform & Partnerships, brings exactly that kind of rigor. Previously, she was the 28th employee and the first partnerships hire at Stripe, where she cultivated partnerships with companies like Shopify, Squarespace and Apple, built out the BD org, and led their new Corporate Card effort.

    After a decade in partnerships, Cristina has bagged big deals, honed her negotiation skills, built out teams — and made plenty of mistakes she hopes others can learn from. Her candor resonates with the realities I see leading product and platform work — the high-leverage wins, the inevitable trade-offs, and the importance of structured decision-making.

    In today’s conversation, Cristina pulls from across her career to share the inside scoop on deals that had an unexpected outsized impact — as well as the ones that went sideways. Hearing how she navigated both reaffirmed a core principle I hold: partner success starts with a clear mutual value narrative and disciplined execution across product, GTM, and ops.

    She also shares her playbook for being a startup’s first partnership hire, including the three critical areas to focus on first, and the common traps to avoid. It’s also full of actionable tactics on everything from dealing with partners trying to push you around, to how to hire for partnerships roles and structure the org chart.

    What stood out to me is how transferable these lessons are to product management leadership. The best partnership strategies are product strategies: prioritizing integrations that deepen product-market fit, sequencing launches to maximize learning, and aligning incentives so partners champion adoption, not just sign paper.

    On negotiation, I’ve seen the same patterns Cristina highlights. Win-win deals come from clarity on your non-negotiables, crisp success metrics, and a shared plan for activation — not oversized concessions. I coach teams to pre-wire decisions, define BATNA early, and document a mutual success plan that ties product roadmapping and sprint planning directly to GTM milestones.

    Hiring and org design matter just as much as the deals themselves. Great partnership talent blends product discovery instincts with zero to one B2B marketing chops and the discipline of outcomes vs output OKRs. Structure the BD and platform teams so ownership is unambiguous: who drives integration quality, who owns co-marketing, and who runs partner QBRs vs OKRs alignment across the business.

    Whether you’re building your first platform integration, leveling up a partner-led GTM motion, or refining how product and BD collaborate, the tactics here can accelerate your path. The stories of how Stripe and Notion scaled offer a rare, practical lens you can apply immediately — from selecting the right lighthouse partners to operationalizing the learnings across your roadmap.


    Inspired by this post on First Round.


    Book a consult png image
  • Inside Tido Carriero’s Playbook: Build World-Class Engineering Orgs and Nail Product/Market Fit

    Inside Tido Carriero’s Playbook: Build World-Class Engineering Orgs and Nail Product/Market Fit

    I’m drawn to leaders who’ve built both high-performing engineering organizations and durable products. Tido Carriero, the Chief Product Officer at Segment, a customer data platform which was recently acquired by Twilio, exemplifies that trajectory. Before that, he built out the engineering teams that worked on the core product and the initial business product at Dropbox. Tido started out his career in 2008 as an early member of the Facebook ads engineering team, and went on to become an eng manager on the Pages team — a pivotal IC to leadership transition that resonates with many of us in product and engineering.

    What stands out in his journey are pragmatic lessons on building engineering orgs and launching new product lines at several top tech companies. His reflections on the pros and cons of single threaded leadership and the black box analogy for assessing a team’s performance offer concrete ways to interrogate how work actually gets done. In my own practice, I pair these lenses with outcomes vs output OKRs, tight product roadmapping and sprint planning, and a clean operating cadence that links QBRs vs OKRs. Together, these mechanisms create clarity in org design, planning, and execution — and make performance visible without micromanaging.

    For new engineering managers and new managers-of-managers, I appreciated the practical “gems of advice.” That IC to manager transition is rarely linear; success hinges on shifting from personal velocity to organizational throughput. I coach first-time managers to build credible operating systems early: explicit decision rights, transparent prioritization, and lightweight feedback loops. One simple ritual I rely on is a weekly narrative update that forces crisp, outcome-focused thinking — a habit that complements any try do consider framework a team may use.

    We also explored the path to product/market fit, especially for multi-product strategies — an area where many B2B teams struggle. Tido shares his advice for going from zero to one in a new product, including the simple milestone his teams have to hit before he’ll greenlight a new project, why he prefers iterative approaches over “big bang launches,” and his thoughts on why Dropbox struggled here. My own playbook mirrors this: invest in fast product discovery, define a clear gate tied to must-have user behavior, and resist vanity launches until repeatable pull exists. Small, well-instrumented bets compound; “big bang launches” rarely do.

    If you want to go deeper on finding product/market fit in the context of multi-product strategies, Tido shares more of his thinking here: https://segment.com/blog/finding-product-market-fit-again/. It’s a useful companion for leaders calibrating zero-to-one efforts alongside an at-scale core business.

    The through line across these lessons is disciplined simplicity. Whether you’re architecting engineering orgs, coaching the IC to manager transition, or charting zero to one in a new product, choose mechanisms that surface reality quickly, reward learning, and keep teams focused on outcomes. That’s how world-class organizations build, ship, and iterate their way to enduring product/market fit.


    Inspired by this post on First Round.


    Book a consult png image
  • From Instacart to Anomalo: Elliot Shmukler’s Zero-to-One Playbook for Product Leaders

    From Instacart to Anomalo: Elliot Shmukler’s Zero-to-One Playbook for Product Leaders

    As a product leader who obsesses over data quality and founder-led GTM, I’m energized by Elliot Shmukler’s trajectory and the problem he’s tackling at Anomalo — which is a platform that validates and documents all of your data. After leading product and growth teams at Instacart, Wealthfront, LinkedIn, and eBay, Elliot stepped into the founder/CEO role to drive a true zero to one build. That arc offers a grounded blueprint for product management leadership, product-market fit, and disciplined execution.

    In this conversation, Elliot’s most recent stop stands out: he was Instacart’s Chief Growth Officer, driving fast and profitable growth and geographic expansion. Before that, he served at Wealthfront as the VP of Product and Growth and as a product leader at LinkedIn and eBay. That context matters because it informs how he now builds Anomalo with an eye for focused experimentation, clear value propositions, and operational excellence.

    From my vantage point, the jump from executive to CEO resets the scoreboard. Elliot’s reflections on the zero-to-one phase mirror what I see in early-stage company-building: the need to aggressively prioritize time, protect founder focus, and qualify demand. He underscores a simple but costly trap I’ve witnessed too — wasting cycles on prospects who aren’t actually buyers. My playbook: define disqualification criteria early, insist on access to the economic buyer, require clear problem urgency, and time-box proofs of concept so founder energy fuels real pipeline, not vanity interest. This is classic founder-led GTM discipline and pays compounding dividends.

    We also dig into how he picks extraordinary companies to work for. Elliot leans on sharp questions as a candidate and borrows decision-making frameworks from his poker playing. I resonate with that expected-value mindset: when stakes are uncertain, structure decisions around odds, outs, and downside protection. In product discovery, I translate that to staged bets, explicit kill criteria, and A/B tests that quantify lift before we scale. It’s a rigorous way to avoid narrative fallacy and to stay outcomes over output in OKRs.

    Another thread that hits home: lessons from the best CEOs he’s worked with. The standout habits are crisp, frequent communication, transparent decision journals, and mechanisms that keep office politics at bay so the best ideas surface. In my teams, we pair written narratives with open metrics dashboards and “disagree-and-commit” rituals to reduce ambiguity and speed alignment. The result is faster feedback loops and clearer ownership across product roadmapping and sprint planning.

    If you’re a founder in customer discovery, an executive eyeing your own startup, or an early-career builder trying to spot the next unicorn, there’s practical guidance here. You’ll find tactics for zero to one B2B marketing, qualifying enterprise demand, navigating product-market fit, and sharpening product management leadership skills you can apply today.

    You can follow Elliot on Twitter at @eshmu.

    To learn more about how Elliot uses A/B testing as a management framework, check out this article on First Round Review: https://review.firstround.com/how-a-b-testing-at-linkedin-wealthfront-and-ebay-made-me-a-better-manager

    And check out “The Goal,” which Elliot cited as the most influential management book he’s ever read: https://www.amazon.com/Goal-Process-Ongoing-Improvement/dp/0884271951


    Inspired by this post on First Round.


    Book a consult png image
  • From Zero Customers to IPO: Eric Berg’s Hard-Won Playbook for the Messy Middle

    From Zero Customers to IPO: Eric Berg’s Hard-Won Playbook for the Messy Middle

    I’ve been revisiting the hard-won lessons behind durable product companies, and Eric Berg’s journey is a masterclass. Eric Berg is the CEO of Fauna, which is an adaptive operational database platform. In joining Fauna as its CEO in the summer of 2020, he brought a wealth of experience as a product leader. Most recently, he was the Chief Product Officer at Okta, scaling the company from 10 employees and zero customers to its eventual IPO in 2017. He started his career in product at Intel, working under the legendary Andy Grove, as well as a five-year stint as a product leader at Microsoft.

    From a product management leadership lens, the earliest chapters at Okta are a blueprint for zero to one B2B marketing and founder-led GTM. I break down his early go-to-market lessons and the keys to honing in on an ICP to get Okta off the ground, highlighting how tight product discovery, crisp problem statements, and ruthless prioritization turn ambiguity into product-market fit.

    What stands out is the often-maligned “messy middle” — the stretch when traction exists but entropy expands. Eric’s moves on “moving upmarket” and evolving a “pricing and packaging model” are reminders that, when done well, takes a company to new heights. For SaaS pricing, I lean on value metrics tied to critical jobs-to-be-done, clear guardrails for discounting, and a win–loss feedback loop owned jointly by product and sales.

    We then switch gears to team building and company building. The cultural patterns that stick with me: hire “folks up and down the org chart with the right ego to talent ratio” and operationalize a “disagree and commit” value so it’s not just a long-forgotten team motto. Practically, that means defining decision types (one-way vs. two-way doors), naming a DRI and approver for every call, time-boxing debate, and documenting the rationale so execution never stalls.

    On execution mechanics, I’ve found that outcomes vs output OKRs paired with QBRs vs OKRs alignment creates a healthy cadence from strategy to delivery. When you layer in forward deployed engineers and structured customer advisory boards, feedback cycles compress without sacrificing focus — a powerful pattern in both product roadmapping and sprint planning.

    Finally, the perspective shifts “as he approaches one year of sitting in the CEO seat” underscore the difference between building products and building a business. Capital strategy, talent density, and narrative become first-class product surfaces. As a product creator, I translate this into designing org APIs, setting explicit burn-to-learn budgets, and treating pricing, packaging, and GTM as core parts of the product.

    If you’re navigating product-market fit lessons, wrestling with “moving upmarket,” or recalibrating SaaS pricing, this playbook maps the trade-offs from 0 customers through the “messy middle” and beyond. It’s a grounded field guide for product folks and operators who want to scale with clarity, strengthen culture, and accelerate learning without losing the thread.


    Inspired by this post on First Round.


    Book a consult png image
  • Ask Why It Won’t Work: Hard-Won 0→1 Lessons, Pre-Mortems, and Founder-Led GTM from Persona

    Ask Why It Won’t Work: Hard-Won 0→1 Lessons, Pre-Mortems, and Founder-Led GTM from Persona

    I recently sat down with Rick Song, the co-founder and CEO of Persona, a platform that enables companies to create the ideal identity verification experience for their customers. Before founding Persona in 2018, Rick was an engineer at Square for 5 years, and an early team member at Square Capital. As someone who leads product teams and thinks deeply about product-market fit and go-to-market, I was eager to unpack the 0 to 1 thinking behind Persona’s trajectory.

    Rick is at an exciting inflection point in his journey of building from zero to one — just last week, Persona shared that they’ve raised a $50 million Series B round. The company plans to double the team this year to keep up with revenue that’s surged more than 10x and a customer base that’s grown to include big logos like Square, Postmates, and Gusto. For anyone operating in B2B SaaS, that’s the kind of signal you can’t ignore.

    In our conversation, one theme stood out: Rick is somewhat obsessed with the idea of pre-mortems, or figuring out why things might not work out. From all the ways a candidate might fail, to why a customer won’t want a product, to how a commonly-used framework might not be a good fit, he brings this mindset to every aspect of running Persona. I share that instinct — when we anchor on “why it won’t work” early, we surface edge cases, stress-test assumptions, and prioritize outcomes over output. It’s a product discovery discipline that keeps teams honest and accelerates product-market fit lessons.

    Rick also shared counterintuitive practices that resonated with my own founder-led GTM experiences. His engineers sell and cold-email prospects, and he doesn’t try to convince candidates that Persona is a company that will change the world. That may sound unconventional, but it’s exactly the clarity zero-to-one companies need: tight customer feedback loops, direct exposure to objections, and authentic hiring that screens for fit over hype. In my experience, these choices reduce handoffs, sharpen messaging, and create a culture that learns faster than the market moves.

    There’s a broader leadership lesson here for product management: treat pre-mortems as a muscle, not a meeting. I apply this to hiring scorecards, roadmap bets, and go-to-market plays — explicitly listing failure modes, customer objections, and “anti-personas” who won’t buy. When we teach engineers to engage customers directly, we’re effectively building forward deployed engineers who carry context from discovery to delivery to launch, closing the feedback loop and improving zero to one B2B marketing execution.

    For founders, engineering leaders, and hiring managers, the takeaways are practical: start with the “won’t,” design for objections, and let builders meet buyers early. Pair this with a clear definition of success metrics and a bias for candid, frequent iteration. The result is a stronger compass for product management leadership and a far more resilient go-to-market motion.

    You can follow Rick on Twitter at @rickcsong and learn more about Persona at https://withpersona.com/


    Inspired by this post on First Round.


    Book a consult png image
  • From Slack’s ‘Where Work Happens’ to CEO: Inside the Product Strategy That Scales

    From Slack’s ‘Where Work Happens’ to CEO: Inside the Product Strategy That Scales

    I’m drawn to leaders who bridge marketing excellence with rigorous product management. Kelly Watkins, CEO of Abstract, exemplifies this. Abstract is a platform for structure and transparency in the design process. What makes her journey distinctive is the transition from a marketing background into the CEO seat — a path that demands both narrative mastery and operational discipline.

    Reflecting on her first year as CEO, what stood out to me was her alternative to yearly planning, borrowing from famed military strategist John Boyd. I’ve wrestled with annual planning cycles myself, and this approach resonates with how I guide product roadmapping and sprint planning — shorter feedback loops, tighter decision cycles, and a bias for learning over lengthy forecasts. It’s a pragmatic way to keep teams focused on the right problems at the right time.

    Her walkthrough of Abstract’s most recent product launch crystallized a leadership stance I value deeply: constantly optimize for trade-offs, rather than chasing clear-cut right and wrong. In my experience, framing decisions as explicit trade-offs elevates cross-functional collaboration, aligns product discovery with realistic constraints, and encourages outcomes over output. It’s the difference between shipping features and shipping meaningful progress.

    Drawing on a storied marketing career at Slack, Github, and Bugsnag, she underscores a jobs-to-be-done approach for crafting a product story when there’s loads of competition. I’ve seen JTBD unlock clarity when teams get lost in feature parity — it centers the product on the customer’s progress, not our roadmap. When the market is noisy, a crisp jobs-based narrative becomes a durable strategic asset.

    The behind-the-scenes look at developing Slack’s “where work happens” tagline is a powerful reminder that great positioning anchors to the job, not the jargon. Moving from a passionate early adopter base to a ubiquitous product requires more than demand gen — it requires crossing the chasm with a value story that scales. I’ve found that the leap from early signals to broad adoption hinges on consistent messaging, intentional onboarding, and instrumentation that proves product-market fit beyond the initial cohort.

    This conversation isn’t just a must-listen for marketing folks; it’s a primer for any leader seeking to collaborate more effectively across the org. The art and science of marketing become a force multiplier when paired with disciplined product management leadership. For teams navigating zero to one B2B marketing, these lessons translate directly into sharper execution and clearer decision-making.

    My takeaways are straightforward: plan in adaptable cycles, not rigid annual cadences; embrace trade-offs as a core leadership tool; use the jobs-to-be-done framework to tell a product story that cuts through competition; ground your tagline in the customer’s real job; and design your path from early adopters to the mainstream with intention. Applied together, these principles turn strategy into momentum and momentum into enduring growth.


    Inspired by this post on First Round.


    Book a consult png image
  • My Battle-Tested Comms Playbook: Kill Bad Stories, Create Categories, Lead With Clarity

    My Battle-Tested Comms Playbook: Kill Bad Stories, Create Categories, Lead With Clarity

    I recently sat down with Shannon Brayton, a Silicon Valley veteran with more than two decades of experience shaping corporate narratives and leading teams at companies like LinkedIn, OpenTable, eBay, Yahoo!, and Intuit. She recently joined Bessemer as the venture capital firm’s first-ever CMO. As I reflected on our discussion, I kept coming back to how closely great communications strategy mirrors great product strategy: clarity of narrative, ruthless prioritization, and the courage to reshape the market when the existing frame doesn’t serve customers.

    What resonated most with me as a product leader was Shannon’s philosophy that comms is a strategic lever — and one of the most underappreciated functions. We dug into the practical side of the craft, from killing stories and creating new categories to the frameworks she uses for building relationships with reporters. The parallels to product management leadership are striking: define the problem space, choose the story you will not tell, and architect the environment where your best story can win.

    On story killing, I’ve learned to treat narrative debt like technical debt. If a storyline no longer advances the strategy, I stop feeding it — even when it’s tempting to chase short-term attention. Shannon’s lens sharpened my own: identify legacy narratives that siphon focus, set a clear “no-story list,” and redirect energy to the few messages that compound. This is as much about leadership as it is about PR — our teams take their cue from the narratives we choose to reinforce (or retire).

    Category creation is where comms and product strategy truly converge. When we define a category, we define evaluation criteria for buyers, shape the problem statement, and set the language for the market. In my experience, this only works when it is anchored in real customer pain and a credible roadmap. Shannon’s approach aligns with zero to one B2B marketing: validate the need, name the space with precision, and build proof that makes the category feel inevitable.

    On media relationships, I subscribe to Shannon’s view that trust is a product you build over time. My framework is simple: be useful, be brief, be accurate. Offer real data, context, and accountable sources; say less and deliver more. The goal isn’t to “pitch” reporters — it’s to become a reliable operator who helps them tell truthful, timely stories. That reputational equity pays off when the stakes are high and nuance matters.

    We also covered leadership arcs and career selection. Shannon’s perspective on choosing companies — align with mission, quality of leadership, and the clarity of the strategic hill to climb — mirrors how I evaluate product bets. Her transition from head of comms to CMO reinforced a lesson I’ve felt in my own roles: the first 100 days are about listening with intent, writing down the strategy, and operationalizing quick wins that build momentum. I also appreciated the nod to lessons from mentors and bosses like Jeff Weiner — durable leadership principles travel well across functions.

    Here’s the reverse mentoring post Shannon mentioned on how she approached taking on the CMO role: https://www.linkedin.com/pulse/how-i-tackled-first-100-days-my-new-role-reverse-brayton/

    You can follow Shannon on Twitter at @sstubo.


    Inspired by this post on First Round.


    Book a consult png image