The Indie Hacker Podcast with Fexingo · 2026-07-01 · 9 min
Key moments - from our scoring
Substance score
56 / 100
Five dimensions, 20 points each
The university market represents an overlooked opportunity for indie hackers willing to navigate higher education's reputation for bureaucratic slowness. Dan, a computer science graduate who started CourseFlow as a personal tool while TAing, discovered that academic departments have dedicated course material budgets separate from IT spending - a crucial insight that shortened approval cycles compared to traditional B2B sales. By pricing at $500 per course per year (rather than per-seat licensing), he aligned with how universities actually allocate budget lines. His growth came primarily from two academic conferences - the Modern Language Association and American Historical Association meetings - where department chairs actively seek solutions. A 40% free-to-paid conversion and 90% annual retention created a highly efficient, low-touch business model. The academic calendar's August renewal spike provides predictable revenue timing. Dan built CourseFlow on a $20 DigitalOcean droplet using Ruby on Rails and Bootstrap, proving that standardized products in non-sexy verticals can scale profitably without external funding or large sales teams. His current $18K MRR comes from roughly 36 paid courses across multiple institutions, with plans to scale to $30K MRR solo before hiring.
Dan charged $500 per course per year and framed it as a course tool rather than software, so it came out of department teaching budgets instead of IT budgets - making approval much faster than traditional per-seat SaaS pricing.
His computer science department (10 courses), the English department where a professor had already asked to use the tool (3 courses), and then academic conferences where he signed 12 more departments from two events at the Modern Language Association and American Historical Association.
90% annual retention, because once professors built syllabi and assignments into CourseFlow, the switching cost became prohibitively high for departments - keeping them locked in with minimal churn.
He built the first version in a weekend using Ruby on Rails, Bootstrap, and PostgreSQL, hosted on a $20/month DigitalOcean droplet, and spent only on conference fees - completely bootstrapped with no outside funding.
Dan believes he can scale to $30K MRR as a solo founder before needing to hire, since CourseFlow is simple, gets one to two support emails per day during the school year, and requires minimal maintenance in summer.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode delivers several actionable, non-obvious insights - per-course vs. per-seat pricing strategy aligned with department budgets, conference-driven sales in academia, 90% retention dynamics, and the academic calendar renewal spike. However, it relies on a single case study and lacks depth on execution challenges, competitive landscape, or failure modes. Some segments (e.g., the closing advice on talking to users) are familiar indie hacker platitudes.
By framing it as a 'course tool' at $500 per course, it came out of a teaching budget, not an IT budget. That made the approval path much shorter.
He attended two academic conferences - the annual meeting for the Modern Language Association and the American Historical Association. He spent maybe $2K total on registration and a tiny booth. But he signed contracts with twelve new departments from those two events.
The framing of universities as an underexploited vertical for indie hackers is relatively fresh, and the per-course pricing workaround is a specific insight. However, the core narrative - finding a niche, building a simple MVP, using conferences to sell - follows well-worn indie hacker playbook beats. The advice to 'talk to users and build what they need' is standard.
Universities are overlooked by indie hackers because of the stereotype that they're slow and bureaucratic. But if you price correctly and align with existing budgets, the sales cycle can actually be shorter than selling to mid-market businesses.
By framing it as a 'course tool' at $500 per course, it came out of a teaching budget, not an IT budget.
This is a critical weakness: the episode does not feature an actual guest. 'Dan' is an unnamed, secondhand case study relayed by the hosts. Lucas cites Dan's data and decisions but never interviews him directly. For a B2B audience evaluating a real business model, hearing from the actual operator - not a retelling - would be essential. The guest caliber is therefore minimal.
Dan told me that university departments have line-item budgets for course materials, not for software seats.
Dan said the conversion rate from free trial to paid was about forty percent.
The episode contains concrete metrics: $500 per course, $10K MRR by month ten, 20 courses, 90% retention, 40% trial-to-paid conversion, 12 conference deals, $2K conference spend, and $18K current MRR. However, evidence is limited to one case study with no comparable benchmarks, no failure examples, and no named companies beyond the fictional 'CourseFlow.' The numbers feel cherry-picked rather than representative.
Within six months, he had seven departments paying $500 per course per year.
By the end of year one, he had twenty courses under license - that's $10K per month in annualized revenue.
Lucas and Luna maintain a friendly dynamic and ask logical follow-up questions (pricing model reasoning, scaling challenges, initial dev costs). However, the conversation rarely pushes back or exposes tension. There is no genuine skepticism - e.g., why universities specifically, what fails, how competitive is the space, or probing on the $20 hosting claim. The hosts seem to affirm each insight rather than interrogate it.
Luna: Wait - per course pricing. So a department with thirty courses would pay fifteen thousand dollars a year?
Luna: That's a good problem to have. But it also raises the question - can you stay solo at that level?
Computed from the transcript - who did the talking, and the words that came up most.
Episode 84 of The Indie Hacker Podcast dives into a fresh playbook: selling SaaS to universities as a solo developer. Lucas and Luna unpack the story of a solo dev who built a simple syllabus-sharing tool called CourseFlow, hit $10K MRR by licensing it directly to university departments, and did it without any VC funding or a dedicated sales team. They break down the specific tactics - starting with one professor, leveraging academic conferences for distribution, and pricing per course - that made it work. Along the way, they discuss how university procurement differs from B2B or B2C, why the academic calendar creates predictable revenue spikes, and what any indie hacker can learn about selling into slow-moving but high-retention verticals. This episode is packed with concrete numbers, including a $500 per-course annual license and a 90% retention rate. If you've ever wondered whether your dev tool or niche SaaS could find a home in higher ed, this is a practical blueprint.
Transcribed and scored by The B2B Podcast Index.
Lucas: You hear 'indie hacker' and you usually think consumer app or B2B tool for startups. But there's a whole category of solo founders quietly selling to universities - and making real money. Luna: I've seen those numbers - higher ed procurement is notoriously slow. How does a solo dev even get through the door?
Lucas: That's exactly what we're unpacking today. I found a case study about a developer - let's call him Dan - who built a tool called CourseFlow. It's a simple web app that lets professors share syllabi, reading lists, and assignments across sections of the same course. Luna: So it replaces a shared drive or email chain.
Lucas: Exactly. Dan was a grad student in computer science at a mid-sized public university. He built it for himself and his teaching assistant gig. After he graduated, a professor in the English department asked if they could use it.
And that's where the lightbulb went off. Luna: He realized there was a real need. Lucas: Right. He spent about three months polishing it - adding role-based access, a simple LMS integration via LTI standard, and a clean interface.
Then he started reaching out to other departments at his own university. Within six months, he had seven departments paying $500 per course per year. Luna: Wait - per course pricing. So a department with thirty courses would pay fifteen thousand dollars a year?
Lucas: Exactly. And that's actually how he hit $10K MRR. By the end of year one, he had twenty courses under license - that's $10K per month in annualized revenue. Not all at once, but by month ten he had signed enough departments to cross that threshold.
Luna: What's interesting is the pricing model. Most SaaS charges per user. He went per course. Lucas: That was deliberate.
Dan told me that university departments have line-item budgets for course materials, not for software seats. By framing it as a 'course tool' at $500 per course, it came out of a teaching budget, not an IT budget. That made the approval path much shorter. Luna: So the procurement workaround is key.
How did he actually find the first few paying departments? Lucas: His own department was first - the CS department had ten courses, so that was $5K. Then he went to the English department where the professor who originally asked had pull. That was three courses.
Then he started cold-emailing department chairs at other universities. He focused on small liberal arts colleges where decisions happen faster. Luna: Did he do any conferences? Lucas: Yes, that was actually his biggest channel.
He attended two academic conferences - the annual meeting for the Modern Language Association and the American Historical Association. He spent maybe $2K total on registration and a tiny booth. But he signed contracts with twelve new departments from those two events. Luna: That's a great return.
And those conferences are where department chairs and deans actually walk around looking for solutions. Lucas: Exactly. He also had a free tier - one course free for a semester. That let professors try it without any paperwork.
After the semester, if they wanted to keep using it, the department had to pay. Dan said the conversion rate from free trial to paid was about forty percent. Luna: That's solid. What about churn?
Once a department buys in, do they stay? Lucas: This is the beautiful part. Dan shared his retention data - ninety percent annual retention. Once a department adopts it for multiple courses, they don't switch.
The switching cost is too high because professors have built their syllabi and assignments in the tool. Luna: That makes sense. And the academic calendar actually helps - you get a renewal spike every August. Lucas: Right.
Dan said August is his biggest month. He sends a simple renewal reminder email to department administrators, and most just approve. No sales call needed. He also added a feature that lets departments bulk-renew all courses with one click.
Luna: That's smart product design. It reduces friction for the buyer. Lucas: It's the same principle as an annual contract with auto-renew. But by aligning it with the academic calendar, it feels natural.
Now, the interesting challenge is scaling beyond a certain point. Dan is still solo - he does all the support, development, and billing himself. He's at about $18K MRR now, and he says he's starting to feel the pressure. Luna: That's a good problem to have.
But it also raises the question - can you stay solo at that level? Lucas: It depends on the product complexity. CourseFlow is pretty simple - it doesn't have a mobile app, it doesn't integrate with every LMS. Dan does maybe one or two support emails a day during the school year.
In summer, it's almost zero. He thinks he can go to $30K MRR before he needs to hire. Luna: That's a really clean business. And I think there's a broader lesson here about choosing the right vertical.
Lucas: Absolutely. Universities are overlooked by indie hackers because of the stereotype that they're slow and bureaucratic. But if you price correctly and align with existing budgets, the sales cycle can actually be shorter than selling to mid-market businesses. Plus, the retention is higher.
Luna: And you don't need a sales team. You just need to show up at the right conference and have a free trial. Lucas: Yeah. And the thing is, this playbook can work for a lot of tools - not just syllabus management.
Think about tools for research collaboration, alumni engagement, student advising. There's a whole ecosystem of academic needs that aren't well served by the big LMS players. Luna: If today's tech conversation gave you something usable... you know, we deliberately don't run ads on these episodes.
We think that keeps the advice cleaner. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Lucas: Yeah, it's a small way to keep this independent. Appreciate anyone who chips in.
Luna: Alright, back to the playbook. One thing I'm curious about - how did Dan handle the initial development cost? Was he bootstrapped from day one? Lucas: Completely.
He built the first version in a weekend using Ruby on Rails, Bootstrap, and PostgreSQL. Hosted on a $20 DigitalOcean droplet. His only costs were time and the conference fees. Luna: So no outside funding, no fancy infrastructure.
That's the indie hacker dream right there. Lucas: It really is. And I think the lesson for anyone listening is: look for pain points in non-sexy verticals. Universities, local governments, trade schools, religious organizations - these are all places where software is often terrible and buying decisions are simpler than you'd expect.
Luna: Do you think there's a ceiling to how big a solo dev can get in this space? Lucas: I think the ceiling is determined by how much customization each customer needs. If you can keep the product standardized, you can scale quite far. Dan's tool is basically the same for every department.
He just changes the logo and the course list. Luna: That makes it a product, not a service. Lucas: Exactly. And that's the key to staying solo.
If you have to build custom integrations for every university, you become a consultancy. But if you can say 'here's the product, here's the price, take it or leave it,' you can keep the margins high and the stress low. Luna: I love that. For anyone looking to follow this path, what would you say is the first step?
Lucas: Talk to one person who works in the vertical. Not a decision-maker at first - just someone who does the job. Ask them what tool they wish existed. Dan's entire product came from being a TA and thinking 'there has to be a better way to share syllabi.'
The insight was free. Luna: And then build the simplest version that solves that one problem. Lucas: Yes. No landing page, no social media posting, no marketing funnel.
Just a working tool that one person can use. Then show it to ten more people in the same role. If they all say 'I need this,' you have a business. Luna: That's the indie hacker way.
Lucas: It really is. And it works in surprising places. Universities are just one example - but the pattern repeats everywhere. Luna: Great episode.
Thanks, Lucas. Lucas: Thanks, Luna. See you next time.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.
#19 - Brooklyn Zelenka: UCAN, Beehive, Beelaylocalfirst.fm · on Role-based access control100 / 100
Governance Is Functions: Why Your AI Won't Scale Without Discipline by DesignDisambiguation · on Role-based access control87 / 100
Observability in the AI Era with New Relic's Nic BendersPlatform Engineering Podcast · on Ruby on Rails76 / 100
Chris Coyier: The Long Game of Maintaining CodePenMaintainable · on Ruby on Rails75 / 100
Robby Russell on Oh My Zsh, Developer Experience, and Open SourceScaling DevTools · on Ruby on Rails70 / 100
614: AI Code AuditsGiant Robots Smashing Into Other Giant Robots · on Ruby on Rails66 / 100
How a Solo Dev Hit 10K MRR With a SaaS That Sells to Other SaaS Companies83 / 100How a Solo Dev Hit 10K MRR With a Product Hunt Launch and Nothing Else85 / 100How a Solo Dev Hit 10K MRR With a CLI Tool and No UI72 / 100How a Solo Dev Hit 10K MRR With a Developer Tool and No Sales Team57 / 100How a Solo Dev Hit 10K MRR With a $0 Marketing Budget57 / 100