You can start with one specific problem.

A long-term contract isn’t a condition for the first step. Just describe the situation and its impact; I’ll clarify any further scope, risks and billing before I start changing your environment.

Indicative prices and billing

What happens next

You don’t need to prepare a technical analysis. Write down the facts you know right now; we’ll clarify anything missing before proposing the next step.

I’ll go through your description and ask for clarification if needed. Based on the actual situation, I’ll recommend a diagnosis, a standalone job, an audit, long-term management or scoping a software project.

A one-off job has six checkpoints.

This order protects both your operations and your decision-making. If the situation can’t be assessed safely from the information available, the first standalone deliverable may be a diagnosis.

  1. 01

    Understand the situation

    I clarify the problem, the expected result, the operational impact and what must not be interrupted.

  2. 02

    Verify the actual state

    I check the environment, available access, dependencies and the likely cause. Anything unclear I verify first.

  3. 03

    Agree the scope

    I separate the necessary work, optional improvements and open risks. I confirm the price or how it will be billed, and the cooperation needed from you. Domains, accounts and data stay under the client’s control.

  4. 04

    Prepare the change

    For changes with a potential impact, I define how they will be verified and, depending on the situation, how to roll back to the previous state.

  5. 05

    Carry out and verify

    I make the change within the agreed scope and check that the expected result has been achieved.

  6. 06

    Document and hand over

    I explain the changes made and hand over the necessary documentation and recommendations for continued safe operation.

A standalone job can be the final result. An audit, fixing another area or long-term management follows only under a separate agreement.

Let’s talk Find the right service

Long-term management and development work differently.

Both can follow on from the initial assessment, but they differ in the type of responsibility, how the work proceeds and what the handover looks like.

Long-term IT management

Ongoing responsibility for an agreed part of your operations

What IT management includes

It starts with an inventory of devices, services, accounts, access, backups and dependencies, from which we jointly define responsibilities and priorities. Within the agreed scope, I then continuously handle monitoring, updates, access, backups, incidents and planned changes.

Routine requests and incidents follow an agreed priority; larger changes have a procedure and verification described in advance. Documentation, configuration, changes and the division of responsibility don’t stay only in one person’s head.

Software development

Delivering a solution for a specific business process

What development includes

First we clarify the workflow, the result you need, the data required, the users and the connections to other systems. The scope of the solution comes from the real task - before work starts, it’s clear what is to be delivered and how the work is billed.

Depending on the brief, implementation, integration, testing and safe deployment follow. I hand over a working, maintainable result; monitoring, maintenance or further development continue only if they are part of the agreement.

Practical questions before the first contact.

What needs deciding straight away, what only after a diagnosis, and where working together creates no automatic commitment.

What happens after I send an enquiry?

I go through the system you describe, the result you need and the impact of the problem. If anything important is missing, I ask for clarification and suggest a suitable first step.

Do I have to sign a long-term contract?

No. Our cooperation can end with a diagnosis or a one-off job. Long-term management is agreed separately, based on the situation found and your company’s needs.

When are scope and price settled?

I confirm the specific scope, price or method of billing before work starts. If a paid diagnosis is needed first, I treat it as a separate step.

Do I need to know the technical cause of the problem?

No. For a first contact it’s more important to describe what you use, what is happening, who it affects and what must not be interrupted.

Can you take over just one part of our IT?

Yes. The scope can cover your whole environment or just servers, the network, backups, monitoring or another clearly defined area.

How quickly can you get to the problem?

For a new client it depends on my current availability, the urgency, the scope and the access required. I’ll tell you a realistic date in advance; a guaranteed service level applies only if it has been explicitly agreed.

Can we work together remotely?

Yes, provided the work can be done safely at a distance. I work on site across the Olomouc Region and the surrounding area; I provide remote services throughout the Czech Republic.

What do you need solved?

Just briefly describe what you need. You do not need to choose the technology or solution in advance.

What you need
A new website, an application, IT management or help with a problem
What should change
What should start working, get faster or become simpler
Timing
When you need it and what is urgent
Email
AreaThe Olomouc Region and surroundings, remotely anywhere in the Czech Republic
AvailabilityMon–Fri 9:00–17:00

Tell me what you need help with

required fields
The facts you know right now are enough.0 / 2000