Built for your practice

AspireOS, shaped around how your practice works.

When your practice does something standard software does not, we can build it a module of its own: designed around your steps, switched on for your practice only, and part of the AspireOS you already use.

Talk to us See examples

What we can build

Modules for the work only your practice does.

Some work is particular to a profession, a service or one practice. Rather than a spreadsheet beside the software, it can live inside AspireOS.

Shaped around your steps

We start from the way your practice already works: who does what, in what order, and what has to be recorded. The module follows those steps rather than asking you to change them.

Switched on for your practice only

A custom module is gated to your practice. Its menu items, pages and actions only exist where it is turned on, so nobody else sees it and nothing else changes.

Part of the AspireOS you use

It works with your calendar, patient files, invoices, letters, team records and permissions. There is no second system to log into and no data to copy across.

Real examples

Two modules we have built.

Both are part of AspireOS today, each switched on only for the practices that use it.

For hearing and audiology practices

School screening

Running screening days at schools: bookings from families, results on the day, letters home and a portal for each school.

Screening days on the calendar, with a booking link for each school's day. Families open the link, add their details, then add each child with date of birth, school year and consent.
One family can book several children at once, and the practice can take a deposit per child through its existing invoices and pay links, or switch deposits off.
On the day, staff mark each child Booked, Attended, Cancelled or Did not attend, then record Pass or Fail. Pass sends the results letter; Fail asks for a reason and sends the referral letter.
A class list exports to CSV, and each child's file shows their school, school year and screening history.
A school portal, with no login, shows the school its screening list, the practitioners on its days with their checks and registration, and only the files the practice chooses to share.

Calendar
Invoices & pay links
Letters
Patient files

For practices with an employed team

Career framework and pay levels

A practice’s own levels, pay terms and reviews, so progression and pay follow a written framework instead of a spreadsheet.

Career levels for clinical employees, each with its own pay band and pay terms, and a record of who was on which level from which date.
Placing someone on a level, with an individual base where their pay sits above the band, set only by the owner with payroll access.
Quarterly reviews built around the current level: competencies, manager feedback, objectives and readiness for the next level, signed by both sides.
A promotion path that a signed review starts and only the owner approves, with a start date. Pay never changes on its own.
Targets that follow the level and pro-rate for part-time hours and approved leave, read from the same timesheets and leave records payroll uses.

Team
Timesheets
Leave
Payroll prep

How it works

From a conversation to a module you rely on.

1. Talk to us
Tell us how the work runs today, what it costs you in time, and what a good result would look like.
2. We scope it
We write down what the module does, who can use it and what it touches in AspireOS, and agree it with you before building.
3. We build and test it
We build it inside AspireOS with checks of its own, then you try it with Testing mode on, before anything reaches a patient or family.
4. It goes live for you
We switch it on for your practice only. The rest of AspireOS stays exactly as it is, for you and for everyone else.

Questions

Questions practices ask

What counts as a custom module?

A part of AspireOS built for the way one practice works: its own pages, settings, letters or rules, switched on for that practice. The School screening and Career framework modules on this page are two examples.

Will other practices see our module?

No. A custom module is gated to the practice it was built for. Its menu items, pages and actions are only available where it is switched on.

Does a custom module change the rest of AspireOS?

No. Your calendar, notes, invoicing and the rest of AspireOS keep working the way they do today. The module adds to them; it does not replace them.

How is a custom module priced?

Each module is quoted on its own, once we have scoped it with you, because no two are the same size. Your AspireOS subscription stays as it is on the pricing page.

Is this the same as Custom Automation?

They are related. Custom Automation is workflows and automations built on the features you already have; a custom module adds new parts to AspireOS for your practice. If you are not sure which you need, talk to us.

Looking for a workflow on the features you already have? See Custom Automation.

Tell us what your practice needs

Talk to our team about a module for your practice, or start with AspireOS as it is: 16-day free trial, no card needed.

Talk to us Start free trial