Skip to content
services and pricing

What I can help with.

I work solo, so you talk to me from the first call through to launch. No account managers, no brief passed between three people — and every service tells you upfront roughly what it costs and how long it takes.

01

Web development.

A website that brings you customers, not bills. Fast on a phone, cheap to run, no monthly fee for an admin panel — and you change the prices and text yourself.

indicative price
from €1,000
typical timeline
2–6 weeks

These are entry points, not a quote. You get the exact price after the first call — and from that moment it does not move unless the scope does. I am not registered for VAT — the prices shown are final.

enquire about this
what's included
  • Company sites and presentations
  • Internal tools and web apps
  • Rebuilding an old site that no longer copes
  • Launch, visitor numbers and a guide to editing it yourself

Prices, opening hours, a new item on the list — you change those yourself, without waiting for me. The text is not locked inside an admin panel you pay for every month: it sits in plain files where you rewrite a line, save, and the site updates itself. The guide for doing that comes with the handover, and it is written for a person, not a programmer. Bigger changes — a new section, a different structure — are my job, but for the everyday edits you do not depend on me.

I build the site so that somebody else can take it over in two years: clean code, no closed platform, and no plugins that stop working after a year with nobody left to fix them.

Why it is quick: the page is finished in advance and the servers keep it ready close to the visitor, so nothing has to be assembled each time someone opens it. It appears almost instantly even on a weak signal, and hosting costs a couple of euros a month rather than hundreds. This site, the one you are reading, is built exactly that way.

What you get

Design and delivery, not just code. We start with what the site has to do and who it is for, and the structure follows from that. As standard it works on a phone, can be operated with a keyboard and a screen reader, is findable in search (structured data, sitemap, hreflang for multilingual sites) — and you can see how many people come.

On handover everything is yours: the source code, the documentation, every access credential and the way the site gets published. None of it is tied to me — carry on yourself, hand it to somebody else, or keep me on for maintenance.

  • Custom-built
  • Fast on mobile
  • You edit the content
  • No locked platform
02

IT analysis.

Want something built, but the quotes you are getting differ by tens of thousands? I write the precise brief you can build from, compare quotes against, and use to tell when it is actually finished.

indicative price
from €50 / h
typical timeline
scope-dependent

These are entry points, not a quote. You get the exact price after the first call — and from that moment it does not move unless the scope does. I am not registered for VAT — the prices shown are final.

enquire about this
what's included
  • Requirements gathering and refinement
  • Process and data models (UML, BPMN)
  • Functional specs and acceptance criteria
  • Impact analysis before a production change

I have spent six years as an analyst in banking. Most projects that stall do not stall on code — they stall because the person asking and the person building picture two different things behind the same sentence. My job is to find that gap before anyone pays for it.

How it runs

I start with the people who actually operate the process, not only the person who commissioned the project. Out of that comes a model of the current state, a list of the real pain points, and a proposal for the target state. Only then do I write the specification — with diagrams, a data dictionary, and acceptance criteria that can be tested.

I can also work inside an existing team as the project’s analyst. I know how change gets pushed through a corporate, and I will not hand you a proposal that dies in security review.

The analysis also stands on its own, with no development from me attached to it. The document you take out to vendors is the same thing that lets you compare what comes back — because everyone is finally pricing the same scope.

  • Requirements
  • Process models
  • Functional specs
  • Impact analysis
03

Integrations and APIs.

Your shop, stock and accounting finally talking to each other, so nobody retypes data by hand. Design, documentation, tests — and above all, clarity on what happens when one side goes down.

indicative price
from €50 / h
typical timeline
1–8 weeks

These are entry points, not a quote. You get the exact price after the first call — and from that moment it does not move unless the scope does. I am not registered for VAT — the prices shown are final.

enquire about this
what's included
  • REST API design and documentation
  • Internal and vendor system integrations
  • Data mapping and migrations
  • Failure paths, retries and monitoring

Integrations are where projects break most often. Two sides agree to “just send it over the API”, nobody writes down what an empty field means, and three months later it is a production incident.

I work the other way round. The contract comes first — an OpenAPI definition, request and response examples, an explicit list of error states. Implementation follows. Both sides then look at the same thing, and testing can start before anything is finished.

Operations are part of it

The design assumes the other side will be unavailable sometimes. Idempotency, retries, queueing and alerting are all in scope — so your partner’s outage is not your system’s outage.

Documentation is written alongside the interface, not after it. Whoever takes the integration over from me does not have to reverse-engineer it out of the code.

  • Systems connected
  • Data migration
  • Failure handling
  • Documented interfaces
04

