Mistakes from my first year of shipping AI products

The errors that cost real time in a year of shipping five production AI apps: no evaluation set, trusting demo data, hosting on hope, under-logging, over-promising to clients, and skipping the privacy conversation.

At an Integral Startup Foundation hackathon
At an Integral Startup Foundation hackathon

A year of shipping five production AI apps produced a portfolio and a long list of things I would not do again. Students hear the portfolio part in talks; here is the list, because it is the more useful half.

1. Building before measuring

The first RAG pipeline was tuned by feel for weeks. The moment I wrote fifty questions with known answers, two weeks of changes turned out to have made recall worse. Now the evaluation set is written before the pipeline; see how to evaluate a RAG system.

2. Trusting the demo corpus

Everything worked on the clean PDFs I tested with. The client's scanned, rotated, bilingual documents broke chunking, OCR and retrieval at once. Test on the ugliest real data you can get, first.

3. Hosting on hope

A free-tier server, a reranker and an embedding model do not fit together without a memory budget. The outage taught me to write the budget down — the free-tier memory-budget playbook exists because of it.

4. Under-logging

A client asked why an answer was wrong and I could not say which chunks were retrieved or which provider answered. Every request now logs an id, the model, the retrieval scores and timing — never the raw personal data.

5. Over-promising accuracy

"It will answer anything in your documents" is a sentence I said once. The confidence gate — the system saying "I don't know" — was as much a client-communication fix as a technical one.

6. Skipping the privacy conversation

Where does the data go? I learned to answer that before a client asked, after one uncomfortable meeting. FaceVision's embeddings-only design is the direct result; see privacy by design for AI apps.

What I would tell a student

Make these mistakes on a small project with a patient user, in Year 2, so that by the time a client is paying you have already stopped making them. That is what mentorship sessions are for, and why I keep telling this list at colleges.

JourneyMistakesShippingLessons
Pranjul Rathour
Pranjul Rathour
GenAI Engineer · Kanpur, Uttar Pradesh, India

GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.

Keep reading

More on Journey

All Journey posts →
Campus talks · hackathon judging · mentoring

Want this as a live session at your college?

Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges.

Pranjul Rathour, GenAI engineer in Kanpur