I came at automation from both ends. Business process optimization since 2009, then eight years building production software. n8n is where the two finally met.
The process half started in finance and moved into process work. I ran cross-functional improvement projects at a building-materials distributor, then consulted externally on process design for construction and industrial clients. Later I collected the operating data a fast-growing restaurant holding was missing and wrote the standards its own sites and its franchise partners opened against. One of those projects took enough load off a purchasing department that the company cut two positions.
The engineering half is superkassa, a high-load airline ticketing platform: web developer first, then team lead, growing the team from 6 to 15 while staying hands-on with backend work. After that I built and sold my own commercial work-tracking and cost-control platform (Go, Vue, PostgreSQL). The client still runs it every day.
The two halves met earlier than I'd thought. As team lead my main job was controlling how work moved through the team, so I built that control into ClickUp: custom statuses and dependencies, review and QA tasks created automatically, payment statements generated over the ClickUp REST API. That was 2020. That's four years before I got to n8n.
Since 2024 I've been building AI automation for business processes: n8n workflows, LLM APIs (Claude, OpenAI, Gemini, local models on Ollama), RAG on Qdrant, REST and webhook integrations.
What I'm after is owning a process problem end to end: talk to the people running it, decide what's worth automating and what should be fixed first, build it, and stay close while it's in use. Full-time or long-term contract, remote.
