Phoenixckk is a husband-and-wife studio. Jack spent two decades building healthcare software, the kind hospitals and clinics quietly 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 building healthcare software, the systems hospitals and clinics 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.
A software engineer with two decades of building healthcare technology. Jack has written the code behind the systems hospitals and clinics rely on every day, wrangling messy data, and sweating the privacy and reliability that healthcare demands. He started Phoenixckk to point all of that experience at the person who usually gets left out: the patient.
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.
info@phoenixckk.com→