health & medical operations · early access

AI workflow software
for healthcare teams

We build software that helps clinical and operational teams move critical patient context through complex, fragmented workflows, with more speed, clarity, and less manual work.

See our approach Talk to the team

Why mylyn

Inspired by the biology of fast, reliable signal transmission.

The name comes from myelin, the biological sheath that insulates neurons and allows signals to travel faster, more reliably, and with less interference through the nervous system.

That metaphor maps directly onto what our software does: it helps healthcare teams move critical patient context through complex, fragmented workflows with more speed, clarity, and less noise.

We build for operational teams where speed and accuracy are not preferences. They are clinical and financial imperatives. The stakes are high. The software should match.

Positioning

mylyn labs builds AI-enabled workflow software for healthcare teams managing complex patient cases.

Brand character

Software-first. We think and move like a sharp AI engineering company that deeply understands healthcare, not a traditional health vendor. Clinical rigor without healthcare clichés.

Mission

Built from personal experience with a broken process.

Our path into this space came through people we know. Friends who went through the organ transplant process, living through both the uncertainty and the life-changing outcomes, made us look harder at how the system actually works, especially around OPOs and the donor evaluation process.

The gap that stood out most was inconsistency. How potential donors are reviewed and how quickly those decisions get made varies more than it should. That inconsistency has real consequences for patients, for families, and for the teams doing this work under pressure.

Our goal is to build software that helps standardize and accelerate donor evaluation, reduce the operational strain on OPO teams, and expand the number of viable donors being considered. We work closely with active critical care physicians to make sure the system reflects real clinical judgment, not static data thresholds.

The vision is a predictive, adaptive tool that learns over time and aligns with each OPO's specific protocols, helping teams make faster, more informed decisions while opening more doors for patients on the waiting list.

The gap we're closing

Inconsistency in how potential donors are evaluated leads to avoidable delays, added strain on staff, and missed opportunities for patients waiting on transplants.

How we approach it

We build with active critical care physicians, not around them. Every design decision is grounded in real clinical workflow, not assumptions about how the process should work.

The problems we work on

OPOs move fast under pressure. The tools haven't kept up.

Organ procurement organizations manage one of the most time-sensitive, high-stakes workflows in healthcare. A warm handoff starts the clock. What happens in the next few hours determines whether a viable opportunity is pursued or missed entirely.

Avoidable activations drain resources

When a case is activated before disqualifying information surfaces, the organization absorbs real cost: staff time, coordinator hours, travel, clinical review, and medical maintenance. Much of that information already existed somewhere. It just wasn't found in time.

Critical information is scattered

The information needed to evaluate a case is rarely in one place. It lives across multiple systems, scanned documents, and inboxes. No single tool connects it. Coordinators piece it together manually, on every case, under time pressure.

Volume grows. Headcount can't keep pace.

As referral volume increases, the manual work compounds. More cases mean more data entry, more system checks, and more coordination overhead. Hiring more coordinators is expensive and slow. The better answer is software that helps the same team do more.

How we work

Built with you. Not sold to you.

We don't fit your team into a generic workflow. We build software shaped around your real referral process, release by release.

The one-size-fits-all model

Generic workflow forced onto your team
Long implementation, slow iteration
Your team adapts to the software
Vendor relationship: tickets and change orders
Enterprise overhead reflected in your price

The mylyn labs model

Software shaped around your real referral workflow
Built in direct collaboration with your team, release by release
The software adapts to you
A product partner, not a vendor relationship
Lean team means lower cost and faster decisions

How a partnership begins

01 · Discovery

Map your workflow

We map your real warm-handoff-to-activation workflow and quantify avoidable waste together. No assumptions, no generic spec.

02 · Pilot

Prove the highest-leverage capability

We ship the single highest-value feature first, in one limited, controlled workflow. Prove value before we ask for more trust.

03 · Expand

Monthly releases shaped by your team

Every release is informed by direct feedback from your team, not a roadmap set in stone a year in advance.

Who you'd be working with

Leadership with outsized, relevant experience

A small, senior team means a short distance between a decision and a shipped change.

Kyler Berry

Kyler Berry

Head of Engineering · Co-Founder

Fifteen years building production systems at Vimeo and Zumba before launching his own AI engineering practice. He specializes in moving AI from proof-of-concept into production: LLM-powered systems, automation pipelines, and workflow architecture built to hold up under real load. His client work spans industries: a 75% cost reduction in an automated content production pipeline, a 44% reduction in support ticket volume through intelligent customer service AI, and roughly $50M in at-risk revenue protected through compliance and systems work. His core conviction: most AI failures aren't model failures. They're systems failures.

Nick Clark

Nick Clark

Head of Product · Co-Founder

Nick Clark has spent the past 14 years designing and scaling complex software products. He was the founding product design hire at Stax Payments, helping shape the platform from an early-stage startup into Orlando’s first unicorn, serving tens of thousands of businesses processing payments every day.
He later joined The Public Health Company, an AI-powered biothreat intelligence company, in its earliest stages and spent more than three years as Head of Design. There, he led product design, brand, and strategic communications efforts, helping translate complex scientific and national security concepts into products and narratives that resonated with government and defense stakeholders. His work played a key role in securing The Public Health Company’s first Department of Defense contract as a prime vendor.

Let's build together

More capacity. Less waste. No added headcount.

We're looking for a small number of founding customers in health and medical operations who are ready to tackle a big, complex workflow problem together. If that sounds like your team, we'd like to talk.