Payer systems
BlueCross BlueShield of Tennessee
Led digital product work across member, broker, employer, administrator, and sales experiences.
Founder · CTO · Product operator
Ian Harman has led payer products, built care-delivery product and engineering teams, co-founded a matching product that was acquired, and built claims and payment systems.
Work history
The work spans payer operations, care delivery, clinical matching, provider networks, claims, and payment.
Payer systems
Led digital product work across member, broker, employer, administrator, and sales experiences.
Clinical communications
Contributed product, implementation, adoption, and enterprise controls as annual revenue grew from $2M to $40M.
Care delivery
Designed, built, and productized a provider-reviewed SOAP-note workflow. It cut documentation time per encounter by 20% across 2,000+ encounters over three months. Patient survey outcome scores did not fall.
Founder to acquisition
Co-founded and built a clinical matching product that TPN.health acquired in 2025.
Network to reimbursement
Works across provider-network data, care navigation, payer rules, healthcare EDI, claims, and payment operations.
Current product
Prepares and checks claims while office staff and providers keep control of release.
Operating range
Choose the buyer, workflow, promise, boundary, evidence, and next strategic option before the roadmap hardens around assumptions.
Connect architecture, data, integrations, privacy, transaction rails, and delivery ownership to the operating reality.
Turn complex infrastructure into proof that a health plan, employer, provider organization, investor, or board can evaluate.
Point of view
Healthcare products rarely fail because one feature is missing. They fail at the seams between workflow, data, policy, implementation, human judgment, reimbursement, and trust.
Ian's work focuses on those seams: making authority explicit, evidence visible, transactions reliable, and the business consequence legible.
Selected perspectives
Atom & Bits
Start with one consequential decision. We will determine whether it needs a working session, a focused product sprint, or ongoing CTO and product leadership.