H2MHuczyńskiSystems you own
Contact

Service 04 / 04 · Bespoke software · all services

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

A subscription you pay per seat for a workflow that is really two tables and a queue is a rewrite waiting to happen. I take the paid tool apart, keep the ten percent your team actually uses, and rebuild it as code on your account with no per-seat bill. Same for data: engines that price per row instead of per licence.

This is the right call when

  1. 01

    You pay per seat for a tool your team uses ten percent of.

  2. 02

    You buy data per licence that a crawler on your account could price per row.

  3. 03

    You need a marketplace or a comparison site where every number can be checked in public.

What you get

What lands on your account

  • 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
  • Public, verifiable numbers where the product is data

How it 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

    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.

Case studies

The systems behind this service, with the numbers their owners cleared for publication.

  1. WhiteContext

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

    Rust → Wasm pipelines, priced per row.

    2.55M
    .pl domains priced
    $0.00033
    per domain

    Read the case See the build

  2. porownajdentyste.pl

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

    Crawling, D1, SEO. Every number verifiable by anyone.

    13,690
    clinics
    497
    cities
    19,541
    prices

    Read the case See the build

  3. Adcare

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

    The agency and every clinic operate the same CRM on one codebase.

    CRM
    owned, no per-seat bill

    Read the case

Runs on

  • Rust
  • Wasm
  • Sqlite
  • Workers
  • Typescript
  • Python
  • Postgresql
  • Docker

Questions I get about this

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

Scoping calls · most weeks

Only if the workflow is narrow enough. The scoping call is where I say no when it is not. When it is, the per-seat bill goes to zero and the code is yours.

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 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.

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

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.