Ignite: Conversations on Startups, Venture Capital, Tech, Future, and Society

Ignite Insights

0,0 (0)
Investering
Varje dag

Thoughts on early stage investing, technology, society, and the future. insights.teamignite.ventures

−3 h

Ignite Product: Jeff Gothelf on Lean UX and Product Strategy in the Age of AI | Ep282

What happens when AI makes it easier than ever to build software—but not necessarily easier to build something people actually want? That is the tension at the center of our conversation with Jeff Gothelf, co-creator of the Lean UX movement, author of Lean UX, Sense and Respond, and Who Does What By How Much?, and co-founder of Sense & Respond Learning. Jeff has spent decades helping product teams move away from rigid waterfall processes, bloated deliverables, and executive-led guesswork. His work has shaped how modern startups and product organizations think about experimentation, customer evidence, design, OKRs, and outcomes. But in 2026, the product world is facing a new problem: AI can now generate designs, prototypes, copy, code, research summaries, and product ideas at incredible speed. That sounds like progress. Jeff’s warning is sharper: speed without judgment just gets you to mediocrity faster. From Failed Musician to Lean UX Pioneer Jeff’s career did not begin in software. It began in music. Before becoming one of the best-known voices in product design, he was trying to make it as a rock musician. He played piano, toured with bands on the East Coast, and gave the dream a real shot. When that did not work out, the early web was beginning to take off. Jeff taught himself HTML and basic web design, first building websites for himself and friends. In 1999, as he puts it, “if you could spell HTML, you could get a job.” That led him into web design, interaction design, UX, product leadership, and eventually Lean UX. His frustration came from a simple but painful realization: on a good day, only half of his design work ever got implemented. The rest was thrown away. Not because the work was bad, but because the process was broken. Teams would spend weeks or months designing software up front, based on assumptions, executive direction, and theoretical requirements. Then reality would hit. Customers did not behave as expected. Engineering constraints appeared. Priorities changed. The work was discarded. Lean UX emerged as Jeff’s response to that waste. Instead of treating design as a big upfront deliverable, Lean UX asks teams to use just enough design to move the conversation forward, get feedback, and decide whether to continue, change direction, or kill the idea. The goal is not to produce more artifacts. The goal is to learn faster. The Moment Jeff Realized Software Development Was Broken One of the most memorable stories from the episode comes from Jeff’s time at America Online. He described working under an executive who micromanaged a massive organization. Jeff had spent about a week working on a design and walked into the executive’s office with a printed version of the work. Before Jeff could even present it, the executive looked at the paper from across the room and said: “There’s nothing remotely close to anything I want to see on that sheet of paper.” For Jeff, that was a breaking point. It was not just a harsh comment. It represented the larger dysfunction of how software was being built: executive opinion above customer evidence, hierarchy above learning, and big upfront work before any real validation. That became one of the emotional roots of Lean UX. Jeff was not simply trying to make design more efficient. He was trying to make product work less stupid. Why AI Creates a New Race to Mediocrity A major theme of the conversation was how AI is changing product work. Jeff is not anti-AI. He sees the tools as powerful and exciting. Designers, product managers, and engineers can now create prototypes and explore ideas much faster than before. But he is skeptical of the idea that AI eliminates the need for product judgment. In his view, AI makes it easier for everyone to generate similar-looking, similar-sounding, similar-functioning work. That creates what he called a “race to mediocrity.” He compared the current AI moment to the era of Twitter Bootstrap. Bootstrap made it easy for anyone to build clean, usable websites. That was useful. But it also made everything look the same. AI risks doing the same thing at a much larger scale. When everyone prompts similar tools using similar language and accepts similar outputs, products start to converge. The market fills with generic interfaces, generic copy, generic workflows, and generic strategy. That is why Jeff believes the human role becomes more important, not less. The future advantage will come from taste, judgment, originality, and a strong opinion about how a product should create value. Strong Product Opinions Will Matter More One of Jeff’s clearest arguments is that the best companies will stand out because they have a strong opinion about the value they provide. He used banking as an example. Traditional banks may have deep infrastructure and long customer histories, but many of their digital experiences remain clunky. By contrast, companies like Wise create a cleaner, more digitally native experience around international money movement. The difference is not just features. It is opinion. A company that believes banking should be simple, fast, multicurrency, and digitally native will build a very different product from one carrying decades of institutional inertia. Brian made a similar point with Mercury, describing how the company makes banking for his venture firm feel dramatically easier than traditional banking workflows. Jeff’s response was direct: “Delightful to bank” is an opinion. And once a company has a real opinion, product decisions can follow from it. That is the work AI cannot fully replace: deciding what should exist, why it should exist, how it should feel, and what kind of customer behavior it should create. Founders Still Need to Talk to Real Customers For founders, Jeff’s advice has not changed much over the last twenty years. The fundamentals are still the same: Solve a real problem for a real customer in a meaningful way. What has changed is that the excuses have disappeared. In 2006 or even 2016, teams could argue that customer research was expensive, slow, or operationally difficult. In 2026, Jeff does not buy that excuse. Founders can find customers, schedule conversations, show prototypes, collect data, and synthesize insights faster than ever. But the core work still has to happen. You need to understand the customer’s current behavior. You need to observe where the pain actually is. You need to test whether your solution changes behavior. And most importantly, you need to be willing to change course when the evidence contradicts your belief. That last part is where many founders fail. They collect evidence, but they do not let it change their mind. Synthetic Users Are Not a Replacement for Real People The episode also touched on one of the more controversial trends in product research: synthetic users. Some startups now claim they can simulate customer interviews using AI-generated personas or artificial societies. Jeff is unconvinced. He sees value in using synthetic users to practice interview scripts, test rough messaging, or prepare for research. But he does not believe they can replace real customer conversations. Why? Because real humans reveal things synthetic users will not. Jeff shared a story from his time at The Ladders, a job board for professionals earning over $100,000. When interviewing executives, his team noticed that many preferred communicating with recruiters through SMS. The surface-level explanation might have been convenience. The real reason was more revealing: they believed their bosses could read their email, but not their text messages. That kind of insight comes from human context, fear, hesitation, and lived behavior. A synthetic user would likely miss it. Jeff’s point is not that AI cannot help research. It is that founders should not confuse simulated answers with actual market evidence. The Real Signal: Behavior Change So how does a founder know they are working on a real problem? For Jeff, the answer is behavior change. Do customers light up when they see the prototype? Do they ask for access? Do they change how they work? Do they come back? Do they refer others? Do they pay? This is where Jeff connects product discovery to outcomes. An outcome is not a feature shipped or a deliverable completed. It is a measurable change in human behavior that drives a business result. This is why old startup metrics like acquisition, activation, retention, revenue, and referral still matter. They are not just dashboard numbers. They are signals of whether customers are behaving differently because of what you built. The danger is when teams measure output instead of value. Shipping more features does not mean you are solving a bigger problem. Generating more designs does not mean you are creating better UX. Producing more AI-generated artifacts does not mean you are making better decisions. As Jeff put it: “Producing stuff is not the production of value.” Product Managers Are Not CEOs of the Product In the rapid-fire section, Jeff challenged a popular product management cliché: the idea that product managers are “the CEO of the product.” He rejects it. Product managers cannot hire, fire, or fully control budgets. They do not have the authority implied by the CEO metaphor. That does not make the role unimportant. It makes the role different. A good product manager guides decisions, aligns people, clarifies outcomes, understands customers, and helps the team make evidence-based tradeoffs. The danger of the “CEO of the product” framing is that it encourages product managers to think in terms of authority rather than influence. Modern product work is not about commanding the team. It is about creating clarity around what matters and why. Why Jeff Changed His Mind About Measuring Customer Conversations One of the most honest moments in the episode came when Jeff talked about something he used to believe but now thinks he got wrong. For years, he

48 min
−2 d

Ignite Startups: How Adam Nash Built Daffy Into a $1B Donor-Advised Fund Platform | Ep281

