← Imedex: the story so far

Imedex journey · Update #1 · July 2026

First demo, first client connected to Claude.

When Imedex committed in June to run its entire company on Healtek Medtech OS, we promised to publish the implementation as it actually happens. This is the first installment.

On Tuesday 28 July 2026 we held the first demo with the Imedex team — and it carried a milestone bigger than one company: Imedex became the first Healtek client connected to Claude, Anthropic's AI assistant, through the Healtek MCP Connector. The next morning, the team started using the system for real work.

Why this matters

Like most distributors, Imedex has run for years on manual data entry, a legacy ERP and a set of information systems that don't talk to each other. The usual way out of that is a migration project: months of exporting, cleaning, mapping and re-keying before the new system does anything useful.

The MCP Connector changes the shape of that work. Claude connects directly to Imedex's Healtek workspace, so onboarding users and uploading existing data becomes a conversation rather than a project. What used to take months of data cleaning and preparation can now be delivered within hours — the same shift we described in our piece on autonomous installed-base import, now running for a real client.

What the first session looked like

Rather than a slideware walkthrough, the demo connected the company's own working context to the system. The team saw their operation through the new layer: existing data brought in as it is — messy columns and all — and structured into records they can act on, with gaps flagged honestly instead of guessed. That discipline is the foundation everything else in this journey builds on: deterministic, real-data-only outputs, every record traceable to its source.

Claude conversation over the Imedex CRM: it lists two Klient accounts with codes and states, the user asks in Czech to set up each client's story one by one, and Claude offers interactive next steps — the Imedex connector visible in the Context panel.
Imedex's CRM, answering in plain Czech — Claude reads the accounts through the Imedex connector (see the Context panel) and proposes the next steps instead of waiting for a form to be filled.
The same session with the Imedex office on camera: the team watches as Claude updates a client record, notes that an account is a test entry created for the demo, and asks before writing the same note to a second record.
The Imedex office during the session. Note the behaviour on screen: the system records that an account is a test entry, and asks before assuming the second one is the same — real-data discipline, live.

What happens next

The goal isn't a new database. It's a different operating rhythm. We're working with Imedex to become an AI-driven company that makes daily decisions based on data — and to drive growth through weekly review cycles that will shape their medtech excellence over the coming months. Each cycle looks at the same live numbers the field generates, decides, and feeds what was learned back into the system.

We'll report from those cycles here — what gets structured first, what turns out harder than expected, and what changes once one system replaces many.

Talk to us about a similar journey →

Owner: Jan Safka · Healtek field notes, July 2026

← Back to the Imedex story

Want to be the next story?