The Excuse That Holds Most People Back
“I’d love to build something with AI, but I don’t have a dataset.” “I’m waiting for someone to give me a problem statement.” “I need a technical co-founder first.”
Sound familiar? I believed these too. For years. Then in November 2025, I stopped waiting — and started building with what I already had: 40 years of domain knowledge and a problem I’d wanted to solve forever. Eleven days later, I had a live product serving thousands of users.
What I Built
The Chennai Music Season 2025–26 Portal — a comprehensive guide to one of the world’s largest classical music festivals.
3,001 concerts
2,264 artists
45 sabhas
55 festivals
79 days (Nov 1 – Jan 28)
Complete with multi-filter search, personal bookmarks, WhatsApp sharing, and printable schedules. Lines of code written by me: Zero.
When The Hindu Validated It
On December 12, 2025, The Hindu published a full-page feature titled “Of Algorithms and Alapanas” by N.C. Srinivasaraghavan. The article described how AI tools now help rasikas filter concerts by geographical preferences and simplify the complex task of sabha-hopping.
“Classical musicians must move past scepticism when it comes to AI. It cannot replace human mastery, but can be a modern instrument for practice, planning and cultural propagation.” — The Hindu
This isn’t a story about coincidence. It’s a story about what happens when domain expertise meets AI capability. And it carries lessons for anyone still waiting for the “right” dataset or the “right” moment.
The Problem That Wouldn’t Go Away
For years, the Chennai December Music Season presented a delightful paradox. One of the world’s largest classical music festivals — with hundreds of concerts across dozens of venues spanning six weeks — had no single, comprehensive, user-friendly guide.
Each sabha published its own schedule: PDFs buried three clicks deep, Instagram posts lost in the feed, WhatsApp forwards of screenshots, physical brochures available only during office hours.
I’d wanted to solve this for years. The estimates: 1–2 lakhs and 5–6 weeks minimum. So the idea stayed an idea. Until I asked a different question:
“What if I stopped waiting for the perfect technical partner and became one myself — not by learning to code, but by learning to collaborate with AI?”
Eleven Days That Changed Everything
Day 1: 2 sabhas, 180 events
Day 3: 10 sabhas, 500 events
Day 6: 25 sabhas, 1,200 events
Day 10: 39 sabhas, 2,300 events
Day 11: 45 sabhas, 3,001 events
Manual coding by me: Zero. AI tools cost: Rs. 6,000. Hosting cost: Rs. 0.
The portal includes advanced filtering, personal schedules, WhatsApp sharing, artist search, and printable itineraries. The design evolved from techy to traditionally elegant — maroon and gold.
The Economics of Reinvention
| Traditional Route | AI-Collaborative Route |
|---|---|
| High cost | Rs. 62,000 true cost |
| Long timelines | 11 days |
| Paid iterations | Unlimited iteration |
When iteration is free, excellence becomes achievable.
Five Pivots That Made the Difference
- Tech aesthetic to Traditional elegance
- Colorful to Clean
- Festival focus to full Season coverage
- Desktop-first to Mobile-first
- Information delivery to Community building
Each pivot was guided by real user behavior, not assumptions.
Five Takeaways for Your Reinvention
Your Action Plan
- Start with your domain — your 10,000 hours of expertise is the unfair advantage AI cannot replicate.
- Your expertise IS the dataset — you don’t need someone else’s data when you have decades of contextual knowledge.
- Iterate relentlessly — when AI handles the code, you can pivot five times in a day.
- Focus on the 60% only you can do — data collection and domain decisions required human judgment. Let AI handle the rest.
- Ship before you’re ready — a live product that helps people today beats a perfect product that launches never.
The best time to start was yesterday. The second-best time is today.
Originally published in the Reinvention in the AI Era newsletter on LinkedIn.
_edited.avif)