Why I Built Biglio: My Most Valuable Learning Project
Sometimes you build products to solve other people's problems. Sometimes you build them because you're frustrated that something you want doesn't exist. And sometimes — if you're honest with yourself — you build them because you need to learn, and the best way to learn is to build something real.
Biglio was all three. But looking back, the most important thing it gave me wasn't a product. It was an education.
The Original Problem Was Real
I'm an audiobook addict. Long drives, gym sessions, cooking dinner — I consume hours of audio content daily. But I kept hitting the same wall: most of the content I wanted to hear didn't exist as audiobooks.
Interesting blog series, niche non-fiction, indie fiction — all stuck in text form. The traditional audiobook industry only converts a tiny fraction of published books to audio. Hiring narrators costs $5,000–$15,000, production takes months, and distribution is controlled by platforms that take massive cuts.
The gap was obvious: massive demand meets massive supply with no infrastructure in between. So I decided to build it.
What I Actually Built — And What I Learned
Biglio became my most technically ambitious project to date, and I used it as a forcing function to level up across the entire stack.
Here's what building it required me to learn:
- AWS Infrastructure — I went deep on AWS for the first time. S3 for audio file storage and delivery, CloudFront for CDN distribution, Lambda for serverless audio processing jobs, IAM roles and policies, and cost management across services. I went from zero AWS knowledge to architecting a multi-service cloud infrastructure that could handle real audio streaming at scale.
- Audio Processing Pipelines — Building a text-to-audio pipeline is more complex than it sounds. I had to handle manuscript formatting, chapter detection and segmentation, async audio generation queues, file stitching, metadata tagging, and streaming delivery — all without blocking the user experience.
- Subscription & Channel Architecture — Designing a creator channel system meant building subscriber relationships, notification systems, content libraries, and discovery features. The data modeling alone was a significant exercise.
- Next.js at Scale — I pushed Next.js and TypeScript further than I had on any previous project — server components, API routes, dynamic audio players, responsive streaming UI.
- AI Voice Integration — Integrating and evaluating AI narration APIs, managing voice selection, handling generation failures gracefully, and delivering consistent audio quality at scale.
Every one of these problems taught me something I've since applied to my B2B products. Biglio was the R&D lab I didn't know I needed.
Where It Ended Up
Biglio launched, ran, and ultimately I shut it down. It worked — the core product functioned, channels were created, audio was generated and streamed. But without a commitment to scaling a consumer product, it didn't make sense to keep it running. Shutting it down was the right call, and I made it without regret.
Why I'm Shifting Focus
Here's the honest part: I'm not going to double down on Biglio right now.
Consumer products are hard in ways that are different from B2B. Acquisition costs are high, churn is constant, and the feedback loops are slower. You're always fighting for attention in a crowded market.
B2B is where I have the most leverage. I understand the commercial lending industry. I have relationships. I know the pain points at the broker and lender level. The products I'm building — SalesLeadAgent, PayoffAgent, BrokerSiteBuilder — solve expensive, specific problems for people who will pay to have them solved. The sales cycle is more intentional, the retention is stronger, and the path to meaningful revenue is clearer.
Biglio taught me that I can build complex consumer infrastructure. But it also clarified that right now, my energy belongs in B2B.
The Real Value of a Learning Product
If you're a technical founder, especially one who's self-taught, I'd encourage you to build at least one project that scares you — something with real infrastructure complexity, not just a CRUD app with a nice UI.
Biglio scared me at the start. AWS felt like a different language. Audio pipelines felt chaotic. Multi-tenant channel architecture felt over my head.
It wasn't. And now I know that.
The skills I built on Biglio are directly funding my B2B roadmap. That's not a consolation prize — that's exactly how it was supposed to work.
Biglio is no longer live — but the lessons from building it are baked into everything I'm building now.
For reference, the project lived at biglio.com.
Questions? Reach Out