Mohit Shrivastava logoMOHIT SHRIVASTAVAtechnology leader · builder · operatormohit@portfolio ~/careerdownload-cv
TERMINAL · mohit@portfolio ~/career
mohit@portfolio ~/careergit checkout ai
AI, Data & Automation

AI and data systems run like production engineering: directed, observable, verified.

For teams turning AI, operational data and automation into dependable product capability — with explicit gates, useful dashboards and evidence behind every claim.

~20 days
Tassenger v3 rebuild
three product surfaces + backend
58 + 230
SQL suites + UAT docs
verification evidence
472+
videos auto-published
Mastroify · ~7 weeks
≈$1/mo
Mastroify run cost
platform + video factory
11
publishing platforms
platform-specific automation
why me, for this
$ cat ai.md

Tassenger is the clearest agent-directed delivery proof: I rebuilt v3 across native iOS, native Android, a web console and the Supabase backend in about twenty days by directing AI coding agents through 21 requirement rounds, 9 architecture decisions, 58 SQL test suites and 230 UAT documents. The speed matters; the verification system is the real signal.

Mastroify proves a different operating model: an autonomous content engine that combines real astronomy, LLM-directed writing, local text-to-speech, Playwright, ffmpeg and native publishing APIs. It produced 472+ videos over about seven weeks, operated across 11 platforms and cost about one dollar a month before I paused the studio after the model was proven.

The data work is operational, not ornamental: Aircraft Flow 360° surfaced delay causes and predicted turnaround risk at Changi; FMT's Chartbeat-to-MongoDB pipeline powers trending and related-content signals; and MXP gave marketing teams a self-service experimentation platform. I turn those systems into analytics reporting senior management can act on.

Automation at FMT follows the same rule. The YouTube-native Video CMS replaced polling with WebSub, reducing API quota use by about 80% and update latency to roughly 30 seconds. The useful result was not a clever integration — it was a simpler production system with fewer moving parts and clear operational controls.

What's here is verified agentic delivery and data systems in production — receipts, not demos — and I'm straight about where my edges are.

the turnaround, in one diff
$ diff ai-data-systems: demo → production
-AI output without requirements or acceptance gates
-Manual content, rendering and publishing loops
-Polling-heavy integrations that spend quota to discover change
-Operational data visible only after the decision window closes
+Agent-directed delivery backed by requirements, ADRs, SQL suites and UAT evidence
+An autonomous LLM content engine operating across 11 platforms
+WebSub events at ~30s latency with ~80% less API quota use
+Changi and FMT signals surfaced where operators can act
the business outcome

Automation should remove work, not hide it.

The Video CMS originally polled YouTube every five minutes. Replacing that loop with WebSub made the system both cheaper to operate and more current: YouTube tells the platform when something changes, quota use fell by about 80%, and updates arrive in roughly 30 seconds. The result is observable, reversible and easier to explain.

Polling baseline — API quota use100% baseline
WebSub event flow~80% less
problems I've already solved
“AI makes us faster, but nobody trusts the output.”
Put the tool inside a delivery system: requirements, architecture decisions, tests, review evidence and explicit release gates.
Tassenger: ~20-day v3 rebuild with 58 SQL suites and 230 UAT documents
“Content automation still needs someone clicking through every step.”
Orchestrate the whole operation — writing, voice, rendering, scheduling, publishing, logs and fallback behavior.
Mastroify: 472+ videos · 11 platforms · ≈$1/month
“Our data exists, but it arrives after the decision.”
Move operational signals into a product surface designed around the action, not around the reporting tool.
Aircraft Flow 360° · delay causes visible · turnaround risk flagged early
“Trending and related content are editorial guesses.”
Feed live audience signals from Chartbeat into a MongoDB pipeline that product surfaces can query consistently.
FMT trending and related-content signals · reporting to senior management
“Polling works until volume makes it expensive and stale.”
Replace scheduled discovery with an event source and keep operational controls for retries, purge and recovery.
WebSub: ~80% less API quota use · ~30-second update latency
“The dashboard reports everything except what to do next.”
Start with the operator's decision, then expose only the cause, threshold and context needed to act.
Changi turnaround visibility · FMT trending · MXP experimentation
first 90 days on your platform
Days 1–30
Map decisions, data and risk
Identify the decisions worth accelerating, trace the data and workflow behind each one, establish the current baseline, and define where human approval and rollback must stay explicit.
Days 31–60
Ship a narrow production loop
Deliver one or two high-value workflows end to end with observability, acceptance tests, cost limits and an owner — useful enough for real operators, small enough to correct quickly.
Days 61–90
Scale only what proved itself
Turn the validated patterns into a repeatable operating model: ownership, review gates, failure handling, data quality, measured outcomes and a clear retirement path for what did not work.
signals
Agent-directed delivery with gates
Tassenger: 21 requirement rounds, 9 ADRs, 58 SQL suites and 230 UAT documents.
Autonomous LLM operations
Mastroify coordinated writing, speech, rendering and publishing across 11 platforms.
Data pipelines that drive product
Chartbeat signals flow through MongoDB into FMT trending and related-content surfaces.
Dashboards operators act on
Changi turnaround visibility and FMT trending put operational signals in front of decision-makers.
Event-driven automation
WebSub replaced polling, cut API quota use by ~80% and reduced update latency to ~30 seconds.
Verification and human approval
AI accelerates delivery inside explicit requirements, tests, review evidence and release gates.
case studies on this branch
related projectsfull archive →
Tassenger — Taskable Chatfeatured
Own product · 2026 · Solo
Chat where tasks don't die — v3 rebuilt from scratch in ~20 days. Live in both stores — iOS on the App Store, Android on Google Play.
Kotlin/ComposeSwiftUISupabaseCloudflareTypeScript
Mastroify — Content Enginefeatured
Own product · 2025–26 · Solo
Self-running content business for ~$1/mo — own astronomy in Next.js, 11-platform AI posting, 472+ auto-published videos.
Next.jsTypeScriptSupabaseChatterbox TTSPlaywrightffmpeg
Aircraft Flow 360°featured
Changi Airport · Accenture · 2021–22 · 3 experts
Surfaces flight-delay causes and predicts aircraft-turnaround delays.
ReactAWS AmplifyGraphQLAppSyncDynamoDB
YouTube-native Video CMSfeatured
FMT · 2025 · Team
33K+ videos, 2M+ daily views, RM0/month — YouTube as the database.
Next.jsMongoDBCloudflareYouTube APIWebSub
News Analytics & Automationfeatured
FMT · 2023–present · Team
Chartbeat-to-MongoDB pipeline powering trending and related-content signals; analytics reporting to senior management.
ChartbeatMongoDBAnalytics pipelines
stack on this branch
CodexClaudeLLM orchestrationNext.jsTypeScriptSupabase / PostgresMongoDBChartbeatGA4GraphQL / RESTWebSubPlaywright / ffmpeg
Available — serving notice · open to interviews now

Need AI and data capability that survives contact with production?

I direct capable tools, instrument the data path and put verification around the result — so the system is useful after the demo ends.