Most financial products are built around one question: how do you help people keep, grow, or spend more of their money? Adam Nash is building around a very different question: how do you help people give it away better? Nash has spent decades at the center of major consumer technology and fintech shifts. He was VP of Product at LinkedIn through its IPO, President and CEO of Wealthfront, VP of Product at Dropbox, and previously held roles at eBay and Apple. He is also a prolific angel investor, with early investments in companies like Figma, Gusto, Opendoor, Firebase, and more. Today, he is co-founder of Daffy, a modern donor-advised fund platform designed to make charitable giving easier, more intentional, and more accessible. In the episode, Nash explains why giving has been one of the most underbuilt categories in consumer finance—and why the donor-advised fund may be a much bigger product opportunity than most people realize. Money Is a Trust Business Nash’s interest in financial products started early. In college, after earning what felt like a large amount of money from an internship, he quickly realized he had spent far more than expected. That experience pushed him to learn about savings, mutual funds, returns, and financial decision-making. Over time, that curiosity became a career thesis: technology keeps getting more powerful, but the most interesting products sit at the intersection of rational systems and irrational human behavior. That lens shaped his work at Wealthfront. Managing people’s money is not just a math problem. It is a trust problem. People are not optimizing spreadsheets in the abstract. They are trying to build lives, care for families, retire comfortably, reduce anxiety, and make decisions they can live with. For Nash, the lesson was clear: in financial products, the emotional layer matters as much as the technical layer. The product must be accurate, safe, and reliable—but it also has to understand how people actually behave. What Wealthfront Taught Him About Company-Building Running Wealthfront gave Nash a broader view of what it takes to build a company beyond product strategy. His definition of the CEO role is blunt: set the strategy, find the right people to execute it, and make sure they have the resources to succeed. Get those three things right, and a company can survive a lot of mistakes. He also argues that culture has to be built early. At scale, behaviors are already locked in. The habits, incentives, and standards created in the first phase of a company become incredibly sticky. That belief extends even to hiring. Nash recalled wanting every candidate—whether they got the job or not—to leave with a clear, positive understanding of what the company did and why it mattered. In his view, every interaction with the company is part of the brand. The eBay Lesson: Operational Excellence Can Become a Trap One of the most interesting parts of the conversation was Nash’s comparison between eBay and LinkedIn. At eBay, he saw an extraordinarily disciplined product organization. Roadmaps were prioritized with financial rigor. Hundreds of features were evaluated, scheduled, and shipped with remarkable precision. By conventional business standards, it was an elite execution machine. But that strength came with a cost. Nash argues that eBay was wound so tightly around operational efficiency that there was less room for exploration, innovation, and riding new technology waves. The company was great at optimizing the current machine, but that made it harder to reinvent itself. LinkedIn taught him a different lesson. Reid Hoffman’s deep understanding of network effects shaped Nash’s view of platform-building: the core product matters, but so does planting seeds for the next 10x opportunity. Great companies do not have one story. They compound through multiple waves. That contrast became part of Nash’s operating philosophy: efficiency is valuable, but if it crowds out experimentation, it can become fatal. Why Daffy Exists The idea for Daffy came from Nash’s own experience with donor-advised funds. After LinkedIn went public, he faced a set of financial decisions around taxes, stock, and charitable giving. His accountant introduced him to donor-advised funds: a structure that lets someone contribute assets, receive the tax deduction, invest the funds tax-free, and later recommend grants to charities. Nash immediately saw the product as powerful. But he also saw how inaccessible it felt. Donor-advised funds had historically been associated with wealth managers, high-net-worth individuals, and legacy financial institutions. Most people who give to charity regularly had never heard of them. That was the opening for Daffy. Nash describes a donor-advised fund as something like a 401(k), IRA, wallet, or even HSA for charity. The idea is simple: put money aside for giving when it is financially convenient, then donate later when inspiration or need arises. That separation matters. Giving usually involves two hard questions at once: how much can I afford to give, and where should I give it? Bundling those decisions together creates friction. Daffy’s goal is to split them apart. Giving Is Emotional, Not Just Financial One of Nash’s strongest product beliefs is that the best consumer products touch people emotionally, not just rationally. He points to Apple as a company that understood this deeply. Photos are not just files. They are memories, children, family, and life history. The best products understand the human meaning underneath the task. Daffy applies the same logic to giving. Charitable giving is not just a tax optimization problem. It is tied to values, family, identity, religion, schools, community, disasters, causes, and the desire to help. That emotional insight shaped Daffy’s product decisions. The company launched mobile-first, supported crypto, added donor-advised fund transfers after users immediately requested them, and built features like family plans that let children, spouses, siblings, parents, and grandparents participate in giving. The family plan example is especially revealing. In wealth management, people talk constantly about multi-generational giving, legacy, and family values. But most donor-advised funds were still structured like individual or joint brokerage accounts. Daffy asked a simple product question: why doesn’t giving have a family plan like every other modern consumer subscription? That led to a feature where families can give together, children can recommend donations, and charitable giving can become a dinner-table conversation. The Business Model Bet: Membership Fees Over AUM Traditional donor-advised funds often charge fees based on assets under management. Nash argues that this model makes sense for investment products, but not necessarily for giving. The work required to administer a very large account is not thousands of times greater than the work required to administer a smaller one. Yet AUM-based pricing naturally biases the product toward wealthy users. Daffy’s contrarian move was to charge a membership fee instead. That supports the company’s broader ambition: make donor-advised funds useful not just for the ultra-wealthy, but for the tens of millions of American households that already give to charity each year. The product is not trying to convert non-givers into givers. It is trying to help people who already give do it more consistently, more intentionally, and with less friction. Are Donor-Advised Funds Just Warehouses for the Rich? We raised one of the strongest critiques of donor-advised funds: that they allow wealthy people to park money, get tax benefits, and delay actually sending funds to charities. Nash’s response was nuanced. He acknowledged that the concern is technically possible, especially at extreme wealth levels. If policymakers want to create rules or caps for very large accounts, he is open to that conversation. But he argues the critique is distorted by an obsession with billionaires. Most people using donor-advised funds are not trying to warehouse billions. They are giving to schools, religious organizations, local causes, national nonprofits, and global crises. He also points to payout behavior. According to Nash, Daffy’s own numbers show that more than half of contributed funds are granted out to charities the following year. His larger point: focus on the average use case, not just the most sensational edge case. The Angel Investing Framework The episode also goes deep on Nash’s angel investing philosophy. He has invested in roughly 160 to 170 companies over 14 or 15 years, but he does not treat angel investing as casual check-writing. He runs it more like a personal venture portfolio, deciding how much of his overall assets he is willing to allocate to startups, then pacing that capital over a decade. That decade-long view matters. Seed investing takes a long time. The best companies may take 10 years or more to reach liquidity. Many angels get excited in year one or two, then realize in year three that none of the money is coming back yet. Nash looks for a few things. First, he wants to understand why the founder is talking to him specifically. If the answer is just money, that is not compelling. He wants to add value through relevant expertise in product, fintech, marketplaces, social, or growth. Second, he listens for distribution. A product insight is not enough. The founder needs a credible path to reach customers and build a venture-scale company. Third, he looks for founder-market fit. Not just “this founder found a way to make money,” but “this founder cares about this problem enough to spend a decade on it.” The Venture Paradox: Saying No Sounds Smart Nash also offered one of the sharpest lines in the episode: in venture, it is easy to sound smart by saying no. There are always reasons a startup will fail. The market is too small. The timing is wrong. The team

53 min
18 juni

Ignite VC: How Jeffrey Becker Bets on Founders Before Product, Revenue, or Traction | Ep280

