Company
Work crossed the boundary. Software didn’t.
Phibian is a Minneapolis company building the operational infrastructure for community-based healthcare. We are founder-led, in early access, and building alongside the organizations doing the work rather than ahead of them.
What we are here to do
Most systems capture fragments of work after the fact.
The clinical record sees the encounter once it is documented. Payroll sees the hours after the period closes. Messaging sees conversations. Scheduling sees plans. Leaders still need a reliable answer to what is happening today.
Mission
Give community-based providers calm, honest operational awareness, so workers are supported rather than surveilled and leaders can act before problems become crises.
Vision
Become the operational layer organizations open first: a trusted view that makes distributed care work visible and legible, without replacing human judgement.
The idea underneath
Modern work doesn’t live in one environment at all.
The first observation was about two worlds, the office and the field. The more useful realization was that there are not two. Work moves between:
- people and technology
- physical activity and digital records
- the office and the field
- independent systems and connected organizations
- execution and intelligence
Phibian is built around the idea that the operational layer should move with the work, and that continuity across those crossings is itself the product, rather than something each organization reassembles by hand.
Why “Phibian”?
Phibian is named for the ability to operate fluently across environments. Not as two disconnected systems, but as one adaptable system that remains itself wherever the work goes.
That idea belongs in the system logic: continuity, connected layers, signal paths, crossing boundaries. It does not belong in decoration, which is why you will not find a pond anywhere on this site.
How we build
Six product design principles.
These are the rules the product is actually held to in review, not values written for a careers page.
Honesty is the interface
Never present a confident operational claim without a trustworthy basis. If the system does not know, it says so.
Attention first
Help people understand what needs attention now, rather than making them hunt through dashboards for it.
Calm over urgency theatre
Use alerts proportionally. Red should mean something, or it stops meaning anything.
Drill-down law
Every summary leads back to the records underneath it. A claim that cannot be traced is not an answer.
Support, not surveillance
Design location and compliance capabilities around worker trust, correction, context and human review.
Domain flexibility
Nothing should look so clinical that an organization outside a clinic feels like it is using hospital software.
Who is building it
Founder-led, and built from the operating floor.
Phibian was started by a healthcare operator who ran a community-based organization across multiple locations and a distributed field workforce, then built what the work required.
Minneapolis, Minnesota · hello@phibian.io
Interested in bringing Phibian into your operation?
We are currently speaking with community-based healthcare organizations interested in early access and design-partner participation.