Things I've built, explored and experimented with.

What was the problem?

End-to-end infrastructure deployment across 71 schools in Gujarat, coordinating field teams, vendors, material flow and school stakeholders across distributed locations.

What was my role?

Operations & Systems Lead — Edwiser Innovation Hub

What did I build or contribute?

61 of 71 sites completed. After 45 days of on-ground execution, a centralised tracking system was deployed in under one week, replacing fragmented manual coordination with shared operational visibility. Communication across 10+ field teams, vendors and school stakeholders was streamlined, cutting issue resolution time by 60% over two months. 95% of operational issues were resolved on the go, reducing query and complaint resolution from 24–48 hours to under 1 hour. The result was a repeatable framework for multi-site deployments.

What was the problem?

A single Google Sheet that ran an entire multi-team deployment: order intake, procurement, school clustering, artwork allocation, readiness, execution and closure, connected by Apps Script.

What was my role?

Process Architect & Builder — Edwiser Innovation Hub (Smartwall, Gujarat)

What did I build or contribute?

School orders, artwork requirements, material planning, stock availability and field updates were not connected in one flow. I mapped the process end to end — order receipt, procurement, school clustering, artwork allocation, school readiness, holiday-calendar status, execution and closure — and built it as a structured workflow inside one workbook. Apps Script consolidated and processed information into multiple connected sheets, giving Procurement, Design, Finance and Execution their own operational view while connected sheets rolled up KPI-level visibility. Automated triggers pushed each team and stakeholder their updated view every evening at 6:30 PM.

What did I learn?

I had never used Google Apps Script before. Rather than adding another application or over-engineering the answer, I learned it while solving the problem, using Gemini, ChatGPT and Claude as development assistants to understand, simplify, troubleshoot and progressively extend the code. What began as one operational fix became a scalable system supporting multiple workflows and departments from inside a spreadsheet. When you understand the problem deeply, the solution rarely needs to be complicated.

What changed because of it?

One workbook served five stakeholder groups with role-specific views, automated evening reporting and KPI rollups — replacing scattered manual coordination.

What was the problem?

A Google Sheets dashboard and Apps Script ETL pipeline that automated production tracking, resource allocation and stakeholder reporting for a 3,515-slide programme.

What was my role?

Architect & Builder

What did I build or contribute?

Achieved 88.6% completion tracking (3,115 of 3,515 slides) with automated updates. Dashboards and KPIs updated dynamically for 6 team members, 46 PPTs (41 completed) and 19 voice profiles. A gamified leaderboard consolidated weekly metrics every Saturday, improving team performance over 3 weeks. Daily stakeholder email reporting covered completed vs. remaining production and team KPI snapshots, removing manual reporting and follow-ups.

What was the problem?

An exploration into a business operating system designed around cognitive agents — not another productivity layer. Currently mapping the path to MVP: architecture, operating principles, agent structure and the first problems to solve.

What was my role?

Founder & AI Architect

What did I build or contribute?

MIM OS asks whether a coordinated cohort of cognitive agents can take on meaningful parts of a business's operating cadence — letting the founder spend more time thinking, building and architecting what comes next. The architecture and governing constitution are being defined now; the cohort is the intended design, not a deployed system.

What did I learn?

Systems dictate outcomes. The interesting question isn't what agents can do, but what should and shouldn't be delegated to them.

What was the problem?

A publication exploring leadership, technology and career growth, built on a content architecture and AI-assisted editorial operating model.

What was my role?

Founder & Editor

What did I build or contribute?

AI-assisted workflows reduced content creation time by 80%, enabling 70% more articles per quarter while maintaining 100% brand consistency. Turning complex, overlooked questions into structured thought leadership drove a 300% increase in audience engagement within one month.

What was the problem?

Converted an aviation academy's manual training records into a centralised, colour-coded digital tracking system.

What was my role?

RPA Technician & Lab Instructor — Flytech Aviation Academy

What did I build or contribute?

Boosted operational efficiency by 60%+ and enabled alumni re-engagement, alongside coordinating DGCA-aligned lab, simulator, field-training, maintenance and documentation workflows for a 64% increase in training efficiency over 6 months.

What was the problem?

Twenty bundled brand and design packages plus a design-to-print delivery network, built from 14+ years of freelance practice.

What was my role?

Founder & Designer — RR Designs

What did I build or contribute?

The packages reduced client-side vendor management by 70% and increased project completion speed by 55% for end-to-end brand experiences. The connected print network contributed to a 60% income increase through higher-value orders.