The Twenty Minute VCJoost de Valk: How I Founded Yoast; The Ultimate Guide to SEO; The Threat of AI | E1000
CHAPTERS
- 0:00 – 3:42
From hobby plugin to breakout revenue: the moment Yoast became a business
Joost explains how the Yoast SEO plugin started as a set of small, specific SEO plugins and got pulled together after repeated user demand for “one plugin that does it all.” The turning point came when an add-on monetization experiment far outperformed expectations, proving there was a real company opportunity.
- •Combined multiple niche SEO plugins into a single “do it all” plugin
- •Framed SEO as technical foundations + content guidance
- •Focused on removing technical SEO burden and giving actionable content feedback
- •Monetization catalyst: first paid add-on hit €100K+ in the first month
- •Lifestyle-business origins rather than a grand startup plan
- 3:42 – 5:51
Why Yoast stayed bootstrapped: cash flow, lifestyle goals, and low capex software
Harry pushes on why Yoast never raised outside capital despite rapid traction. Joost argues they didn’t need it: the business generated enough cash, and the main cost lever was hiring people rather than expensive infrastructure or inventory.
- •No early intention to build a huge venture-scale company
- •Growing alongside WordPress created powerful organic tailwinds
- •Bootstrapping fit family/lifestyle priorities at the time
- •Software economics: people are the main cost; cash needs were limited
- •Blissful ignorance about “go faster with capital” was beneficial in hindsight
- 5:51 – 7:13
Hindsight lessons: hiring, optimizing for fun vs. profit, and company scale realities
Joost reflects on what he might change if he could go back—mainly being more conservative with hiring at certain points. He emphasizes that many decisions were made because they were enjoyable or aligned with values, not because they maximized exit value.
- •Hindsight is easy; outcomes weren’t planned from the start
- •Potential over-hiring at times, especially relative to revenue scale
- •Yoast’s headcount is modest considering the huge user base
- •A lot of decisions were driven by curiosity and enjoyment
- •Few major regrets despite alternative “optimization” paths
- 7:13 – 9:56
Open source + freemium is hard: conversion design, forks, and ‘web-scale problems’
Joost breaks down why freemium is inherently tricky (what’s free vs. paid) and why open source adds a unique risk: if premium feels too restrictive, people can fork it. He highlights the mismatch between massive usage and comparatively small revenue, creating operational pressure.
- •Freemium challenge: balancing adoption with premium conversion
- •Open-source challenge: premium features can be forked if trust breaks
- •Requires deep trust and consistent superiority vs. alternatives
- •‘Web scale problems, small company income’ dynamic
- •WordPress’s massive footprint is still underestimated by investors
- 9:56 – 11:52
Brand and community as the moat: what VCs miss in open source businesses
The conversation shifts to what actually drives durable advantage in open source: brand and community alignment. Joost argues WordPress’s enduring power comes from people and culture, and that open source investing requires understanding those social dynamics—not just code.
- •Branding is the most underestimated lever in open source
- •Community gravity: “Come for the software, stay for the people”
- •Open source is built ‘in the open’—a different company-building rhythm
- •What’s sold is often brand + trust, not just copyable software
- •VCs often misunderstand the model; there’s an open market for better investors
- 11:52 – 16:49
Developer-led brands and ‘decisions, not options’: product simplicity at scale
Joost explains the tension between serving power users and keeping the product usable for everyone. He emphasizes defaults as the true product for most users and cites WordPress philosophy—avoid unnecessary options and make strong decisions for the majority.
- •Avoid over-optimizing only for power users; most users want simplicity
- •Keep UI minimal while doing advanced work automatically under the hood
- •Defaults matter because most users never touch settings
- •WordPress principle: “decisions, not options”
- •Operational advantage: ship quickly when Google changes and adapt fast
- 16:49 – 18:11
Biggest product mistake: building features without usage data (and fixing it with telemetry)
Joost names the core product misstep: assuming users relied on features that were rarely used. Because plugin ecosystems often lack built-in telemetry, Yoast initially built in the dark and later corrected course by adding tracking and refocusing on where users actually work—inside the editor.
- •Built features without knowing whether they were used
- •WordPress plugins historically lacked rich telemetry feedback loops
- •Adding tracking revealed wasted effort on low-use functionality
- •Shifted effort to the editor experience (SEO + readability guidance)
- •Reinforced focus on real user interaction points, not theoretical features
- 18:11 – 24:26
Freemium in a tougher macro: cheap pricing, scrappy teams, and platform risk
They discuss how freemium changes when purchasing power shifts toward CFOs and budgets tighten. Joost argues many freemium startups carry enterprise-style cost structures that don’t match low ACVs, and he warns about becoming easy to replace when big platforms ship adjacent features.
- •Macro shift can reduce frontline purchasing autonomy
- •Yoast-like pricing (€99/yr) is easier to approve than enterprise tools
- •Mismatch risk: enterprise org structure + freemium price points
- •Scrappy operations and reasonable pricing can be strategic advantages
- •Platform bundling risk: incumbents can replicate ‘thin’ paid value quickly
- 24:26 – 28:02
What it means to invest in SEO: product-language fit, CMS choices, and content fundamentals
Joost reframes SEO as more than tactics: it starts with understanding what users search for and how they describe their problems. Practical execution requires a technically solid platform and consistent content creation—often founder-led early on.
- •Founders should learn SEO basics because it sharpens product messaging
- •SEO starts with mapping user problems to real search language
- •Two pillars: technical foundation + content production
- •Strong bias toward WordPress as a cost-effective SEO-friendly CMS
- •Early-stage content often has to come directly from the founder
- 28:02 – 31:36
When to start SEO and the early traps: brand names, invented categories, and demand limits
Joost advises starting SEO early in a lightweight way—choose an SEO-friendly stack and turn repeated support answers into knowledge-base content. He cautions founders against unmemorable branding and against inventing new terms that users aren’t searching for, since SEO captures existing demand rather than creating it.
- •Start early with fundamentals; don’t begin by hiring expensive consultants
- •Convert recurring customer support questions into indexed help content
- •Choose memorable, recognizable brand names for repeated SERP exposure
- •Avoid “clever” new category terms; use the language customers already use
- •SEO is demand-driven; brand and other channels help create demand
- 31:36 – 36:31
SEO org design, budgeting, and measurement reality: attribution is imperfect
The conversation gets operational: where SEO sits in an org, why it gets harder as companies ship faster, and how to allocate budget. Joost recommends reallocating a slice of paid spend and warns that SEO impact can’t be cleanly measured because Google obscures keyword data and attribution is biased toward last-click.
- •SEO specialists become valuable as teams scale and shipping accelerates
- •SEO must collaborate with product, dev, content, and comms/PR
- •Budget heuristic: move ~10% of CPC spend into SEO and iterate
- •Attribution is structurally difficult; Google limits keyword visibility
- •Not everything measurable matters—and not everything that matters is measurable
- 36:31 – 40:13
Best vs. worst SEO teams: stop obsessing over minor tech fixes; build story + content that serves users
Joost contrasts ineffective teams that grind through long technical checklists with strong teams that fix only the biggest issues and focus on narrative, intent, and user needs. He links SEO success to clarity of brand story and to creating content people actually want to read, share, and revisit.
- •Worst teams: months of low-impact technical tweaks while the story is weak
- •Best teams: prioritize brand narrative, then address major technical blockers
- •SEO success depends on content that matches user intent and solves problems
- •For horizontal products: create use-case pages and customer stories by vertical
- •Organic growth can be strong when combined with clear positioning and UX
- 40:13 – 46:41
AI and the future of SEO/content: hallucinations, authorship signals, and quality amid a content flood
Joost argues AI will accelerate content workflows but still struggles with truthfulness, so human uniqueness and editorial responsibility become more valuable. He predicts search engines will lean harder on expertise/authority/trust and author credibility to filter an explosion of low-quality, AI-generated pages.
- •AI hallucinations make fully automated content risky without oversight
- •High-value uses: outlines, summaries, excerpts, and research distillation
- •Uniqueness and creativity become differentiators as supply explodes
- •Prediction: author credibility and E-E-A-T style signals become more important
- •Yoast-style scoring can cause over-optimization; focus on overall quality for users
- 46:41 – 55:43
The problems with AI: transparency, training data rights, regulation, and societal impact
The discussion broadens from SEO to AI governance and ethics. Joost calls for transparency about training data and explores licensing/robots-style controls, then shifts to concerns about productivity shocks, explainability, prompting literacy, and worsening wealth inequality.
- •Transparency concern: users should know what LLMs were trained on
- •Training data ownership and compensation remains unresolved
- •Need for licensing and potential ‘robots.txt for LLMs’ style controls
- •AI as a steam-engine-level productivity shift, but hype is still hype
- •Risks: explainability gaps, prompting skills divide, and increased wealth inequality
- 55:43 – 1:02:00
Angel investing playbook and quick-fire: check size, involvement, and what impresses him in growth
Joost shares how he approaches angel investing—preferring meaningful checks and founders focused on building sustainable products rather than plotting fundraising calendars. In quick-fire, he reiterates core themes: branding, limits of measurement, work-life design, and admiration for strong developer marketing and docs.
- •Prefers larger checks (~€100–200K) and faster path to sustainability
- •Avoids founders who plan rounds more than product delivery
- •High involvement: shared Slack channels; frequent founder interaction
- •Quick-fire themes: branding-first SEO, measurement limits, realistic work-life balance
- •Impressed by Bing’s AI push and developer-first growth (e.g., Algolia, great docs)