Most investors say they want to back outlier founders. Jeffrey Becker is trying to find them before the company even exists. As General Partner at Antler, Jeff co-leads the firm’s US Fund from New York, investing at what he calls the “inception” stage: before a polished pitch deck, before obvious traction, before the market has voted. Antler’s model is built around a simple but difficult premise: spend time with founders in person, understand how they think, watch how they operate, and back the ones who seem capable of building something massive from zero. Jeff calls it “backing maniacs.” Not reckless founders. Not loud founders. Not people performing ambition for investors. The kind of maniac Jeff is looking for is someone with deep obsession, extreme urgency, resilient optimism, and a personal relationship with the problem they are solving. Someone who does not just want to start a company, but almost cannot imagine doing anything else. That distinction sits at the heart of this conversation. From LinkedIn Hypergrowth to Day-Zero Venture Before joining Antler, Jeff spent nine years at LinkedIn during one of the company’s defining growth periods. He held nine roles across sales and leadership as LinkedIn scaled from roughly 1,500 people to around 20,000. That experience shaped the way he thinks about company building. Jeff points to LinkedIn’s leadership, culture, communication, and focus as major lessons. The best leaders he observed did not simply tell people what to do. They taught people how to think. They gave teams frameworks, principles, and operating systems that created leverage across the organization. That matters in venture because founders are not just building products. They are building cultures, decision-making systems, and teams that must survive chaos. For Jeff, the LinkedIn years gave him a front-row seat to what high-performance organizations look like before they become obvious from the outside. That now informs how he evaluates founders at the earliest stage. Why Antler Invests Before the Noise Starts Antler is not trying to be a traditional accelerator. Jeff frames the firm as an inception-stage investor: a place where founders can answer the questions that come before the company. Should I start this?Who should my co-founder be?Is this the right market?What problem do I understand better than everyone else?Am I actually ready to live this life? Antler operates in 27 cities globally and has backed roughly 1,900 portfolio companies. The firm brings founders together in person through a residency-style model before equity or capital changes hands. That gives founders a chance to meet co-founders, test ideas, sharpen conviction, and decide whether this is really the arena they want to compete in. Jeff believes this stage is less noisy than later pre-seed or seed investing. Once there is a product, a few customers, and early revenue, investors can get distracted by signals that may or may not matter. A customer loves it. Another hates it. A non-customer says they would never buy it. Suddenly the investor is buried in conflicting information. At inception, Jeff is focused on the person. Can they sell?Can they recruit?Can they learn fast?Can they move with urgency?Can they attract people into their orbit?Do they understand something deeply?Are they resiliently optimistic?Are they unusually spiky in at least one important way? That is the core bet. The Founder Who Talks Too Much About Money One of Jeff’s sharper views is that founders who lead with “I want to build a billion-dollar company” can make him nervous. At first, that sounds counterintuitive. Venture capital depends on massive outcomes. Shouldn’t VCs want founders with billion-dollar ambition? Jeff’s point is more precise: if a founder talks about a billion-dollar company too early, it can reveal that they already have a price in mind. If they would sell at $100 million or $400 million, that may be a perfectly rational life decision—but it may not fit the venture model. The founders Jeff trusts more are often less obsessed with the financial endpoint and more obsessed with the problem. They may understand the economics. They may be realistic about acquisition offers. But their relationship with the problem is deepening over time, not weakening. The rarest founders are the ones doing their life’s work. They are not building because a market map looks attractive. They are building because the problem has grabbed them by the throat. That is the magic Jeff is hunting. Why Antler Increased Its Check Size Antler’s US fund is now writing checks of up to $600K at inception. That is a meaningful jump for a stage where many companies may not yet have meaningful revenue or even a finalized product. Jeff’s explanation is straightforward: the quality of founders is rising, and great founders can do more with capital than ever before. AI and modern software tools have collapsed the cost of building. A small team can now prototype, launch, and iterate faster than at any prior point in startup history. The right founders can turn early capital into real leverage. But Jeff also sees a dangerous funding gap. Too many companies get stuck between not having enough traction to raise and not having enough money to get traction. Antler’s larger check is designed to break that paradox. The firm typically splits the capital into two parts: an upfront check that gives founders room to build, and a follow-on check intended to help catalyze the next round. The goal is to let founders spend more time building the company and less time endlessly fundraising. The Most Overrated Metric at Pre-Seed Jeff’s answer is blunt: customers and revenue. That does not mean customers are irrelevant. It means that at the earliest stages, traction is often noisier than investors want to admit. A founder might have five customers, but those customers may represent five completely different stories. One loves the product. One is lukewarm. One hates it. One bought because of the founder’s personal network. Another may churn in two months. At that stage, the investor can confuse motion for signal. Jeff gives the example of Harper, an Antler portfolio company that later became one of the standout companies in the fund. When Antler first invested, the company had a different name and was pursuing a different idea. Jeff did not love the original concept. But he believed deeply in the founders, especially their intensity, speed, and ability to build. The company pivoted into insurance and took off. Had Jeff evaluated only the initial idea or early traction, he might have missed it. That is the danger of over-indexing on metrics too early. At inception, the founder may matter more than the first version of the business. The Case for Diversification at Inception Jeff is also direct about portfolio construction. At the earliest stage, he believes diversification is not a weakness. It is a requirement. If you are investing before the company is fully formed, you are taking extreme risk. The way to manage that risk is not by pretending you can perfectly predict winners. It is by building a system that gives you exposure to enough exceptional founders while maintaining the ability to follow on when the winners begin to emerge. That is the logic behind Antler’s global model. The firm sees an enormous top-of-funnel: around 150,000 global applications per year, with roughly 400 investments. In the US, Antler sees around 15,000 applications and makes roughly 60 to 70 investments. But Jeff is clear that diversification alone is not enough. A great inception fund also needs a strategy to concentrate capital over time. You need the sourcing engine, the selection engine, and then the follow-on engine. That combination—broad exposure early, concentrated capital later—is where the model becomes powerful. AI Is Changing Startups, But Not Everything Becomes Software Jeff acknowledges that AI is collapsing the cost of company creation. Founders can now spin up products, automate workflows, and launch businesses with far less capital than before. But he pushes back on the idea that this means venture capital is dead or that all major companies will be built by one-person teams. Yes, AI will create enormous leverage.Yes, more founders will reach revenue without raising.Yes, some software businesses will require fewer people and less capital. But Jeff argues that the world is still full of hard problems that require teams, systems, complexity, and capital. Data centers, satellites, longevity, quantum computing, stablecoin infrastructure, physical-world systems—these are not trivial products that can be one-line-prompted into existence. The future is not just “AI makes startups cheaper.” The future is that ambitious founders can now attack bigger problems with more leverage. Why Being Different Is Not Optional One of Jeff’s strongest beliefs is that to be better than average, you have to be different. That applies to founders. It applies to investors. It applies to how people pitch, build, hire, and distribute. Too many founders show up with the same deck, the same language, the same AI-generated polish, and the same safe narrative. Jeff sees that as a problem. If everyone looks the same, sounding competent is not enough. Founders need to understand where they are different and exploit that difference. Their wedge, insight, personality, obsession, speed, or worldview has to stand out. Venture is not a game designed to reward average behavior. It rewards outliers. So the founder’s job is not to look like the median fundable company. It is to make investors feel that they are seeing something rare. The Cave Walls Test Toward the end of the conversation, Jeff shares a story from his managing partner about “the cave walls.” The idea is simple: life is like leaving a cave, collecting experiences, and returning with stories, memories, and symbols that e

54 min
16 juni

Ignite VC: The Capital Markets Hack Founders Are Missing with Jonathan David Nelson | Ep279

