Process automation
The repetitive work someone does by hand every day, moved into a pipeline that runs without them and escalates when it is unsure.
- Document intake and parsing
- Scheduled jobs and queues
- Human review where it belongs
I build the systems you are missing.
Automation, integrations, internal tools and websites. Shipped to production, measured, and still running.
Most businesses do not need more software. They need the software they have to stop needing a human in the middle.
I work where the money and the rules are strict: healthcare operations, regulated finance, compliance. That is the hardest place to automate, because a wrong record is not a bug report, it is a liability. Everything on this page survived that environment.
What I do
Integrations
Two systems that were never designed to talk, made to exchange data reliably, with a rollback ready before the first write.
- Vendor APIs and file transfer
- Healthcare and finance formats
- Reconciliation you can audit
Internal tools
The portal, CRM or dashboard your team keeps faking with spreadsheets, built properly and put behind real access control.
- Portals and CRM
- Live operational dashboards
- Access control and audit trail
Websites and landing pages
Fast, accessible, owned by you. Deployed, wired to a real database, with analytics that answer a question rather than decorate a slide.
- Design and build
- Deploy and domain setup
- Forms that reach a database
Data and reporting
Your numbers pulled out of vendor platforms into a database you control, so a new question does not require a support ticket.
- Mirrors of closed systems
- Metrics that survive scrutiny
- Reports on a schedule
Models on your own hardware
Language models running inside your network, quantized to fit the hardware you already own and measured on your own data before an answer is trusted.
- Quantized to fit your hardware
- Evaluation harness on your data
- Nothing leaves your network
Selected work
Current client names are withheld on purpose. Where an organization is named it is a former employer, not a client. Numbers below are operational, never financial and never personal data.
Inbound faxes turned into radiology orders
A fax arrives, gets read, gets parsed, and lands in the imaging system as a structured order. No retyping.
Read the case- 1,110queued faxes reconciled
- 722auto-matched to existing orders
- 96%fields located without external OCR
Measuring how long a department makes people wait
A shared inbox with no visibility became a measured service line with a response time anyone can check.
Read the case- 26.5hmedian reply, starting point
- 0.9hmedian reply, two years later
- 0message bodies stored
A voice assistant answering a retail bank's phone line
Part of the program that built Oleg, Tinkoff Bank's Russian-language voice assistant for retail customers.
Read the case- StackSpeech recognition, Text to speech, Intent classification, Dialogue management
What people were actually complaining about
Free-form feedback from customers and staff, classified by language models, so the bank saw real complaints instead of a hand-read sample.
Read the case- StackPython, Language models, Text classification, Annotation pipeline
Federal student aid, end to end
Application intake, packaging, disbursement and return calculations for federal aid, in one system instead of four spreadsheets.
Read the case- StackNext.js, PostgreSQL, Node.js, Bank verification API
A closed vendor system, mirrored into a database you own
Read-only mirror of a proprietary clinical system in standard healthcare format, so reporting stops depending on the vendor.
Read the case- 21versioned migrations applied
- 0writes back to the source system
Track record
18
systems described on this site, none of them a demo
7.5
years at Tinkoff Bank, 15 promotions in one of Russia's largest tech companies
3
years from arriving in the US to running finance and AI
2
languages the work is delivered in
How the work actually goes
Measure first
Before anything is built, the current state gets a number. Without it, nobody can tell later whether the project worked.
Ship the smallest real thing
One working slice in production beats a complete plan in a document. The slice proves the assumptions were right.
Keep it reversible
Export before every mutation, a rollback written before the change, and nothing that touches production without a log.
Hand it over
Once paid, the code, credentials, runbook and the reasoning behind the design are yours, with a perpetual license to anything of mine built into the work. No dependency on me by construction.
Also shipped
Live operations2026
A phone system you can actually see
in production
CRM and outreach2026
Outreach that knows who was already called
in production
Internal tools2026
One place the staff handbook actually lives
in production
CRM and automation2025-2026
Admissions pipeline with automations that fire on their own
in production
Integration2026
Electronic transcripts landing in the registrar's queue
in production
Integration2025-2026
Order exchange between two systems that were never meant to meet
delivered
Finance operations2026
A billing layer that watches and never touches
in production
Operating model2026
The whole company as one diagram, in three views
internal
Service management2026
A service desk with a boundary that holds
in production
Infrastructure2026
Workstation monitoring with signed self-update
in production
Desktop software2026
Procedure calendar for accounting operations
own product
Product security2026
Security audit and beta launch of a consumer app
delivered
Tell me what is broken
Describe the process that eats your week. I reply from this form myself, usually within a day. Please do not include patient data.