Kumi
Founder Engineer · Veterinary practice platform
Kumi removes the cognitive overhead of veterinary consultation paperwork. Record the consult, the platform writes the report and the annex documents. A multi-tenant SaaS for solos, clinics, and students.


The pain
A typical veterinary consultation produces a stack of documents, the report, the prescription, the discharge note, the referral letter. Each one takes time and cognitive load. No existing tool combines the case log with the document generation in a single ecosystem.
Covet dominates the market, but the UX feels dated and the feature set is thin. There's room for better.
The team
Started in August 2025 with Maximilien Bozon, vet student at the Royal Veterinary College in London. His family runs Hopia, a veterinary hospital outside Paris, giving us direct access to practitioners.
I run engineering end-to-end. Maximilien drives the medical-product feedback.
Organization
The patient list is built around one idea, surfacing everything that matters at a glance. A clean photo-rich layout, a fast searchable case log, differential diagnosis badges on each animal so the chart speaks before you even click. Search filters tuned to bring any patient up in a single click, by specialty or otherwise. The watchword on this screen was organization.


Recording the consult
The patient page is where most of the work happens. The goal is to keep the vet in flow and make recording effortless. The audio recorder is built into the page. Browser-side preprocessing prepares the capture before upload, then the AI pipelines transcribe the audio and generate the consultation content. Vets can also build a consult by hand, skipping the recording entirely.


The block editor
Once the consult is generated, it lands in a block-based editor. Vets can verify the AI output, customize it, add or remove blocks, drop in exam sections. Modularity and speed of execution drove the design. Annex documents are produced in the same flow, and everything is exportable.


What Kumi taught me
More than a product, Kumi has been a learning roadmap. I've grown my backend skills here, sharpening my Go mastery one feature at a time. Running into walls, fighting through problems, then implementing concepts that got more specialized as the app matured. From the basics to the deeper cuts.
Same story on the frontend. Same on the infra and ops side. The most formative project I've worked on lately.
And there's always more code to evolve. The goal is to keep pushing it, keep learning. In the meantime, it lets me ship similar projects much faster. I've seen and refined this scale, so the next one starts a lot closer to the finish line.
What's next
Personalized exports carrying each clinic's identity, logo, name, signature. Then full traceability with OpenTelemetry.
After that, graphical content blocks like schemas and anatomical diagrams. The goal is to move the consult toward something more readable, visual, and expressive, away from long-form prose. The block system was built extensible for exactly this.
And a consult agent always-on in the page, helping vets edit and add to a consult through voice or text. Less of a pipeline, more of a collaborator.