Most startup founders are trained to think about capital in one narrow way: raise venture money, grow fast, stay private as long as possible, and eventually hope for an acquisition or IPO. Jonathan David Nelson thinks that model is broken. Not slightly inefficient. Broken. In this episode of the Ignite podcast, Jonathan joins Brian Bell to unpack why the startup financing machine no longer works for most growth-stage companies, why the U.S. public markets have become hostile to smaller public companies, and why the London Stock Exchange may offer a smarter path for founders stuck between venture capital and private equity. Jonathan’s background makes him an unusual voice in capital markets. He grew up in Latin America, trained as an ER and ICU nurse, went back to school for software engineering, built Hackers and Founders into a global startup community, advised on crowdfunding policy, worked across emerging startup ecosystems, and now runs HF Capital—an AI-native investment bank focused on IPOs, secondaries, and M&A. That mix gives him a rare lens: part operator, part hacker, part capital markets obsessive, part outsider who never agreed to pretend the system made sense. From Trauma Nurse to Capital Markets Contrarian Jonathan’s path into venture did not start at Goldman Sachs, Stanford, or a Sand Hill Road fund. It started in Honduras. He grew up in Latin America as the child of missionaries, in a small village hours down a dirt road. As a kid, he was already programming and managing his father’s mailing list. When he later came to the U.S., he expected to follow a missionary path. His father pushed him to get a practical trade first, so Jonathan became a nurse. He worked as an ER trauma nurse before eventually injuring his back and moving into software engineering. That transition led him to Silicon Valley, where he became obsessed with startups. His wife, tired of hearing him talk about startups nonstop, pushed him to get out of the house one night a month. That became Hackers and Founders, a meetup that started as a casual bar gathering and grew into one of the largest founder communities in the world. But the more founders Jonathan met, the more he saw the same pain point repeat: raising capital was brutally inefficient. Founders wanted to know where the “money tree” was in Silicon Valley. Jonathan’s answer was blunt: there is no money tree. Fundraising is a grind. It takes months. It is a brute force algorithm. That realization became the foundation for his current work. Fundraising Is Still a Brute Force Algorithm One of the clearest themes in the episode is just how inefficient fundraising remains. Jonathan compares fundraising to a brute force algorithm: knock on doors, get meetings, pitch, get rejected, and hope that one out of every ten or fifteen conversations converts. Brian adds his own experience from raising venture funds, describing thousands of “no’s” even with an existing track record. The point is not just that fundraising is emotionally hard. It is structurally wasteful. Founders spend months selling stock instead of selling product. VCs spend years raising funds. LPs sit behind layers of intermediaries. Capital moves slowly through a system that is supposedly designed to fund innovation. Jonathan’s frustration comes from seeing the full chain. As a former nurse, he thinks in systems. In medicine, understanding how blood flows through the body tells you where to apply pressure when something goes wrong. He applies the same logic to capital markets: how does capital actually flow through the startup ecosystem? When he realized that pension capital could pass through fund-of-funds, venture funds, and multiple fee layers before reaching entrepreneurs, he saw the system as an inefficient capital delivery mechanism. His conclusion: the ecosystem is sick, and someone needs to heal it. Why Crowdfunding Did Not Fully Democratize Startup Capital Jonathan also reflects on his work around the JOBS Act and equity crowdfunding. Crowdfunding was supposed to democratize startup investing. In some cases, it worked—especially in real estate. Real estate can generate dividends, rent, and recurring distributions. Investors have a clearer path to getting money back. Startup equity is different. If a small business or startup raises money from its community, when do those investors get liquidity? Usually, only through an acquisition or IPO. And those paths are not equally available to everyone. Jonathan points out that much of tech M&A is highly network-driven. It depends on who knows corporate development teams at major acquirers. If you are outside the club, your odds of finding liquidity are much lower. That is the core flaw: crowdfunding can help people buy private equity, but it does not solve the exit problem. More access to illiquid assets is not the same thing as democratization. Why Jonathan Thinks the U.S. IPO Market Is Broken Jonathan’s most provocative argument is that the U.S. public market system no longer works for most companies below massive scale. In his view, the U.S. exchanges are optimized for large hedge funds, high-frequency traders, and mega-cap companies. They are not well optimized for capital formation for smaller growth companies. If a company goes public in the U.S. at a $100 million, $300 million, or even $1 billion valuation, Jonathan argues it can quickly become an orphaned public company. The risks include: * Limited or no analyst coverage * High volatility * Activist hedge funds * Short selling pressure * Expensive legal and compliance obligations * Difficulty competing for attention against companies like OpenAI, SpaceX, Anthropic, or other dominant tech names For a smaller public company, being technically public does not guarantee liquidity, coverage, or investor interest. It can mean higher costs, more scrutiny, and less control—without the full benefits of being public. The London Stock Exchange as a Startup Financing Hack Jonathan’s alternative is not “never go public.” It is: consider going public somewhere else. He became interested in the London Stock Exchange after learning that its market structure is very different from the U.S. system. After studying dozens of global exchanges, he came away believing London has one of the best-engineered IPO products for smaller growth companies. The appeal, according to Jonathan, includes: * Lower IPO costs compared with the U.S. * Lower ongoing public company maintenance costs * A sponsor bank model * More reliable analyst coverage * A market maker relationship * A less litigious environment * Different rules and norms around short selling * Better support for smaller public companies The key insight is that a company doing $50 million in revenue and growing 50% year over year may no longer be a fit for venture capital—but it may be a very interesting public company in the right market. That is the gap Jonathan wants HF Capital to serve. The 50 and 50 Company Jonathan describes his target company as being in the “50 and 50” range: roughly $50 million in annual revenue and growing around 50% year over year. That kind of company can be awkward for venture. It may not be growing fast enough for top-tier late-stage VC. It may not want private equity control. It may not want to take punishing liquidation preferences. But it may still be a strong, valuable, growing business. In Jonathan’s view, companies like this should have more financing options. An IPO on the London Stock Exchange could let them raise capital, create liquidity, and use public stock as a strategic asset without being forced into another painful private round. The founder tradeoff is real. Once public, the company no longer controls its valuation in the same way. The market sets the price. Macro shocks, sector sentiment, and public investor perception can all move the stock. But Jonathan argues that private markets have their own version of the same risk. Founders just understand those risks better because they are familiar. The unfamiliar option is not necessarily the worse option. Why Late-Stage Private Rounds Can Hurt Founders and Early Investors The episode also gets into one of the least understood parts of startup finance: liquidation preferences. When a late-stage investor puts money into a company, they may receive preferential rights that determine who gets paid first in an exit. A 2x liquidation preference means that investor gets twice their money back before common shareholders or junior preferred investors receive proceeds. If the preference is participating, the investor may get their preference and then also participate in the remaining proceeds. That can be excellent for the late-stage investor. It can be brutal for founders, employees, and early backers. Brian and Jonathan discuss how late-stage investors may prefer an acquisition because liquidation preferences can matter in an M&A outcome. In an IPO, the cap table typically converts to common stock, which can wipe out those special preferences. That creates a boardroom conflict. Founders may benefit from going public. Early investors may benefit. Employees may benefit. But late-stage investors with structured terms may prefer a private equity acquisition. That is why Jonathan’s idea can face resistance from boards, even when founders are interested. Why SPACs Went Wrong Jonathan is also skeptical of SPACs. A SPAC, or special purpose acquisition company, is a shell company that goes public with the goal of acquiring an operating company later. In theory, it offers companies an alternative path to public markets. In practice, Jonathan argues, SPACs are often stacked against the company being acquired. Investors in the original SPAC can have incentives to redeem or sell, and the operating company can end up public without the same preparation, reporting maturity, or investor base it would have built through a traditional IPO process. The result can be

47 min
9 juni

Ignite AI: Dennis Mortensen on Startup Failure, AI Agents, and Why Boring SaaS Problems Win | Ep278

