The roleRevenue cycle is where the economics of healthcare get decided. A clinician finishes a visit. Their notes sit in a coding queue. A coder maps that documentation to ICD-10 codes. Those codes determine hospital funding. A single missed code costs tens of thousands of dollars. A backlog of uncoded episodes costs millions. At one hospital we visited, eight million pounds in claims had sat uncoded for 6 months. The coder workforce is ageing, attrition from training programs runs above 60%, and the people who do this work spend most of their day pulling information across five fragmented systems.
Heidi's revenue cycle product makes clinical documentation land as accurate, complete codes: automatically, with a coder in the loop when it matters. You will own the clinical coding engine, the coder seat (a purpose-built interface for HIM staff, CDI, and clinical coders), and the forward-deployed workflow design that embeds this inside health systems. You will own the commercial story too. The financial model that justifies a health system contract, the ROI proof points that move procurement forward, the outcome metrics that make renewal straightforward. If you cannot quantify the value, you are not yet building the right thing.
This role sits on one of our highest-leverage pods and is closest to our enterprise customers. You will spend time on-site at hospitals, in coder queues, with clinicians and billing directors simultaneously. You will need to arrive already knowing the workflow: ICD-10, DRG assignment, HCC capture, E&M levelling. There is no ramp time when you are in a customer's coding room on day one.
This role is based in San Francisco.
We don't care about logos. Show us a health system workflow you've taken from on-site discovery to deployed outcome, and tell us what the numbers looked like.
What you'll do- Own the revenue cycle product across our primary markets: Australia, the UK, and the US. Decide what we build, what we don't, and what we sequence next across the clinical coding engine, the coder seat, and the EHR connections that close the loop from documentation to funded claim.
- Work forward-deployed: go on-site at health systems, watch coders work their queues across fragmented systems, and come back with a scoped pilot, a clear done-state (accuracy and throughput targets, the workflow being replaced, the date you finish), and a prototype
- Make ROI legible end-to-end: build the financial model for every engagement, communicate it in language a CFO will sign off on, and bake the proof points into the product itself so every deployment shows its own value
- Own coding accuracy as a product metric: define what accuracy means (against coder ground truth, auditor review, or CMS standard), build the evaluation infrastructure to measure it, decide where the human-in-the-loop earns its place, and ship fixes with before/after evidence
- Sit with the clinicians upstream: shape the CDI queries, documentation prompts, and point-of-care nudges that turn a good visit into a codable one before the coder ever opens the queue
- Navigate AI resistance in coding departments: from the coder who does not want to be replaced to the IT team with six months of procurement ahead of them, find the path through
- Partner with engineering on the connection and evaluation layer: code mapping, workflow orchestration, and the accuracy framework each health system deployment relies on
- Shape the commercial posture for revenue cycle: pricing structure, the proof points that support enterprise deals, the outcome metrics that make renewal straightforward, and the case studies, ROI narratives, and sales enablement that Marketing, Sales, and Solutions Engineering need to close
- Be the connective tissue across functions: weekly with Sales and Solutions Engineering on live deals, Customer Success on deployed accounts, Engineering on what ships next, and Marketing on what the market hears
If we'd worked together the last 6 weeks, you'd have:- Flown to a health system, sat in their coding room for two days, and come back with a prototype and a scoped pilot
- Built the financial model for a Medicare Advantage customer: HCC capture value, quality CPT codes, and year-one ROI in dollars, ready for their VP of Finance
- Caught a coding accuracy failure mode (suspected diagnoses coded in psych encounters, z-codes assigned incorrectly) and shipped a fix with a before/after accuracy metric
- Sat in on three clinician visits and identified the documentation gaps upstream that cost the coder twenty minutes downstream, then specced the CDI prompt to close them
- Navigated a coder department where the director wanted Heidi, the coders were resistant, and IT had six months of procurement ahead, and found a path through all three
- Written the competitive teardown: where we win, where we don't yet, and what we'd need to ship to close the gap
- Defined the done-state for a hospital deployment: throughput target, accuracy threshold, the specific workflow being replaced, and the date
- Built the first version of the deal narrative with Sales and Solutions Engineering, then watched it close a pilot
What you'll need- 5+ years shipping product in healthcare: selling to or building for health systems, not adjacent to them. We care more about what you've deployed than years on the clock.
- Working fluency in revenue cycle: ICD-10, DRG assignment, HCC capture, E&M levelling. You should not need to be taught the workflow you are building for.
- ROI-first thinking: you start with the financial model and work backwards. You can build a health system's business case without a commercial analyst.
- Passion for AI, shown through hands-on building, prototyping, or side projects
- Fluency with core LLM concepts and systems (prompting, fine-tuning, embeddings, retrieval, evaluation) and the judgment to translate these into reliable, user-facing products
- You default to building over requesting
- Strong opinions, weakly held; you'll shift the room when you're right
- Data fluency with diagnostic teeth: you can look at a coding accuracy report, identify where the model is failing, and specify what needs to change
- -igh tolerance for 0-to-1 ambiguity: this product is at discovery and prototype stage. You will help decide what it becomes. If you need a backlog handed to you, this is the wrong role.
- A romantic streak about software and a belief that great design transforms someone's day
If you answer 'NO' to these questions, this may not be the job for you:- Are you an execution powerhouse?
- Have you shipped something this week?
- Are you good at games?
- Did you have a weird teenage hobby?
- Are you able to execute without a legion of data analysts, product marketers, and research coordinators at your beck and call?
- Does the prospect of making health systems a lot nicer make you feel fuzzy inside?
