Adam Grudziński

Szczecin, Poland. Remote, in Polish, German and English.

I build the whole product, not a piece of it.

Database, backend, interface, deployment, and answering for what runs. Four things I built are live right now, with my own name on the terms of service. Open any of them before you write to me.

4
products running live
49
exam papers that solve themselves
3
languages in Panel and Planer: PL, DE, EN
10 yrs
in operations at German companies before I wrote code

New product

A whiteboard for maths lessons that the student joins from a link.

I teach my own lessons on it. Now I am taking it out of Algebra i Spółka as a product of its own for tutors and teachers: function plots, 3D solids, formulas from the keyboard, voice and camera next to the board.

Work

Each one has its own page: what it does, who it is for, how it is built and what was hard about it.

  1. 01 · Website builder

    Panel Biznesu

    A website builder for small service businesses. Copy written for the trade, editing like a slide deck, payment after approval.

    Read the case study
  2. 02 · Field service planning

    Planer Operacyjny

    Scheduling for field crews: map, calendar, recurring inspections, PDF report. A demo for five trades and a student mode.

    Read the case study
  3. 03 · Maths platform

    Algebra i Spółka

    Exam papers that solve themselves on a chalkboard, with voice-over. Games, a level test and video lessons in one tab.

    Read the case study

What I can build for you

Business websites and landing pages
Astro or React, your own domain, forms that arrive, language versions, structured data for local search, and a panel where you change text and photos yourself.
Web applications
Scheduling, customer and equipment records, roles and permissions, two factor login, PDF generation, recurring jobs and alerts. Built for people who are not developers.
Python integrations and automation
Data from an API into a database or a warehouse, incremental loads that survive a failed run, file processing, migrations. A log for every run, an alert after two failures in a row.

How I work

  1. 01

    A conversation

    I ask about the process, not the technology. After the first call you know whether the job is for me.

  2. 02

    Something to click

    I send a working version early rather than a status report.

  3. 03

    A date I keep

    If something slips, you hear it from me in advance, not on the deadline.

  4. 04

    After launch

    You get documentation and someone who picks up the phone. The code is yours.

Tell me what you need built.

Two or three sentences about the job, the deadline you have in mind, and a link if something already exists. You get a straight answer on whether I am the right person, usually the same day.

Or write straight to my inbox:

a.grudzinski1992@gmail.com
Reply time
usually the same day
Billing
contract per task, invoiced through Useme
Where
Szczecin, Poland. Remote, on site near the German border

The message lands in my mailbox and nowhere else. No newsletter.