Frenztalk
A tuition business.
A connected operating system.
A three-person collaboration became a long-term client project. For v1, I scoped requirements and feasibility, built frontend and backend features, and supported users. I then took sole ownership of the v2 rebuild.
Inside the rebuildFrom the admin’s first booking to the student’s class link.
Fix the workflow.
Build the right foundation.
The problem
The original Firebase-based booking workflow could allow overlapping reservations. As the business relied on the system, scheduling consistency became a practical operational issue.
The decision
I rebuilt v2 around a relational PostgreSQL model. Database exclusion constraints prevent overlapping Zoom-account reservations, while a central booking engine coordinates allocation and rescheduling.
The implementation
I built the v2 interface, backend, billing workflows and Zoom integration, with legacy synchronisation to support the transition. I also established feature branches, Vercel previews and automated release checks.
The follow-through
I continue to maintain the platform and help the client resolve issues. AI-assisted development and Supabase MCP support investigation and delivery within the Git release workflow.
Keep in touch.