AI automation.

Does someone in your company retype numbers from e-mails and invoices into a system every week? A machine can take that over — wired into your real data, not a demo that only works on stage.

indicative price
from €1,400
typical timeline
2–8 weeks

These are entry points, not a quote. You get the exact price after the first call — and from that moment it does not move unless the scope does. I am not registered for VAT — the prices shown are final.

enquire about this
what's included
  • Manual work with documents and e-mail taken off people
  • Documentation and reports that write themselves
  • An honest read on where AI pays off and where it is pointless
  • Wiring into the programs you already run — safely

Most of what people do inside a company is not thinking — it is moving figures from one place to another. Somebody retypes orders out of e-mails, somebody hunts through contracts for a clause, somebody assembles a Friday report out of five exports. That is the kind of brief I enjoy most: take something a person does by hand every week and hand it to a machine.

Last year I built one of those at Raiffeisenbank — it helps colleagues with API documentation work. It earned me a bonus, and it is now being wired into a project an external vendor runs there.

First I ask whether it is worth it

Not every job wants AI. If the task has clear rules I will write an ordinary program — cheaper to run, and it never invents anything. AI belongs where the rules cannot be written down in advance: invoices that all look different, customer e-mails, contract text.

For the tool to be of any use it has to reach into the systems you already run. That is what MCP is for: a standard way to expose specific data and specific actions to a model, rather than the whole system.

When we do go ahead, I handle the boring part too: where the data flows, what gets logged, how output is verified, and what happens when the model gets it wrong. Without that, an AI tool is just risk with a nice demo.

  • No more retyping
  • Reports that write themselves
  • Wired to your systems
  • Verifiable output
how I work

Four steps, every time.

I do not start with code. I start by working out what the thing actually has to do and why — because most projects do not stall on the technology, but on everyone picturing something different behind the same sentence.

  1. A call and a scope

    We sit down and go through what you need and why. I also talk to the people who will actually use it. Out of that comes a scope, a price and a date — not an estimate that triples in a month.

  2. Design and preparation

    I write down exactly what the thing has to do, where the data comes from and what happens when something fails. For a site that includes page structure and visual design. Before the first line of code, we both know what is being built — and how we will know it is finished.

  3. Build in slices

    I deliver continuously, not once at the end. You see the work in progress and can steer it while steering is still cheap — not at handover, when a change is expensive.

  4. Launch and hand-over

    I put it live, measure it, document it. You get the source code, every access credential and a guide to running and editing it — written for a person, not for a programmer. I can stay on for maintenance, but it is not compulsory.

common questions

Before you write.

Seven things almost everyone asks. If yours is not here, write — the answer comes as fast as the quote does.

What will it cost?

A website from €1,000 and AI automation from €1,400 — both quoted as a single total, not an hourly rate. IT analysis and connecting systems from €50 per hour, because their scope keeps being refined as the work goes. Either way these are entry points: the exact number comes after the first call and does not move from there unless the scope does.

How long does it take?

A smaller site takes two to six weeks, connecting systems one to eight, an AI tool two to eight. I confirm the date after the first call rather than guessing in a proposal — and I deliver in slices, so you see a usable version well before the end.

You work alone. What if you get ill or move on?

Yes, I work solo — which is why you talk directly to the person building it. The source code, the documentation and every credential are with you as the work happens, not only at the end, so anyone can pick the project up. On larger jobs I say upfront where I bring in a specialist.

How does working together actually go?

A no-obligation call, then preparation and a fixed quote, then delivery in slices you can watch as it happens, then launch, documentation and hand-over. The full version is in the How I work section.

Can you take over an unfinished or inherited project?

Yes, and it comes up more often than you would think. I start by going through what exists and writing down what is worth repairing and what is cheaper to rewrite. That analysis is billed separately, but it tells you the truth before you spend on development.

How do invoicing and contracts work?

I trade as a Czech sole trader (reg. no. 08946043) and I am not registered for VAT, so the prices quoted are final. I invoice in CZK and bill larger engagements against milestones rather than in one lump at the end. Scope, price and date are in writing before work starts.

Do you do maintenance afterwards? And does this work in English?

I do maintenance if you want it — either a retainer covering small changes and monitoring, or ad hoc as needed. It is not compulsory: turn it down and you pay me nothing monthly, and the site keeps running, because it is built so anyone can take it over. I run projects in Czech and English, usually remotely, and meeting in Prague is no problem.

work with me

Got a project that is not moving?.

Send me a few sentences about what you are solving. You get an answer within one working day — and if I am not the right person, I will say so straight away and ideally point you at who is.

home