Questions and answers

A project team built around the scope, led by the founder. Jakub Zając is responsible for technical direction and delivery quality: he agrees the scope with you and stays your contact for the decisions that follow. He leads part of the work himself, and where the scope calls for additional expertise we bring in trusted specialists. On every project we say plainly who does which part. There are no account managers and no intermediaries, so nothing is lost in handovers and decisions take days, not weeks.

We maintain a focused delivery structure and expand project teams with trusted specialists when the scope requires it — which is why the work ranges from single deployments to systems maintained for years. Scope, schedule and who is on the team are agreed before we start, and larger work is split into stages approved separately. If a project needs a scale we cannot deliver at the quality we promise, we say so at the estimate stage, not halfway through.

Everything is designed from day one so that dependency doesn't exist: the repository, the documentation and the access are kept so they can be handed over, and the contract settles before work starts which rights pass to you. We build systems so any competent team can take them over — so the system outlives any vendor, including us.

We do both. Software projects, consulting and IT support for companies run remotely for clients across Poland. On-site work covers Bydgoszcz and the surrounding area — mostly computer service and jobs that genuinely require being at the hardware or the network in person.

We work in Polish and English. We run meetings and write documentation and correspondence in either language, which matters for international clients and mixed teams.

Yes. We operate a registered business, Usługi informatyczne Jakub Zając, and every service is invoiced. VAT status: VAT-registered.

Honestly: we don't publish a price list, because the gap between a simple website and a transactional system is bigger than the gap between two invoices. What you get instead is a process: a free first conversation, the scope and estimate in writing, and larger work split into stages you approve one by one. You hold the estimate before any decision is made.

With a free, no-obligation conversation about the problem you want solved. We then do a short analysis and come back with specifics: a proposed approach, the scope written down and an estimate. Only then do you decide whether we go ahead.

Yes — for larger scopes we actively recommend it. The first stage ends with a working version you can click through, not a progress presentation. After each stage you decide on the next step, so the budget and the direction of the project stay in your hands throughout.

The transfer of rights to the code, the repository and the documentation, and the handover of access, go into the contract before work starts — that is where we settle what passes to you and when. After launch you can stay with us for ongoing care — updates, monitoring, further development — or hand the system to your own team. We run projects so that both paths remain realistic at any point.

Yes — it is a common starting point. We begin with an audit of the code, infrastructure and access, which gives you an honest picture of the project: what works, what is a risk, and what needs fixing first. You decide on further work only once you have that picture.

We treat testing as part of the job, not a separate line on the invoice. Code is covered with automated tests, critical paths are also verified by hand, and every change goes through CI before it reaches production. The founder's QA practice helps here: we look at our own code the way a tester looks at someone else's.

It is ongoing IT support in which we take on everything an in-house IT department would: a helpdesk for staff, Microsoft 365 administration, the network, servers and backups, security and monitoring. The difference is that instead of salaried positions there is one agreement with the scope and response times written into the SLA, and one partner who knows your company answers for the whole. We work remotely with companies across Poland, and on site in and around Bydgoszcz.

Companies of 5 to 100 people with no IT department of their own, where computers, accounts and the network are needed for work every day: offices, law firms, clinics, service, trading and manufacturing businesses. They usually come to us when "the person who knows computers" can no longer keep up or leaves, when Microsoft 365 has grown beyond anyone's control, or when a client or an insurer starts asking questions about security.

One salaried person has one specialism, holidays and a notice period — while a company of 5 to 100 people needs expertise from several areas at once, only not full time. Under ongoing support you get the helpdesk, Microsoft 365 administration, the network, backups and security in one agreement, with documentation that stays in the company and continuity that does not depend on someone's holiday. When the company grows into its own IT department, we hand it a tidy environment — and we will say plainly when that moment has come.

Support is billed as a fixed monthly fee, agreed before the start and written into the agreement. The amount depends on the number of users and devices, the complexity of the environment (servers, branches, industry systems), the plan and the SLA response times you choose, and how much of the work is to happen on site. We do not publish a price list, because each of these factors changes the scope — after the free audit you get the scope and the fee in writing.

