Product Requirements Document
Proposal: add one product
manager who ships.
This document proposes Anirudh Jagtap for your product team. Like any good PRD, it contains a problem, a solution, metrics, and shipped evidence. Review time: ~4 minutes.
Status
Open to opportunities
Author & subject
Anirudh Jagtap
Location
Mumbai, IN
Document
PRD-2026-AJ · v3.0
Last updated
July 2026
Reviewer
You
TL;DR
011.5+ years of end-to-end product ownership at an enterprise CPaaS company (WhatsApp, RCS, SMS, Email, AI chatbot — 10+ enterprise accounts).
02Two SaaS products designed, built, and launched entirely solo — both live, with real users: Projanix and WhataCampaign.
03Technical enough to be dangerous (Python, SQL, Figma, AI-native workflow); product enough to know shipping beats specifying.
Problem statement
Most early-career product hires can write user stories. Very few have taken a feature from client discovery to production — and almost none have done it alone, end to end, with their own product and their own users.
Hiring for product sense from interviews alone is expensive guesswork. The strongest signal is a track record of shipped, measured outcomes — which is exactly what this document contains.
Proposed solution
One Associate Product Manager who has run the full loop repeatedly: discovery → PRD → design → sprint → QA → launch → measure — at work on enterprise omnichannel platforms, and after hours on products he owns completely.
The rest of this document is the evidence. Start with the numbers (§3), inspect the shipped work (§4), open the live products (§5), then make the call (§9).
Success metrics (actuals, not targets)
Every number below shipped to production and was measured there. No projections.
Avg. ticket resolution time
ReplyCX ticketing module · intl. telecom client
End-user engagement & conversion
BFSI journey redesign
Email deliverability
Routing & segregation logic · enterprise
Records processed < 60 s
Data Merger · replaced 4–5 h daily manual work
Time-to-market
Techalpha IO · enterprise SMS platform
Client communication efficiency
Across 10+ enterprise accounts
Shipped features
Four representative specs from the day job. Each one: owned end-to-end. Expand for detail.
Agents switched between four tools, lost context, and let tickets fall through the cracks. The client needed one system across every channel.
Took sole ownership: ran discovery with the client, mapped the ticket lifecycle, authored the full spec, designed the UI in Figma (accelerated with Galileo AI/Uizard), and coordinated engineering to launch.
Shipped on deadline. 25% reduction in average resolution time.
Independent releases
Strategy, design, code, launch, support — one person, zero funding. Both links are live; click them and judge for yourself.
Projanix
AI-native project management. Describe a project in one sentence — get structured boards, timelines, predictive delay detection, and smart task-team matching.
1 enterprise client · 3 beta teams · 10+ users
projanix.onlineWhataCampaign
WhatsApp campaign planning without getting banned — AI spam screening, cooldown enforcement, contact shuffling. Zero API dependency.
Live for businesses
whatacampaign.inChangelog
Version history, newest first. Breaking changes only.
Projanix — major release
AI-native project management platform launched solo. Enterprise client + beta teams onboarded.
WhataCampaign shipped
Second solo SaaS — safe WhatsApp campaign planning, zero API dependency.
Techalpha Group — Associate Product Manager
Feature ownership on ReplyCX (omnichannel CPaaS). Ticketing module, Techalpha IO, Data Merger, BFSI redesign all shipped under this version.
Data Analyst Intern — Think Of It Foundation
Large-scale electoral datasets: SQL, Python, Power BI (DAX), classification models.
Jr. Business Analyst Intern — AH Beta Dynamics
First BRDs/PRDs, dashboards, SQL analysis in production settings.
B.Tech, Computer Science & Business Systems
Bharati Vidyapeeth, Pune — CGPA 9.12.
Diploma in Computer Technology
Bharati Vidyapeeth Institute of Technology — 85.5%.
Capabilities
Risks & mitigations
He will ask “why” in the first meeting.
You ship the right thing instead of the loud thing.
A prototype may appear before the kickoff ends.
Alignment happens on screens, not in paragraph six.
The title says 1.5 years.
The evidence says two live products, ten enterprise accounts, and measured outcomes. Weigh the shipping, not the tenure.
Appendix A — Reviewer exercises
Reading a PRD is passive. Reviewing one isn't. Three short exercises from the PM trenches — calibrate yourself, then compare against the subject.
Roughly how many WhatsApp messages are sent per day in India?
Approval
Every PRD ends with a decision. This one is yours.
Anirudh Jagtap
author · subject
______________
you · reviewer