H2M ML LabThirteen distillation experiments on real corpora. Students from 230M to 1.2B parameters, quantized, about a second on CPU.
See case studyFor companies paying too much for IT that still gets in the way
Your site, CRM and automations,
rebuilt as one system you own.
One engineer with the output of a team replaces the three vendors and the per-seat licences. You get a written plan with a date first, then a system on your own accounts, then someone who keeps it running. Warsaw, in English or Polish.
Case study 
Case study - pozyskajpacjenta.plCase study
porownajdentyste.plCase study - WhiteContextCase study
seecontainerpool.chCase study
- Harpagan
- pozyskajpacjenta.pl
- porownajdentyste.pl
- WhiteContext
- seecontainerpool.ch
Systems running today for a 25-person marketing agency, a clinic marketing agency, a Swiss pool manufacturer and two public comparison sites.
Services
Four problems I take off your plate. Each card: the situation it fixes, what you get, and the systems behind it. All four on one page →
01 · AI Engineering
Stop paying per token for a task that has not changed: a small model on your own server
Distill, fine-tune and deploy the smallest model that does the job, then wire it into the place your team already works.
The right call when Your frontier-API bill grows every month for a task that has not changed since spring.
See moreH2M ML Lab
AdtripSlack-native AI operator for a 25-person agency: headless Claude Code behind one write-gated gateway.
Read the case
AdcareA clinic marketing operating system operated from Claude through its own MCP server.
Read the case02 · Systems: architecture, build, operation
One system instead of three vendors: site, CRM and automations on your accounts
Web products, internal apps and e-commerce shipped as one codebase on your own Cloudflare account, and kept running after launch.
The right call when The site, the CRM and the automations come from three vendors and nobody owns the whole.
See more
SeecontainerpoolA Swiss brand with a 3D pool configurator; one pricing truth shared by the configurator and a partner API.
Read the caseAdcareMulti-tenant CMS plus agency and per-clinic CRM for a clinic marketing agency.
Read the case
pozyskajpacjenta.plClinic SaaS shipped in under four weeks: custom hostnames, booking, CRM, Stripe. Zero paying users so far, published as-is.
Read the case03 · AI training for teams
Your team automating its own work in a day, safely
Workshops for business teams built from 75-minute modules, up to four a day, on site or remote. Bring any device with a browser: the sandbox, the tools and the API tokens come from me.
The right call when Your team pays for AI subscriptions and uses them like a search box.
See more
awesome-ai-system-promptsThe public reference collection of production system prompts, used as teaching material for prompt and agent design.
See the build
h2mai.comThis site: a research build of a five-layer silver UI, WebGL cloth, shader type and a six-step intake, used as teaching material for the workshop.
See case study04 · Bespoke software
Replace the per-seat licence with code you own
Software cut to your process, and paid SaaS you rent by the seat rewritten into code you own.
The right call when You pay per seat for a tool your team uses ten percent of.
See more
WhiteContextData platforms that pay per row, not per seat: a Rust-to-WebAssembly extraction engine behind a vet marketplace.
Read the case
porownajdentyste.plDental price comparison built on an owned crawler instead of a paid data feed; every price checkable in public.
Read the caseAdcarePer-clinic CRM that replaced a per-seat subscription for an agency and its clinics.
Read the case
Work
Six systems in production, each card a case study with the live thing linked. Under every title: what changed for the business. The numbers are the ones their owners cleared, including the zero.
AdcareFlagshipCMS + CRMone MCP serverClinic marketing operating systemThe 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.Multi-tenant CMS plus agency and per-clinic CRM, operated from Claude through its own MCP server.AdtripAgency2,315call transcriptsSlack-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.Headless Claude Code behind one write-gated gateway; brand voice distilled from 2,315 call transcripts.SeecontainerpoolHardbox3languages, one priceA Swiss brand with a 3D pool configuratorThe configurator is the sales conversation: the price on the site is the price, on deals the size of 149k PLN and 37.5k EUR.One pricing truth shared by the configurator and a partner API; de-CH launch with factory GLB models.WhiteContextData2.55Mdomains pricedData 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.Vet marketplace on a Rust-to-WebAssembly extraction engine; 2.55M .pl domains priced at $0.00033 each.porownajdentyste.plConsumer13,690clinics, publicDental price comparison, verifiable in public13,690 clinics and 19,541 prices with no licence bill and a public audit trail for every number.13,690 clinics, 497 cities, 19,541 prices, every one checkable by anyone.pozyskajpacjenta.plHonest one<4 wkto ship, 0 payingClinic SaaS shipped in under four weeksZero paying users so far. Published so you can judge the engineering separately from the market.Custom hostnames, booking, CRM, Stripe. Zero paying users so far, published as-is.Swipe. Tap a card to read the case. All six, with the numbers →
Process · 01 / 06
From brief to roadmap
Six short steps, about twenty minutes of your time. The first is a free 30-minute call; the deposit comes after it and is credited to your first invoice.
- 01Fill the brief5 min
- 02Record a video request3 min
- 03Add attachments2 min
- 04Leave contact details1 min
- 05Pick a call slot1 min
- 06Pay the deposit2 min
Step 01
Fill the brief
Ten questions about goals, constraints and what exists today. Short answers are fine.
- What should change, and by when
- Your current stack and data
- One number that means success
Step 02
Record a video request
Optional. Voice or camera, up to three minutes, if that is easier than typing. Say it the way you would say it to me over coffee.
- Voice or camera, your choice
- Transcribed as you upload
- Only I see it
Step 03
Add attachments
Documents, screenshots, exports. They go straight into a private bucket, nowhere else.
- Drop anything in
- Stored in your own bucket
- Scanned, then indexed for the call
Step 04
Leave contact details
An email and a phone number. One consent for the one reply that matters.
- Phone
- Consent to be contacted
Step 05
Pick a call slot
Choose when you want to talk and confirm the number. I call you, not the other way round.
- Pick a time
- Confirm the number
- Reminder by SMS the day before
Step 06
Pay the deposit
After the call: $1,250 funds the roadmap and the architecture. If we go ahead, it becomes a discount on the build.
- Roadmap and architecture, in writing
- Yours to keep, whatever you decide
- Credited in full when we start
Scroll
Questions I get on every call
Tap a question. The answer comes back like a text, because that is how most of these arrive.
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.
The roadmap gives you a fixed number before you commit to anything. Small changes start within days; a rebuild of a site, a CRM and the automations is weeks, with the date written down. The 30-minute call is free.
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.
The roadmap gives you a date before you commit to the build. The stack is small and one person builds every layer, so nothing waits in a queue between departments.
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.
One person holds the whole picture: site, CRM, automations, MCP servers. No handoffs, no account manager translating. Agents give me the output of a team; you get one name to call.
They keep running until the new system is live. Your data is exported from the old tools into your own database, checked against the source, and the switch happens on a date we pick together, with a way back if something is off.
Yes. They keep what they run well; I take the piece that hurts. Everything I build sits on your accounts, so they can read the code and the docs from day one.
The code, the accounts and the documentation are yours, and the system runs on Cloudflare without a server to babysit. Another engineer can pick it up from the docs I leave. That is also why every scheduled task leaves proof of its last run.
The call is free. The roadmap is the $1,250 deposit, credited to the first invoice. The build is invoiced by milestone on the dates from the roadmap; operation, if you want it, is a monthly retainer.
Yes. The roadmap often starts with the one piece that costs you the most, and the rest waits until that piece pays for itself.
Yes, before you send the brief if you need it. Send yours or use mine.
Both. Calls and documents in whichever you prefer. The code and the commits stay in English.
Something else? Ask it on the call
A 30-minute call, free
One email. I reply within one working day with three questions and a proposed plan, not a deck.