I build internal tools, data pipelines and LLM-powered automation. 25 years running engineering and infrastructure projects before I started automating them.

Independent consultant and developer. I build internal tools, data pipelines and LLM-powered automation.

Before this I spent 25 years running projects in energy, infrastructure and industrial construction — as founder, director, and program lead. I built two organizations from zero: an engineering and construction company that grew to 70 staff, and a university R&D centre that grew to 100 people.

Some of what I ran: a regional power grid development program covering 12,000 km of lines and 32 utilities, defended at the Russian Ministry of Energy. An optimal energy supply scheme for a remote Kuril island, from wind and geothermal scenarios through to tariff impact. A district heating scheme for a city of half a million. An industrial retrofit for a petrochemical major.

Deputy Chairman of the Cross-Industry Consumer Council on Natural Monopolies under the Governor of Tomsk Region since 2016.

That background is the reason I am useful here. Most automation work fails not because the code is wrong, but because nobody understood the process being automated. I understand processes — schedules, cost estimates, procurement, reporting — from having run them.

WHAT I BUILD NOW

Data pipelines: scraping, enrichment, cleaning, scheduled runs.
LLM-powered tools: document processing, extraction, classification, multi-step reasoning workflows over your own data.
Internal dashboards and reporting over existing systems.
Prototypes your team can take over and extend.

Stack: Python, Flask, SQLite/Postgres, APScheduler, Docker, Firecrawl, Anthropic and OpenAI APIs, Google Sheets API.

I take work where the question is not "who can write this script" but "who can see what actually needs building."

Russian (native), English B1 — I work in written channels and prefer written technical discussion over calls.

Work Terms

AVAILABILITY
Mon-Fri, and weekends when a deadline needs it. Time zone GMT+7: my afternoon overlaps European mornings, my early morning overlaps the US East Coast evening. I answer within one business day, usually faster.

COMMUNICATION
Written channels preferred. My English is B1 — precise in writing, slower on calls. For detailed technical discussion this is a feature: everything is on record, nothing is lost in an accent. Short calls are fine once we have a written scope.

HOW I SCOPE
1. You describe the process, not the solution. What happens today, who does it, where it breaks.
2. I come back with a written scope: deliverable, milestones, price, what is explicitly out of scope.
3. We agree before any code is written. If I think the tool you asked for is the wrong tool, you hear it at this stage, not after.

PAYMENT
Through Guru SafePay only. Fixed-price milestones for defined deliverables; hourly for open-ended or exploratory work. Minimum engagement $500.

DELIVERY
Working prototype early, iteration after. Code delivered readable, commented, with a README your team can follow. You own it outright — no lock-in, no dependency on me.

REVISIONS
Two rounds of revision inside the agreed scope, included. Scope changes are re-quoted, not absorbed silently.