PhoenixCKK is a husband-and-wife studio. Jack spent two decades inside healthcare IT — building the interface plumbing and clinical dashboards that hospitals run on. Glenda lives with multiple sclerosis and has a history of breast cancer. Our flagship app exists because the tools she needed, as a patient managing complex daily care, didn’t exist.
Jack spent two decades inside healthcare IT — building the interface plumbing and clinical dashboards that hospitals depend on every day. The work taught him a strange lesson: the systems clinicians rely on were mostly built decades ago, by people who never met the patient. And the data the hospital collects barely overlaps with the data the patient actually lives with.
Then it got personal. Glenda was diagnosed with multiple sclerosis. She already had a history of breast cancer behind her. Suddenly the gap between the software clinicians use and the tools a patient needs at home wasn’t an abstract problem — it was something we were navigating at our own kitchen table.
PhoenixCKK exists to close that gap. We build small, focused apps that put patients back in the room — with their data organized, their patterns surfaced, and their next conversation with their doctor already half prepared. We’re a studio, not a startup. We don’t scale headcount, we don’t chase rounds, and we don’t ship features we wouldn’t use ourselves.
Two decades inside healthcare IT — hospital interface plumbing, EHR integrations, clinical dashboards. The systems that move clinical data and rarely meet the patient. Started PhoenixCKK to flip that perspective.
Thirty years in healthcare — twenty of them in healthcare IT — and the patient our flagship app was designed for. Lives with multiple sclerosis and has a history of breast cancer, so she brings both deep professional knowledge and the lived experience no spec doc could capture. Every design decision routes through her, because the tools she needed didn’t exist.
Healthcare software fails patients when it ships unfinished. We take longer than feels comfortable, and we say no to features that don’t earn their place.
On-device AI, end-to-end encryption, opt-in sync. We assume PHI should stay with the patient unless they explicitly choose to share it.
Our tools observe patterns. They do not give medical advice. There is a difference, and we hold that line carefully.
We build for users, not for an exit. Independent funding means we get to make the long-term call when it matters.
We take on a small number of partnerships each year. Send a note — tell us what you’re building, and what hurts about it.
jackwilliams@phoenixckk.com →