AI Projects
mostly built on weekends, with chai ☕Each one has the full story: who it's for, what I decided, what broke, and what I'd do next.
Responsible Nagrik
Report a pothole in under a minute, then see if anyone's actually fixing your neighbourhood.
Works in English, Hindi and Hinglish. Every locality gets a public status page, so complaints stop disappearing.


Ridge Health
A food and fitness coach for people who've quit tracking apps before.
You speak your meal, plans use the food you actually cook, and a bad week doesn't reset everything. It also has its own admin console for evals and SLOs.


MoodMango
A 30-second mood check-in. You name the feeling, it gives something kind back.
This one is mostly about design: ten practices I leaned on, how it changed from v1 to v3, and my own critique of what to fix.


RAG from Scratch
I asked my RAG pipeline "Which plan supports SSO?" It said the free one.
Six visible stages from document to cited answer, two real bugs, and why chunking (not the model) caused most of the wrong answers.


Case studies
kind, but honest feedbackTeardowns of tools I use a lot, written up as proposals for the teams that build them.
Replit improvements
Where Replit users burn time and budget, and a three-phase plan to fix it.
I mapped the "token leakage" loop I kept running into while building, then shared a short deck with Replit's product team: guided prompts, smoother handoffs, and cost visibility.
Read the case study →The same four steps, every time
I pick the model last. It's rarely the hard part.
Talk to people first
Before I write a prompt, I look for the step people skip, fake or give up on.
Pick one bet
I write down the one behaviour that has to change, and how I'd know it did.
Build the small version
The smallest thing that tests the bet, with evals, fallbacks and cost limits from day one.
Measure, then cut
Keep what moves the number. Delete the rest, even the parts I liked.
Ten years in product. Still building.
I started out in engineering and customer success, spent a few years deep in data science, and ended up in product. That's why I'm as happy in a SQL query as in a roadmap review.
Outside work, I build my own AI apps. It's how I stay close to the hard parts: real users, models that fail at odd hours, and costs that sneak up on you.
LinkedIn ↗ · Resume on request
- 2024 – nowSunrunSales enablement and fintech portfolio management for consumer and partner payments · San Francisco
- 2022 – 2024GoDaddyCommerce, and experiments to drive activation, retention, engagement and monetization · Santa Clara
- 2020 – 2022HPE-commerce personalization, ROAS optimization and an AI-enabled supply chain platform · Palo Alto
- 2019Stanley Black & DeckerFreight and shipment cost optimization · Hartford
- 2019Warner Bros. EntertainmentNatural language processing and customer sentiment analysis · Los Angeles
- 2014 – 2018BroadcomCustomer success for enterprise software · Hyderabad
Building something with AI? I'd love to hear about it.
I'm always happy to walk through any of these projects, including the parts that broke.
divyachaturvedi189@gmail.com
LinkedIn ↗



