One system for every site you run

We build, launch and run the patient pathway for your whole group on wai. Your data, your brand. You own it.

Every site on one record, one booking system and one set of workflows

Consult notedrafting liveReady to signAudioRecord

We work in your clinic

Define a useful care pathway with clinicians and operations staff, then agree how its outcomes will be measured.

statin therapy in CKD?nice.org.ukJournalsThe record12[1][2][3]

We start from a live platform

Evaluate the available wai components and integration scope for your specific pathway before committing to a build.

Referral letter12 Jul 2026Compliant ✓Coded ✓From consult

You own what we build

Agree data, workflow, configuration and model rights, portability and exit terms in your contract.

What we build for clinic groups and chains

Built on wai around your workflows. You own it.

One record across sites

A patient seen at one site is known at the next. The consult, the front desk and the follow-up use the same record.

Booking and payments

wai Checkout takes bookings and payments for every site under the group's brand. Revenue reports in one place.

Notes and letters

wai Clinicians drafts the note during the consult and the letter after it. The clinician reviews and signs.

Front desk

wai Admin handles patient messages, bookings and follow-up across the group. Staff approve before anything is sent.

Built to be trusted

What is in place today. Open certifications are listed on the security page.

Human oversight

Review which actions require approval, what can happen automatically and how exceptions are handled before use.

Audit review

Ask to see the event log, export process and retention controls for the workflows you plan to use.

Security review

Review encryption, access controls and incident procedures with your information-governance team.

Data location

wai hosts each clinic's records in its own country, under that country's rules. We set this up with your clinic.

How it works

A fixed fee for the first build, then a monthly fee per site. wai Clinicians seats and payments sit in the same agreement.

1. Pick one pathway

Choose a clinically useful pathway with measurable outcomes and a named owner.

2. Build and validate

Define safety, information-governance and acceptance gates before any live use.

3. Add the next

Assess each additional workflow against its own risks and integrations.

Questions

What healthcare teams ask us before a build.

What does wai build for clinic groups and chains?

A system of your own on the wai platform, covering one record across sites, booking and payments, notes and letters, front desk. We build it with your team, on your data and under your brand.

Who owns the system?

Agree data, workflow, configuration and model rights, portability and exit terms in your contract.

Do you build from scratch?

Evaluate the available wai components and integration scope for your specific pathway before committing to a build.

How is it priced?

A fixed fee for the first build, then a monthly fee per site. wai Clinicians seats and payments sit in the same agreement.

How does a build start?

Choose a useful pathway with your team, agree the controls and validate the workflow before live use.

How is patient data protected?

Review which actions require approval, what can happen automatically and how exceptions are handled before use. Review encryption, access controls and incident procedures with your information-governance team. Ask to see the event log, export process and retention controls for the workflows you plan to use.

Where is data hosted?

wai hosts each clinic's records in its own country, under that country's rules. We set this up with your clinic.

When it has to work, it runs on wai

Request a demo. We will show you the first pathway we would build.

Who else we build for