I worked on a casino floor management platform that needed to support a wide range of operational workflows: voucher control, game data integration, payment processing, employee management, administration, reporting, permissions, audit trails, machine and floor status, and player or customer records.
The project started with a broad operational need, not a tidy technical spec. Stakeholders and investors knew the business problem the platform needed to solve, but the system still had to be translated into requirements, workflows, data structures, APIs, screens, permissions, reporting, and production-ready behavior.
I started by working with stakeholders and investors to document requirements and understand the operational pieces that needed to fit together. This included what information had to move through the system, who needed access to it, what actions different users needed to take, how auditability should work, and how the platform would integrate with third-party game data.
From there, I designed the architecture and data structures, created MongoDB schemas, and wrote the backend APIs in Node and Express. I also established an ongoing technical dialogue with the third-party game API provider so the platform could integrate with external game data correctly.
My hands-on work included the full backend and the first version of the frontend. That first frontend gave the product its initial working interface: the starting point for managing operational workflows, viewing information, handling administrative actions, and proving the system could function as a real platform rather than just an idea.
After that foundation was in place, I built the team that improved on the original frontend and carried the product forward. I created the technical direction, helped the team understand the system, and guided the transition from initial build to a more complete production application.
The system went live in production in 2016.
This project is a useful example of how complex operational systems become buildable. The work was not just coding screens or APIs. It required understanding a business domain, translating stakeholder needs into system design, connecting third-party data, building the backend foundation, creating the first usable interface, and forming a team that could continue the product.
