Skip to content
JZ Technology

Bydgoszcz and the surrounding area · ongoing IT support

Managed IT for companies in Bydgoszcz. Your external IT department.

We take over the whole of your company's IT: help for your people, Microsoft 365, the network, computers, servers, backups, security and monitoring. One monthly agreement, one team accountable for all of it, and response times written into an SLA. Most matters we close remotely, and when a problem needs hands on the hardware we drive to your office in Bydgoszcz.

The call costs nothing and commits you to nothing. It ends with a straight answer on whether and how we can help.

Scope
Helpdesk · Microsoft 365 · network · computers and servers · backup · security · monitoring
How we work together
A monthly agreement with a fixed fee and response times written into an SLA
On-site visits
Bydgoszcz and the surrounding area — office, shop, practice, warehouse. Registered at: ks. Jana Konopczyńskiego 1, 85-309 Bydgoszcz

or call us: +48 573 021 012

01Why companies call us

When a company starts looking for someone to run its IT

Almost nobody goes looking for “IT outsourcing” because they read an article about it. They go looking because something on this list happened.

02Bydgoszcz · ongoing support

What changes in a company that moves to ongoing IT support

Fast response to incidents
Most requests are resolved remotely; when a problem requires being at the hardware, we come on site in and around Bydgoszcz, within the visit scope set in your agreement. Response times for each level of urgency are written into your SLA, not left to goodwill.
Proactive monitoring and maintenance
Updates, backups and check-ups run on a schedule, not after the damage. Monitoring tells us about most problems before your staff notice them.
One dedicated IT partner
You talk to someone who knows your environment, your accounts and your history, not a different technician every time. No ticket lottery, no explaining everything from scratch.
Documented infrastructure
We keep an inventory of devices, accounts, licences, the network and access. The company is not hostage to anyone's memory — not ours, and not a departing employee's.
A predictable monthly arrangement
The scope and a fixed monthly fee are agreed up front, in writing. Everyday questions from staff do not turn into hourly invoices, and you know in advance what IT costs each month.
Cybersecurity and backups
Multi-factor authentication, endpoint protection and backups we test by actually restoring them — because a backup nobody has ever restored is just hope.

We also build software, integrations and automation — so when we notice during support that someone retypes the same data between two systems every day, we can fix it rather than just note it down. See software and automation

Who it is for

Managed IT support works best for companies that do not want to hire their own IT person, yet cannot afford to have work stop because of a computer, the mail or the network.

03What we cover

What we are responsible for in your company

Six areas and one team accountable for them. No being passed between the internet provider, the printer service and “the computer guy” — if something does not work, the ticket comes to us and we are the ones who work out whose problem it is.

04How we work

Remote where it works, on site when it genuinely takes hands

Remote support

Most tickets — a mail problem, a locked account, an application that stopped starting, permissions on a folder — we resolve over a secure remote connection, without anyone waiting for a car to arrive. You can see on screen what we are doing. Tickets come through one channel, not to the private phone of whoever picked up last time.

On site in Bydgoszcz

We come out where remote work cannot reach: hardware failures, work on the network and cabling, replacing or setting up workstations, fitting out a new office, a server or NAS that has to be touched. We cover Bydgoszcz and the surrounding area — offices, shops, practices, warehouses and production halls. For addresses further out we confirm travel when the agreement is drawn up, not after the fact.

What we promise, and what we do not

The urgent-ticket channel is available 24/7, but that is the availability of the channel, not a claim that every matter is dealt with instantly. Companies on an ongoing agreement have response times written into the SLA — depending on how serious the ticket is and which plan they are on. We always say plainly when we will realistically get to a problem, instead of quoting a deadline we will not meet.

Need help right now, with no agreement in place? Emergency IT support in Bydgoszcz

The business is registered in Bydgoszcz: Usługi informatyczne Jakub Zając, ks. Jana Konopczyńskiego 1, 85-309 Bydgoszcz, VAT ID 9532802271 — VAT-registered. We invoice from a Polish VAT number.

05The SLA

What happens when something stops working

Not every failure is the same. The whole company stopped, one person blocked, and “the printer is behaving oddly” are three different matters with three different priorities. Below is exactly what goes into the agreement: how we classify a ticket, what we do first, and how quickly we respond.

Request levels

  1. Critical

    The company or a key department cannot work, or there is a real risk of losing data.

    Examples

    • Email or Microsoft 365 is down for everyone
    • A server, network or internet failure across the office
    • A suspected break-in or ransomware

    What happens first

    The request takes precedence over everything else. We start by securing data and restoring work, on site if needed, and keep you informed until the matter is closed.

  2. High

    One person or one process cannot work, but the rest of the company runs.

    Examples

    • A key employee's computer will not start
    • The printer that dispatch depends on is out
    • A locked account or no access to an important file

    What happens first

    We handle it ahead of standard requests, usually remotely. If the fix takes time, we find a workaround so the person can work before the problem is resolved for good.

  3. Standard

    The matter is a nuisance or needs planning, but nobody is stopped by it.

    Examples

    • A new account or workstation for an employee
    • Installing a program, changing permissions, a question about licences
    • Minor faults with a workaround

    What happens first

    Handled in order and at a time agreed with you; anything disruptive is scheduled outside your busiest hours.

Current contract terms

  • Standard request: we respond within 3 working days.
  • Urgent request: we respond within 12 hours.

These are the current standard contract terms for ongoing support — a contractual commitment, not a best-effort promise. The IT Business and IT Critical plans receive individually agreed, shorter response windows written into the SLA.

