The organisation needed one SaaS customer operations platform for customers, account teams, support staff, and platform administrators. The existing journey divided trial onboarding, workspaces, plans, subscriptions, usage, billing, account changes, product updates, support, and customer health between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
A complete SaaS customer operations platform shaped around customers, account teams, support staff, and platform administrators
The organisation needed one SaaS customer operations platform for customers, account teams, support staff, and platform administrators. The existing journey divided trial onboarding, workspaces, plans, subscriptions, usage, billing, account changes, product updates, support, and customer health between separate tools and informal follow-up, so the project had to solve the operating model as well as the interface.
Discovery followed the full journey from the first customer or staff action to its operational and commercial close. That exposed the handoffs between customer onboarding, subscriptions, and account operations, including the exceptions that a feature list would have missed.
- Map the people, decisions, and records across the whole SaaS customer operations platform.
- Separate firm software services rules from habits created by the old tools.
- Agree what the first release must complete from end to end.
The product joined customer onboarding, subscriptions, and account operations without blurring roles
Connect commercial entitlement to the workspace and product usage while keeping billing, access, and support histories independently reviewable.
In the SaaS customer operations platform, each audience receives a focused home while the underlying state remains shared. The interface shows what needs attention, who owns the next action, and why work is blocked, while secondary detail stays available for review without crowding everyday tasks.
- Design the primary journey for every audience named in the brief.
- Give exceptions, corrections, and cancellations an explicit route.
- Use realistic records to test the complete flow before widening the surface area.
Next.js, ASP.NET Core, PostgreSQL formed one supportable SaaS customer operations platform
The architecture follows business ownership rather than the navigation menu. Next.js, ASP.NET Core, PostgreSQL share versioned contracts, server-side permissions, observable integrations, and one authoritative record for the decisions behind subscriptions.
In the SaaS customer operations platform, slower or external work runs through durable jobs with idempotent handling and visible failure states. Logs retain the organisation, actor, and product record needed to investigate a problem without guessing from a generic error message.
- Next.js supports the primary product surface.
- ASP.NET Core owns a bounded part of the product journey.
- PostgreSQL keeps operational data and handoffs reviewable.
The release had to prove the whole SaaS customer operations platform, not one polished screen
Customers can manage their account in one place and internal teams can understand the full relationship without stitching together tools. The release plan therefore followed representative work across every audience and the complete path through customer onboarding, subscriptions, and account operations.
Acceptance for the SaaS customer operations platform included ordinary work, missing inputs, repeated requests, failed integrations, permission boundaries, and the route back to a trustworthy state. The team checked whether staff could understand and recover from a problem without direct database help.
- Run the busiest realistic journey from start to operational close.
- Rehearse a failed integration and a repeated customer action.
- Confirm that every role sees only the work and data it owns.
- Trace a management result back to the records that produced it.
What the work established
Customers can manage their account in one place and internal teams can understand the full relationship without stitching together tools.
- 01
The SaaS customer operations platform now gives customers, account teams, support staff, and platform administrators one shared operating record.
- 02
Customer onboarding, subscriptions, and account operations follow the same product rules.
- 03
The system makes ownership and exceptions visible instead of hiding them in manual follow-up.
- 04
The product can grow from clear workflow, data, and service boundaries rather than isolated features.