Research
We wrote a page on each problem, with the receipts.
Every figure on these pages belongs to somebody else, and every source is printed at the bottom. If you already know the problem, skip to why nobody has fixed it.
27 problems researched so far, across 1 market.
Not sure which one
Your problem may not be on this list yet.
These are the ones we have written up. Tell us yours and we will say plainly whether we have seen it before, and what the figures look like where we have.
There is a monthly payment you are allowed to bill and are not
A new bundled monthly code. Most practices qualify. Most are billing nothing.
United StatesIn January 2027 prior authorisation gets an API. Almost nobody is ready.
The payers are legally obliged to open up. The providers who built the workflow first will own the transition.
One in four residents falls each year, and the warning was in the logs
Falls are the leading cause of injury death for people over 65. The signals that precede one are already being recorded, in systems that do not talk.
United StatesNobody wants a sixth dashboard
The sensors work. The problem is that each one arrived with its own screen.
Nine out of ten denials are never appealed
Appealing works nineteen times out of twenty. Almost nobody has the hours to do it.
United StatesThe condition was in the nursing note. It never reached the MDS.
The qualifying detail is usually already written down. It just never made it onto the assessment.
United StatesEvery building reports. Nobody can see the portfolio.
The data exists in every building. Getting it into one place still means exports and re-keying.
Not here yet
Your problem is probably on the list we have not written up.
We are working through these one at a time, because a page written without research is worse than no page. If yours is missing, the call is the faster route anyway.
Research is how we start. Building is what we do.
These pages exist because we looked something up properly. The work that follows is a system, a device, or both.
See everything we build-
Software -
Hardware -
Ways of working -
Whole ventures
However hard, whatever it is
These are the ones we wrote up. There are many more.
A page here exists because somebody read the regulator, the study and the data. That is the same thing we would do for a problem that has no page yet, and it does not take longer.
-
01 We sit with you
Days where the work happens, not a workshop in a meeting room. We watch the job get done and write down the shortcuts nobody wrote down.
-
02 We read everything
Your data, your rules, your vendors and their documentation, and the published research on your sector. We report what is actually in there.
-
03 We break it to first principles
Not which tool fixes this. What is actually causing it, taken apart until we reach the piece that cannot be divided further.
-
04 Then we build
Weeks, not quarters. By this point we are not guessing what to build, and guessing is the thing that makes projects long.
Intelligence, plumbed in
These pages exist because somebody read the source.
Same discipline in the build: a scored test set from your records, not a demo on three hand-picked rows.
How we make AI survive real data-
Connectors -
A semantic layer -
Evals you can check