Ryszard Sandak
👋 Hi, I'm Ryszard.

I build the systems behind small businesses.

The automation, integrations, and internal tools that have to actually work. You talk to me — the person who designs it, writes it, and ships it — start to finish.

Open for a couple of projects in Q3 2026

I run a one-person engineering practice. No team behind a curtain, no account manager, no "we" — when you hire me, you get me, and I stay on the project from the first sketch to the server it runs on.

I especially like working with small businesses and small teams — people who are great at their own thing and just need someone technical they can trust. I keep the scope tight, build the thing, and hand it over working — source, docs, and all.

Tools I reach for most
  • React
  • Next.js
  • TypeScript
  • Node.js
  • Python
  • PostgreSQL
  • Supabase
  • Tailwind
  • Docker
  • Cloudflare
  • n8n
  • Telegram
  • Gemini
  • OpenAI
  • Ollama
  • Linux
What I do

The problem picks the tools — not the other way around.

01

Connect your tools

integrationsn8nwebhooksscheduled jobsTelegram / Discord bots

Your data lives in five places and someone re-types it by hand. I wire your apps, APIs, and databases into one pipeline that just runs.

02

Put your data to work with AI

LLM extractionRAG over your docsGemini / OpenAI-compatibleself-hosted Ollama

Pull the fields out of documents and messages, summarise, translate, route. Real AI in your real workflow — not a chatbot bolted on the side.

03

Build the tool you keep doing by hand

React + Next.jsPostgres / Supabaseauthdashboardsadmin panels

That spreadsheet that's quietly become a full-time job. I turn it into a proper internal app your team can actually use.

04

Take it all the way to running

DockerCloudflare Tunnelself-hosted handoverfull docs

Idea → built → deployed → live. I handle the whole stack, from the interface to the box it runs on, and document it so it's yours to keep.

How I think

A few things I believe about building software.

The smallest version first.

I'd rather get a small, working version into your hands early — something you can actually use and react to — than disappear for months chasing perfect.

You should own everything.

Source, docs, deployment — all handed over. No vendor lock, no "managed" hostage situation.

AI is plumbing, not magic.

A model on its own is just a demo. What makes AI actually useful is the unglamorous plumbing around it — fitting it to your real data and workflow — and that's the part I build.

I'll tell you when not to build.

If something off-the-shelf already covers what you need, I'll say so — and wire it in rather than rebuild it. When the fit isn't there, or it needs to be your own, that's when building from scratch earns its keep.

Work

Shipped, not slides.

See all work

A few things I've built. Every write-up follows the same shape: the problem, the constraints, the hard part, the outcome.

A real vision system built under tight constraints. I'll walk you through the process and the outcome — the client's specifics stay private.

Built end-to-end: data capture, the model, and the pipeline around it that turns it into something usable. I can talk through the approach and what it achieved on a call — the client and the specifics stay private.

See it on the work page
Anonymised·patent-adjacent

A self-hosted product I built alone. The genuinely hard part was the transit routing — OTP over messy real-world GTFS feeds.

BudgetMyUni screenshot

A full web app — auth, a preferences editor, an interactive map, and a dashboard that computes commute time and monthly transport cost. The hard part: Slovenia publishes no open transit data, so I built a custom GTFS feed for the Koper–Piran line to drive the routing.

Read the full write-up
Next.js·Postgres·self-hosted

Little products for the same people I work with — small enough to ship, real enough to use.

Small, focused tools for the people I work with — the kind of thing that's quicker to build right once than to keep doing by hand. More write-ups landing here soon.

See it on the work page
Coming soon
How we'd work together

Scope it, build it, ship it, then iterate.

(01)

Scope

We agree on the smallest version that proves the idea — fixed scope, a clear definition of done.

(02)

Build

I build it end-to-end with you in the loop, not behind a wall. You'll see it take shape.

(03)

Ship

A working version you can test, demo, or pitch. Hosted for you or set up to self-host — documented, and yours.

(04)

Iterate

We refine on real feedback. A follow-up, a retainer, or a clean handoff — whatever you need.

Get in touch

Tell me what you're trying to build.

A few sentences is enough to start. I read every message myself and reply within 3 business days.