Onboarding
Collect the information needed for an agreed workflow. Sensitive records require a separate assessment.
CLIENT PORTALS
A simpler way to work with your customers.
Give clients one branded place to complete agreed tasks, share information and see what happens next. We design around your workflow—not the other way around.
ClinicOS
Pilot-stage productClinic workflows, connected.
- Client portal & family profiles
- Intake & consent forms
- Service-based booking
TradeOS
Pre-launchBuilt for the work behind the work.
- Client-facing portals
- Requests & quotes
- Invoices & receivables
Client-facing portals built into our own software products.
POSSIBLE MODULES · NOT AN INCLUSION LIST
One place. A clearly defined purpose.
Files & updates
Organise document handoffs and progress updates with appropriate access rules and retention decisions.
Booking
Connect an agreed provider or scope a booking workflow. Availability, changes and reminders need end-to-end testing.
Payment-provider links
Use supported payment services. Fees, account ownership and reconciliation must be agreed.
Roles & permissions
Define what customers, staff and administrators may see and change. Test cross-account access before launch.
A focused administration area
Manage the core workflow without promising a complete business-management platform.
START NARROW
Map the journey before adding modules.
An initial portal proposal identifies the included workflow, roles, screens, data and integration. Optional modules are not automatically bundled.
Client-facing portals are built into our own products, ClinicOS and TradeOS — see our software products. Your portal is scoped around your own workflow.
INVESTMENT
A portal is more than a login screen.
Why there's no price list here
A portal's price depends on the workflow, number of roles, and which optional modules you actually need — publishing one number wouldn't be honest across that range.
What we scope first
Which modules you need (onboarding, files, status, booking, payment-provider links), how many roles, and what handover looks like. See Pricing for our published website prices.
A PRACTICAL PATH TO LAUNCH
Good work starts with
a clear plan.
No vague scope. No promise to build everything at once.
Discover
Understand your users, workflow and what needs to improve.
Plan
Agree the first useful version, budget, milestones and exclusions.
Build & Test
Review progress and test the experience and key workflows.
Launch & Support
Confirm handover, access and ongoing responsibilities.
PORTAL QUESTIONS
A few useful answers.
Which modules are included to start?
Only the ones agreed for your initial scope — onboarding, files, status updates, booking or payment-provider links are optional add-ons, not automatic.
How many client/staff roles are supported?
Role count and access levels are agreed during scoping — a simple portal is different from a multi-role one.
Can it handle regulated or sensitive data?
Not by default. Healthcare, financial or other regulated data needs a separate assessment before we commit to that scope.
Does it connect to our booking or payment provider?
Only where the provider's API supports it — checked during scoping, not assumed.
Who owns the portal and the data in it?
Ownership of your paid-for deliverables, your data and the handover are confirmed in your project agreement.
LET’S MAKE THE NEXT STEP CLEAR
Have a project in mind?
Tell us what you want to build—or what is not working today.
Discuss Your Project