Sefton
Founder
2026–Present
An operating system for allied health
Context. Lean practices juggle six to eight disconnected tools, and often give a billing vendor a cut of collections. Decision. Build the operating layer itself: billing-first, bilingual, one place.
I design AI for expert users doing regulated work, where the system drafts and the professional confirms. Sefton is that applied to allied health. It is bilingual and billing-first, and it replaces six to eight vendors with one layer that runs the visit, the back office, and the business. Care is bilingual to the core: real-time interpreted telehealth with live captions in ten languages, voice dubbing in seven, and a written patient portal in eleven. Sefton Voice is not a scribe, it's the pipeline from conversation to revenue: it writes down the note the clinician dictates, suggests ICD-10/CPT codes with confidence scores, and hands a clean claim to built-in billing (claims, prior auth, denials, ERA). Nothing is coded or billed unattended, and practices keep 100% of their revenue.
The same layer runs the practice itself: onboarding fills itself in through real-time eligibility checks, and the visit, the billing queue and the practice's receivables sit on one dashboard, on web and native iOS. Sefton is named for the part of Liverpool I grew up in, and built alongside a speech-language pathologist of 18 years who is the user the product serves.
The same layer, native on iOS
Not a responsive shell. The billing queue ships natively, and every claim carries one next action so the list answers “what needs me” before it answers “what exists”. Rows waiting on a payer say so rather than sitting blank.
Three decisions
Two actions, not one. Sefton Voice could have gone from recording straight to a submitted claim, and that is the version that demos better. It generates codes as one action and submits as another, because a suggestion that bills itself is a liability rather than a feature, and the clinician who signs the note is the one carrying the risk.
Fail open, not closed. Billing views render even when the billing history behind them is missing, because a practice that cannot see its queue stops working entirely, while a practice looking at an incomplete queue still gets paid.
Bilingual in the product, not in a translation layer. Interpreted telehealth, captions, dubbing and the portal read from one set of language rules rather than a bolted-on translation pass, because a translated portal in front of an English-only workflow is a demo, not care.
What I got wrong first
The first billing queue sorted by claim age, which is what a biller asks for. It was wrong. Aged claims are mostly waiting on payers, so the list filled with rows nobody could act on. Sorting by whose move it is put the actionable work at the top, which is the “Your move” badge above.
