Patient and user management SaaS
Xntral
An all-in-one SaaS product to manage users, track patients, and give clients one place to run their operation.
The product
Story
Xntral is one SaaS workspace for managing users, tracking patients, and giving clients a single place to work. The calendar is a view of those records, not a separate product.
The shape of the system
Four record types carry the product: users, patients, locations and functions. Everything else is a view over them. That decision is what keeps scheduling from turning into a second system with its own version of the truth.
Recurring appointments are booked against those records rather than stored as standalone calendar entries. A booking knows which patient, which location and which function it belongs to, so the calendar screen and the patient record are always describing the same fact.
What was delivered
- Users, patients, locations and functions in one workspace
- Recurring appointment scheduling against those records
How the work ran
The system came to five modules, delivered across four sprints in 56 days. That is the 14-day sprint shape repeated four times, with each sprint ending in something reviewable rather than a single long build with one delivery at the end.
Counting the surface up front is what made that plan realistic. Five modules was never going to be a two-week job, and saying so before the first sprint meant the schedule matched the work instead of fighting it. The reasoning behind that count is written up in how to scope a first SaaS system in 14 days.
Why it was built rather than bought
Generic scheduling tools can hold appointments. What they will not hold is this operation's own records, with these relationships, in one place a client can run their day from. When the records are the business, an owned system is the cheaper answer over time, which is the argument in when to build custom software instead of buying.
Client feedback
Rodney, CEO of Xntral, noted that every feature on the project was completed, and pointed to the technical expertise, consistent problem-solving and collaborative approach behind it.
Similar work runs as a fixed-scope SaaS MVP sprint or, where the workflow is specific to one operation, as custom software development.
Impact
4
Sprints
5
Modules
56
Days
Delivery
- Users, patients, locations and functions in one workspace
- Recurring appointment scheduling against those records
Client feedback
“Successfully completed every feature on our recent project. The technical expertise and commitment were instrumental in driving our progress, with consistent problem-solving and a collaborative spirit that made a significant impact on the team.”
Related services and guides
Service
Saas Mvp Development
Service
Custom Software Development
Guide
How to scope a first SaaS system in 14 days
Fix time and budget, then scope. One workflow, one system, a clear handover.
Guide
SaaS MVP architecture: what to build in version one
Monolith, auth, database and API boundaries for a first SaaS product.
Guide
When to build custom software instead of buying
The cases where an owned build beats another subscription.