300+
orders in the first 3 days
An order generator for a group of e-shops replaced two legacy applications. It ran in shadow mode for several weeks and now sends orders to the manufacturer in their format, after an operator check.
Vít Šafařík
Freelance engineer. I build and run systems with AI agents.
I build the system your business runs on and keep it running.
In IT since 2009. From 2021 to 2026 I led development at a small web agency: the team, delivery, estimates, servers and production. Since 2026 I bring that experience directly into companies as a freelance engineer. I build with AI agents, but I own the architecture, the data model, the security and every decision, and I answer for what runs in production: tests, monitoring, backups with verified restores.
- 17 years
- in IT, since 2009
- 4 systems
- shipped to production in 2026
- 80 sites, 20 servers
- operations I led at an agency, 2021–2026
Who this is for, and who it is not for
A good fit if
- You need someone who gets AI into production, not into a slide deck.
- You have an AI pilot that still does not run in production.
- You have one process that today depends on a person at a keyboard.
- You need a senior engineer a few days a week without hiring one.
Not a fit if
- You want an agency with an account manager and a team of people.
- You want a strategy document without anyone implementing it.
- You need someone full time, in your office.
How I work with AI agents
Most of my commits today list Claude as a co-author. Agents make me faster, but they add a kind of error that only a human catches. In three months I logged eight incidents caused by agents. No automated check caught any of them and human review caught all of them. My process is built around that.
What it looks like
- I start with a written brief and a plan that you sign off on.
- I split the work into small batches that can be read and reviewed.
- Agents implement each batch and write the tests for it.
- An independent agent, and then I, check the result against the brief, not against the plan.
- The new process runs next to the old one on real data before anything is switched over.
- In production it is watched by monitoring that only speaks up when something needs a human.
What I keep for myself
- Architecture and the data model.
- Security and access to your data.
- Decisions about scope and priorities.
- The final review before deployment.
- Communication with you.
What agents never do
- Merge code without tests and review.
- Touch production.
- See your data outside an environment where I have your consent for it.
- Make decisions on my behalf.
What is running today
~4,000
inquiries in one system
A dispatch CRM for a company that makes and installs window blinds keeps inquiries, calls and field visits in one place and hands jobs to the technician planning tool. Live since May 2026, 27 users.
17 → 1
e-shops in 6 countries, one dashboard
Sales, orders, invoices, ad spend and margin for 17 e-shops on Shoptet and Shopify, refreshed every ten minutes. 141,460 invoices and credit notes verified against the accounting API to the cent.
How we work together
You need an AI engineer on your team
We agree on a number of days per week and I work as part of your team for the long run, without a hire and without agency overhead. You set the priorities. I get AI into production and teach your people to work with it.
You have one specific process
One process or system as a bounded, fixed-price project: orders, inquiries, an owner dashboard. We start with mapping and end with a handover.
- 3 to 5 days
Map
I go through your company with you to find where work depends on a person today and what should run on its own. You get a list of those places ranked by impact and a fixed quote for the first one.
- weeks, not months
Build
I build in small batches and run the new process next to the old one on your real data. We switch over only once it is visibly working.
- as agreed
Hand over and watch
You get documentation and a trained team. The code and the data are yours. If you want, I keep running it: monitoring, backups with verified restores, and changes.
The goal is that you do not need me for day-to-day operation. Another developer can take over, and nothing ties you to me.
Engagement shapes
Three shapes. Which one is yours usually becomes clear during mapping.
Mapping
For a company that knows it needs something and wants to know exactly what, and what it costs.
Three to five days in which I go through your processes, systems and data and talk to the people doing the work today. You get a ranked list of opportunities and a fixed quote for the first project.
Fixed-price project
For a company with one specific process or system.
I build it, test it, document it and hand it over. Automated tests, a run next to the old process, documentation, training, and code and data that belong to you. The price is fixed and known before we start.
Days per week
For a company that needs a senior engineer for the long run, but not full time.
An agreed number of days per week. You set the priorities. I build, operate what we have built, and train your team to work with AI on your real tasks.
I quote after mapping, always up front and always fixed. I do not bill by the hour.
About me
I am Vít Šafařík from Opava, Czechia. I have been in IT since 2009, after seven years in B2B sales, and a developer since 2018. From 2021 to 2026 I led development at a small web agency. Since 2026 I bring that experience directly into companies as a freelance engineer. I build with AI agents, keep architecture, data and security in my own hands, and answer for the result.
Available from November 2026. As of September 24, 2026.
Tell me what you need
A few sentences are enough: what should work, what does not work today, or whether you are looking for someone a few days a week.
[email protected] · +420 778 093 308
What happens next
- I reply within 24 hours on working days, personally.
- A 30-minute call about what you need, free and without obligation.
- If it makes sense, I suggest a shape for the engagement and, after mapping, a fixed price.