Building software for internal business operations involves clear constraints: users need high data density, structured access control, and dependable tracking for daily administrative and financial workflows.

1. Monitoring Operations, Reports & Revenue Tracking

During my rendered OJT hours at Zhuren TechSolutions, I was assigned by the CEO to design and engineer an internal operations system to replace fragmented tracking tools.

The platform serves as an operational hub: monitoring day-to-day business activities, generating automated management reports, and tracking historical project records and company revenues.

2. Choosing the Stack: Laravel, Inertia & PostgreSQL

I selected Laravel paired with Inertia.js, Tailwind CSS, and PostgreSQL. Inertia provided a responsive single-page application experience without requiring an independent REST API surface to be maintained.

PostgreSQL provided strict relational data modeling, transactional boundaries for financial and revenue records, and reliable query execution across operational tables.

💡

Direct collaboration with leadership enabled rapid feedback loops: shipping iterative working prototypes directly into staging for review.

3. Security, Authorization & Privacy

Because the system manages internal operational records and revenue metrics, data privacy was a primary consideration. I implemented role-based authorization gates and ensured no proprietary business data leaked outside the protected environment.

Conclusion & Takeaways

The project reinforced the value of practical engineering: delivering dependable software that streamlines business workflows, provides actionable reporting, and solves tangible operational needs.