My Work ( Overview )

Module 0: XOR Enterprise & Manufacturing Traceability

Role: Product Manager | Timeline: 9 Months | Status: Phased Development

1. Executive Summary
When a finished product fails, the factory needs to know which component, supplier batch, and production step were involved. In IoT manufacturing, that history spans customer requirements, procurement, materials, assembly, and quality checks.

Following Elecbits’ ₹50 crore funding round in December 2025, I took product ownership of XOR Enterprise in January 2026, working across connected Admin, Vendor, and Manufacturing platforms.

Over nine months, I led development across six core modules, with a shared goal: connect the customer’s order to the material and quality records behind the finished product, with MES managing shop-floor execution.

2. The Connected Manufacturing Flow

Confirm the Build
Capture customer requirements, receive the PO, and approve the project scope.
Source the Materials
Send RFQs, compare quotations, select suppliers, and issue vendor POs.
Receive and Inspect
Reconcile deliveries, assign lot or package identities, and record incoming quality checks.
Execute through MES
Use Work Orders to connect operations, material consumption, production progress, and quality checks.
Release and Dispatch
Link finished-product identities and final quality approvals to dispatched goods.

3. The Six Core Modules

Box Build: Adaptive requirements capture and Work Order flow.
Sales Orders: Customer PO validation and controlled order release.
Vendor Management: Supplier registration, capabilities, and qualification.
RFQ Enhancements: Supplier selection and structured quote collection.
Procurement & Inward: Purchasing, expected deliveries, and receiving.
Inventory & IQC: Material identity, inventory records, and incoming inspection.

Each module addresses a different handoff in the same journey: what was ordered, what arrived, what was used, and what was delivered.

Module 1: Box Build Forms & AI Project Creation

Role: Product Manager | Timeline: ~2 Months | Status: Designed

1. Executive Summary
Customers want fewer questions. The factory needs every critical answer. XOR’s Box Build projects involve 110+ possible fields, from Component sourcing to final labeling—but every customer needs a different combination of services.

I designed adaptive forms and synchronized AI chat to capture what the customer supplies and what XOR must build. Customer and production-team approval turn those inputs into an agreed scope for manufacturing.

2. The Problem Space

Variable Scope: Full turnkey builds, customer-supplied PCBs, and assembled PCBAs each require different information and responsibilities.
Form Fatigue: A fixed form exposes customers to irrelevant questions across 110+ possible fields.
Approval Gaps: Unconfirmed requirements create confusion, rework, and delays during production.

3. The Solution

Ask According to Scope
Fields appear based on selected services and supplied inputs. Customers providing assembled PCBAs answer questions about the remaining work; turnkey customers provide requirements for the complete build.
Two Ways to Complete One Form
Customers enter requirements through structured fields or AI chat, with both synchronized to the same project.
Align Before Manufacturing
The customer confirms what is needed; the production team confirms what will be built. Both approve the requirements before execution.
Carry Scope into Production
- Bare PCB supplied: Required assembly and subsequent operations.
- Assembled PCBA supplied: Remaining programming, testing, enclosure, or packaging work.
- Full turnkey build: All applicable manufacturing stages.

4. The Impact

Completion: Increased form completion by 40%.
Clarifications: Reduced follow-up rounds from 20 to 2.
Accuracy: Cut requirement-related production errors by 30%.

Module 2: Sales Order Creation & Customer PO Processing

Role: Product Manager | Timeline: ~6 Weeks | Status: Designed

1. Executive Summary
One wrong BOM revision can turn a confirmed sale into the wrong purchase. I designed XOR’s Sales Order Creation module to connect customer commitments with the correct commercial and technical baseline, using a Draft → Released approval flow before procurement begins.

2. The Problem Space

Manual Interpretation: Different PO formats and scattered payment terms make order entry slow and error-prone.
Wrong Purchasing Basis: Customer PO lines do not always reflect the components and quantities procurement needs.
Premature Action: Teams can begin purchasing before discrepancies and approvals are resolved.

3. The Solution

Upload → Extract → Confirm
OCR prefills PO details for human review, reducing manual entry.
Connect the Right Sources
The PO defines commercial commitments; the approved BOM/MCMA defines procurement requirements. Payment and tax conflicts go to Finance.
Approve Before Purchasing
Only released orders permit procurement planning. Release locks the approved record, with later changes handled through amendments.

