← Projects

Client platform 02 / 03

Extraction

AI image-extraction platform — scoped, shipped, and still operated for Swift ProSys.

Workflow

FOLDER Resumable batch queue PREP Compressed in a worker TEMPLATE Prompt + schema, no code MODEL One interface, any provider VALIDATE Checked against schema EXPORT JSON · XLSX · DOCX · MD RUN LEDGER Tokens and cost per run ESCALATE
  • ~200people use it daily
  • 6Btokens processed in five months
  • 5model providers behind one interface

What I built

The platform replaced manual document and image data entry for language-specific teams — a cross-platform desktop app on a self-hosted Supabase/Postgres backend, with encrypted key vaulting, role-based access, and over-the-air updates.

I own it from the first scoping call to production support.

Routing

Work routes across five model providers — OpenAI, Google Gemini, Qwen, Vector Engine and local Ollama — behind one interface, so workloads move on price or capability.

Operators

Template-driven extraction lets non-technical operators add new document types without engineering involvement, and per-project cost analytics make spend predictable before a run.

Getting it right

Every response is validated against the template's JSON schema before it counts. A failure doesn't just retry — it escalates: a firmer instruction, then a larger output budget, then a different reasoning setting. Long runs checkpoint to disk, so closing the app mid-batch costs nothing.

Client
Swift ProSys — freelance, remote
Stack
  • TypeScript
  • Electron
  • OpenAI · Gemini · Qwen · Ollama
  • Supabase · Postgres
  • RBAC
  • OTA updates
Next — 03 News Pipeline