# Filip Barcík

> Understand the work first. Build second.

Law / operations / automation / software.

I am most interested in work that is still done by hand simply because everyone got used to doing it that way. I look at how the work actually happens. Then I look for a better route: a workflow change, automation, a custom tool, or a few small parts that need to work together.

## What I do

I do not have a fixed menu of services. Bring me a concrete problem and I will work out what kind of intervention actually makes sense.

Some work is too specific for off-the-shelf software and too small to justify traditional custom development. That used to mean spreadsheets, email or manual workarounds. It does not have to stay manual anymore.

The solution does not have to become an app. It might be a script, an automation, a local utility, a small internal tool or a few connected parts. The job decides the format, not the other way around.

I can automate a manual process, connect applications, extract and structure information from documents, or build a tool exactly where generic software stops fitting.

**I start with the problem, not the technology.**

## Selected projects

### Neuroprotect Scribe

Neurosonology / Windows / local-first / STT / OCR / Mindray Elite i9.

From voice and examination data to a cleaner factual backbone for a report. Less retyping, more time for the work that must remain with the physician.

**Problem:** A specialist report is dictated, but some facts already exist before dictation in measurements, parameters and other examination outputs. The same information is still retyped, dictated, corrected and assembled into final documentation.

**Tool:** After observing the real workflow in a neurosonology laboratory, I built a local Windows tool for specialist dictation and documentation with Czech speech-to-text, custom terminology, OCR and connected workflow steps.

**Local-first:** Speech-to-text runs locally and sensitive health data stays on the device. The workflow is designed to avoid unnecessary transfer through additional services.

**Active development:** The next layer works with outputs from a Mindray Elite i9 ultrasound system. The goal is to reliably extract existing measurements and parameters, normalise them into structured facts and pre-build the factual backbone of the medical report. Review, interpretation and conclusions remain with the physician.

The project is deployed in day-to-day use and continues to evolve from real usage.

### Fire-Safety Documentation

Documents / rules / provenance / validation.

The workflow converts source documents into individual machine-readable facts, preserves provenance, detects conflicts and separates interpretation of unstructured inputs from deterministic rules and calculations. AI helps where text must be read and understood; it does not decide where a rule should decide.

Used in real work by an authorised Czech construction professional; expert review remains part of the process.

### Digital Submission Converter

Windows / batch / documents / in use.

A simple Windows drag-and-drop application for batch conversion and validation of documents used in Czech digital building proceedings. It preserves originals and checks structure, metadata, page count and dimensions. Used in real work by an authorised Czech construction professional.

### Visual Pipeline

Image / SVG / vector / headless / pipeline.

Browser, API, batch and headless utilities for image and SVG work, tracing, presets, operation history, exports, downloading and archiving. Some make sense alone; others gradually became one production pipeline. I use them in my own visual work.

## How I work

1. **See the work.** What a person actually does, what they work around and which inefficiencies have become invisible through repetition.
2. **Shrink the problem.** What must stay, what can disappear and what does not need software at all.
3. **Build the minimum.** If a script is enough, there is no reason to build an application. If an application is enough, there is no reason to build a platform.
4. **Test and connect.** Real data, edge cases and users reveal what works. I add more components only when the workflow actually needs them.
5. **AI with boundaries.** I use coding agents and language models heavily, but not as the default answer to everything. Exact rules stay deterministic. Where privacy matters, I prefer local processing. Outputs that matter must remain verifiable.

A model can write a lot of code. It cannot decide for me whether we are building the right thing.

## About

I am a lawyer by education. Today I work somewhere between operations, software, automation and AI-assisted development.

Law taught me to work with rules, evidence, responsibility and edge cases. Administration and business operations showed me how far real work can be from the process described on paper.

I build software heavily with current coding agents and language models. My role is mainly to understand the problem, define the boundaries of the solution, connect the right parts and verify that the result works in reality.

Many of my tools start with my own work. If I repeat something often enough, I start asking whether I should be doing it by hand at all.

**Technology interests me most when it removes a real problem for someone.**

## CSTM•WRKZ

CSTM•WRKZ is my technical workshop for small tools, custom systems, pipelines and things that exist because generic software was not the right answer. Useful software does not need a large market. Sometimes one person, one team or one unusually specific workflow is enough.

- https://cstmwrkz.com/

## Contact

You do not need to know whether you need AI, an application or automation. Describe what happens today, who does it, which part is annoying and what happens when something fails.

I am open to concrete projects as well as long-term work inside a company when the problem is more interesting than the job title.

- Email: filip@filipbarcik.cz
- Website: https://filipbarcik.cz/