4. Impact Targets — Illustrative

50% Faster Processing: Reduce order review from 30 to 15 minutes.
60% Fewer Follow-ups: Reduce clarification rounds from 5 to 2 per order.
25 Team Hours Saved: Saving 15 minutes across 100 orders frees up 25 hours.

Module 3: RFQ Management & Supplier Organization

Role: Product Manager | Timeline: ~2 Months | Status: Designed

1. Executive Summary
XOR had 4,000 suppliers in Excel, but only around 10 available for sourcing in the platform. Procurement selected suppliers individually, chased responses, and manually entered emailed quotes.

I designed a connected RFQ flow to make that supplier database searchable, invite relevant suppliers in bulk, and collect quotes directly against the requested line items.

2. The Problem Space

An Offline Supplier Network: Thousands of supplier records sat outside the live sourcing workflow.
Repeated Selection Work: Every RFQ meant searching for and selecting suppliers individually.
Unstructured Responses: Emailed quotes created manual entry, follow-ups, and difficult comparisons.

3. The Solution

Turn Excel into a Searchable Supplier Base
Import records with field mapping, validation, and duplicate review. Tags and reusable collections organize suppliers by capability, category, and geography.
Build the Supplier List Once, Reuse It
Procurement selects relevant groups or multiple suppliers and sends one RFQ with shared requirements and a deadline.
Bring Quotes Directly into XOR
Suppliers use a secure link to quote against each RFQ line, including partial quantities, alternatives, or “No Quote.” Structured responses feed comparison without routine re-entry.
Make Follow-ups Visible
Track invitations, access, responses, and overdue submissions, with reminders for pending suppliers.

4. Expected Impact

~400× Supplier Availability: Expand the searchable base from approximately 10 to 4,000 records, subject to import validation.
One Bulk Invitation Action: Replace repeated individual invitations with a single send to selected suppliers.
Zero Routine Quote Transcription: Target direct capture of supplier-submitted prices and quantities for comparison.

Module 4: Vendor Portal & Qualification

Role: Product Manager | Timeline: ~2 Months | Status: Designed

1. Executive Summary
Inviting more suppliers only helps if we know what they can deliver. The RFQ enhancements brought XOR’s supplier network into the sourcing workflow. The Vendor Portal builds on that foundation by capturing the capabilities, contacts, and documents needed to select suitable vendors.

I designed a connected journey from vendor discovery → registration → qualification → RFQ participation, linking supplier profiles to the sourcing opportunities they can serve.

2. The Problem Space

Contacts Without Context: A supplier’s name and number do not explain their manufacturing capabilities.
Generic Registration: Component suppliers, PCB fabricators, and testing labs need different qualification questions.
Repeated Verification: Duplicate records and missing documents force teams to recheck vendor information during sourcing.

3. The Solution

Capture First, Qualify When Needed
Save a prospect with basic details, then complete registration when a relevant sourcing opportunity arises.
Build Profiles Around Services
Collect shared business details alongside service-specific capabilities and required documents.
Connect Profiles to RFQs
Make vendor capabilities searchable through the RFQ module’s filters, tags, and collections. Selected suppliers then use the secure RFQ flow to submit structured quotes.
Make Qualification Visible
Show missing information and document-review status so Procurement and Finance know what still needs attention.

4. Impact Targets

Faster RFQ Selection: Reduce vendor selection time by 50% within 6 months.
Quicker Onboarding: Capture prospects in under 2 minutes and complete qualified profiles in under 20 minutes within 6 months.
Cleaner Supplier Records: Reduce duplicate vendor creation by 50% within 6 months.

Module 5: Procurement, Inventory & Incoming Quality Control

Role: Product Manager | Timeline: ~3 Months | Status: Designed

1. Executive Summary
A delivery can match the purchase order and still contain material the factory cannot use. After supplier selection and procurement, XOR needed to track what actually arrived, identify each lot or package, and connect it to incoming inspection.

I designed the flow from material requirement → sourcing → receiving → material identity → IQC, preserving the project context through every handoff.

2. The Problem Space

Different Supply Routes: Materials can come from customers, their vendors, XOR suppliers, or existing stock.
Delivery Mismatches: Partial, excess, short, or damaged deliveries complicate reconciliation.
Traceability Gaps: Receiving quantities alone cannot tell Quality which lot or reel to inspect—or where it came from.

