User (Mike Egloff) reached out requesting to integrate Heidi directly into their in-house telemedicine tool. Their workflow centres on work ability plausibility checks via telehealth consults, and they've built a small internal platform to centralise their processes. Specifically, they want to: • Trigger Heidi transcription from within their own platform • Have the generated report stored directly back into their system • Use Heidi's AI to generate additional reports on top of the consult They confirmed API access would work for them — the level of integration they pursue depends on what functionality is exposed. Why this matters: • Signal from a real paying-intent customer that API/embedded integration is a wanted capability, not just an enterprise ask • Small clinics building their own tooling are an emerging segment — likely more inbound of this shape over time • Currently no SOP exists for handling these requests, so support has to decline. Formalising an API access / partner integration path (even a lightweight one) would unblock revenue and reduce ad-hoc handling