Most founders want to build the future. Dennis Mortensen has done it repeatedly—and he has the scar tissue to prove how expensive that ambition can get. A Danish-born, New York-based serial founder, Dennis has built and sold four companies, shut one down, and is now building his sixth venture, LaunchBrightly. His career has moved through analytics, media optimization, AI scheduling, and now product documentation automation. Along the way, he has learned a hard truth that most startup advice skips over: the best companies are not always built around glamorous ideas. They are built around painful, persistent problems that someone is already paying humans to solve. That is the thread running through this episode of Ignite. Dennis is not interested in founder theater. He does not angel invest while building. He does not sit on boards. He does not treat advising startups as a badge of honor. His view is blunt: building a company is already improbable enough. Why make the odds worse by scattering your attention? That philosophy comes from experience. The “Expensive MBA” of Startup Failure Before the exits, Dennis had a failed startup he still refers to as an expensive MBA. He tried to build what was essentially an early Grubhub-style business in Europe, but with a twist: instead of running a pure marketplace, his company controlled the customer-facing brand and relied on third-party food operators behind the scenes. The model gave him better margins and helped revenue ramp quickly. But there was a structural problem underneath the growth. He did not control the quality of the product. Customers blamed his brand when food quality slipped. Partners had little loyalty. And while the business looked promising from the outside, the underlying mechanics were broken. Dennis had a chance to merge with Just Eat, one of the major European players in food delivery. He turned it down. Four months later, his company was dead. The lesson was not simply “take the acquisition offer.” Dennis is more precise than that. The real lesson was that the market was telling him something and he refused to listen clearly enough. He was too attached to the original model when the market was shifting toward marketplaces. That distinction matters. Founders are told to be persistent, but persistence can become delusion when the market is obviously rejecting the mechanism, not the mission. Dennis still dislikes dramatic pivots. He does not romanticize the classic startup story where one company morphs into something completely unrelated and becomes a massive success. To him, that is often luck dressed up as strategy. But he does believe founders must be willing to adjust the business model when the pain is real and the current solution is wrong. In his case, the pain was real. The model was wrong. Build From a “List of Hate,” Not a Whiteboard One of Dennis’s strongest founder habits is deceptively simple: he keeps a “list of hate.” Instead of sitting in a room with smart people, ordering pizza, and brainstorming startup ideas from a blank whiteboard, Dennis tracks the things that annoy him in real life. Bad workflows. Broken processes. Repeated friction. Small moments where the world feels unnecessarily stupid. He does not immediately act on the list. He lets it accumulate over years. Then, when it is time to start something new, he studies the list and looks for recurring pain. Some ideas get deleted because they are just personal irritation. Others have already been solved. But the valuable ones show up again and again—and those are worth investigating. This is a powerful founder filter because real pain tends to persist. Technologies change. Interfaces change. Distribution channels change. But the underlying job-to-be-done often remains stubbornly intact. Dennis used that process across multiple companies. It helped lead him to Visual Revenue, X.ai, and eventually LaunchBrightly. Market Challenge or Science Challenge? Dennis also uses a sharp framework for evaluating startup ideas: are you attacking a market challenge or a science challenge? A science challenge is something people clearly want, but the technology is hard. Self-driving cars are the obvious example. If cars could reliably drive themselves, the market would exist. The question is whether the technology can actually work. A market challenge is different. The technology may be straightforward, but customer behavior is uncertain. Airbnb was not hard because the website was impossible to build. It was hard because people had to become comfortable sleeping in strangers’ homes or letting strangers sleep in theirs. Dennis’s warning is simple: know which one you are attacking. Better yet, avoid attacking both at the same time. X.ai was a science challenge. People already hated scheduling meetings. The fantasy was obvious: someday, when they climbed high enough in the organization, they would have an assistant who handled scheduling for them. The demand was not mysterious. The question was whether software could do the job. And in the pre-LLM era, that was brutally hard. Building AI Agents Before AI Agents Were Cool Long before ChatGPT made AI agents mainstream, Dennis was building X.ai, an AI scheduling assistant that could coordinate meetings over email. Today, that sounds almost obvious. At the time, it was anything but. X.ai had to solve scheduling through natural language before modern large language models existed. That meant building much of the machinery from scratch: annotation tools, intent classification, entity extraction, workflows, and huge labeled datasets. Dennis says the company hand-labeled 32 million data points. They identified 47 scheduling intents, including new meetings, rescheduling, running late, adding participants, and changing durations. They focused on three core entities: time, location, and people. This is what building AI looked like before the current tooling stack existed. Before the modern agent hype cycle, the work was painfully manual. And Dennis learned something important: he became too attached to making the AI feel human. He wanted to win what he calls the daily Turing test. He wanted users to believe the assistant was human. That was intellectually thrilling, but commercially distracting. If users did not know it was a machine, they did not know they could buy one for themselves. And when the assistant made mistakes, people judged it differently because they thought they were interacting with a person. Eventually, Dennis accepted the more useful product truth: it is okay for a machine to behave like a machine. A button can be better than a sentence. A workflow can beat a performance. The goal is not to fool the user. The goal is to solve the pain. That lesson feels especially relevant now, when the AI market is full of products trying to look magical instead of becoming reliable. Selling vs. Being Bought Another major lesson from Dennis’s journey is the difference between selling and being bought. Early in a startup’s life, founders are selling. They are convincing customers that the problem matters, that the product works, and that the company deserves a chance. But at some point, if the market is real, the dynamic changes. Customers already know they have the pain. They arrive with better arguments than the founder could give them. At that point, the job is no longer to sell harder. The job is to make buying easier. That sounds obvious, but many startups miss the transition. They keep optimizing the sales motion when the market has already moved into demand capture. Dennis argues that founders need to recognize when buyers are no longer being educated from scratch. Once people are trying to buy, friction becomes the enemy. Why Dennis Talks to M&A and Corp Dev Early Dennis also rejects a common piece of startup advice: avoid corporate development and M&A conversations because they are a waste of time. His view is the opposite. Talk to people. Keep them updated. Build relationships long before you need anything. Every one of his exits came from this kind of long-term relationship building. A pitch that seemed irrelevant later led to Yahoo acquiring IndexTools. A casual conversation with another startup eventually led to the introduction that became the X.ai acquisition. The point is not to constantly shop the company. The point is to build optionality. Founders often underestimate how much future opportunity comes from seeds planted years earlier. A 30-minute conversation can look useless in the moment and become decisive later. LaunchBrightly and the Value of Boring Problems Dennis’s current company, LaunchBrightly, is aimed at a problem most people would never call exciting: keeping product screenshots in help centers up to date. But that is exactly why it is interesting. Every software company ships product updates. Every update risks making documentation stale. Old screenshots confuse customers, create support tickets, slow down onboarding, and make the product look worse than it is. The faster engineering ships, the harder it becomes for documentation, support, and product marketing teams to keep up. LaunchBrightly automates that process. It logs into a software product, captures updated screenshots, scans help center articles, detects mismatches, and helps teams update documentation without manual screenshot drudgery. This is not glamorous AI. It is not a general-purpose agent promising to change the world. It is a narrow, painful workflow that already exists inside software companies. That is the point. Dennis likes markets where the customer already has a human doing the work. You may or may not buy his product, but you cannot avoid the problem. If your documentation is stale, you pay somewhere else: in support costs, customer confusion, and slower product adoption. The Founder Who Still Loves Zero to One After four exits and one failure, Dennis is still building. Not because he needs another trophy, but

1 tim 19 min
5 juni

Ignite VC: Charlie O’Donnell on Founder Unfriendly and the Real Game of Startup Fundraising | Ep277