3. The Solution

Source Each Requirement Correctly
Assign one of four supply routes to each requirement. Connect XOR purchasing to the RFQ and vendor workflows; link existing-stock requirements to inventory.
Separate Expected from Received
Stores records actual arrivals against expected deliveries, including quantity differences and damage.
Give Each Lot an Identity
Link lots, reels, trays, or packages to the GRN, with duplicate checks and quantities reconciled to the receipt.
Carry Receiving Data into IQC
Create inspection tasks from received material, carrying forward supplier, item, quantity, and lot details. Inspectors record sample measurements, defects, and evidence against the same identity.

Scope: This phase ends at IQC submission; disposition, putaway, and production issue follow separately.

4. Impact Targets — Illustrative

50% Faster GRN Entry: Reduce entry time from 20 to 10 minutes per receipt.
80% Faster Tracebacks: Reduce time to locate source and inspection records from 10 to 2 minutes.
~17 Hours Saved per 100 Receipts: Save 10 minutes of GRN entry per receipt.

Module 6: FolderLM — NotebookLM Organization & Research Tools

Role: Builder (My Own Product ) | Timeline: Ongoing | Status: Live

1. Executive Summary
Saving research is easy. Finding it again across 100+ notebooks is the harder problem. NotebookLM’s flat list made growing research collections difficult to navigate.

I built FolderLM, a Chrome extension that organizes notebooks and simplifies repeated research tasks. I owned the journey from user research and prioritization to AI-assisted development, store launch, and a feedback-driven roadmap.

2. The Problem Space

Notebook Overload: Related research disappeared inside a growing list of titles.
Lost Context: Users repeatedly opened notebooks to rediscover where they had left off.
Repetitive Work: Importing sources, combining notebooks, and reusing prompts required separate manual steps.

3. The Solution

Solve Retrieval First
Folders, colour-coding, favourites, and bulk movement help users group research and return to it quickly.
Build Around Complete Research Tasks
Bulk imports, notebook merging, and reusable prompts reduce repeated setup. Copying answers with citations helps users carry research into their next document.
Let Feedback Set the Next Priority
Requests for access across computers led to sync support. I balanced recurring user needs against development effort and product simplicity.

4. The Impact

Adoption: Reached 40,000 Chrome Web Store users.
User Validation: Earned 4.2/5 across 54 ratings.
Organic Discovery: Attracted 29,877 listing sessions through organic search, accounting for 32.5% of sessions.

Adoption and ratings as of September 29, 2026; traffic figures cover January 1–September 29, 2026.

Module 7: In-Store Retail Analytics & Shopper Tracking

Role: Product Manager | Timeline: ~4 Months | Status: Built

1. Executive Summary
The retailer knew how many shoppers entered and what sold. Everything between those moments was a blind spot. This customer accounted for 50% of our revenue, and we were already building its store cameras.

We extended that work into retail analytics using computer vision, person tracking, and re-identification (ReID). The pipeline converted CCTV footage into anonymous visitor sessions, showing how shoppers moved through the store, where they spent time, and which zones they revisited.

2. The Problem Space

Invisible Shopping Journeys: Entry counts and transactions could not explain how shoppers explored the store.
Unreliable Counting: A shopper disappearing behind a shelf and reappearing could be counted as a new visitor.
Limited Decision Context: Merchandising and operations teams lacked journey-level evidence to assess product placement, layout, and staffing.

3. The Solution: From Video Frames to Retail Decisions

Person Detection — Locate People in the Footage
A computer-vision model detects people in individual camera frames. This establishes where people are visible at a given moment.

The important distinction: the same shopper appears in many frames, so counting detections would inflate visitor numbers.
Tracking + ReID — Connect Observations into One Visit
Tracking connects a person’s observations across consecutive frames. ReID, or re-identification, helps associate a person who reappears after a tracking interruption with an existing visit.

For example, when a shopper walks behind a shelf and returns to view, the system can reconnect the observations instead of automatically creating another visitor.

This continuity supports more reliable footfall and dwell calculations.
Visitor Sessions — Give Each Journey a Record
Connected observations form an anonymous visitor session containing first-seen and last-seen timestamps, visit status, and associated movement events.

