Sebastián Gálčik · Slovakia · Central European hours
You have already sold the automation. I am the person who builds it, on your terms, under your name. Your client never learns I exist.
All of it in production, none of it a portfolio piece. Client names above are used with their permission, and references are available on request.
Banking & finance integration
Full OAuth token lifecycle with unattended refresh, CAMT053 statement parsing into a normalised SQL schema, and incremental daily runs with duplicate suppression scoped to the statement header — so a re-run mid-day cannot double-post a transaction. Deployed as a compiled Windows binary and as a Raspberry Pi service.
3 banks · production · runs daily, unattended
Operational data plumbing
Point-of-sale APIs reconciled into MSSQL on a schedule. Power-meter telemetry from IoT relays logged continuously. CNC and CAD files parsed for geometry and pushed into production planning. Excel workbooks turned into a two-way sync instead of a manual re-key. Around twenty-five of these, for real businesses that depend on them.
~25 delivered systems · manufacturing, retail, facilities, agriculture
Research infrastructure
My own long-running project, and the reason I am worth trusting with something unattended. Automated backtesting over minute-resolution market data, orchestrated across parallel agents and four independent research lanes. Over 560 documented research rounds, each with a prediction registered before the test, and a graveyard registry that blocks re-testing an idea already killed. Method and strategy stay private; the discipline is the point.
560+ rounds logged · 4 research lanes · predictions on record
Built in one evening, to show the pace
Writes the script, synthesises the voiceover, drives a real browser through a live SaaS product and records it with a synthetic cursor, times captions from the measured audio rather than from speech recognition, renders to 9:16 and publishes to three platforms. Zero human steps per video.
9 modules · 3 platforms · 1 evening
A theme across all of it: the hard part is never the API call. It is the failure modes that report success — a caption field that silently discards programmatic input, a vendor 200 that is a job id rather than a published post, a recording with no cursor in frame, a backup nobody has ever restored. Those decide whether an automation survives a month unattended, and they are what I spend my time on.
No retainer, no minimum, no discovery phase to pay for. If the first build is good you send the next one. If it is not, you have lost a week you were not going to spend anyway.
Slovak rates, your timezone. I invoice as a registered EU sole trader, so there is no offshore payment friction and no overnight gap to manage.
Reply to the email this link came from, or write to [email protected].
Fastest way to judge me: send the messiest spec you have. I will tell you what I would cut and what it costs, before you commit to anything.