06Getting started

How we start: a conversation, an audit, a handover

Three steps. The first two are free and commit you to nothing, and after them you know more about your own IT than you did before — whether or not we sign anything.

  1. A conversation — 30–45 minutes, free

    We ask what gets in the way most today, how many computers and people there are, what you already run (Microsoft 365, a server, a NAS, industry software) and who looks after it now. Remotely or at your office in Bydgoszcz — whichever you prefer. No slide deck, no pitch.

    You get: a straight answer on whether and how we can help, and what happens next.

  2. A free audit — a few hours of work, mostly remote

    We go through the computers, accounts and permissions, Microsoft 365, the network, backups and security. It is a review of configuration and risk, not surveillance of your staff and not a penetration test. You get the findings in writing, ordered by impact on the business — including if you decide not to work with us.

    You get: an honest picture of the state of your IT and a proposed order of work.

  3. The agreement, the handover and the first weeks

    We propose a scope, a plan and a fixed monthly fee; the SLA records ticket severities and response times. Once signed, we take administrative access and passwords into a vault, inventory the devices, licences, network and suppliers, switch on monitoring and backups, and open one ticket channel for your staff. The urgent findings from the audit — usually multi-factor authentication and backups — are dealt with first.

    You get: a documented environment, monitoring that works, and one channel your people report to.

We plan the handover so there is never a day without cover. If another company looks after you today, we agree a date for transferring access and switch nothing off before then.

07Free IT audit

Start with a free infrastructure review

Before we propose a scope and a price, we check how IT works in your company today: computers, mail, the network, backups and access. You receive a written summary with priorities — whether or not you decide to work with us.

  • Backups and recovery

    What is backed up, where and how often — and whether anyone has ever checked that it restores.

  • Microsoft 365 configuration

    Email, sharing and security settings, licences, and what is still running on the defaults.

  • Accounts, permissions and MFA

    Who has access to what, who holds administrator rights, and whether accounts are protected by a second factor.

  • Network architecture and firewall

    Network segmentation, router and firewall settings, the guest network, remote access — and whether anyone knows the router password.

  • Endpoint security

    Protection of the computers, disk encryption, operating system updates, and who works from an administrator account day to day.

  • Software and licensing

    Outdated or unsupported software, missing or surplus licences, and applications nobody knows are there.

  • Inventory and documentation

    Whether there is a current list of devices, accounts, licences and vendors — and where it is written down how it all works.

  • Onboarding, offboarding and single points of failure

    How staff are onboarded and offboarded, whether former employees still have access, and what happens when one person, one device or one password becomes unavailable.

What you receive after the audit

  • A concise written summary of the risks, ranked by their impact on the business
  • Concrete recommendations: what to change, why, and with what effort
  • A proposed order of work — from what threatens a stoppage to what can wait
  • If you want one — a proposal for ongoing support with the scope and monthly fee

The audit is a configuration and risk review, not a penetration test. It takes a few hours of remote work plus one conversation, and commits you to nothing.

08Support plans

Three support plans — choose a level, not a bundle of hours

We do not sell bundles of hours, because a bundle of hours rewards the supplier whenever something breaks. You pay a fixed monthly fee for an agreed scope. The amount is set after the audit — it depends on the number of users and devices, how complex the environment is, the response times you need and how much of the work has to happen on site.

Compare the full scope of all three plans

09An honest comparison

An in-house IT employee or an external IT department

We get this question on almost every first call, and we answer it the same way whether or not it suits us. Both options make sense — in different companies.

When an in-house IT employee wins

  • They are there every day, know everyone by name and see a problem before anyone reports it. Help at someone's desk “for a second” needs no ticket at all.
  • They learn your industry and your systems more deeply than anyone from outside ever will.
  • They do things that formally are not IT: setting up the meeting room, connecting the projector, helping a new joiner on day one.
  • If there are enough tickets to keep someone busy full time, the cost per ticket can be lower than under an external agreement.
  • With production systems, machinery and infrastructure that needs daily physical presence, being on site is simply a condition of the job.

When an external IT department wins

  • A company of five to a hundred people needs several areas of competence at once — helpdesk, Microsoft 365, networking, servers, security — but none of them full time. One person has one specialisation; the rest they learn on your environment.
  • Holidays, illness and notice periods do not stop IT. One employee is by definition a single point of failure for the whole company.
  • Documentation is a contractual obligation rather than good will. What is known about your IT is written down, not held in one person's head and notebook.
  • The cost is one predictable line. A salary comes with contributions, recruitment, holidays, training, tools and cover — and none of those disappear in a month when nothing breaks.
  • Response times and the escalation path are written into the agreement. With an employee, you are relying on good will.

When we say plainly that hiring is the better answer

Once a company grows past a hundred workstations, runs its own production systems that need someone there daily, or has enough tickets that somebody has to sit on site permanently, an in-house IT department is cheaper and faster. We will say so on the first call rather than sell an agreement you would cancel within a year. A mixed model works too: you hire one person for day-to-day help, and we take on what one person cannot carry — servers, security, backups, cover during holidays. And when you do grow into your own department, we hand it an environment that is ordered and documented, not a mess to unpick.

10Questions and answers

Questions companies in Bydgoszcz ask us

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.

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.

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.

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.

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 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.

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 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.

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.

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.

Let's talk about IT support for your company in Bydgoszcz

Thirty minutes on how your IT looks today ends with a proposed scope and a fixed monthly price. If you would rather start from facts than from a conversation, request the free audit. We are based in Bydgoszcz, so we can simply meet.