That session becomes the link between the shopper’s entry, product-zone visits, checkout activity, and exit.
Zone Mapping — Give Movement Business Meaning
We mapped the camera view to meaningful store areas: entrances, product categories, checkout, and exits.

As a tracked visitor moves between those areas, the system creates timestamped events such as:
- Entered the electronics zone.
- Left the electronics zone.
- Revisited the electronics zone.
- Reached checkout.
- Exited the store.
This converts movement in video into a structured shopping journey.
Dwell and Revisit Calculations — Measure Time and Repeat Interest
For visits with recorded entry and exit events:

Store dwell = Store exit time − Store entry time

Zone dwell = Zone exit time − Zone entry time

Separate visits to the same zone remain separate before their durations are added.

For example, a shopper spends 4 minutes in electronics, leaves, then returns for 2 minutes. The record shows 6 minutes of total zone dwell across 2 visits, preserving the revisit signal.
Engagement Signals — Combine Behaviours
We combined store dwell, time in relevant product zones, zones explored, revisits, and checkout reached into retailer-defined engagement signals.

A shopper repeatedly returning to a product zone may warrant different analysis from someone passing through it. These signals describe observed behaviour; confirmed purchases require transaction data.

4. The Impact

Strategic Customer Value: Added shopper analytics to the camera offering for an account representing 50% of revenue.
Journey Visibility: Connected entry, browsing, revisits, checkout activity, and exit within anonymous visitor sessions.
Actionable Store Insights: Gave merchandising and operations teams evidence to evaluate layout, product placement, and staffing.

Module 8: Construction Budgeting Module

Role: Lead Product Manager | Timeline: 6 Months | Status: Live (v1.1)

1. Executive Summary
Managing a $100M construction budget on Excel is financial suicide. One formula error can hide millions in cost overruns. I led the 0-to-1 development of the Budgeting Module, a centralized financial command center that replaced disconnected spreadsheets with a gated, version-controlled approval engine.

2. The Problem Space

Excel Hell: Budgets were living documents managed on local desktops. There was no Single Source of Truth.
Manual Drudgery: Estimators spent 2-3 days every month manually splitting costs across a 24-month schedule.

User Personas

The Estimator (Rahul): Frustrated by manual data entry and constant version emails.
The PMO Head (Suresh): Anxious about hidden costs and unauthorized budget changes.

3. Strategic Vision
To build a financial operating system where every Rupee is tracked, versioned, and approved before it is spent.

4. The Solution (Deep Dive)

The Monthly Distribution Logic
I designed an algorithm to automate the cash flow forecast.
Input: Total Cost (e.g., ₹50L) & Schedule Duration (e.g., 100 Days).
Innovation: For Materials (like Steel), I added a Payment Milestone logic (e.g., 40% Advance, 60% Delivery) to reflect real-world cash outflows.
User Flow & UX
Auto-Fetch: User selects a project. The system pulls all Work Packages and Quantities from the Engineering DB.
Rate Entry: User only inputs the Unit Rate. The system auto-calculates the Total Amount.
Key Artifacts
Gated Workflow: Draft -> Pending Approval -> Locked.
Revision History: A GitHub-style diff view showing exactly which line item changed between V1 and V2.

5. The Impact

Efficiency: Reduced budget creation time from 5 days to 4 hours.
Control: 100% elimination of Shadow Budgets (offline spreadsheets).

Module 9: Schedule Planning & Real-Time Engine

Role: Product Manager | Timeline: 4 Months | Status: Live (v2.41 & v2.42)

1. Executive Summary
A construction schedule is usually obsolete the moment it is printed. I built a Real-Time Predictive Engine that uses live site data to auto-calculate the project's completion date every single day. It's not just a tracker; it's a GPS that reroutes the project when it hits traffic.

2. The Problem Space

The Reality Gap: Project Managers (PMs) compared progress against "Lifetime Average," which masked recent slowdowns (e.g., due to rain).
Reactive Management: Delays were only discovered after the deadline was missed.
No Sandbox: PMs couldn't ask "What if we double the workforce?" without messing up the live data.

3. The Solution (Deep Dive)

