I named my AI fitness app after my son. His name is Avyaansh. The app is called Avya.
That single decision changed how I build. When a product carries your child's name, every shortcut feels like a betrayal. Every lazy design choice feels personal. You do not ship something half-baked when your son's name is on it. You build it like it matters — because it does.
Avya is an AI fitness assistant. Not another calorie counter. Not another workout log with a chatbot bolted on. It is an intelligent system trained on 14 years of real calisthenics experience, designed to give people the kind of personalized fitness guidance that currently only exists if you hire an expensive coach or get lucky enough to know someone who actually lives this life.
The Problem Avya Solves
Fitness advice is abundant. Open YouTube and you will drown in workout videos. Search Google and every fitness website will tell you to eat protein and lift weights. There is no shortage of information.
The shortage is in personalized fitness intelligence.
Here is what I mean. A 22-year-old guy in Pune who weighs 60 kg, has never trained, works a desk job, and wants to start calisthenics — he does not need the same advice as a 35-year-old woman in Delhi who has been running for 5 years and wants to add strength training. The information they find online will be roughly the same generic advice. What they actually need is radically different.
A good coach adjusts everything — exercise selection, volume, progression, nutrition timing — based on the individual. That is what makes coaching valuable. Not the knowledge itself, but the application of knowledge to a specific person with specific constraints and specific goals.
Avya does that. It takes the knowledge I have accumulated over 14 years — not textbook knowledge, lived knowledge from training my own body through Navy service, injuries, plateaus, and breakthroughs — and applies it intelligently to whoever is asking.
Fitness information is free. Fitness intelligence is rare. Avya exists to close that gap.
The Technical Stack Behind Avya
Avya runs on a stack I chose for longevity, not trendiness.
Anthropic API (Claude) — the brain. Claude handles the conversational intelligence, the ability to understand context, remember previous interactions, and generate responses that sound like a knowledgeable coach, not a robot reading a textbook. I use Sonnet for most interactions and Opus for complex programming and deep analysis. The model quality from Anthropic is the reason Avya sounds human.
Next.js 14 — the frontend and server layer. App Router, server components by default, deployed on Vercel. Fast, reliable, and built to last. No exotic framework that will be abandoned in two years.
Supabase (PostgreSQL) — the data layer. User profiles, workout history, conversation logs, progress tracking — all in Postgres with Row Level Security so every user's data is protected at the database level, not just the application level.
Voice interface — because the best interaction with a fitness coach should feel like talking to a person, not typing into a form. Voice input makes Avya accessible while training, when your hands are on a pull-up bar, not a keyboard.
Every technology choice answers one question: will this still work in 10 years? If the answer is uncertain, I pick something else. Avya is not a weekend project. It is infrastructure that needs to outlast trends.
What Makes Avya Different
Most AI fitness apps are built by tech people who do not train. They read research papers, scrape bodybuilding forums, and train their models on generic fitness content. The result is an AI that can recite textbook answers but cannot tell you what it actually feels like to plateau at month 8 of handstand training and how to break through.
Avya knows because I know. The training data includes my 14 years of real experience — the progressions that actually work for calisthenics in India, the nutrition strategies that work with Indian food and Indian budgets, the mental frameworks that keep you training when motivation disappears and only discipline remains.
Avya knows that the first three months of calisthenics are the hardest not because of physical difficulty but because of ego. You walk into a park, you cannot do a single pull-up, and every teenager around you is banging out sets. That psychological barrier kills more beginners than any physical limitation. A generic AI does not understand this. Avya does, because I lived it.
Avya also knows the Indian context. Training with limited equipment in a public park. Nutrition on a non-corporate salary. Managing fitness around Indian work culture and family obligations. These are not edge cases — for most people in India, these are the entire reality. And most fitness AI is trained on Western gym culture that does not apply.
The Moment Everything Clicked
There was a moment when I was testing an early version of Avya — asking it questions I wished someone had answered when I was 22 and just starting out. How do I start calisthenics with zero equipment? How do I eat enough protein on a vegetarian Indian diet? How do I train consistently when my job moves me to a new city every two years?
And Avya answered them. Not with generic platitudes but with the specific, experience-backed guidance that took me years to figure out on my own.
That was the illuminati moment. I was building the tool I needed at 22, for people who are 22 right now. The tool that would have saved me years of trial and error, years of following the wrong advice, years of thinking calisthenics was only for people with genetics or money or time I did not have.
If Avya existed when I was a young Naval recruit, skinny and clueless about training, my entire fitness trajectory would have been different. Not because the information did not exist — but because the personalized application of that information did not exist.
I was building the tool I needed at 22. That realization turned Avya from a project into a mission.
icanbefitter.com as the Platform, Avya as the Brain
Here is how the pieces fit together. icanbefitter.com is the platform — the blog, the content, the community, the products, the legacy. It is the public face of everything I have learned and built.
Avya is the AI brain that sits inside that platform. When someone reads a blog post about calisthenics progressions and has a specific question about their situation, Avya answers it. When someone joins the Inner Circle and wants a personalized training plan, Avya generates it. When someone needs accountability, Avya checks in.
The platform provides the content. Avya provides the intelligence. Together they create something that neither could achieve alone — a fitness ecosystem that is both broadly educational and deeply personal.
This architecture is intentional. I did not want to build just another blog where content sits passively waiting to be consumed. I wanted to build a system where content and intelligence reinforce each other. Every blog post makes Avya smarter. Every Avya interaction reveals what content people actually need. The feedback loop drives the entire platform forward.
Building Something That Outlasts Its Creator
Here is the part that keeps me building at midnight when the rational thing would be to sleep.
Avya carries my son's name. And icanbefitter.com is being built so that Avyaansh never starts from zero. When he is old enough to understand, he will inherit not just a website but a complete system — content, AI intelligence, a community, and the technology that connects them all.
Every design decision, every architecture choice, every line of code is made with one question in mind: will this still work when Avyaansh is old enough to use it? Not just the technology — the ideas. The fitness knowledge. The investment frameworks. The building philosophy.
Naming the app after him was not marketing. It was a promise. A promise that this product would be built with the same care I would put into anything I hand directly to my child. No shortcuts. No cutting corners. No shipping something I would be embarrassed for him to see.
That is the standard. And every day I fall short of it, I know exactly what I am falling short of — because his name is right there in the product name, reminding me.
So my son never starts from zero. That is not a tagline. It is the architectural requirement that drives every technical decision I make.
Har Har Mahadev. Go Win!