Axle Health Innovation & Technology Culture

How does innovation show up in your company culture?

At Axle, innovation shows up in how we choose which problems to solve, not just what technology we use. Healthcare operations look structured and formulaic on paper, but in reality, they are deeply human. It’s why healthcare teams have had to resort to manual solutions for so long. A patient doesn’t say, “I need a 60-minute visit between 10:00 am and noon.” They say, “I get anxious with new clinicians,” “I can only answer the door after dialysis,” or “Mornings are hard because of my medication schedule.” Traditional scheduling systems force those needs into rigid machine-like constraints, which means the system loses the real-life context that matters most.

So we applied an LLM to this layer of the product, allowing clinicians and admins to capture the nuance of our patients’ lived realities. Our platform turns organic, free-form patient and clinician preferences into actionable constraints inside the scheduling engine. The innovation wasn’t “add AI” and instead recognized that healthcare is a qualitative domain and required choosing tools that respect that reality. The result is software that adapts to people rather than forcing people to adapt to software.

What’s one recent innovation that improved user or employee experience?

We recently launched a customized dashboard with intelligent work queues that schedulers land on when they first start their workday. Our users manage hundreds of visits per day across clinician teams for patients in all different states of care and need. The challenge isn’t just accessing information; it’s knowing what needs attention right now. A late-running visit, a clinician calling out or a patient emergency can quickly turn into missed opportunities for care or expensive compliance-related penalties.

We built intelligent work queues that prioritize visits and patients requiring intervention. The system evaluates clinician availability changes, compliance risks and urgent scheduling needs, and then surfaces the patients who may not get seen without action. Instead of digging through schedules and reports, users are guided through their day. The queue updates continuously as conditions change, so teams can reassign visits, adjust routes, and respond quickly. We changed the product from a system users monitored to one that actively supports daily healthcare operations. Rather than just displaying schedules, Axle helps teams stay on track and focus attention where it matters most

How do you balance experimentation with stability?

Healthcare forces you to be thoughtful about how you innovate. Our users are coordinating real patient care, so we can’t treat experimentation casually, but we also don’t believe stability means stagnation. In practice, we introduce changes carefully. We roll features out to small groups first and spend time thinking through how things could fail before they reach customers. When something doesn’t behave the way we expected, we’re set up to respond quickly and adjust.

As we introduce more advanced or experimental technology, we keep humans in the loop. Automated recommendations support decision-making, but human edits always take precedence, and those edits feed back into the system so it can improve over time. The software adapts to how clinicians and scheduling teams actually work, not the other way around.

We’re intentional about where we apply innovation: We focus it where it creates real leverage and competitive advantage, while keeping foundational workflows predictable and reliable. That balance lets us reduce repetitive, manual work without taking control away from the people in the field who ultimately know best.

What tools support your day-to-day work?

At our stage, tools are less about standardization and more about speed and leverage. We lean on AI like Claude to go from idea to something tangible quickly, whether that’s a rough prototype, a workflow or just a sharper way to frame a problem, shrinking the gap between spotting an opportunity and putting it in front of users.

That speed shows up most in our product lifecycle. Pylon’s support agent triages B2B customer issues and pipes the signal into Slack, where the team discusses and pressure-tests it. From there, a Linear integration turns a raw feature request into a refined, trackable item in our agile workflow. Discovery to implementation, with automation carrying the handoffs.

We’ve also started building a lightweight “Ask Axle” Claude plug-in and a growing repo of skills and actions where people share useful prompts and workflows. It’s not overly structured, but it helps good ideas spread fast across a small team.

More than anything, the tooling is about enabling people to act. When everyone can build and iterate on their own ideas, we move faster without heavy process.

How does your team experiment?

The point isn’t running “formal” experiments, it’s continuously testing assumptions as we build. A lot of that is learning quickly what won’t work, which lets us stay flexible and put our energy into what will. It keeps us honest about what’s genuinely valuable versus what just sounds good in theory.

We try to keep experimentation as close to the work as possible. Instead of writing heavy specs, we can go straight from a customer insight to a mockup or prototype, but when a customer request comes in, we resist speccing the first description. We break the “ask” down to its raw parts to find what’s actually driving the need, then test against that so we build toward the underlying value, not just the literal request.

Because the team is small, feedback loops are tight. Claude and Figma make it easy to show what an idea might look like and get reactions before investing too heavily. We can put something in front of customers, engineering or leadership the same day and refine it in real time.

How does Axle Health adapt to change? 

For us, adapting to change is less about reacting to requests and more about sensing what’s shifting around each customer, such as their market, their regulations or the Electronic Medical Records they live in, and getting ahead of it.

That matters because our customers don’t schedule the same way. A home health agency and a hospice have very different priorities, so the logic our scheduling algorithm is built on has to flex to each, and we integrate with multiple EMRs that each ship changes on their own timelines.

A clear example: A recent federal rule reshaped how hospices schedule patient visits, requiring certain follow-ups to happen within a strict two-day window. We saw how hard that would be for our customers to stay on top of and built our system to automatically flag when one of those visits was due instead of leaving staff to track it by hand before clients even asked.

That’s the discernment we try to practice: understanding the context a customer operates in, not just the requirement they hand us. When an EMR or a regulation shifts, we’d rather have already adjusted than wait to be told.