The Rolling Window Algorithm
This is the core innovation. Instead of using Planned Duration, the system calculates two dynamic metrics:
15-Day Average PR (Production Rate): How fast is the team working right now?
Required PR (The Catch Up Metric): How fast must we work to hit the deadline?
User Flow: The Parallel Universe Sandbox
To solve the No Sandbox problem, I designed a Multi-Plan Architecture.
Create Plan: User creates "Recovery Plan A".
Simulate: User tweaks variables (e.g., increase Production Rate by 20%).
Commit: User clicks "Set as Active" to overwrite the live schedule.
The Ghost Bar Visualization
We needed to show Plan vs. Reality instantly.
Ghost Bar (Outline): Represents the Planned Schedule.
Solid Bar (Filled): Represents the Actual Progress.

4. The Impact

Forecast Accuracy: Improved completion date prediction accuracy from 60% to 90%.
Proactive Action: PMs identified critical delays 3 weeks earlier than before.

Module 10: My Startup – Lovedit App

Role: Founder & Product Manager | Timeline: 12 Months | Status: Acquired (Data Exit)

1. Executive Summary
I bootstrapped Lovedit, a relationship wellness app, with just ₹10,000. By focusing on hyper-specific user problems (breakups & intimacy), I scaled it to 1,000+ users and secured a 10X exit in just 12 months by selling our unique user behavior data to a larger incumbent.

Note: Read the full story of this journey in my dedicated blog post: My Bootstrapped Startup.

2. The Problem Space

The Gap: The market had dating apps and therapy apps, but nothing for the "messy middle"—breakups, relationship maintenance, and financial stress for couples.
The Rejection: VCs dismissed it as "too niche" or "just a student project".

3. The Solution (Deep Dive)

Product Strategy: Instead of fighting the giants on matching, I built a Relationship Healthcare ecosystem.

Content Engine: We created high-value guides that drove massive organic traffic.
Financial Feature: We introduced a Marriage Loan feature, connecting couples to banks.

4. The Impact

Data Valuation: Our user behavior data became so valuable that an incubated company acquired the data report for 1 Lakh—a 10X return on my initial capital.

Module 11: Matrimony App Onboarding Enhancement

Role: Product Manager | Focus: UX & Growth | Status: Live

1. Executive Summary
In matrimony apps, trust is the currency. A generic Sign Up form causes high drop-offs because it feels transactional. I redesigned the onboarding flow to be Context-Aware, changing the entire app's language based on who is creating the profile (Parent vs. Self).

Note: Read How to Enhance User Onboarding & Profile Creation for Matrimony App in my dedicated blog post: Read More.

2. The Problem Space

The One-Size Fail: Most apps ask "What is your name?" even if a father is creating a profile for his daughter. This breaks immersion and trust.
Data Fatigue: Matrimony profiles require 100+ data points.

3. The Solution (Deep Dive)

The Digital Doorstep Flow
The Magic Question: The very first screen asks, "Who are you creating this profile for?"
If Daughter: The UI changes to "What is her education?"
If Myself: The UI says "What is your education?"
Privacy-First Income: Replaced exact salary fields with Income Ranges (e.g., 5-10 LPA), reducing user friction.

4. The Impact

Trust: The Context-Aware language immediately established the app as a serious, family-oriented platform.
Completion: Reduced drop-offs by ~40%.

Module 12: Fintech Loan App Conversion (The EMI Screen)

Role: Product Manager | Focus: Conversion Rate Optimization (CRO)

1. Executive Summary
The Select EMI Plan screen is the graveyard of loan apps. I redesigned this critical screen to focus on Transparency and Psychological Safety, transforming it from a Debt Calculator into a Plan Selector.

Note: Read How to Stop Losing Customers on Your Loan App’s Most Important Screen in my dedicated blog post: Read More.

2. The Problem Space

Hidden Fees: Users would select a plan, see a higher number on the next page, and feel cheated.
Choice Paralysis: Presenting 10 different EMI tenures overwhelmed users.

3. The Solution (Deep Dive)

The Transparency UI
The Breakdown Card: I added a dynamic breakdown right on the selection card (Principal, Interest, Processing Fee).
The Recommended Tag: We used data to highlight the tenure with the highest success rate (e.g., "6 Months - Best Value") to guide indecisive users.

4. The Impact

Trust: By showing the exact final amount upfront, we reduced drop-offs at the final Sign Agreement stage.

Module 13: E-Commerce Seller Onboarding

Role: Product Manager | Focus: Supply Side Growth

1. Executive Summary
I digitized the onboarding process into a Self-Serve Seller Portal that automates GST verification and catalog upload, reducing activation time from days to minutes.

