What we doServicesSix offers

Six offers, and one team that answers for all of them.

Every engagement below is the same shape: a call about what is slowing the clinic down, a proposal in writing, then weekly releases into a live building. What changes between them is the material we work in.

Where to startEvery offer opens the same brief form, with that service already selected. If none of them is obviously yours, the first one you read is close enough.
Each offer · what it is · what ships · the brief form for itEach offer · what ships · the brief form01 → 06
01

Websites & patient portals

The public site and the logged in half of it. Booking a receptionist trusts, records a patient can find, and pages that load on a waiting room connection.

What ships
Sitemap and content modelBooking flow with staff confirmationPatient portal login and records viewContent in two languagesPerformance budget held at launchStaff walkthrough and written handover
You end up withA live site and portal, the content model your team edits it through, and a recorded walkthrough for new staff.
02

Answering & follow-up

The enquiries nobody is awake for. Messages that arrive at 2am get answered, missed calls get followed up before the clinic opens, and referrals stop falling through.

What ships
Enquiry triage across web, phone and channel inboxesOut of hours answering with staff handover rulesMissed call follow up queueReferral routing to the right clinicianEscalation policy written with your teamWeekly review of what it answered
You end up withA queue your front desk opens in the morning that is already empty, and a log of every answer given in your name.
03

Product & interface design

Interfaces a clinician can finish during the consultation. We design against real charting flows and the way the room is actually laid out, then test with the staff who will use them.

What ships
Flow mapping against current chartingInterface design for the clinical screensComponent library your build team works fromPrototype tested with clinical staffAccessibility reviewDesign handover to engineering
You end up withScreens signed off by the people who will use them, and a component library the build cannot drift from.
04

Growth & content

The channels that bring patients through the door. Local search, clinic channels, and writing a doctor is willing to put their name on.

What ships
Local search and listings setupChannel calendar owned by your teamWriting reviewed by a clinician before publishPatient facing explainersEnquiry source reportingMonthly read of what worked
You end up withA calendar your team can keep running without us, and a report that ties enquiries back to where they came from.
05

Strategy & operations

Where the queue backs up, which system to build first, and what it costs to run. Written down and argued through before anyone opens an editor.

What ships
Operations audit on site with your staffQueue and handover mappingBuild or buy recommendation per systemSequenced roadmap with dependenciesRunning cost estimateWritten decision record
You end up withA document that says what to build, in what order, and what it will cost to keep running. Useful even if you never hire us.
06

Product engineering

Long running systems we still own after launch: records, billing, and the integrations with labs and machines already in the building. Sparsha came out of this work.

What ships
Records and billing systemsLab and device integrationsMigration off existing toolingWeekly releases into the live clinicOn call ownership after launchAudit trail and access controls
You end up withA system in daily clinical use, and the same team on call for it afterwards.
How it goes

Five steps, and the last one does not end.

Same arc for all six offers
01

Scoping call

A call with the people who will build it, not a salesperson. You describe what is slowing the clinic down; we say plainly whether we are the right team for it.

You getA written summary of the problem in your words.
02

Proposal

Scope, sequence and cost in writing, with what we are not doing stated as plainly as what we are.

You getA proposal you can take to your board.
03

Build cadence

Work goes into a live clinic weekly. You see it in use on the floor rather than in a demo, and the sequence changes when the floor says it should.

You getA release every week, and the note explaining it.
04

Launch

Staff walkthroughs happen before the switch, not after. The system goes live with the people who built it watching it work.

You getTrained staff and a system in daily use.
05

We stay on the account

No handover to an account manager. The people who built the system are the ones who answer the phone, and there is no date after which that stops.

You getThe same team, the same phone number.
no end date on step 05
Ready to Start?

Tell us what you're
building.

Whether you have a detailed brief or just an early idea, we'll help you figure out the right approach and turn it into more booked appointments.

About the Team
Start a project

Tell us what is breaking and we will tell you what it takes.

The first call is scoping, not sales. You will speak to the people who would build it.

RegionSouth Asia
CareersOpen roles
Budget$15k
$5k$15k$30k$50k+
Goes to the team that would build it.