2026. Next.js, Tailwind CSS, Neon Postgres, Auth.js, Vercel

Hello Central

Hello Central is the internal portal I built for Hello Sugar, a waxing and laser franchise with 300+ locations. It brings resources, weekly video updates, a knowledge-base library, a community ideas board and a support-ticket system into one mobile-first hub for franchisees, estheticians and corporate staff.

Screenshot of Hello Central

Hello Sugar is a waxing and laser franchise with more than 300 locations, and the information franchisees needed was scattered everywhere. Links, training documents, weekly video updates and policies lived across Google Drive, Notion, email threads and messaging apps, so owners spent time hunting for answers or asking corporate directly. Support requests had no central place to go and were hard to track, and estheticians used a separate standalone app. Most franchisees work from phones and tablets on the salon floor, which made the problem worse.

I built Hello Central, a mobile-first portal that puts all of this in one place. I moved the original vanilla HTML/JS site to Next.js, React and TypeScript page by page, backed by Postgres on Neon and deployed on Vercel. Then I merged the esthetician app into the same codebase as its own portal with phone-number sign-in. The platform includes:
- a support-ticket system with Slack alerts and per-agent replies
- a Franchise Library that syncs automatically from Notion and supports highlight comments
- a "Voice" board where owners post and vote on ideas
- a video library with unread badges
- a shared events calendar synced from Google Calendar

It connects to the company's main tools, including Boulevard, Pronto, Notion and Google. I also built an MCP server so AI assistants can query ticket and feedback data directly.

Hello Central is now the main hub for franchisees, estheticians and the corporate support team across all 300+ locations. Owners find resources and get help in one place instead of searching several tools. Support requests are tracked from start to finish, so the support team can see what's open, who's handling it and how long responses take. Retiring the standalone esthetician app left one codebase to maintain, and the integrations and MCP server let leadership pull insights from tickets and owner feedback without digging through the app.