Venture capital looks simple from the outside. Build something interesting. Pitch investors. Get funded. Grow fast. But anyone who has actually raised money knows the process is rarely that clean. Great companies get passed on. Mediocre companies get funded. Investors give conflicting feedback. One VC says the market is too small. Another says it is too crowded. One says come back with revenue. Another says the revenue is the wrong kind. For founders, the whole thing can feel arbitrary. Charlie O’Donnell wants founders to understand something uncomfortable but useful: venture capital is not a fairness machine. It is a financial product with a very specific job. Charlie has seen that machine from almost every angle. He started on the institutional LP side at the General Motors Pension Fund, evaluating venture funds after the dot-com crash. He later became the first analyst at Union Square Ventures, helped First Round Capital open its New York office, and eventually launched Brooklyn Bridge Ventures, the first VC fund based in Brooklyn. Across his career, he wrote first checks into more than 100 companies and built a reputation as one of New York’s most accessible early-stage investors. Now, after stepping away from active fund investing, Charlie is helping founders understand what VCs often do not say directly. His book, Founder Unfriendly: What Investors Won’t Tell You About Getting Funded, is written for the founders who are not already famous, not already backed by elite networks, and not already surrounded by five venture-backed friends who can review every pitch deck, co-founder decision, and investor intro. In other words, most founders. Venture Capital Is Not the Same as Business Validation One of the biggest mistakes founders make is assuming that a VC pass means the business is bad. That is wrong. A business can be excellent and still be a terrible fit for venture capital. Charlie points out that a company generating $5 million in free cash flow every year might be a phenomenal business for the founder. But if it cannot become large enough to return a major venture fund, it may not fit the VC model. This is where founders often misunderstand the investor’s job. VCs are not simply asking, “Is this a good business?” They are asking, “Can this become big enough to return our fund?” That distinction matters. A profitable, durable, founder-owned company may be far more attractive than a venture-backed company forced onto an unnatural growth path. But if a founder walks into a VC pitch without understanding the risk-return model of venture, they can mistake rejection for judgment. It is not always judgment. Sometimes it is just fund math. The Best Founders Do Not Pitch Small Charlie’s strongest fundraising advice is also one of the most counterintuitive: founders often lose investor interest because they pitch what they can confidently promise, not what the company could become. That instinct is understandable. Many founders do not want to overstate. They do not want to look naïve. They do not want to project $200 million in revenue and then fall short. This is especially true for founders who feel they are under more scrutiny because of their background, gender, race, or lack of insider status. But according to Charlie, that caution can backfire. VCs are not looking for a conservative promise. They are looking for fund-returning potential. That does not mean founders should lie or inflate numbers. It means they need to clearly explain what happens if the company works. What does more capital unlock? What would it mean to double the sales team, expand into more cities, launch faster, or capture the market before competitors do? Charlie frames it simply: fundraising is not a promise conversation. It is a potential conversation. Founders who only pitch the safe version of the company often make the opportunity sound too small. The investor may never see the upside case because the founder never actually says it. Control the Meeting or the Meeting Controls You Another mistake founders make is letting investors take over the pitch. VCs will ask questions. Some will be useful. Some will be distracting. Some will pull the conversation into downside risk before the founder has even explained the upside. If the founder simply follows every question wherever it goes, the meeting can become fragmented and defensive. Charlie argues that founders need to bring structure. That does not mean being obnoxious or overbearing. It means setting the frame. A founder might start by saying: here are the three things that get people excited about this company. If I convince you of these three things, would this be worth spending more time on? That structure changes the meeting. It gives the founder a clear agenda. It lets the investor opt into the logic. And at the end, the founder can bring the conversation back to the original case: did I convince you of the things that matter? This is not just presentation polish. It is a signal. Investors are not only evaluating the business. They are asking whether this founder can recruit great executives, close impossible customers, handle skeptical partners, and keep control of high-stakes rooms. A founder who cannot control a VC meeting may struggle to convince the investor they can control much harder rooms later. Networks Are an Unfair Advantage Charlie is blunt about one of the least fair parts of fundraising: networks matter enormously. A founder with five venture-backed friends has a major advantage. Those friends can review the deck, make warm intros, explain how firms think, help evaluate a VP of Sales candidate, and translate confusing investor feedback. That knowledge is not evenly distributed. Founders outside those circles often have to work much harder to get the same information. They may be just as capable, but they are operating without the same insider map. This is one of the reasons fundraising can look meritocratic while quietly favoring people who already know the rules. Charlie’s advice is not to complain about the unfairness. It is to recognize it and deliberately build the network anyway. The best founders are often better not because they were born with perfect judgment, but because they have better access to people who sharpen that judgment. That is not fair. But ignoring it is worse. The AI Era Has Raised the Bar One of Charlie’s clearest reversals is around product. Years ago, he was willing to back founders before they had a product. In some cases, that made sense. If the team was exceptional and the idea was complex, getting in before the product existed could create a pricing advantage. But that logic has changed. In the AI era, the bar for building something has dropped. For many software startups, showing up with no product is no longer a sign of being early. It can be a sign of adverse selection. If the tools to build are faster, cheaper, and more accessible, then investors expect more. A founder pitching a software company without even a basic product now faces a harder question: why not? For founders, the implication is direct. The old “idea-stage” pitch is weaker than it used to be. Unless the company is in deep tech, hard science, or another category with real technical barriers, investors increasingly expect proof that the founder can turn insight into something tangible. Fundraising Is Winnable, But It Is Not Fair The central lesson from Charlie’s career is not that VCs are villains or founders are naïve. It is that both sides are operating inside a system with incentives that are often misunderstood. VCs need outlier outcomes. Founders need to understand the type of outcome they are pitching. Investors are pattern matching. Founders need to know which patterns help them and which ones hurt them. The process is biased toward networks, confidence, and clarity. Founders who lack those advantages need to build them intentionally. The danger is pretending the process is fairer, more rational, or more transparent than it really is. Charlie’s message to founders is not comforting. It is more useful than that. A VC pass does not mean your company is bad. A fundraise is not a referendum on your worth. A good business is not always a venture-backable business. And if you are pitching investors, your job is not to present the smallest thing you can safely defend. Your job is to make the upside impossible to miss. Because venture capital does not fund what is merely sensible. It funds what could become enormous.👂🎧 Watch, listen, and follow on your favorite platform: https://tr.ee/S2ayrbx_fL 🙏 Join the conversation on your favorite social network: https://linktr.ee/theignitepodcast Chapters:03:55 — Surviving the Dot-Com Crash and Negative Returns06:29 — What LPs Don’t See About Venture Capital09:39 — Why VCs Are Still Middlemen in the Startup Ecosystem11:33 — Lessons from Being the First Analyst at Union Square Ventures14:02 — Building a Network Without Money or an Ivy League Background17:10 — Creating Access Through Community and Events19:57 — Joining First Round Capital After a Failed Startup20:31 — Pitching During the 2008 Financial Crisis21:01 — Helping Spark the Foursquare Funding Race22:28 — Why New York Needed a Different VC Playbook24:26 — GroupMe, SinglePlatform, and Early Wins at First Round25:33 — Price Sensitivity vs. Price Takers in Early-Stage VC28:05 — Why One Lucky Deal Is Not an Investment Strategy32:15 — Leaving First Round to Launch Brooklyn Bridge Ventures34:21 — Why Charlie Walked Away From Active Fund Investing37:09 — Writing Founder Unfriendly for the 99% of Founders39:20 — Why Good Businesses Still Get Rejected by VCs41:00 — Pitching Potential Instead of Conservative Promises45:35 — Why Fundraising Is a Potential Conversation46:10 — What Founders Can Learn From Parenting a Small Child47:30 — Why Every Slide Needs to Scream Fund-Returning Outcome

58 min
3 juni

Ignite Design: Lauren Von Dehsen on Scaling UX, AI Design Tools, and Product Leadership | Ep276

