H2MHuczyńskiSystems you own
Contact

Work · six systems in production

The work, with the numbers

Six systems, each one a page: the situation, what was built, what changed for the business, how the pieces connect, and the live thing linked. The numbers are the ones their owners cleared, including the zero.

AdcareSystemsA clinic marketing operating system, operated from ClaudeThe per-seat CRM subscription is gone; the agency and every clinic run the same CRM they own, and a new clinic is a tenant, not a project.66tables199migrations180tools in the MCP serverRead the case AdtripAI EngineeringA Slack-native AI operator for a 25-person agencyThe team asks the operator in the client's own Slack channel, 87 of them, and every write is auditable.87client channels95tools in the gateway27skillsRead the case SeecontainerpoolSystemsA Swiss brand with a 3D pool configurator and one pricing truthThe configurator is the sales conversation: the price on the site is the price, on deals the size of 149k PLN and 37.5k EUR.3languages, pl / en / de1pricing API for site and partners149k PLNa deal size the business closesRead the case WhiteContextBespoke softwareData platforms that pay per row, not per seatBuyers pay for the rows they take; the engine is owned, so the unit price is a number we set, not a licence we resell.2.55M.pl domains priced$0.00033per domain4,650vet clinics on porownajweterynarza.plRead the case porownajdentyste.plBespoke softwareDental price comparison, verifiable in public13,690 clinics and 19,541 prices with no licence bill and a public audit trail for every number.13,690clinics497cities19,541pricesRead the case pozyskajpacjenta.plSystemsClinic SaaS shipped in under four weeks. Zero paying users so far.Zero paying users so far. Published so you can judge the engineering separately from the market.<4 wkfrom brief to production0paying users, honestly4modules: hostnames, booking, CRM, StripeRead the case

How every one of these started

Three steps. The six-step version, with the brief and the video request, is on the home page.

  1. 01

    Scoping call

    30 min, free

    You describe the situation; I ask three questions and propose a shape.

  2. 02

    Roadmap and architecture

    $1,250 deposit

    A written plan with a date. The deposit is credited to the first invoice; the documents are yours either way.

  3. 03

    Build, handoff, operate

    date on the roadmap

    One engineer builds every layer on your account, documents it, and can keep operating it.

Questions I get about this

Tap a question. The answer comes back like a text.

Scoping calls · most weeks

Maksym Huczyński, the engineer who built the systems on the Work page. I write the roadmap, the code and the reply to your brief. Agents do the volume; one person stays accountable for the whole system.

A written roadmap and an architecture for your system, delivered after the scoping call. If we build together, the full amount comes off the first invoice. If not, the documents are yours to take to anyone.

You do. The repository, the Cloudflare account, the domains and the data sit under your company from day one. I get access, not ownership.

The system keeps running on Cloudflare with no servers to babysit. You can operate it yourself, keep me on for changes, or hand it to another engineer with the docs I leave behind.

Something else? Ask it on the call

A 30-minute call, free

Thirty minutes, then a written plan

Leave an email. I reply within one working day with three questions and a proposed plan, not a deck.