We start with an audit: a review of hardware, accounts, network, backups and security, and a conversation about what hurts the company most. Then we take over access and document the whole environment — inventory, passwords in a vault, a network diagram, the licence list — so that no information stays in someone's head. In parallel we open the helpdesk for staff and switch on monitoring, and the urgent items from the audit, usually MFA and backups, are dealt with first. At the end you get a summary of the state of IT and a plan for the months ahead.

Every request is given one of three severity levels — critical, high or standard — and for each of them the SLA sets a response window that depends on the plan you choose. Those windows are a contractual commitment, not a best-effort promise. Current standard terms: a response within 3 working days for standard requests and within 12 hours for urgent ones; on higher-priority plans the windows are set individually in the agreement. The channel for urgent reports is available 24/7. Requests outside a standing agreement are handled as availability allows, and we always say plainly when we can realistically get to a problem.

The basics that stop the typical incidents in small companies: multi-factor authentication on every account, endpoint protection and patching, backups tested by restoring them, tidy access revoked on the day someone leaves, and hardening of Microsoft 365 and the network. The free audit we start with is a configuration and risk review, not a penetration test — if your industry requires one, we will help you scope it and choose a specialised firm.

Yes — and it is what sets us apart from a typical support provider. We are an engineering firm: we build web and mobile applications, internal systems, integrations and automations, including for the companies whose IT we run day to day. In practice this means that when, while supporting you, we see data retyped by hand between systems or a process run in a spreadsheet, we can propose and build a solution — and when such an investment would not pay for itself, we say so.

No. Most issues can be diagnosed and fixed remotely over a secure connection, which is faster and cheaper for you. We start remotely and come on-site when the job genuinely calls for it: hardware failures, network work, physical installs.

Both. We start remotely because it is faster for you: most tickets — email, accounts, permissions, software, configuration — can be resolved over a secure connection without waiting for anyone to drive over. We come to your office in Bydgoszcz where remote work cannot do the job: hardware failures, work on the network, setting up workstations, servers and NAS devices. How often we visit on a regular basis is agreed in the contract — some companies want a fixed day each month, others only need a visit when something calls for one.

Calmly, and without putting them on the spot — in the first weeks they are usually our most valuable source of knowledge. During the audit we write down what exists and where: administrator accounts, the router and Microsoft 365 passwords, supplier contracts, licences, where the backups live. Then we move the access into a password vault and document the environment. That person stops being “the one who does computers” and goes back to their actual job, and the company stops depending on one person's memory.

You get everything that is yours: the environment documentation, the inventory, the administrator passwords and the access. Microsoft 365 accounts, domains and licences are registered to your company from the start, not to us — we do not build dependency on something sitting in our name. The notice period is agreed in the contract before we start, and we propose one that does not turn leaving into a penalty. If you move to another provider or to an in-house IT person, we hand the environment over to them normally, in a conversation.

Yes, provided the handover is planned rather than sudden. We start with the audit while the previous contract is still running, agree a date for transferring access, and only switch the ticket channel and the monitoring once we have it. We turn nothing off before we have confirmed our own access to everything that matters. The most common problem in a change like this is that the client does not hold the administrator passwords — the earlier we check that, the fewer surprises there are.

Usually from five people upwards, but the number of workstations is a worse measure than the question of what a day when nobody can work costs you. An eight-person accounting office in April loses more than a thirty-person services company in July. If after a conversation we conclude that an ongoing contract would not pay for itself, we will say so — and offer help on demand instead of a monthly fee.

Administering the environment requires administrative permissions, not access to the contents of your documents — and we grant ourselves only the permissions a given task actually needs. Before the work starts we sign a data-processing agreement and a confidentiality undertaking. Administrative access is issued by name and documented, so it is visible at any point who used it and what for.

We are responsible for keeping it running: the server or workstation it sits on, the database, the access, the backups, the updates and the network connection. We do not replace the software vendor and we do not pretend to know every industry system on the market. What we do take over is the contact with its technical support, so that your bookkeeper is not the one reading out an error message down the phone. In the audit we check whether such a system is covered by backups at all — surprisingly often it is not.

