Wojciech Turek: agents that use real software
This page is an interactive terminal. Every command's output is reproduced below in reading order, so it can be read without typing anything.
whoami: who is typing back
you: unknown. nothing here tracks you, so that is honestly all I have.
me: Wojciech Turek. I build agents that use real software.
Real software meaning the kind with buttons, login screens, and a menu item three levels deep that nobody on the team remembers. Desktop apps. Phones. Browsers. Whatever the work is actually trapped inside.
Not a chatbot. Chatbots talk. These ones click.
work: what I actually do
I take the slow, repetitive, human-occupied parts of a business and give them to something that does not get bored.
Most automation advice quietly assumes an API. The work people actually hate usually has none. It lives in an application somebody bought in 2014 and cannot replace, so the agent uses the application, the way a person would, only at 4am and without sighing.
usual suspects
a person moving records between two systems every morning
a queue that only moves when somebody opens each item and clicks approve
a report that exists because someone assembles it by hand
onboarding: forty tiny steps, all boring, all mandatory
If you can screen record it, it can probably be taken off your desk.
how: how a job goes, honestly
1 watch I do the job by hand, badly, at your speed, once.
2 build the agent does it instead. your machine or mine.
3 break it fails at 3am, on the one input nobody mentioned.
4 fix this step is the job. everything before it was setup.
5 leave it runs. you stop thinking about it.
Step 5 is the deliverable. Not the script, not the demo: the part where it stops being your problem.
Anyone who skips step 4 is selling you a video.
agents: what the word means, minus the hype
"Agent" has been stretched to mean roughly everything, so here is the narrow version I mean when I use it.
A program given a goal, which then operates ordinary software to reach it: opening windows, reading what is on the screen, clicking, typing, noticing when something looks wrong, and trying again a different way.
The useful part is not the intelligence. It is doing the four hundredth item as carefully as the first.
stack: what I build with
Playwright ADB
Claude OpenAI
Gemini Python
TypeScript React
Next.js Tailwind CSS
Shadcn UI Node
Docker PostgreSQL
Supabase FFmpeg
The list is not the point. The tool that matters is whichever one your work already lives in, including the awkward one.
price: no numbers, but a real answer
No numbers on a website. Any number here would be wrong for your case, and you would remember it anyway.
Three shapes this usually takes:
pilot one workflow, fixed scope, so you can watch it work before you have to believe me
build the real thing: hardened, monitored, documented, handed over so it is not hostage to my calendar
retainer I keep it alive while your tools keep changing, and your tools will keep changing
Tell me what the task is and roughly how often it happens. That is genuinely enough for a number.
`msg` sends it to my phone. `book` puts it in my calendar.
game: a small demonstration
An interactive demonstration: twenty four rows of data that have to be moved one click at a time, timed, and then finished by an agent instead. The point of it is that the agent treats row 19 like row 1.
contact: email and links
email studio@wojciechturek.com
linkedin www.linkedin.com/in/wojciech-turek
github github.com/wojciech-turek
or type `msg` and it lands on my phone in about a second. no phone number. that one is deliberate.
book: put something in my calendar
Meetings can be booked directly at https://www.cal.eu/wojciechturek.
msg: send me a message, it buzzes my phone
Messages sent here arrive on my phone in about a second. Email works just as well: studio@wojciechturek.com.
contact
Email studio@wojciechturek.com.