Healthcare

From expertise to digital care

Practices, knowledge and parents on one foundation.

Built and running

One ecosystem, three layers

16 years as an osteopath is systems thinking for the human body. 10 years in tech and AI is that same thinking for software, and actually building it. The two meet in an AI-first ecosystem around osteopathy: three layers on one vision for practices, knowledge sharing and patient guidance. The throughline: the expert must not stay the bottleneck.

Live

OsteosOnline

The professional layer for practices and networks

Digital presence, scheduling, findability and growth for osteopathy practices across Belgium and the Netherlands, without starting from scratch each time.

Live

Coel.ai

The knowledge layer that scales expertise

One knowledge base, assistants and standards, deployable anywhere. Distributing professional knowledge at scale for associations, schools and expert groups.

In progress

Lumi

The patient layer between consultations

Continuity of care beyond the treatment room: preparation, follow-up and education for parents and patients.

Under the hood

The operating system behind OsteosOnline

No slides. The full system map of a real business: what exists, where the truth lives, how the agents work, and how every loop makes the system smarter.

defines
start
drives
delivers
improves
OsteosOnlineHow the system works

One map: what exists, where the truth lives, how we look at it, how agents work, and how work turns into evidence and learning.

Knowledge

How we work

Canonical source: repo / markdown / data

  • RouteTemplates · areas & flows
  • RouteParts · steps & tasks
  • Runbooks · data & execution
  • Procedures / SOPs · explanation & standard
  • Agent Recipes · machine-runnable

Toolbox

Integrations
Google Search ConsoleGoogle Analytics 4Meta AdsGoogle AdsSendGridOdoo

Inflow

Signals
  • New starter · website / intake
  • Partner request · form / contact
  • Patient search · website / Google / maps
  • Booking made · schedule
  • Analytics signal · GSC / GA4
  • Content idea / question · team / market

Operations

What runs

Canonical source: Operation entry (repo → later Supabase)

OperationStarter onboarding · Luke
Progress3 / 6 steps
Statein_progress

Progress

  • Process intake
  • Create profile
  • Schedule intro
  • Add practice
  • Review & GO
OwnerLuke
Work fileGitHub issue
Next actionSchedule intro
BlockersNone
Done whenWrapped up & followed up

Agents

Execution

Work through an Operation Context Package

Operation Context Package

  • State · live status
  • Runbook · how to run it
  • Knowledge · rules & knowledge
  • Data · sources & context

How an agent works

  • 1. Prepare · get ready
  • 2. GO · human approval
  • 3. Action · external action
  • 4. Evidence · capture proof

Work file

Issue

GitHub issue per Operation

  • Queue
  • Discussion & context
  • Handoff
  • Review & GO
  • Agent runs (log)

Not a source of truth for state.

Evidence

Proof & artifacts

Canonical source: evidence refs + external systems

Transcripts · Drive
Contracts · Drive
Profile page · Website
Emails · SendGrid
Reports · Drive / PDF
Bookings · schedule

Analytics

What we measure
Signalraw data
Metricmeasurements
Reportoverviews
Insightinsights

Source data (today)

GSCGA4BookingsAds

The source data already exists, the model follows.

Learning

Back into the system
What worked?analysis
What can improve?insights
Procedure / SOPadjust
Runbook / Recipeimprove
RouteTemplateupdate

Learning feeds the Knowledge layer.

Principles

Always true
  • One source, many viewers
  • One truth per concept
  • Prepare → GO → Action
  • Working method first, automation second
The fundamental loop
SignalsRouteTemplateOperationWork fileProcedureAgent RecipeAgent runOutputGOActionEvidenceLearningBetter knowledge

The system behind OsteosOnline. One business, one map, and the loop that makes it smarter.

Something like this for your organization?

It always starts small: a two-session Product Discovery, and only then you decide.

Book your discovery