Independent developer · Brno / remote
I build process automation, internal tools and web applications for teams in Czechia and remotely across Europe. I help replace repetitive work, connect the systems you already use, or take over a process that off-the-shelf software cannot handle.
From the brief to a working system
I describe projects without names or sensitive details. The focus is on the problem, the solution and the technologies I actually used.
The application monitors prices, evaluates configured rules and executes purchases in a time-sensitive environment. Users can plan strategies, manage a budget, review history and manually confirm risky situations.
A local service controls an authenticated browser session and processes requests through a queue. It tracks every job, rejects duplicates and stops before a step that requires user confirmation.
It connects topic planning, content preparation and review, translations, sitemap generation and scheduled publishing. One repeatable workflow supports several independent sites.
A scheduled serverless task recalculates a fixed amount using a live rate. Before sending, it checks the network, fees, balance and an external condition. Completed jobs are recorded to prevent accidental duplicates.
The Chrome extension lets a tester choose a location on a map, change the active page's geolocation and verify the result immediately. It includes diagnostics, saved locations, error records and an optional AI assistant with separate conversation memory.
I automate repetitive browser work, scheduled tasks, data transfers and handoffs between systems. The result includes progress records, safe retries and clearly defined steps that remain with a person.
Playwright / Python / Node.jsI build web and desktop applications around a real workflow. From a focused prototype to an operational tool with roles, history and configuration.
Next.js / PyQt / API / dataI design data collection, cleaning and transformation, recurring reports or publishing workflows that combine several sources.
ETL / scraping / localization / CIIf a system fails silently, is hard to change or gives no clear indication of what happened, I review the critical parts and fix them according to their impact.
audit / tests / monitoringBefore development, we agree what the solution must do, what stays out of the first version and how we will verify the result.
Automation that depends on another website or API always has operational risk. I explain the limits and propose checks, fallbacks and recovery paths.
I deliver functional pieces in smaller increments. If a decision affects cost, timing or scope, we discuss it before it becomes expensive to change.
I use it for research and implementation. Architecture, security review and responsibility for the result remain with me.
You do not need a finished technical specification. It is more useful to describe the current workflow and the problem the solution should remove.
It depends on the process, the number of integrations and operational requirements. We first define a small, verifiable first version and use it to set a realistic scope.
No. Describe the current process, the systems involved and the desired outcome. I choose the technology based on integrations, reliability, security and operations.
Yes. I first review the critical paths, deployment and documentation. Then we separate the highest-risk fix from later features so the project can move in controlled steps.
Explain how the process works today, where the delay or error appears, which tools are involved and what the software should change. A finished technical specification is not required.
I write about decisions, failure modes and technical trade-offs from projects I have worked on.
Queues, retries, state checks and a clear handover to a person when the result is uncertain.
Explore the service ↗Mapping, validation and recovery paths for APIs, webhooks and recurring transfers.
Explore the service ↗A smaller first version with roles, history and a useful path to future changes.
Explore the service ↗Tell me how the process works today, what the result should be and which systems are involved. I will look at the problem and tell you whether and how I would approach it.
hello@softflow.cz ↗I usually reply within one business day.