EO StudioSilicon Valley’s Top Investors Bet on This 22-Year-Old Founder | Sola, Jessica Wu
CHAPTERS
- 0:00 – 1:00
Choosing startups over stability: ownership, optionality, and happiness
Jessica contrasts the misery of a conventional finance job with the energy she gets from building her own company. She frames the decision to pursue startups as a question of optionality, personal fit, and feeling fulfilled day-to-day.
- •Working fewer hours can still feel worse if you don’t own the work
- •Startups can mean nonstop work but higher intrinsic motivation
- •Optionality (especially when young) enables bigger career bets
- •Use “what feels right” and fulfillment as decision criteria
- 1:00 – 1:30
What Sola does and why investors are betting on it
Jessica introduces Sola as an agentic process automation platform that modernizes RPA with AI for enterprise workflows. She highlights rapid growth, enterprise traction, and recent fundraising from top-tier firms.
- •Sola automates critical operational workflows with AI, faster than legacy RPA
- •Originated at YC ~2 years prior
- •Seed led by Conviction; Series A led by a16z
- •Metrics: 5x revenue growth; execution volume doubling MoM
- •Customers include Fortune 100, AM Law 100, logistics and healthcare leaders
- 1:30 – 3:31
Competitive upbringing and MIT: building discipline and resilience
She connects competitive piano/math and her MIT environment to a mindset of discipline, risk-taking, and learning quickly. MIT’s culture of ambitious technical experimentation becomes a foundation for tackling hard problems.
- •Competition built willpower, discipline, and comfort with pressure
- •Risk-taking before feeling “ready” builds resilience
- •MIT as a high-density learning environment (“dumbest person in the room”)
- •Exposure to frontier research helps adapt in fast-changing tech
- 3:31 – 4:01
First-principles problem solving in an era of constant model change
Jessica explains how a technical background helps simplify problems and stay anchored to customer needs despite rapid AI progress. The emphasis is on identifying root causes rather than building for surface-level complaints.
- •Break complex problems into simple, communicable components
- •Center on the customer’s real job-to-be-done
- •Avoid being distracted by weekly model releases and hype cycles
- •Root-cause focus enables outsized value delivery
- 4:01 – 5:31
From finance and quant research to founder: rational decision-making under emotion
Her time in venture and hedge funds taught her to think in odds, remain objective, and apply statistical frameworks—useful counterweights to the emotional volatility of startups. She likens startup choices to poker-style expected value decisions.
- •Youngest quant researcher experience shaped analytical rigor
- •Finance taught objectivity and “calculate the odds” thinking
- •Startups are emotional; first-principles + probabilistic thinking help
- •Decisions (customers, features, deployments) can be framed as trade-offs
- 5:31 – 7:02
The “oldest inconvenience” becomes the opportunity: brittle enterprise workflows
Sola’s genesis came from witnessing massive manual work inside legacy systems at hedge funds and hospitals. She explains RPA basics and why existing tools were hard to use, brittle, and disconnected from how real companies operate.
- •Legacy brokerage and hospital systems required heavy manual operations
- •RPA automates human-like UI actions (clicking, typing, moving through apps)
- •Even with CS background, building simple automation was hard
- •Real-world ops spans spreadsheets, portals, files, and disconnected systems
- 7:02 – 8:33
YC search phase and MVP evolution: recorder to scalable orchestration
During YC, the team narrowed from broad curiosity to the RPA/AI wedge and built a minimal initial product. Over time, Sola expanded from local playback to scalable execution, granular editing, logic, and orchestration across many VMs.
- •Entered YC without a fixed plan; spent ~1 month deciding what to build
- •MVP: simple workflow recorder + upload + replay on one machine
- •Product matured: run across hundreds of VMs, edit steps, add logic
- •Balancing ambition vs. shipping something useful quickly
- 8:33 – 9:38
Saying no early: turning down revenue to protect product focus
Jessica describes difficult early trade-offs, including declining big-name customers when the team wasn’t ready or when requests would derail the roadmap. The chapter emphasizes focus and capacity management as existential for early-stage teams.
- •Legacy incumbents have 20-year feature depth; startups must prioritize
- •Early-stage teams get pulled in many directions
- •Turning down exciting revenue can be necessary to build the core product
- •Avoid customer commitments that force damaging trade-offs
- 9:38 – 11:08
The counterintuitive YC playbook: sell first, then build
She explains YC’s push to validate demand before overbuilding, even using mock or minimal front-ends. While unintuitive and risky, it creates fast “yes/no” clarity and forces teams to align on what customers will pay for.
- •YC encourages selling even without a fully working product
- •Mockups/minimal “fake” versions can test willingness to pay
- •Validation is strongest when customers pay (and keep paying)
- •Risk: potential bridge-burning; must be honest and deliver quickly afterward
- 11:08 – 12:08
Stop overbuilding, start selling: early customer discovery in practice
Jessica recounts meeting an early customer during YC by pitching a product that didn’t exist yet—paired with transparency about timelines. The takeaway is to invert the typical build-then-sell pattern to speed learning and iteration.
- •First customer conversation happened very early around YC
- •They disclosed the product wasn’t ready; customer asked to revisit later
- •Selling-first runs counter to traditional “finish then present” training
- •If you do sell early, you must execute fast to deliver
- 12:08 – 13:39
Delivering Happiness: customer delight as a growth engine
Drawing from the book Delivering Happiness, Jessica argues that customer experience is the compounding advantage for an early enterprise startup. Word-of-mouth growth comes from shipping fast, listening deeply, and being exceptionally supportive.
- •Customer delight as a North Star beyond “on-time delivery”
- •Trust barrier is high for software running critical operations
- •Most customers come via word of mouth from strong experiences
- •Weekly feedback loops with design partners and rapid iteration
- 13:39 – 15:09
Enterprise-grade reliability and “above-and-beyond” deployments
She illustrates the stakes of operational automation: downtime can halt invoicing, shipping, or patient data workflows. A story of a Christmas Day deployment highlights the team’s commitment to reliability and customer trust.
- •Critical workflows mean Sola “can never go down”
- •Examples: invoices/AP, shipments, patient data entry
- •Christmas Day deployment to minimize customer risk during low volume
- •Early-stage teams compete by reliability, responsiveness, and support
- 15:09 – 17:26
Playing the long game: surviving the founder rollercoaster for 10+ years
Jessica closes on the psychological realities of startups—rapid swings, bad news, and constant uncertainty—and how teams learn resilience over time. She emphasizes choosing a mission you can pursue for a decade and the belief that automating rote work frees humans for more meaningful work.
- •Founding is a compressed cycle of extreme highs and lows
- •Perspective comes from pattern recognition: crises usually normalize
- •Endurance requires a market big enough for a 10-year effort
- •Mission: eliminate manual drudgery so people focus on creative, strategic work