Most people do not think about design when a thermostat works, a fitness band syncs, or a banking app helps them make a decision without friction. That is usually the point. Great design disappears into the experience. It reduces confusion, hides complexity, and makes hard technical systems feel obvious. But behind that simplicity is a long chain of decisions: what gets built, what gets cut, what gets explained, what gets tested, and what actually makes it into the customer’s hands. Lauren Von Dehsen has spent her career working inside that chain. Across Nike FuelBand, Nest, Google Health, Matter, and SoFi, Lauren has helped shape products at the intersection of hardware, software, and human behavior. Her work has touched connected devices, smart homes, healthcare, fintech, and now the emerging world of AI-assisted design. Her biggest lesson is blunt: documentation is not the product. The process is not the product. The customer only judges what ships. That idea sounds obvious until you watch how teams actually work. The Product Is the Only Thing the Customer Sees Early in her career, Lauren wrote about the idea of designing the product, not the documentation. At the time, she was working in environments where hardware and software had to come together in new ways. These were not mature product categories with well-worn patterns and obvious playbooks. Teams were inventing the product, the process, and sometimes the testing methods at the same time. On Nike FuelBand, for example, people were literally running up and down stairwells to test whether the device was tracking activity correctly. That is the reality of building something new. You do not always have a clean lab environment, a perfect spec, or a known answer. You have a product that needs to work in the messiness of the real world. For Lauren, that shaped a core belief: a designer cannot just hand off polished screens and assume the job is done. The real work is making sure the idea survives contact with engineering, testing, constraints, trade-offs, bugs, edge cases, and launch pressure. A beautiful design file does not matter if the shipped experience fails. That mindset is especially relevant for startups. Founders often confuse design with surface area: colors, screens, typography, polish. But design is more fundamental than that. It is the practice of making decisions about how a product behaves, how people understand it, and how the experience holds together under pressure. Nest and the Power of Cross-Functional Design Culture One of the chapters Lauren looks back on most fondly is her time at Nest. Nest was not just a company that made better-looking thermostats and smoke detectors. It helped redefine how people thought about everyday objects in the home. Before Nest, most people did not spend much time thinking about their thermostat. It was a beige plastic box on the wall. Functional, forgettable, and usually ugly. Nest changed that by bringing software-level interaction design, hardware craft, and brand-level attention to a category that had been ignored. But the real lesson from Nest was cultural. Lauren described an environment where she did not have to constantly explain why design mattered. Everyone cared about the product experience. Engineers, product leaders, designers, and other functions could debate almost any aspect of the product. The difference was that, after the debate, the team trusted the person closest to the decision to make the final call. That balance is rare. In weaker cultures, design is either isolated as “the designers’ job” or diluted into endless committee feedback. At Nest, design was everyone’s responsibility, but designers were still trusted as experts. That is a powerful distinction. For founders, this is one of the most important takeaways from the conversation. If design matters to your company, it cannot be something you bolt on at the end. It has to be part of how decisions are made from the beginning. What Founders Get Wrong About Design Early-stage companies often bring designers in too late. A founder may define the product direction, product managers may shape the requirements, engineers may begin scoping the system, and only then does someone ask design to “make it usable” or “make it look good.” That is backwards. Lauren argues that designers are most valuable when they get context early. Not when every decision has already been boxed in. Not when the team simply needs a screen. Early context allows designers to understand the customer, the business goal, the constraints, the technical trade-offs, and the hidden assumptions behind the product. That does not mean every startup needs a huge design team. It does mean founders need to be honest about what they expect design to do. Are you hiring someone to make the MVP presentable? Are you hiring someone to define the customer experience? Are you hiring someone to help shape product strategy? Those are different jobs. They require different levels of seniority, different skill sets, and different levels of organizational trust. The mistake is not choosing one path over another. The mistake is pretending you want strategic design while treating designers like production support. Scaling Design at SoFi Lauren joined SoFi in early 2020, just weeks before the pandemic changed how teams worked. At the time, SoFi was in a high-growth phase, operating across a wide range of financial products: banking, investing, lending, crypto, and insurance. That created a very different design challenge from Nest. At Nest, the work centered on tightly integrated hardware and software experiences. At SoFi, the challenge was scale, complexity, and coherence. How do you create one unified customer experience across financial products that behave very differently? What should be shared across the brand? What needs to be specific to each vertical? How do you build a mature design and research organization that can keep pace with a growing company? Lauren eventually scaled SoFi’s design and research function into a 100-person organization. That required more than hiring. It required building rituals, processes, expectations, and cross-functional relationships that could evolve as the company changed. One of her points is especially useful for leaders: rituals have to serve the outcome. They cannot become the outcome. Design critiques, reviews, sprints, and research processes all have value. But as companies scale, the same rituals that once created alignment can become bottlenecks. A critique with five people may be useful. A critique with 30 people may be theater. Good design leadership means knowing when to change the system. Process Is Useful Until It Becomes the Point Design teams love process. Design sprints. Double diamonds. Workshops. Critiques. Frameworks. Research panels. Naming conventions. Some of that is useful. Some of it becomes internal language that does not help the broader company. Lauren’s view is practical: use the tool if it helps the team get to the next decision. Do not worship the tool. Do not over-explain the ritual. Do not assume cross-functional partners care about the purity of the method. Most partners want to know what decision is being made, when the answer will be ready, and whether it will help the product move forward. That does not mean design should become reactive or shallow. It means design leaders need to translate their work into business-relevant outcomes. The best design process is the one that helps the team build a better product faster, with fewer blind spots. Anything else is overhead. AI and the Next Wave of Design Tools The conversation also turned to AI and how it is changing design. Lauren sees clear productivity gains. Designers, like everyone else, can use AI to brainstorm, write, summarize, explore concepts, and accelerate early work. But she also sees a major limitation: design is not only language. For many software tasks, moving from keyboard input to conversational prompting is a relatively natural abstraction. But design often involves spatial judgment, visual hierarchy, motion, color, breathing room, sequencing, and subtle interaction details. Describing those details in words can become frustrating fast. AI tools may generate strong first concepts. But as the designer tries to refine the work, make precise changes, and bring the output closer to a specific vision, the process can become fatiguing. The more exact the desired change, the harder language-only prompting becomes. This is why Lauren is interested in tools that combine chat-based interaction with direct visual manipulation. The future of AI design probably will not be pure prompting. It will be a hybrid interface where designers can generate, edit, manipulate, critique, and refine in the same environment. The open question is which tool becomes the design equivalent of the AI coding copilot. The Hardest Design Trade-Off: Craft vs. Reality One of the most honest parts of the conversation was Lauren’s reflection on how her own thinking has changed. Earlier in a design career, it is natural to want everything to be elegant, complete, polished, and deeply considered. That instinct is valuable. It creates standards. It pushes teams beyond mediocrity. But leadership requires a different kind of judgment. Sometimes speed matters more. Sometimes a business constraint matters more. Sometimes the right call for the company is not the designer’s ideal recommendation. Lauren described moments as a leader when she had to make decisions against her team’s design preference, not because the team was wrong, but because other constraints had to win. That is the maturity curve of design leadership. The goal is not to abandon craft. The goal is to know when craft is the decisive variable and when it is not. The Real Job of Design The through-line in Lauren’s career is not just design excellence. It is systems thinking. FuelBand required understandi

44 min
29 maj

Ignite Startups: How ChargeMate Is Fixing EV Charging Reliability with AI with Brad Crist | Ep275

