Saizen Acuity Customer Portal

Overview

I built the Saizen customer portal because project delivery was scattered across email, messages, shared drives, and manually prepared updates. The portal pulled that mess into one secure place where clients could see active projects, progress, documents, milestones, updates, and conversations without asking the team to reconstruct the story every time.

What It Delivers

• Secure authentication separating client access from Saizen administrative and staff access.
• Client-specific visibility so each customer can access only their own projects, documents, updates, and conversations.
• A project dashboard displaying active projects, current status, percentage completion, and upcoming milestones.
• Individual project workspaces containing delivery timelines, progress information, latest updates, files, and communication history.
• Project timelines showing completed stages, current work, upcoming actions, and delivery milestones.
• Structured project updates containing the update title, message, publication date, and responsible team member.
• Threaded client replies beneath project updates so feedback remains connected to the relevant delivery event.
• Dedicated project-level messaging between clients and the Saizen team.
• Google Drive-connected file access for sharing proposals, deliverables, working documents, and supporting assets.
• Notifications for new updates, replies, messages, milestones, and client actions.
• Administrative controls for creating projects, assigning clients, changing progress, publishing updates, and managing conversations.
• A visible audit trail of project communication, progress changes, uploaded documents, and delivery activity.
• A foundation for client sign-off, responsibility tracking, testimonials, smart reminders, and automated onboarding workflows.
• A single source of truth for the complete client relationship after payment and project activation.

What I Did

• Defined the portal's product structure, client journey, project hierarchy, and access model.
• Designed the distinction between client, Saizen administrator, and Saizen staff permissions.
• Built the backend application, authentication flow, database structure, project records, update system, progress tracking, messaging, and file-access logic.
• Created the customer-facing dashboard and individual project interfaces.
• Implemented project percentage tracking, timelines, latest updates, threaded replies, and project-specific chat.
• Structured the portal so new customers and projects could be created dynamically rather than hard-coded into static pages.
• Connected the portal concept with Saizen's onboarding process, including payment activation, welcome communication, information collection, kickoff, delivery, and eventual sign-off.
• Deployed and tested the application through GitHub and Render.
• Configured database initialization, authentication, application startup, and deployment behaviour.
• Worked through limitations associated with SQLite persistence on free-tier cloud deployment and structured the portal for later migration to more durable infrastructure.
• Continued improving the system based on internal feedback around mobile usability, client responsibilities, reminders, proof of delivery, and testimonial collection.

Outcomes

• Client projects moved from fragmented communication into structured digital workspaces.
• Customers gained direct visibility into percentage completion, project timelines, recent activity, documents, and next milestones.
• Project communication became attached to the relevant project and update rather than being lost across unrelated email and messaging threads.
• Saizen gained a repeatable delivery interface that could support different clients, services, and project types.
• The portal created a clearer boundary between pre-sale CRM activity and post-sale customer delivery.
• Project progress, client feedback, files, and conversations could be reviewed as a continuous audit trail.
• The system established the foundation for automated onboarding, milestone sign-off, responsibility tracking, reminders, testimonials, and reporting.
• The portal strengthened Saizen's ability to present delivery as an organized and transparent operating system rather than an informal consulting process.

Proven Impact

• Deployed as a functioning browser-based customer portal.
• Used a multi-role structure covering clients, Saizen administrators, and Saizen staff.
• Supported multiple projects per customer through dedicated project workspaces.
• Combined progress tracking, messaging, timelines, files, updates, and replies inside one application.
• Used as the secure customer-delivery layer within Saizen's broader onboarding and project-management process.
• Reduced reliance on disconnected status emails, shared links, messaging threads, and manually prepared progress reports.

Why It Matters

• Professional delivery requires clients to understand what is happening without repeatedly requesting updates.
• A secure portal preserves project context, accountability, and evidence throughout the customer relationship.
• Bringing progress, communication, files, and milestones together reduces ambiguity for both the client and delivery team.
• The project demonstrated my ability to build a complete multi-user application involving authentication, databases, roles, project state, communication, and deployment.
• It converted Saizen's delivery methodology into reusable digital infrastructure.