H2MHuczyńskiSystems you own
Contact

Services · H2M

The problems I take off your plate

Each one ends with a system your team can operate without me, on your own accounts, with the code in your hands. Pick the one that sounds like your week.

  1. 01 / 05 · 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.

    • Model distillation
    • Fine-tuning on your corpora
    • Quantized CPU deployment
    • Agents with MCP tool access
    • Eval suites with published negatives

    The right call when

    1. Your frontier-API bill grows every month for a task that has not changed since spring.
    2. Your team already lives in Slack or Claude and wants the CRM, the CMS and the reports reachable from there.
    3. You need an agent that acts on company data, with every write audited.

    You get

    • Eval suite on your data, with the negatives published
    • The smallest model that passes it, quantized, deployed on CPU or your account
    • MCP server exposing your systems as tools, one write-gated gateway
    H2M ML Lab

    Thirteen distillation experiments on real corpora. Students from 230M to 1.2B parameters, quantized, about a second on CPU.

    See case study
    Adtrip

    Slack-native AI operator for a 25-person agency: headless Claude Code behind one write-gated gateway.

    Read the case
    Adcare

    A clinic marketing operating system operated from Claude through its own MCP server.

    Read the case
  2. 02 / 05 · 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.

    • Web development
    • Internal apps
    • E-commerce and configurators
    • CRM and automation as one system
    • Fractional operation with proof of last run

    The right call when

    1. The site, the CRM and the automations come from three vendors and nobody owns the whole.
    2. You need a product, an internal app or a configurator that has to be live before the quarter ends.
    3. Something is running and nobody can say whether it ran last night.

    You get

    • Architecture on one page, then the system on your Cloudflare account
    • Site, CRM, automations and the MCP server as one codebase
    • Scheduled tasks that leave proof of their last run
    Seecontainerpool

    A Swiss brand with a 3D pool configurator; one pricing truth shared by the configurator and a partner API.

    Read the case
    Adcare

    Multi-tenant CMS plus agency and per-clinic CRM for a clinic marketing agency.

    Read the case
    pozyskajpacjenta.pl

    Clinic SaaS shipped in under four weeks: custom hostnames, booking, CRM, Stripe. Zero paying users so far, published as-is.

    Read the case
  3. 03 / 05 · AI training for teams

    Your team ships with Claude Code in two days; your best people keep shipping for a quarter

    Two products. A fast workshop: one or two days on your own repository, up to twelve people, a sandbox and the API tokens from me. A mentoring programme: a quarter with the one person who will own the tooling, on their live work.

    • Fast workshop: a day per skill
    • Mentoring programme: a quarter per person
    • Agents, git, MCP, browser automation
    • Your repository, your accounts

    The right call when

    1. Your team pays for AI subscriptions and uses them like a search box.
    2. Two people in the company can automate things; the other twenty send them tickets.
    3. You want the team to build its own small tools and agents, safely, and keep them in git.

    You get

    • A shared repository with everything the team built, in git, with history
    • Each participant's sandbox for 30 days after, and an install script if they want it locally
    • A team playbook: prompts, guardrails, what to automate next
    awesome-ai-system-prompts

    The public reference collection of production system prompts, used as teaching material for prompt and agent design.

    See the build
    h2mai.com

    This 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 study
  4. 04 / 05 · 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.

    • Replace per-seat SaaS with owned code
    • Data platforms that pay per row
    • Crawling and extraction engines
    • Marketplaces and comparison sites

    The right call when

    1. You pay per seat for a tool your team uses ten percent of.
    2. You buy data per licence that a crawler on your account could price per row.
    3. You need a marketplace or a comparison site where every number can be checked in public.

    You get

    • The paid tool taken apart: what you use, what you do not
    • The rebuild as code on your account, no per-seat bill
    • Crawling and extraction engines priced per row
    WhiteContext

    Data platforms that pay per row, not per seat: a Rust-to-WebAssembly extraction engine behind a vet marketplace.

    Read the case
    porownajdentyste.pl

    Dental price comparison built on an owned crawler instead of a paid data feed; every price checkable in public.

    Read the case
    Adcare

    Per-clinic CRM that replaced a per-seat subscription for an agency and its clinics.

    Read the case
  5. 05 / 05 · Recovery

    Production failing? The data secured first, then the cause fixed while you keep selling

    When the shop, the CRM or the system your company runs on is failing: the data secured first, the cause measured on live production, small reversible fixes. The business keeps selling while it happens.

    • Off-site backup before any change, proven by a restore
    • The cause measured on live production, not guessed
    • Reversible fixes, each with a written rollback
    • A written report: what broke, what changed, what is left

    The right call when

    1. Your shop or system goes down several times a week and nobody can say why.
    2. The admin panel is so slow the team cannot do its daily work.
    3. There is no backup you have ever restored, and the person who built it is gone.

    You get

    • A full off-site backup, restored and checked before any fix
    • The root cause, measured and written down
    • Fixes on production, each with a one-line rollback
    Auto-parts shop

    An e-commerce shop with ~100k products whose database crashed three times a day, stabilised on live production without planned downtime.

    Read the case

How every engagement runs

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

    Savings audit

    €1,200 / $1,400 net, 5 business days

    The 36-month cost comparison, the order of moves, the risks and a fixed build price. Paid by bank transfer after the call, once you accept the offer; credited in full against a build ordered within 60 days of the report. If the audit does not show savings of at least twice its fee over 36 months, you get the fee back.

  3. 03

    Build, handoff, operate

    fixed price from the audit

    One engineer builds every layer on your account and documents it. The offer includes a monthly plan by default, so the system is looked after from launch day.

Questions I get about this

Tap a question to see the answer.

Scoping calls · most weeks

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

The 30-minute call is free. The audit costs €1,200 / $1,400 net and gives you a fixed build price before you commit to anything; builds start at €14,000 / $16,000 net. The offer includes a monthly plan by default: Care at €590 / $690 a month or Lane at €2,090 / $2,400 a month, starting on launch day. All prices are on the pricing page.

Savings audit. In 5 business days: the 36-month cost comparison, the order of moves, the risks and a fixed build price in writing. It costs €1,200 / $1,400 net, paid by bank transfer against an invoice after the call and after you accept the offer. If you order the build within 60 days of the report, the full amount comes off its first instalment; if not, the report is yours to take to anyone. If the audit does not show savings of at least twice its fee over 36 months, you get the fee back.

The repository, the Cloudflare account, the domains and the data sit under your company from day one, and the data is yours. Code built only for you becomes yours once it is paid for, as the contract sets out; H2M modules come with a perpetual licence. I get access to your accounts, not ownership of them.

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 system keeps running on Cloudflare with no servers to babysit, and a monthly plan starts on launch day. Care (€590 / $690 a month) keeps it monitored and backed up and takes up to 2 small changes a month; Lane (€2,090 / $2,400) keeps one change always in progress. On top, every plan takes more changes in a relaxed queue, from 4 small ones a month on Care to 8 on Lane: no deadline, done when there is capacity. The code and the docs stay yours, so you can also run it yourself or hand it to another engineer. Plans and SLA

Yes, before you send the brief if you need it. Send yours or use mine.

English: the calls, the documents, the code and the commits.

Something else? Ask it on the call

A 30-minute call, free

Thirty minutes, then an offer for the audit

Pick a free time in my calendar. Or leave an email: I reply within one business hour with three questions and a proposed time for the call, not a deck.