Note: Read How to Enhance Your E-commerce Seller Onboarding in my dedicated blog post: Read More.

2. The Problem Space

The Document Black Hole: Sellers emailed PDF documents. Verification took 48 hours.
Catalog Friction: Uploading 100 products via a CSV file was too technical for small vendors.

3. The Solution (Deep Dive)

The Instant Workflow
API Verification: Integrated with GSTIN APIs. Sellers enter their GST number, and the system auto-fetches their business name and address.
Smart Catalog: Built a "Clone Product" feature. Sellers can search for an existing generic product (e.g., iPhone 13) and just add their price/stock.

4. The Impact

Speed: Reduced "Sign-up to First Product Live" time by 90%.

Module 14: HubSpot CRM (Churn Reduction)

Role: Growth PM (Case Study) | Focus: Retention Strategy

1. Executive Summary
I analyzed the Activation Gap and proposed a Template-First Onboarding strategy to get users to their Aha! Moment within the first session.

Note: Read How to Tackle the High Churn Rate ~ A HubSpot CRM Case Study in my dedicated blog post: Read More.

2. The Problem Space

The Blank Slate: A new CRM is empty. It requires contacts, pipelines, and templates to be useful.

3. The Solution (Deep Dive)

The Pre-Filled Strategy
Industry Templates: During signup, ask "Industry?" (e.g., Real Estate).
Auto-Population: Immediately load the CRM with a Real Estate Pipeline (Lead -> Site Visit -> Negotiation) instead of a generic Sales Pipeline.
Dummy Data: Include 5 Sample Leads so the user can practice moving cards immediately.

4. The Impact

Psychology: Users immediately saw how the tool would work for their specific business.

Module 15: Dating App Revenue Strategy

Role: Product Strategist | Focus: Market Positioning & Revenue

1. Executive Summary
To build a $10M business, you can't just copy Tinder. I developed a blueprint for a High-Intent Premium App that focuses on scarcity and curation rather than volume.

Note: Read the blueprint for a $10M premium dating app in the next 6 months in my dedicated blog post: Read More

2. The Problem Space

Burnout: Users are tired of swiping endlessly with low match rates.
The Freemium Trap: Ad-based models require millions of users to make money.

3. The Solution (Deep Dive)

The Club Model
The Waitlist Gating: Create artificial scarcity. You can't just sign up; you must be approved or invited.
The 3 Matches Rule: Instead of unlimited swipes, give users only 3 highly curated matches per day.
High ARPU: Charge a high subscription fee ($30/month).

4. The Impact

Brand: Establishes the app as a Status Symbol rather than a utility.

Module 16: Vudio.ai (Shoppable Video AI)

Role: Product Manager | Focus: E-Commerce Growth | Status: Live (Shopify App)

1. Executive Summary
I led the development of Vudio.ai, an AI-powered Shoppable Video widget for Shopify. This feature allows influencers to explain products in 30-60 second reels directly on the product page, with an integrated Add to Cart button.

2. The Problem Space

The Static Trap: Traditional product pages are boring. Users bounce because they can't visualize how the product looks or feels in real life.
Missing Sales Assistant: There is no one to answer "Does this lipstick match my skin tone?"

3. The Solution (Deep Dive)

The Contextual Suggestion Logic
This isn't just a video player; it's a recommendation engine.
Context Check: The system identifies the product attributes (e.g., "Dusky Skin Tone" variant selected).
AI Suggestion: The video widget automatically updates to show an influencer with a similar skin tone applying that exact shade.
Key Features
AI Scripting: The system uses LLMs to auto-generate high-converting scripts for the influencers.
Multi-Format Widget: The video can live as a Reel, a Story, or a Popup.

4. The Impact

Sales: Generated 12,000+ Orders directly attributed to the video widget.
Conversion: 10.65% Plays-to-ATC (Add to Cart) Rate.

Module 17: Digitizing Concrete Quality Control

Role: Product Manager | Timeline: 3 Months | Status: Live

1. Executive Summary
I built a digital Concrete Testing Module that automates the scheduling, recording, and verification of all quality tests.

2. The Problem Space

The Missed Interval Crisis: Concrete must be tested at specific ages. QEs were manually tracking dates on whiteboards, often missing the 7-day window.
User Personas: The Site QE says, "I have 50 cubes curing right now. I don't know which one needs testing today."