The urgent-ticket channel is available continuously, but how much work happens outside business hours depends on the plan and on what we wrote into the SLA — the IT Critical plan covers out-of-hours support within an agreed scope. We do not promise in an offer what cannot be written into a contract. If your company works shifts or on Saturdays, say so on the first call: it changes both the scope and the price.

We advise on what to buy and prepare a specification against your real needs, so that a five-thousand-złoty laptop does not end up with someone who works in a single spreadsheet. You can buy the hardware yourselves — and it is often cheaper that way. If you would rather we handled the purchase, we say plainly on what terms we do it. We never recommend hardware because somebody pays us to, and we have no reason to talk you into replacing something that still works.

You have one standing contact for the cooperation and one ticket channel — you are not calling a different person each time and explaining your environment from scratch. Jakub Zając, the firm's founder, is responsible for delivery, and for work that needs a particular specialisation we bring in trusted specialists for that task. We do not build the impression of a larger organisation than we are: this is an engineering firm working at this scale on purpose, with documentation kept so that continuity does not depend on one person's memory.

Yes. On-site work covers Bydgoszcz and the surrounding area; remote work covers the whole of Poland, wherever you are. For a company further from Bydgoszcz we establish before signing how often you genuinely need someone on site and whether we can provide it. We would rather say “we cannot drive out every week” at the start than have to explain it later.

For the fact that nothing broke. In the background there are updates, monitoring, permission reviews, backup checks and restore tests — work nobody sees until it is missing. On top of that comes readiness: a critical ticket takes priority because there is a contract, not because somebody happens to have a free afternoon. Every month you get a summary of what was done, so you do not have to take it on trust.

Because it is how we win clients, and we would rather say so plainly. Before we can propose a scope for ongoing support we have to see what you actually run, so we do that at the start, with no invoice and no charge added later. You are the one who gains: the scope in our offer rests on what stands in your office, not on what usually stands in a company your size. The review has a beginning and an end — it does not roll into a service and there is nothing to cancel.

We agree the scope of access before the review starts and keep it to a minimum; wherever possible we work with read-only permissions. We need to look into the Microsoft 365 or Google Workspace panel, the router settings, the backup console and a few typical workstations — usually together with the person who knows where your administrator passwords are kept. At this stage we establish which accounts and passwords exist and where they are held; moving them into a password vault belongs to the handover after a contract is signed, not to the review. Any access created for the audit can be revoked the moment we finish.

It stays between us. What we see in your configuration is not discussed with anyone outside — including your current provider, unless you ask us to — and is never shown anywhere as an example without your agreement. We can sign a confidentiality undertaking before the review; you only have to say so. The notes we take exist solely to write the summary, and if you decide against working with us and want them deleted, we delete them. The summary itself is yours: show it to anyone, including a firm that wants to compare itself with us.

Because every finding is written so that it can be checked. We do not write “security is weak”; we write what we actually saw: this administrator account has no owner, this licence is still being paid for someone who no longer works for you, this router is running on its factory settings. Your current IT person, or any other firm, can verify it — the summary has to hold up even when someone is checking it against us. Where a recommendation needs no agreement with us, we say so: you can do it yourselves, or hand it to whoever looks after your IT today.

The request channel is available 24/7, and every call-out across Bydgoszcz and the Kuyavian-Pomeranian Voivodeship is confirmed individually — get in touch and we will find a time that works.

Get in touch straight away and briefly describe what is happening. The channel for urgent reports is available 24/7. We will tell you plainly whether and how fast we can help — an honest answer beats a deadline that cannot be kept. The scope and terms of an urgent call-out are always agreed before work starts.

Yes — diagnosis first, decision second. Once we have examined the machine, you learn what is wrong, what the repair will cost and whether it is worth doing at all; if replacing the machine is the better deal, we will say so. Paid work starts only after your go-ahead.

We treat your data as confidential: we only look where the repair requires and never copy anything for our own use. Computer service is handled personally by the firm's founder, Jakub Zając. Before touching the disk or the operating system we always discuss a backup — if you do not have one, we can make one before work begins.