Products our engineers scoped, built and still support. Client names are
withheld where the contract asks for it. What is not withheld is the shape of each build, what it
replaced, and which part was actually difficult.
Typical build
6 to 12 weeks
Team size
1 to 3 engineers
Still supported
All of them
Sectors
Health, education, industry
Client names
Withheld on request
Three builds
Different sectors, the same shape of engagement.
One engineer close enough to the business to argue with the brief, a first deploy
early enough to be wrong cheaply, and nobody to hand over to afterwards.
01
Healthcare · Clinical AI
Consultation Summarizer
Turning a live doctor and patient conversation into an accurate transcript and a structured SOAP-format summary, without the clinician typing anything.
Before
Clinicians wrote their notes after the fact, from memory, at the end of a shift. The record was thin, late, and occasionally wrong in ways nobody could audit.
What we built
A speech pipeline that handles overlapping speakers and clinical vocabulary, feeding a language model constrained to the SOAP structure so the output lands in the fields the record system expects rather than as free prose. Handling was built to HIPAA and GDPR requirements from the first commit, not retro-fitted before launch.
The hard part
Clinical language is exactly where general transcription falls over, and a summary that invents a symptom is worse than no summary at all. Most of the engineering went into the checks around the model, not the model itself.
Speech to textLLM pipelineSOAP structuringHIPAAGDPR
A learning platform that generates practice material, scores what candidates write and say, and shows them where the marks actually went.
Before
Preparation meant buying a book and guessing. Feedback, when it existed, came from a tutor days later and rarely explained the band score.
What we built
Question generation across the four papers, automatic scoring models for writing and speaking that return a band with the reasoning attached, vocabulary tools that adapt to what the candidate keeps getting wrong, progress tracking, and a full administrative panel for the people running cohorts.
The hard part
Scoring is the whole product. A model that marks generously is pleasant and useless, so the scoring was calibrated against real examiner marks before anything shipped to candidates.
Web appScoring modelsContent generationAdmin panelProgress tracking
One system of record for employees, approvals and reporting, replacing the spreadsheet and email workflow it grew out of.
Before
Employee records lived in a shared spreadsheet, approvals lived in email threads, and reporting meant somebody rebuilding the same pivot table every month.
What we built
Employee records with a proper permission model, approval flows that carry their own audit trail, and reporting built on defined views so that two managers asking the same question get the same number. Delivered as a normal web application their own IT team can host and maintain.
The hard part
The difficulty in internal tools is never the software. It is that the existing process has undocumented exceptions everyone relies on, and finding those means sitting with the people who do the work.
The first deploy lands before the spec would have been signed off.
Every one of these reached a real environment in about a fortnight. Not because
the work was small, but because an early deploy is what turns assumptions into corrections
while they are still cheap.
The interesting part is the last node. Nobody hands the code to a support desk.
What clients said
Three people who agreed to be named.
“
Each developer I had worked with from Zeki Experts was talented, efficient, communicative, and self-starting.
“
Working with the team at Zeki Expert Solutions has been a pleasure. They are professional and efficient.
“
Zeki Experts’ team was exceptional: talented, efficient, communicative, and self-starting.
Questions
The things people ask about this page.
Because most of the contracts say so. Companies that hire engineers to build the thing their business runs on tend not to want that advertised, and we would rather keep the work than the logo. The three named references on this page agreed to be named.
Yes. Ask on the first call and we will arrange it, with the client’s agreement, for work that resembles yours. A reference who built something unrelated to your problem is not much use to either of us.
Yes, all three are still running and still supported. That is the part of the model that matters: the engineer who built it is the engineer you call when it breaks, rather than a support desk reading a handover document.
You do, in your repository, from the first commit. No escrow arrangement, no licence back to us, and no component that only works while you keep paying us.
Next step
Bring us the problem, not the spec.
Thirty minutes, no commitment. If your problem looks like one of these we will say so, and if it does not we will tell you that too.