3. The Solution: A Smart Testing Workflow

The Auto-Generation Logic
The Timeline: The system generates a visual timeline for that specific sample, marking the 7th, 14th, and 28th days as "Due Dates".
Alerts: On the due date, the QE gets a mobile notification: "Test Cube #402 today".
The Conditional Logic
Rule: If the 28-Day test passes, the workflow closes.
Exception: If the 28-Day test fails, the system automatically unlocks the "36-Day Test" (conditional) and flags the sample for Review.

4. The Impact

Compliance: 100% adherence to testing intervals (zero missed tests).

Module 18: Material Inspection Suite

Role: Product Manager | Timeline: 2 Months | Status: Live

1. Executive Summary
I unified three fragmented processes—Material Testing, Sample Testing, and Methodology Testing—into a single Material Inspection Suite, ensuring that no vendor material is used without a digital Pass certificate.

2. The Problem Space

The Fragmented Workflow: The Material Inspector checks the quantity, but the Quality Engineer checks the quality. They used different systems.

3. The Solution: The Gated Procurement Flow

I built a dependency between Inward and Payment.

Trigger: Security creates a Gate Entry.
Hold: The system puts the material in a "Quarantine" state.
Release: Only after the test passes does the system move the material to "Inventory" and enable the "Payment" button.

4. The Impact

Cost Savings: Prevented payment for 20 Lakhs worth of defective steel in the first month.
Efficiency: Unified 3 disparate logs into one Quality Dashboard.

Module 19: Invoice Rejection Workflow

Role: Product Manager | Timeline: 6 Weeks | Status: Live

1. Executive Summary
I built a Conditional Rejection Workflow that decouples the physical exit of the vehicle from the financial rejection of the invoice.

2. The Problem: The Gate Deadlock
When a material failed quality checks, the Site Store Manager had to physically stop the truck from leaving until the paperwork was done. Trucks blocked the gate for hours.

3. The Solution: Decoupling Logistics & Finance

Physical Stream: If material fails, generate a "Gate Pass (Returnable)" immediately. Let the truck leave.
Financial Stream: Trigger a "Debit Note" workflow in the ERP.
The Trigger Rule: The "Reject Invoice" button is hidden by default. It only appears if Material Test Status == Failed OR Quantity Check == Shortage.

4. The Impact

Logistics: Reduced gate turnaround time for rejected vehicles from 4 hours to 15 minutes.
Audit: Created a 100% traceable digital trail for every rejected item, ending he-said-she-said disputes with vendors.

Module 20: User Onboarding & Activation (SaaS)

Role: Product Manager | Timeline: 2 Months | Status: Live (v1.1)

1. Executive Summary
I designed a Gamified Onboarding Sequence that guides users through a strict, dependency-based setup path.

2. The Problem: Analysis Paralysis

The Empty State: A new user lands on the dashboard. It's blank. There are 50 buttons.
The Error: Users would try to create a "Schedule" before defining the "Calendar", causing the system to crash.

3. The Solution: The Golden Path

The Guided Journey
I forced a linear setup process.
Step 1: Build Project Tree (Highlighted). All other buttons disabled.
Step 2: Set Working Days.
The Progress Tracker
I added a permanent widget in the top-right corner:
Red: Setup Incomplete.
Green: Ready for Launch.
Psychology: Users hate seeing a Red status. This drove them to complete the boring setup tasks quickly.

4. The Impact

Activation: Reduced time-to-value for new projects from 1 week to 1 day.
Support: Reduced "How do I start?" support tickets by 70%.

Module 21: Global Configuration System

Role: Product Manager | Timeline: 3 Months | Status: Live

1. Executive Summary
I built a Global Configuration Engine that acts as the Single Source of Truth, enforcing corporate standards across all sites.

2. The Problem: Data Fragmentation

Site A calls it M25 Grade. Site B calls it M-25 Concrete.
Result: Analytics was impossible.

3. The Solution: Parent-Child Inheritance

The Cascading Update
Global Layer (Admin): The HQ defines the master list (e.g., M25, M30).
Local Layer (Project): When a new project starts, it inherits this master list.
Update Logic: If HQ changes the standard test for M25 from Slump to Flow, this change automatically propagates to all new projects.

4. The Impact

Analytics: Enabled true cross-project benchmarking for the first time.