EO StudioHow an 18-Year-Old High School Dropout Raised $6.2M | Nozomio, Arlan Rakhmetzhanov
CHAPTERS
- 0:00 – 1:06
Meet Arlan: 18-year-old YC founder building Nozomio (and the PG car-chase teaser)
Arlan introduces himself as an 18-year-old high school dropout from Kazakhstan who just completed Y Combinator. He sets up the story of chasing Paul Graham after a talk—an example of his “start before you’re ready” approach.
- •Background: Kazakhstan, dropped out of 11th grade, relocated to San Francisco
- •Just finished YC Summer 2025 batch
- •Teases how he got Paul Graham’s attention (running to his car, emailing instantly)
- •Frames the theme: boldness and initiative early
- 1:06 – 1:36
What Nozomio builds: Nea API to reduce coding-agent hallucinations
He explains Nozomio’s mission and flagship product, Nea, positioning it as infrastructure for more reliable coding agents. The product promise is tangible: less hallucination, faster shipping, and time saved per developer each week.
- •Nozomio is a product lab building “context super intelligence”
- •Nea is an API improving context for coding agents like Cursor
- •Goal: reduce code hallucinations and speed up development
- •Impact claim: save ~2–5 hours per person per week
- 1:36 – 2:07
Early ambition shaped at home: discovering YC and Silicon Valley as a kid
Arlan credits his parents—especially his dad’s construction-tech background—for exposing him to startups early. Hearing about YC at age 10 planted a long-term goal even before he understood Silicon Valley.
- •Dad had ~20 years in construction tech and talked about startups at home
- •First heard about YC around age 10 during a walk in Almaty
- •Silicon Valley/YC initially felt abstract, later became a clear target
- •Family influence set an “aim big” mindset early
- 2:07 – 2:37
The Stanford fixation—and why optimizing for university can be a trap
He describes how high school culture pushed him toward elite university admissions, making Stanford the central goal. Over time, he realized the biggest university value is community—and that prestige alone doesn’t guarantee a good outcome.
- •High school peers prioritized grades and top universities
- •He pursued extracurriculars mainly to strengthen applications
- •Realization: the most valuable part of university is the network/community
- •Prestige can still lead to a “ruined” path if you’re not intentional
- 2:37 – 3:37
First product at 15: an early AI counselor that hit 20K users
Arlan recounts learning to code and quickly shipping a product in the early ChatGPT era. The project gained real traction and revenue, but he admits the initial motivation was admissions-driven rather than a long-term startup mission.
- •First coding class at 15 in Kazakhstan
- •Built an AI scholarship/counselor tool for summer program applications
- •Reached ~20,000 active users and made a few thousand dollars
- •Initially treated as a resume/applications asset, not a lifelong company
- 3:37 – 4:10
Dropping out and choosing accelerators over the traditional path
He explains the mental shift away from university as the default, reinforced by his dad’s YC rejection and his own desire to accelerate learning. His strategy became to seek environments that compress years of progress into months.
- •Noticed a harmful pattern: wanting startups but still optimizing for university
- •Dad applied to YC, got rejected—motivated Arlan to try earlier
- •Belief: YC/accelerators can “kickstart” a career faster than 4 years of school
- •Decision point: stop thinking in 10-year traditional timelines
- 4:10 – 5:11
Don’t start local: going global from day one (London → YC → SF)
Arlan shares his deliberate choice to build for global distribution and to embed himself in startup hubs. Acceptance into Entrepreneurs First in London forced a decisive move, and later YC acceptance triggered relocation to San Francisco.
- •Applied broadly to accelerators worldwide with a “global first” mindset
- •Accepted into Entrepreneurs First (London) → quit school and moved
- •Applied to YC while in London; celebrates the WhatsApp acceptance call
- •Relocated to San Francisco to build full-time in the ecosystem
- 5:11 – 6:11
Why Nea exists: the missing ‘up-to-date context’ for coding agents
He outlines the core technical/product insight behind Nea: coding agents can browse the web but still hallucinate without accurate, current documentation context. Nea began as a small Cursor plugin/server and grew into a larger commitment.
- •Heavy user of Copilot/Cursor; chose dev tools due to personal domain focus
- •Problem: agents lack reliable, up-to-date knowledge bases and docs context
- •Example: Cursor can hallucinate when docs/packages change (e.g., Vercel SDK)
- •Nea started small (plugin/server) and evolved into a full pivot
- 6:11 – 7:14
Distribution playbook for global dev tools: Product Hunt, Hacker News, founder outreach
Arlan argues that dev tools should default to worldwide distribution because the marginal cost is low. He highlights specific channels and a rapid build-launch-iterate loop to earn feedback and relationships across countries.
- •Rationale: dev tools are globally usable—no need to “start local”
- •Launch on global platforms like Product Hunt (Product of the Day)
- •Use Hacker News as a high-leverage YC-adjacent audience
- •Cold DMs/emails to YC founders and others to think bigger and iterate faster
- 7:14 – 8:14
Collison installations: founder-led onboarding that drove $11K MRR in 4 weeks
He adopts the Stripe founders’ early tactic of personally installing the product with users to uncover friction. By visiting YC founders’ homes/offices, documenting installs, and pairing it with merch and feedback, he rapidly grew revenue and adoption.
- •Explains “Collison installation” as sitting beside users to onboard and observe
- •He visited users in person to install the software and learn quickly
- •Shared installs publicly and gave merch to build goodwill and momentum
- •Results: ~11K MRR in 4 weeks; notable penetration in YC batches
- 8:14 – 8:45
Using brutal feedback as fuel: asking users to ‘roast’ the product
Arlan frames negative feedback as a competitive advantage when sought proactively. He explicitly invites harsh critique to accelerate iteration and avoid comfort-driven blind spots.
- •Actively asks customers to roast the product and point out flaws
- •Treats constructive criticism as the most valuable user signal
- •Maintains high tolerance for demoralizing input to improve faster
- •Connects feedback culture to YC/PG expectations
- 8:45 – 10:47
From public roast to angel check: how Paul Graham decided to invest
He recounts being criticized by Paul Graham for an unclear pitch, then taking immediate action to improve it. A bold follow-up (the car stop + memorable email subject) led to a longer meeting where PG evaluated the founder and billion-dollar potential—ending in an investment offer.
- •PG criticized the pitch publicly and warned fundraising would be hard
- •Arlan chased PG after the talk, got told to email, and emailed instantly
- •Email tactics: memorable subject + concise, clearer one-line pitch
- •Office hour in Palo Alto; highlighting Collison installs resonated with PG’s Stripe history
- •Outcome: PG offered to invest (pre-seed)
- 10:47 – 13:17
Cold email mechanics: better subject lines, fewer sentences, persistent follow-ups
Arlan breaks down what he learned from sending huge volumes of outreach emails starting at age 16. He explains why generic subjects fail, why brevity wins, and how sustained follow-up can convert a non-response into a yes.
- •Sent massive outreach to professors for opportunities; most ignored/rejected
- •Bad patterns: cliché subjects like “Inquiry/Exclusive/Seeking” feel bot-like
- •Good patterns: direct, curiosity-inducing subjects and 4–5 sentence max body
- •Example: persistence over two months led to a Stanford VC research opportunity
- •Rule: if they don’t respond, follow up repeatedly—determinism matters
- 13:17 – 14:38
Don’t limit yourself: curiosity and action as the real ‘talent’ advantage
He closes with a motivational thesis that extraordinary builders aren’t fundamentally different—they’re simply more curious and more willing to act. The key is breaking self-imposed ceilings and operating at a bigger scale through consistent doing.
- •People self-limit by assuming they aren’t ‘meant’ for big outcomes
- •Great builders/leaders are “the same people as you,” differentiated by curiosity
- •Staying curious into adulthood enables exploration and scale
- •Core advice: break barriers—“just do it” through action
