A few days ago, Shekhar Kirani (
@skirani), Partner at Accel (
@Accel), moderated a conversation focused on understanding what it actually takes to build products using AI.
He was joined by Anand Arvind of Zenoti (
@gozenoti), Dhimil Gosalia of BrowserStack (
@browserstack) , Noel Curtis of BookMyShow (
@bookmyshow_sup) , Ramesh Parthasarathy of DreamTeam, and Vivek Sharma of 1Wrk – operators who’ve spent years in the trenches building AI into real systems, products, and workflows.
The conversation stayed grounded in execution: what breaks, what changes inside teams, and what starts to matter once AI moves from demos into production.
Some observations that came up repeatedly:
1. How you build matters more than what you build. The companies that last are the ones treating feedback, notes, and lessons learned as part of the foundation, not extras to add later.
2. Writing things down is now part of the product. The prompts you write, the odd cases you catch, the rules you set — that's what teaches your AI how to behave.
3. Every mistake should teach the system something. When things break, the fix shouldn't just be a patch. It should change how the system thinks, so the same mistake doesn't happen twice.
4. Don't confuse usage with progress. A lot of people are using AI. Fewer are shipping things that actually work, hold up, and keep working under pressure.