Selected work
Systems and builds for the niches I work in. Every case starts from what hurt, not from what was built — the problem first, then the decisions, then what it cost to get them right.
151 vehicles in one catalogue, four contract types, one enquiry
Van and minibus rental in Warsaw. Short, medium and long-term hire plus a replacement vehicle after an accident — four different contracts, one catalogue, one enquiry form.
12 services priced on the page, before any call
A detailing build for a niche where every competitor sells the same words. This one sells numbers: paint depth per panel, prices published before the call, five jobs documented.
62 checkpoints published before the visit, not after
A cleaning build that answers the two questions which normally cost a phone call — what does my home need, and what will it cost — before anyone has to call.
412 projects catalogued across two markets and two currencies
A design-build renovation build across two markets and two currencies. Nine of four hundred and twelve finished projects given their own page, with price ranges for both cities standing in front of the paid survey.
3,000 records the team publishes without a developer
Save Ukraine returns children deported by Russia. Its site is a newsroom, an evidence archive and a donation channel in English and Ukrainian — over three thousand records the team publishes itself, and one number that has to be right everywhere it appears.
117 course pages in three languages, one site, one admin
A Warsaw academy of cosmetology and aesthetic medicine. 117 course pages and fifteen instructors in Polish, Ukrainian and Russian, on one site, kept by the academy's own staff — and enquiries that reach the sales team's phones, not an inbox.
142 congregations findable by name or town, with or without the map
The Volyn regional union of the Ukrainian Church of Christians of Evangelical Faith. 142 congregations in one directory — by map, by name, by town — plus news, a video channel and a donation path, run by people whose job is not websites.
None of them started as a request for a website. They started as a business problem: a catalogue nobody could search, four kinds of contract pushed through one form, a directory of a hundred and forty-two locations kept in a spreadsheet, an organisation whose work was invisible because there was nowhere to publish it.
So each case is written the same way: what hurt, what I built, which decisions had a real trade-off, how it behaves on a phone, and what I would do next. Where a number appears, it was counted rather than estimated — and where the content on a published build is demonstration data, the case says so.
The problems repeat across sectors far more than people expect. A course catalogue in three languages and a rental fleet with four contract types are the same modelling exercise wearing different clothes.
Mostly WordPress, used as an application framework rather than as a blog with plugins bolted on: custom post types that model the actual business, fields registered in code so the structure lives in version control, queries written for the data that exists. Where a project genuinely suits another approach — including no content management system at all — that is what it gets, and I say so before the work starts rather than after.
A full list of what I build is on the services pages, ordered from a single task to an ongoing technical partnership. If one of these cases looks like your situation, describe the problem in writing and you get a written scope and a fixed number before any work begins.