Selected work
Four engineering case studies with the numbers behind them, plus 37 interface designs across eight industries. Client names are withheld by agreement — the results are not, and we'll walk you through any of them live.
50+
Products shipped
13
Engineering disciplines
99.9%
Uptime we hold to
24/7
Support coverage
3.2M+
Payments / month
120ms
Median settle time
A PCI-compliant transaction engine processing thousands of payments per minute.
Payments were settling through a batch job that ran four times a day. Merchants saw balances that were hours stale, disputes were reconciled by hand from spreadsheets, and the existing system had no path to the transaction volume the business had already sold.
We rebuilt settlement as an event-driven ledger with idempotent handlers, so a retried or duplicated message can never double-charge. Reconciliation runs continuously against the processor rather than nightly, and the merchant dashboard reads from a projection updated in real time.
Median settlement dropped from hours to 120 milliseconds. Manual reconciliation went from a daily task to an exception queue, and the platform now clears over three million payments a month on infrastructure that costs less than the system it replaced.
Worth knowing
Services used
4.9★
App store rating
60k+
Consults booked
HIPAA-ready iOS & Android app connecting patients with clinicians in seconds.
Patients were booking video consultations through a desktop portal that failed on mobile browsers. Call quality collapsed on cellular connections, and clinician notes lived outside the medical record, so somebody re-typed them afterwards.
Native iOS and Android apps with WebRTC tuned for lossy networks — adaptive bitrate, audio-only fallback, and reconnection that keeps the consultation alive through a signal drop. Notes write straight into the record over FHIR, and everything sensitive stays encrypted end to end.
Sixty thousand consultations booked in the first year at a 4.9-star average across both stores. Clinicians stopped duplicating notes, and completed-call rates on cellular rose sharply once reconnection was handled properly.
Worth knowing
Services used
10k+
Devices online
98.7%
Fleet uptime
Embedded firmware plus a live cloud dashboard tracking 10k+ devices in the field.
Ten thousand devices were deployed with no remote update path. Firmware fixes meant a site visit, faults were discovered when a customer called, and the only record of what was running where was a spreadsheet.
New RTOS firmware with signed A/B updates and automatic rollback, so a bad image can't brick a unit. Telemetry buffers locally through connectivity gaps and drains over MQTT when signal returns. A Go service ingests it into a time-series store behind an operations dashboard.
Fleet uptime settled at 98.7% with zero bricked units across staged rollouts. Firmware releases go out over the air in cohorts instead of by van, and faults now surface on a dashboard before the customer notices.
Worth knowing
92%
Less manual review
8s
Avg. doc turnaround
An LLM pipeline that extracts, classifies, and routes documents automatically.
A team of reviewers was reading every inbound document to classify it and pull out a handful of fields. Throughput capped at whatever the team could process in a day, and an earlier AI prototype had stalled because nobody could show it was accurate enough to trust.
A graded evaluation set came first, so quality was a number before anything shipped. Extraction runs through a retrieval pipeline with schema-validated output and per-field confidence. Anything below threshold routes to a human instead of guessing, and every call is logged with its cost.
Ninety-two percent of documents now clear without human review, averaging eight seconds each. Reviewers handle the genuine edge cases, accuracy is tracked continuously against the evaluation set, and per-document cost is visible on a dashboard.
Worth knowing
Design showcase
37 website designs across 8 industries. Filter by sector to see how the same engineering standards adapt to very different audiences.
Screens are shown without client branding where an agreement requires it. Ask us for a walkthrough of any of them.
Project names and client details are anonymized — confidentiality is part of every engagement we take on, including yours. On a call we can walk through architecture, decisions and numbers in detail, and several clients are happy to speak to prospective ones directly.
Ask for a walkthroughClient stories
Your project
Tell us what you're building. You'll get a scope, a number, and an honest opinion from the engineer who'd lead it — within one business day.
Prefer email? support@zeetek.net
