Open to new projects · Prague

I build the software your business actually runs on.

Hey there —

Let me guess how things work today. Jobs live in a spreadsheet. The schedule lives in a WhatsApp group. Hours are on paper, and everything else is in somebody’s head. It sort of works — until a crew shows up at the wrong address, or it’s the end of the month and nobody can say what to invoice.

That’s exactly the kind of problem I like solving. I’m Dima, a freelance developer based in Prague. I design and build custom operations apps, internal tools and AI automations for small and growing companies — software that fits the way your team already works, and that people genuinely use every day.

No agency layers, no hand-offs. You talk to the person writing the code, from the first call to launch and long after.

Thanks for stopping by,

Dima

Tell me about your project See what I’ve built

Selected work

Real software, in use every day.

Both projects below are internal tools for real businesses, and I keep my clients’ names private — so the screens are illustrations, not screenshots. I’m happy to walk you through the real thing on a call.

In production · Client kept confidential

Operations app for a cleaning company

For a Prague cleaning company looking after offices, residential buildings and homes across the city.

The problem
A cleaning business lives and dies by its schedule: lots of client sites, recurring jobs, a team spread across the city and plans that change every day. Spreadsheets and chat threads stop scaling fast.
What I built
A web app the company uses to run its operations day to day — keeping jobs, people and places in one place, with a clear overview for the office and a simple view for the team on the go.
  • Responsive, app-like interface that works on a phone as well as on a desktop
  • Multilingual UI for an international team
  • Fast single-page app, self-hosted behind Caddy
  • React
  • Material UI
  • Zustand
  • i18next
  • Vite
  • Caddy

In production · Client kept confidential

Operations app for a construction company

For a Prague construction company doing house and flat renovations and outdoor building work.

The problem
Construction means many jobs running in parallel, crews moving between sites, and a lot of important information that tends to live on paper or in someone’s phone.
What I built
A private, login-protected web system for the whole team — one place where everyone signs in to see and manage their work, instead of chasing it across paper and messages.
  • Personal area for every team member, behind a secure login
  • Server-rendered and lightweight — quick even on a weak connection on site
  • Runs on the client’s own server, no per-seat SaaS fees
  • PHP
  • JavaScript
  • Tachyons
  • nginx

Got something similar in mind? Let’s talk about it →

Services

What I can build for you.

One developer, the whole job: planning, design, front end, back end, servers and support. Here’s where I’m most useful.

  • Operations apps & internal tools

    Swap spreadsheets, paper and chat threads for one app built around how your team works — scheduling, jobs, people, clients, hours and reports.

    Good fit: service businesses with teams out in the field.

  • AI automation & assistants

    Put LLMs to work on the boring parts: answering questions from your own documents, sorting email, pulling data out of invoices, drafting reports. Practical, measurable and private.

    Good fit: repetitive office work that eats hours every week.

  • Web apps & MVPs

    Customer portals, dashboards, booking systems and solid first versions of new products — built with React, Angular, Node.js and TypeScript.

    Good fit: founders who need a reliable v1 without a big team.

  • Hosting, DevOps & care

    CI/CD, Docker, cloud or self-hosted setups, backups and monitoring — plus ongoing maintenance and careful modernisation of older apps.

    Good fit: an app that works, but nobody dares to touch.

How I work

Simple process. No surprises.

  1. A free 30-minute call

    You tell me what’s slowing your team down. I ask a lot of questions. No sales pitch, no obligation.

  2. A clear proposal

    Scope, timeline and a fixed price in writing — including what I’d deliberately leave out of version one.

  3. Small, steady releases

    You’ll see a first working version within days, then improvements every few days. Changing your mind is fine — that’s what short cycles are for.

  4. Launch, then look after it

    I deploy it, help your team get comfortable, and stay around for fixes, improvements and new ideas.

working-with-dima.ts 
// what a project with me looks like
const project = await dima.start({ client: "you" });

await project.introCall();      // free, 30 minutes
await project.proposal();       // scope, timeline, price
await project.ship({ every: "few days" });
project.support();              // as long as you need
// press “Run” to see the output

Ways to work together

  • Fixed-price project

    For a well-defined first version or a new feature. Clear scope, clear price, clear finish line.

  • Most popular

    Monthly retainer

    A set number of days each month for improvements, support and new features. Like having a developer on the team — without hiring one.

  • Consulting & audits

    A second pair of eyes on your architecture, your AI plans, or an app that needs rescuing. Billed by the day.

Portrait of Dima Bondarenko
that’s me, Dima

About

Hi, I’m Dima.

I’m a full-stack software engineer with a degree in Computer Science and years of experience building cloud-based software in big tech engineering teams.

Now I bring that same engineering discipline to smaller companies, without the enterprise overhead. I like understanding how a business really works before writing a line of code, and I care a lot about the people who’ll use what I build every day.

I live in Prague, work in English and Czech, and I’m always happy to meet in person if you’re nearby.

Things I believe

  • Boring, proven technology is a feature. Your business shouldn’t depend on this month’s hype.
  • If your team doesn’t enjoy using it, it isn’t finished.
  • You own everything. The code, the data, the servers. No lock-in, ever.
  • Small, frequent releases beat big-bang launches.
  • AI is a tool, not a strategy. I’ll use it where it pays off — and tell you when it doesn’t.

Toolbox

I build with AI coding agents. They take care of the routine work, while I do the thinking, the architecture and the code review — that’s how projects ship in days, not months.

  • OpenAI Codex
  • Claude Code
  • GitHub Copilot

FAQ

Good questions, straight answers.

How much does a project cost?

It depends on the scope, so I don’t publish a price list. After our first call you’ll get a fixed quote in writing — no open-ended hourly billing. If the budget is tight, I’ll suggest a smaller first version that still pays for itself.

How long will it take?

Usually just a few days. I build with AI coding agents that handle most of the routine work, so a focused internal tool or MVP can be up and running within days, not months. Bigger systems then grow from there in small, steady releases.

Do you only work with companies in Prague?

Not at all. I work remotely with clients across Europe and beyond, in English or Czech. If you’re in or around Prague, we can also meet in person.

Who owns the code?

You do. The code, the repository, the domain and the servers belong to you, and everything is documented so another developer could pick it up. No lock-in.

Can you take over an existing app?

Yes. I’ll review it, fix whatever is urgent, and then modernise it step by step — no risky “let’s rewrite everything” projects unless it truly makes sense.

What happens after launch?

Most clients keep me on a small monthly retainer for support and improvements. If you’d rather run it in-house, I’ll hand over documentation and help your team get up to speed.

Contact

Write me a letter.

Fill in the blanks and hit send — it opens your email app with everything ready to go. I usually reply within one working day.

Hi Dima,

my name is from .

We’re looking for help with .

Ideally we’d start .

You can reach me at .