Case study
Operations Hub
Eight internal tools for procurement, logistics, manufacturing, and facilities, connected through one shared data layer.
Technology stack
- React
- Firebase
- Python
The challenge
Work was split across repetitive handoffs, files, and team-specific tools. The platform needed to connect them without forcing every process into the same workflow.
My role
I designed and built the platform, translating operational requirements into software used for day-to-day work.
Design approach
- Share status and ownership through one Firebase data layer.
- Use React for work that needs a screen and Python for repeatable processing.
- Keep approval rules separate from exceptions.
- Release useful modules instead of waiting for the whole platform.
Capabilities
PO Automator
Creates purchase orders from approved requests and applies supplier and approval rules.
Python
Invoice Processor
Extracts invoice data, checks open purchase orders, and flags mismatches.
Python
Location Tracker
Combines carrier and internal data to show asset and shipment locations.
React · Firebase
Manufacturing Orders
Tracks production orders, schedules, and capacity conflicts.
React · Firebase
Logistics Automator
Selects carriers and prepares bookings and documents from routing rules and rates.
Python
File Organizer
Classifies and files documents by type, supplier, and date.
Python
Inbound Control App
Tracks inbound deliveries from expected arrival to goods receipt.
React · Firebase
Utility Metrics App
Combines electricity, gas, and water use for reporting and cost allocation.
React · Firebase
Outcome
The tools now share records and workflow status. This public write-up leaves out employer data, internal interfaces, and figures I cannot show.