At 19, Zach Yadegari has raised $10 million for his new AI startup, Persona. The round, led by Vine Ventures, also includes Cory Levy, founder of Z Fellows, and Collective Global. It’s a headline-making milestone, but the path behind it is what many founders may find most useful.
In April 2025, Yadegari shared that 15 of the 18 universities he applied to had rejected him, including Harvard, Yale, and Stanford. He had a 4.0 GPA and a 34 ACT score. He enrolled at the University of Miami, but his story was already making a point: a prestigious institution’s decision is not a final verdict on what you can build.
Yadegari had started learning to program at seven. As a teenager, he built a gaming website that gave students access to games blocked on school networks, then sold it for about $100,000 at 16. Later, he co-founded Cal AI, a calorie-tracking app that passed 15 million downloads and more than $30 million in annual revenue within two years. MyFitnessPal acquired the company in March 2026. Yadegari left in June. Now he is building Persona.
The big lesson isn’t that rejection automatically leads to success. It’s that rejection doesn’t have to be permission to stop. For entrepreneurs waiting on a credential, a green light, or the perfect moment, Yadegari’s story is a timely reminder: progress often starts when you put a real idea in front of real people.
The rejection was a headline. Building was the work.
It’s easy to focus on the 15 rejections. It’s also easy to turn the story into a neat formula: get rejected, prove everyone wrong, raise millions. Real entrepreneurial journeys are messier than that.
A college decision does not tell you whether customers will use your product. A funding announcement does not prove that a new business has found lasting demand. And a founder’s age does not explain the time, experimentation, and execution behind a company.
What the timeline does show is a repeated willingness to make things and put them into the world. Yadegari learned to code, built a website, sold it, helped grow an app, and moved on to a new challenge. Each step created experience that a rejection letter could not provide.
That’s useful whether you’re building a startup, growing a small business, or developing a creative career. Your first version does not have to be impressive. It has to give you something real to learn from.
Ship something small enough to learn from
Persona is an ambitious bet: a personal AI assistant with a planned screenless wristband. While the device is still in development, the company has introduced a free beta through iMessage. The $179 band is expected to ship in December 2026, and early reports describe a few thousand beta users and five figures in preorder revenue.
That distinction matters. The product’s promises still need to stand up to everyday use, and preorders are not the same as long-term customer satisfaction. But beginning with a beta gives the team a way to test interest in its core idea before the hardware is in customers’ hands.
Founders can use the same principle without raising venture capital or making a device. If you’re thinking about launching a service, try it with a few customers before designing a whole business around it. If you’re developing software, test the central feature before building every menu and setting. If you’re a creator, share a sample or a small first release and listen closely to the response.
The question is not “Can I build the complete version?” Start with: What’s the smallest useful version someone can try?
Move from guesses to evidence
A founder can spend weeks debating what customers might want. A small test can replace some of that guessing with evidence.
Before investing in a polished product, write down the assumption that matters most. Maybe it’s that people will pay for your service, use an app more than once, or trust a new tool with a particular task. Then find a low-cost way to test that assumption.
Try these steps:
- Name one audience. Be specific about who has the problem. “Small-business owners” may be too broad; “independent cafés that need help promoting weekly events” gives you a clearer place to start.
- Describe one frustration. Focus on a problem people already experience, not just a feature you’re excited to build.
- Offer a simple test. That might be a paid pilot, a prototype, a sample, or a manually delivered version of the service.
- Watch what people do. Compliments are nice, but repeat use, payment, referrals, and thoughtful feedback are stronger signals.
- Change one thing at a time. Use what you learn to improve the offer, then test again.
You don’t need every answer before you begin. You do need a way to notice whether your idea is helping.
Build in public, at a pace that fits you
Yadegari’s university rejections became public, and that visibility helped make his story widely known. But building in public doesn’t mean sharing every setback or turning your life into a constant performance.
It can be as simple as showing how you work: explaining why you chose a particular feature, sharing a lesson from a customer conversation, or documenting what changed after your first test. Done thoughtfully, that kind of communication helps people understand what you’re building and why.
There’s a practical benefit, too. When you explain an idea in plain language, you can see where it’s still fuzzy. When people respond, their questions may reveal an issue you hadn’t considered, or an opportunity worth exploring.
Choose boundaries that feel right. Share the learning, not information you need to keep private. Your goal is not to look like you have everything figured out. It’s to make your progress legible and invite useful feedback.
Treat permission as optional, not your business model
Credentials, investors, partnerships, and institutional support can open doors. They can also be valuable. But they aren’t the only way to begin.
If you’re waiting for someone to tell you that you’re qualified, consider what you can demonstrate instead. A working prototype can show initiative. A paying customer can validate a need. A consistent body of work can establish credibility. A small project can give you experience you don’t yet have on paper.
That doesn’t mean ignoring risk or making reckless decisions. Keep your commitments realistic. Be honest about what your product can do. Protect your time and finances. Ask for advice when the stakes are high. Moving before you feel fully ready is not the same as moving without thought.
And remember that Yadegari’s outcome is exceptional. Most founders will not raise $10 million at 19, and they don’t need to. The more transferable lesson is the habit of turning an idea into a test, then using what happens to decide what comes next.
Your next step can be smaller than your ambition
Persona’s funding marks a major new chapter for Yadegari, but the business still has to deliver on its product and earn users’ trust. That’s part of what makes the story worth watching: an exciting announcement is a beginning, not a guarantee.
For every founder, the next move can be modest and still matter. Write down the problem you want to solve. Talk to three people who experience it. Make a rough demo, run a pilot, or offer a simple first version. Set a date to review what you learned.
The entrepreneurs and builders we feature don’t all take the same route. But a common thread is the willingness to keep learning through action.
A rejection can sting. A missing credential can feel like a closed door. A green light may never arrive. You can acknowledge those realities without letting them decide what you try next.
Start with the part you can build today. Show it to someone who might use it. Listen, adjust, and keep going.