Product pressure
What the business needed to make true before the next stage of growth.
Back to Case Studies
Case Study
Salvus Care
Care Services Website
From a confusing care directory to an accessible path families can follow.
Zyvor designed and developed Salvus Care as an accessible, responsive care-services website so participants, families, carers and referral partners could understand NDIS and daily-support options — then take a next step with less friction.
Clarity and trust first.
Industry
Healthcare / Disability & Aged Care
Services
Accessible UX, Web Design & Development, Technical SEO
Engagement
Design and development
Timeline
September 2022 – December 2022
Product type
Care services website
Case study structure
Overview
What this engagement was about.
Zyvor designed and developed Salvus Care as an accessible, responsive care-services website so participants, families, carers and referral partners could understand NDIS and daily-support options — then take a next step with less friction.
Delivery path
How strategy, design, and engineering stayed connected through the engagement.
Operating model
The decisions that kept ownership, state, and next actions clear for the team.
Outcome lens
Why the work was sequenced for trust, scale, and a reusable foundation.
Challenge
People were making care decisions under pressure.
Care-service websites have to explain multiple support options to people who may already be navigating complex personal circumstances. If the experience is clever instead of clear, it blocks the people it is meant to help.
Product pressureState gapsNext action
Signal
Homepage
Context
Accessible service design is a product decision.
Care-services homepage focused on trust, reassurance, and service discovery.
Business problem
Salvus needed a professional digital presence that made NDIS and daily-support services understandable and enquiry straightforward.
User problem
Participants, families, carers and referral partners needed reassurance, plain language and an obvious next step.
Operational limitation
Multiple support types needed reusable service-detail pages so content stayed consistent as the directory grew.
Product limitation
Vague service names, a homepage that explained everything at once, and hidden mobile navigation would have added confusion.
What was breaking
The friction points that made the old approach expensive to keep.
Service pages using vague names
Homepage explaining everything at once
Mobile navigation hiding important support paths
Enquiry disconnected from the service being viewed
Hierarchy that was hard to scan under stress
Strategy
Reduce confusion before adding persuasion.
A clear service hierarchy, reusable detail templates and simple enquiry paths would help people understand support options without friction.
Organize support services into clear categories
Use reusable service-detail templates
Keep navigation and enquiry paths simple
Validate mobile usability for visitors arriving on phones
Solution
A collaborative, end-to-end partnership.
Zyvor designed around service clarity and trust, then built accessible information hierarchy, responsive layouts, enquiry workflows and technical SEO.
Discover
Understood how participants, families, carers and referral partners look for NDIS and daily-support services.
Define
Set the service directory, reusable detail templates and a straightforward enquiry model.
Design
Created a calm, accessible hierarchy with trust-focused content and readable service pages.
Build
Implemented responsive pages, contact workflows, analytics, technical SEO, QA and deployment.
Launch / Scale
Left a maintainable service structure for additional support content.
Strategy — Key Decisions
Accessible hierarchy over clever marketing.
These are the choices that shaped the product — not a gallery of what shipped, but why the work was sequenced this way.
Service directory before brand flourish
People need to recognise the support they are looking for before they will trust the organisation.
Reusable service-detail templates
Personal activities, travel, daily tasks and community participation should be understood in the same way.
Accessible information hierarchy
Care decisions are often made under stress; scanning has to work.
Mobile-first usability
Many visitors will arrive on phones and cannot afford a hidden next step.
Enquiry tied to the service being viewed
Contact should continue the page the person was reading, not reset the conversation.
Design
A care-service experience that feels reassuring.
Visitors should understand what support is available, feel they are in the right place, and know how to enquire without decoding jargon.
Care-service websites must be clear before they are clever.
Homepage focused on trust, reassurance and service discovery
Plain-language service categories
Reusable detail pages for each support type
Simple navigation and contact options on every key page
Trust, clarity and accessibility
Accessibility is part of the product, not a visual style
Trust content should calm, not overwhelm
Technical SEO should never compromise readability
Homepage
Care-services homepage focused on trust, reassurance, and service discovery.
Services
Service directory helping visitors understand available support options.
Personal activities
Reusable service-detail structure for participant support information.
Development
From service hierarchy to an accessible live website.
The site was built with PHP, MySQL, responsive front-end, contact forms, analytics, SEO tooling and hosting/SSL, with production deployment after QA.
Accessible structure
Clear hierarchy and reusable service-detail templates.
Responsive delivery
Mobile-first navigation and service scanning.
Enquiry workflows
Contact paths connected to the service being viewed.
Launch operations
Technical SEO, analytics, QA and production deployment.
Key Features
The parts of the system that mattered.
Homepage
Trust, reassurance and a way into support options.
Services directory
A scannable map of available care support.
Personal activities
Reusable service-detail structure for participant support.
Travel & transport
A clear support page for a specific need.
Daily tasks
Accessible explanation of everyday assistance.
Community participation
Support content that stays consistent with the rest of the directory.
Life skills
Another support line using the same readable pattern.
Enquiry
Straightforward contact from the service being considered.
Outcome
Support services that are easier to understand.
Salvus Care gained a clear professional digital presence that made support services easier to understand across desktop and mobile, with a reusable structure for future content.
Clearer service understanding
Support options are organised so people can find the relevant path.
More consistent pages
Reusable templates keep the directory coherent as content grows.
Better mobile access
Key support paths remain usable on a phone.
Maintainable foundation
New service content can follow the same accessible pattern.
Technology
Stack used on this product.
The tools that supported delivery — chosen for the product shape, not as a generic stack list.
PHP
MySQL
HTML5
CSS3
JavaScript
Responsive Web Development
Contact Forms
Analytics
SEO Tooling
Hosting & SSL
Key Takeaways
What made this engagement successful.
Start with visitor needs
Care websites should reduce confusion for people already under pressure.
Name services plainly
Vague labels force families to decode the organisation instead of finding help.
Reuse the detail pattern
Consistency is how a directory stays understandable.
Keep contact beside the service
The next step should not require starting over.
Related Case Studies
More stories like Salvus Care.
B2B Service Website
MJ Facility Services
From a generic brochure to a B2B site built around the quote.
B2B Corporate Website
VALIDATE Group
From insider language to a B2B journey buyers can follow.
Lead Generation Website
GMS Painting & Decorating
From an unclear local presence to a site that makes enquiry easy.
Next step
Have a similar challenge?
If this story feels close to the pressure in your product, the useful next step is a conversation about the problem — not another gallery of screens.