Electric vehicles are supposed to represent the future of transportation. Cleaner. Smarter. More connected. More efficient. But for many drivers, the future still gets stuck at a broken public charger. That tension is exactly what Brad Crist, co-founder and CEO of ChargeMate, is trying to solve. After spending years in climate tech and EV infrastructure, including work at companies like Accenture, Faraday Future, Volta, and Spring Free EV, Brad saw the same problem again and again: the industry was great at deploying chargers, but not nearly as good at making sure they actually worked when drivers needed them. The result is a massive trust problem. EV adoption is not just about getting more cars on the road or installing more charging stations. It is about whether a driver can pull up, plug in, and confidently get back on the road. Right now, that experience still breaks too often. The Hidden Bottleneck in EV Adoption Brad’s founding story started with a very human moment: a road trip in his Rivian. He had been an early EV adopter and was excited to show friends what a luxury electric vehicle could do. Instead, the trip exposed the frustrating reality of public charging. New apps. Slow chargers. Damaged equipment. Confusing payment flows. Stations that appeared to be online but did not actually work properly. That experience sharpened the problem ChargeMate is now focused on: the gap between charger “uptime” and real driver success. A charger may show up as available in a system. It may technically be online. But from the driver’s perspective, the session can still fail because of payment issues, app problems, charger-vehicle handshake errors, slow charging, connectivity failures, or confusing user flows. Brad noted that more than 20% of charging attempts fail, a brutal number for an industry trying to convince mainstream consumers that EVs are ready for everyone. That is not a minor inconvenience. It is a category-level adoption blocker. ChargeMate’s Bet: AI as the Operating Layer for EV Infrastructure ChargeMate is not just building another customer support chatbot. The company is building an AI-powered operating layer for EV charging networks. Its platform uses chat and voice agents to help drivers in the moment, while also integrating into the backend systems that manage chargers. That matters because fixing the experience requires more than answering basic questions. ChargeMate can check whether a charger is online, identify faults, inspect transaction status, and in some cases take remote actions like rebooting a unit or releasing a stuck plug. The goal is not just to respond faster. It is to actually resolve the issue. That is the core wedge: using AI to turn fragmented, unreliable charging support into something closer to real-time infrastructure management. Why Generic Support Tools Are Not Enough A natural question comes up: why can’t Zendesk, Intercom, or an incumbent charging network just build this? Brad’s answer is that EV charging is not normal customer support. This is a messy intersection of software, firmware, hardware, payments, vehicles, field service, and physical infrastructure. One ChargeMate customer has dozens of hardware products to manage, and one hardware SKU alone has hundreds of unique error codes. That complexity is exactly where vertical AI has an advantage. A generic AI support system can answer questions. ChargeMate is designed to understand the specific failure modes of EV charging: the charger, the vehicle, the network, the transaction, the driver behavior, and the operational workflow behind it. The more hardware types, vehicles, networks, and failure modes ChargeMate sees, the better its resolution engine can become. That creates a potential data advantage that broad horizontal tools will struggle to match. The Business Case: Better Support, Better Margins EV charging operators are under pressure to prove that their networks can become profitable businesses. That is hard when support and operations costs are high, charging sessions fail, and customers abandon the experience. Brad described customer support and operations as a major cost burden for operators, especially when calls can cost $10 to $15 each. ChargeMate’s early results are meaningful. Brad said the AI can resolve roughly 50% to 70% of calls without involving a human. He also pointed to one client seeing a roughly 5.5% lift in charging success rate, which can translate into millions of dollars of margin at larger network scale. That is the real investor-relevant insight: ChargeMate is not selling “AI support.” It is selling recovered revenue, lower support cost, better asset utilization, and improved driver retention. In infrastructure markets, reliability is margin. The Pivot That Made ChargeMate Work ChargeMate did not start exactly where it is today. The original idea was closer to a consumer product: helping EV drivers find available, working chargers near desirable stops like coffee shops or clean bathrooms. The problem was real, but the go-to-market path was ugly. Competing with Google Maps or trying to become a consumer endpoint would have required massive distribution. Accessing vehicle data would have been difficult. Monetization would have been uncertain. The sharper wedge was on the operator side. Charging networks were already paying for failed sessions, expensive support calls, unhappy drivers, and fragmented operations. ChargeMate could solve a painful B2B problem with direct ROI. That pivot matters because it reflects one of the biggest lessons in startup building: the best product idea is not always the best business. ChargeMate became more interesting when it moved away from broad consumer convenience and toward a painful operational problem with budget attached. Voice May Be the Real Unlock One of Brad’s more interesting reflections was that ChargeMate may have started too heavily with chat. When a driver is stranded at a charger, frustrated, and trying to get moving, the natural behavior is not always to open a chat window. It is to call. That is why ChargeMate is now investing in voice AI as a major interaction point. Voice fits the urgency of the moment. It also lets ChargeMate take over the first line of support while escalating to humans when necessary. This is where the company’s hybrid model becomes important. ChargeMate combines AI with human call center partners, creating an AI-enabled service layer rather than a purely software-only experience. That is likely the right architecture for messy infrastructure markets. Full automation is attractive, but trust is built by solving the problem. Sometimes that means AI. Sometimes that means a human. The winning system routes intelligently between both. Where the Market Goes Next Brad sees EV charging as the beachhead, not the full opportunity. The larger idea is that AI can become the operating layer for energy infrastructure. Chargers are just one class of distributed physical assets that need monitoring, support, diagnostics, and coordination. Customers are already asking whether ChargeMate’s AI can help manage other systems, including batteries, building management systems, and broader site-level energy assets. That points to a bigger future: self-healing infrastructure that can detect problems, communicate with humans, coordinate workflows, and resolve issues before they become expensive failures. For EV charging, that future cannot arrive fast enough. The Takeaway The EV industry has spent years racing to deploy more chargers. That was necessary, but it was not sufficient. The next phase is reliability. Drivers do not care whether a charger is technically online. They care whether it works when they pull up. Operators do not just need more stations. They need better uptime, better support, better diagnostics, and better economics. ChargeMate is betting that AI will become the connective tissue between drivers, chargers, operators, vehicles, and field teams. That is a sharper thesis than “AI for customer support.” It is AI for physical infrastructure reliability. And if EVs are going to move from early adopters to the mainstream, that may be one of the most important layers still missing.👂🎧 Watch, listen, and follow on your favorite platform: https://tr.ee/S2ayrbx_fL 🙏 Join the conversation on your favorite social network: https://linktr.ee/theignitepodcast Chapters:00:01 – Brad Crist, ChargeMate, and the EV Reliability Gap00:34 – From Utilities to EV Charging Startups01:16 – The Rivian Road Trip Problem02:39 – Tesla, Non-Tesla EVs, and Market Fragmentation04:07 – Why Public Charging Fails05:55 – ChargeMate’s AI Support Layer06:18 – Why Incumbents Struggle with Reliability08:09 – AI-Enabled Support and Call Deflection09:33 – The First Design Partner Breakthrough11:16 – The Pivot Away from Consumer Route Planning13:39 – Why Zendesk and Intercom Are Not Enough15:38 – Complexity, Protocols, and Charging Standards16:42 – Autonomous Vehicles and Future Infrastructure18:11 – Natural Language Interfaces for Energy Assets19:25 – Early Decisions That Nearly Killed the Company20:55 – Contrarian Beliefs About EV Infrastructure21:37 – Enterprise Sales Challenges22:38 – Starting with Voice First Transcript Brian Bell (00:00:57): Hey everyone, welcome back to the Ignite podcast. Today we’re thrilled to have Brad Crist on the mic. He is the co-founder and CEO of Chargemate, an ai platform tackling one of the biggest bottlenecks in EV adoption: unreliable charging infrastructure and broken driver experiences. Prior to Chargemate, Brad spent over a decade in climate tech and helped scale EV charging networks at Volta from hundreds to thousands of stations globally. Thanks for coming on, Brad. Good to see you again would love to get your origin story. What’s your background for the audience? Brad Crist (00:01:26): Absolutely. So as you introduced us, we spent

23 min

Visa alla (280)

Thoughts on early stage investing, technology, society, and the future. insights.teamignite.ventures

Skapad av

Ignite Insights
Aktiva år

2023 - 2026
Avsnitt

280
Åldersgräns

Vuxet innehåll
Programmets webbplats

Ignite: Conversations on Startups, Venture Capital, Tech, Future, and Society

Investering

Investering

Varje dag
Teknologi

Teknologi

Varje vecka
Investering

Investering

Varje vecka
Sport

Sport

Två gånger per vecka

Ignite: Conversations on Startups, Venture Capital, Tech, Future, and Society

Ignite Product: Jeff Gothelf on Lean UX and Product Strategy in the Age of AI | Ep282

Ignite Startups: How Adam Nash Built Daffy Into a $1B Donor-Advised Fund Platform | Ep281

Ignite VC: How Jeffrey Becker Bets on Founders Before Product, Revenue, or Traction | Ep280

Ignite VC: The Capital Markets Hack Founders Are Missing with Jonathan David Nelson | Ep279

Ignite AI: Dennis Mortensen on Startup Failure, AI Agents, and Why Boring SaaS Problems Win | Ep278

Ignite VC: Charlie O’Donnell on Founder Unfriendly and the Real Game of Startup Fundraising | Ep277

Ignite Design: Lauren Von Dehsen on Scaling UX, AI Design Tools, and Product Leadership | Ep276

Ignite Startups: How ChargeMate Is Fixing EV Charging Reliability with AI with Brad Crist | Ep275

Om

Information

Du kanske också gillar

Ignite: Conversations on Startups, Venture Capital, Tech, Future, and Society

Avsnitt

Ignite Product: Jeff Gothelf on Lean UX and Product Strategy in the Age of AI | Ep282

Ignite Startups: How Adam Nash Built Daffy Into a $1B Donor-Advised Fund Platform | Ep281

Ignite VC: How Jeffrey Becker Bets on Founders Before Product, Revenue, or Traction | Ep280

Ignite VC: The Capital Markets Hack Founders Are Missing with Jonathan David Nelson | Ep279

Ignite AI: Dennis Mortensen on Startup Failure, AI Agents, and Why Boring SaaS Problems Win | Ep278

Ignite VC: Charlie O’Donnell on Founder Unfriendly and the Real Game of Startup Fundraising | Ep277

Ignite Design: Lauren Von Dehsen on Scaling UX, AI Design Tools, and Product Leadership | Ep276

Ignite Startups: How ChargeMate Is Fixing EV Charging Reliability with AI with Brad Crist | Ep275

Om

Information

Du kanske också gillar