SUCCESS-STORY · 2026-02-26 · 5 MIN READ

How a Teacher Sold Her Cursor-Built App for $15K

Sarah Martinez had been teaching middle school math for eight years. She'd never written a line of code. By December 2025, she'd sold an app she built

BY BIREXIT TEAM

·

2026-02-26

·
How a Teacher Sold Her Cursor-Built App for $15K
TAGS:SUCCESS-STORYVIBE-CODINGEXITCURSORNON-TECHNICAL-FOUNDEREDUCATION

How a Teacher Sold Her Cursor-Built App for $15K

Sarah Martinez had been teaching middle school math for eight years. She'd never written a line of code. By December 2025, she'd sold an app she built with Cursor for $15,000.

This isn't a fairy tale. It's a blueprint.

The Problem That Started Everything

Every teacher knows the frustration: you spend hours creating worksheets, only to watch students zone out. Sarah was tired of it. She wanted something interactive - a tool that would let students practice math problems and get instant feedback.

"I searched everywhere," she told me. "Everything was either too expensive for my budget or too complicated for what I needed."

So she decided to build it herself.

Week 1: From "I Can't Code" to Working Prototype

Sarah had heard about Cursor from a TikTok video. She downloaded it on a Saturday morning with zero expectations.

"I just started typing what I wanted," she said. "Like I was texting a friend who happened to know how to code."

Her first prompt was simple: "Create a web app where students can practice multiplication tables and get immediate feedback."

Three hours later, she had something that worked.

"I kept waiting for it to stop working. Like, there's no way this is real. But it just... kept working."

Week 2-4: Adding Features Without Understanding Code

What started as a multiplication trainer evolved. Sarah kept prompting:

  • "Add a progress tracker so students can see their improvement"
  • "Create different difficulty levels"
  • "Add a teacher dashboard where I can see which students are struggling"
  • "Make it work on phones because my students don't have computers at home"

Each request, Cursor handled. When things broke (and they did), Sarah just described the problem and asked for a fix.

"I never felt like I was coding," she explained. "I was just... directing. Like being a movie director who doesn't know how to operate a camera but knows exactly what scene they want."

Month 2: From Personal Tool to Side Hustle

Sarah shared her app with other teachers at her school. Word spread. Teachers from neighboring districts started asking for access.

She did something smart: she added Stripe payments (again, just by asking Cursor) and started charging $5/month per classroom.

By the end of month two, she had 47 paying teachers and $235 in monthly recurring revenue.

"It wasn't life-changing money," she said. "But it was proof. Proof that people would pay for something I made."

The Unexpected Message

In month three, Sarah received a LinkedIn message from an EdTech company. They'd found her app through a teacher who'd been raving about it in a Facebook group.

Their opening offer: $8,000.

Sarah almost said yes immediately. Instead, she did something that changed everything.

The Exit: From $8K to $15K

Sarah asked a simple question: "Why do you want to buy this?"

The answer revealed everything. The company had been trying to build a similar feature for months. Their development team quoted $40,000 and six months of work. Sarah's app already worked, already had users, and already had proven demand.

She countered at $20,000. They settled at $15,000.

"I still can't believe I negotiated," she laughed. "Me! Negotiating with a tech company!"

What Made Her App Sellable

Looking back, Sarah identified five factors that made her app attractive to buyers:

1. Real Users, Real Feedback

She didn't just build it - she used it with her own students. Every feature came from actual classroom needs, not assumptions about what teachers might want.

2. Clean, Working Code

"Cursor doesn't write spaghetti code," the buyer told her during due diligence. "It's actually easier to maintain than some stuff our own team writes."

3. Documented Everything

Sarah kept a simple Google Doc with every prompt she used and why. When the buyer asked how features worked, she could explain the intent even without understanding the technical implementation.

4. Proven Revenue

$235/month might seem small, but it proved the business model. The buyer saw a path to scaling what already worked.

5. Niche Focus

She didn't try to build "the everything education app." She built a math practice tool that did one thing exceptionally well.

The Transfer: Easier Than Expected

Sarah was terrified about the handoff. "What if they ask me technical questions I can't answer?"

It turned out not to matter. She transferred:

  • The GitHub repository (Cursor had been saving everything there)
  • Her Stripe account access
  • The domain name
  • Her prompt documentation

The buyer's team took it from there. They even said her documentation was better than what they got from acquired startups with "real" developers.

What Sarah Would Do Differently

Not much, actually. But she shared two regrets:

  1. Started charging earlier. "I gave it away free for too long. I should've charged from week two."

  2. Talked to potential buyers sooner. "I didn't even know selling was an option until someone approached me. If I'd known, I might have built with exit in mind."

The Bigger Lesson

Sarah's story isn't about getting lucky. It's about a fundamental shift in who gets to build and sell software.

"A year ago, I thought tech was for tech people," she said. "Now I know that's not true. Tech is for anyone with a problem worth solving."

She's already working on her second app - this time for tracking student reading progress. And yes, she's building it with exit in mind.

"The $15K was nice," she admitted. "But you know what's nicer? Knowing I can do it again."

Key Takeaways for Non-Technical Builders

  1. Start with a problem you personally experience. Sarah built for herself first.

  2. Ship ugly, iterate fast. Her first version looked terrible. It didn't matter.

  3. Get paying users before seeking buyers. Revenue, even small revenue, proves everything.

  4. Document your prompts. It's the closest thing to documentation you'll have.

  5. Don't undersell yourself. If someone wants to buy, there's a reason. Find out what it is.

Ready to build your own vibe-coded app? The tools have never been more accessible. The only question is: what problem will you solve?

TAGS:SUCCESS-STORYVIBE-CODINGEXITCURSORNON-TECHNICAL-FOUNDEREDUCATION

RELATED POSTS