02 · Websites and software

Web apps and tools

Interactive tools for your customers and custom tools for your team, built on your real data.

In short

A good tool answers one question better than any article: when to plant, how many hens, which perfume is closest. That is the part of a site people bookmark and come back to.

The same work builds tools for your own team: an admin panel, an internal calculator, a screen that replaces the spreadsheet everyone is afraid to touch.

What's included

  • Tools for your customers

    Calculators, planners, configurators, finders and comparisons that answer a real question with your data.

  • Member areas and accounts

    Sign-in, saved results, uploads and profiles, with personal data limited to what each feature needs.

  • Internal tools

    Admin panels, back-office screens and small apps built around one team's process, instead of a shared spreadsheet.

  • Dashboards

    The numbers a team checks every morning, pulled from the systems that hold them, on one screen.

  • An API behind it

    A documented API, so other systems or an AI agent can use the same data and rules.

  • Tests

    End-to-end tests with Playwright, accessibility checks with axe and tests for the calculations themselves.

How I run it

  1. The question

    What the tool must answer, for whom, and what a good answer looks like.

  2. Data and rules

    Where the numbers come from and how they are combined, written down with sources.

  3. Prototype

    A working version on real data early, so the rules can be checked against cases you know.

  4. Build

    Interface, API and database, tested on the calculations as well as the screens.

  5. Release

    Launch checks, monitoring and a short guide for the people who will use it.

Content Monitor · Site Scanner · Polaris CMS

Run on my own tooling

Tools are pages too: they have to load fast, get indexed and keep working. My tooling covers both sides.

Site Scanner

A 98-item launch checklist, a crawler and Lighthouse

  • Checklist and Lighthouse

    Tool pages go through the 98-item checklist and Lighthouse like every other page, so a heavy script can't slip in unnoticed.

  • Findings as an agent prompt

    Scan results become a ready prompt for an AI coding agent, so every fix starts from an exact list.

Content Monitor

The dashboard every live site is run from

  • Search and analytics per page

    Which tool pages bring visitors from Google and how engaged they are, from Search Console and GA4.

  • Index status

    New tool pages are checked in Search Console until Google indexes them.

Polaris CMS

My own CMS, this site included

  • Articles that lead to the tool

    Guides around a tool are published through Polaris CMS, with link suggestions that point readers to it.

About Polaris CMS

Infrastructure

Docker on my own servers, behind Cloudflare

  • Portable by design

    Every app is a Docker image with its data in Postgres, deployed through Coolify, so it can move servers without a rewrite.

Proof

Questions

Can you build a tool that only my team sees?

Yes. It sits behind a login, stays out of search engines and can run on its own server. The same tests apply.

Can a tool replace our spreadsheet?

Often. I start by rebuilding what the spreadsheet does, check that the results match on your real data, and only then add what it could not do.

Can it run on our own servers?

Yes. Every app ships as a Docker image with its data in plain Postgres, so it runs on my servers or on yours.

All services →

Tell me what you need

A few lines are enough: what you want to build, fix or automate, and any date that matters. I reply in English or Polish.