Srinath Pedi · About

Building a Data and AI Platform, One Decision at a Time

I lead data and AI engineering: the modernization of an organization's data platform, the internal applications built on it, and the governed AI practice the team works in. I am based in the Philadelphia suburbs.

This site records the reasoning behind that work: what got built, what got rejected, what I got wrong, and what I still have not solved.

The idea behind all of it

Every business exists to serve people. That is the essential, the work people came to do and care about. Around it sits the must, the layer that keeps an organization fundable, auditable, and alive: documentation for customers and audits, the trackers, the status reports, the training material, and the paperwork that makes billing possible. Nobody joins a service organization for that layer, which is why it is everywhere late, thin, or missing.

AI is an accelerator, not a replacement. It absorbs that layer, so the same people deliver more of the mission while the machinery that funds it runs faster and more reliably. AI does not do the serving. It does the paperwork that funds the serving. The 12 projects below are the working proof.

The projects

The AI layer On-Premises AI Evaluation Measuring 16 local language models against real warehouse work, on the hardware we already had Private AI Program (RAG, MCP) Building our own RAG on our own hardware, behind one governed MCP doorway, keeping protected health information off every cloud service
Applications Residential Client Portal Replacing spreadsheets and 11 SharePoint lists with a single system of record for residential client management Legacy Ticket Archive Keeping a decade of retired ticketing history searchable after the system itself was decommissioned BI Platform Upgrade Planning a major reporting platform migration as a solo administrator, with vendor documentation as the primary source
Shared infrastructure Job Scheduler A shared scheduling application for business-process jobs, and what three silent outages taught about keeping them alive Application Template Turning hard-won lessons from three production applications into a starting point for the next one Shared AI Skills Library One repository so a team's AI working habits stay consistent, versioned, and auditable Internal Documentation Platform The team's documents, published where a colleague can open them
The foundation Data Extraction Platform (Sluice) Replacing a nightly data job that had outgrown its original infrastructure with a purpose-built extraction platform Data Warehouse (Medallion Hub) Rebuilding a nightly data warehouse pipeline as version-controlled SQL, without a single big-bang cutover Encrypted Backup Key Rotation Keeping a vendor's encrypted nightly database backups restorable across certificate rotations

Hover over a project for its one-line description, or see all 12 written out on one page →

The bigger picture

These 12 projects are not a set of unrelated builds. They form one modernization effort: extraction fixed before the warehouse it feeds, shared infrastructure before the applications that reuse it, and AI capability built as its own governed layer, with the same discipline pointed back at the AI's own work.

The reasoning behind that order, and the economics that changed which work is worth doing at all, are told in the bigger picture →

Read next

The journey: how I got here, one tool generation at a time →

The part I have not solved: getting a team to adopt it →

How these projects get built →

What building with AI actually costs →

Have a comment? Send it to me →