Technical partner for founders building with AI.
I set the architecture, lead the engineers, and optimise what it costs to run.
Tamas kept communication open, had a great attention to detail, and was patient with our project's progress. We are grateful for his work getting the system's technical foundation set and running.
A real professional in his field. He delivered a comprehensive AI-driven data transfer for my company and definitely overdelivered on this project. I truly value his work.
What impressed me most was the care he took to make sure I could confidently operate and evolve the system myself. A rare ability to listen deeply and turn ideas into elegant, practical solutions.
A brand protection system that scans Google, marketplaces, and reverse-image search for counterfeits and flags the real ones. It caught 20 genuine violations in the first run. Handed over clean, would hire again.
He built both n8n automation systems cleanly and efficiently, with well-structured workflows that are easy to understand and duplicate. Clear communication and solid documentation. Would definitely hire again.
If I needed automation work done by someone who thinks in systems, not tools, Tamas would be my first call. He builds solutions teams can maintain and scale.
An exceptional AI and automation tutor. He translates complex ideas into practical understanding, and leads by example.
A consistent contributor to our automation efforts, particularly with n8n. He developed solutions tailored for our Sales and Business Development teams.
What sets him apart is his ability to remain calm under pressure, guiding the team through complex challenges with a clear vision.
His leadership is marked by a strategic mindset and a commitment to high-quality results. Even under pressure, he stays composed and organized.
A department, not a ticket queue.
I run the AI and Automation department for a US e-commerce brand doing around USD 1 million a month. Three engineers report to me. I set the architecture, wrote the technical assessment we hire against, and own what every system costs to run.
Nobody owned API spend before I arrived. At the volumes this company is heading for, unit cost is the margin ceiling. I put a spend gate on one system without locking anyone out of their own work, and its bill went from USD 925.51 to USD 64.82 in twelve days. A 93 percent cut, measured on the vendor's own ledger.
I build as well. I took the video pipeline apart and rebuilt it in code over a day and a half. The old one scored quality with prompts. I dissected the four reference videos the founder had approved, then rebuilt the flow so lighting, speech cadence, volume and background noise became numbers a computer checks. Cuts per minute went from 3.9 to 30.7 and the longest unbroken avatar shot from 68 seconds to 5.4, every value inside the corridor those four files set. A prompt gets ignored by a model. A number does not.
Most companies start with the diagnostic.
Lead the department
Architecture, hiring, unit costYou have engineers and no one setting the standard. I set the architecture, write the assessment you hire against, and own what every system costs to run.
BMap the estate
The paid diagnosticNobody has mapped what you have. Two or three days of read-only access, then a written recommendation with the decisions named and priced.
CBuild the systems
n8n, Python, Claude, and the app layerYou know what needs building. I ship it with tests, a cost ceiling, and a handover pack, on infrastructure you own.
Selected work
Read-only access, then questions.
I ask for read-only access first, so nothing breaks and nobody wonders who changed what. I spend a day or two mapping the architecture and building a knowledge base of your systems. I click through the product like a user.
Then I send you my questions, and they are all why questions. Most companies have never had anyone do this. One client had four years of work in GitHub and not one page of documentation. The first map of it took me an afternoon.
Two things worth knowing before you write.
I do not sell hours.
I sell outputs, on a fixed price or a monthly partnership. Commit to a year and the number comes down. You get the monthly running cost before the build starts, not after.
I will talk you out of things.
I told one founder to put his budget into ads instead of the system he asked me to build. I told another his vendor was about to write logic in the wrong place entirely. Both are still clients.
Tell me what your systems are supposed to do.
And what they do today. I will tell you where the gap is.