Questions and answers

Directly with me, from the first conversation through delivery. There are no account managers or intermediaries: the person you agree the scope with is the same person who does the work and answers for it. Nothing gets lost in handovers, and decisions are made quickly.

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.

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

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

With a free, no-obligation conversation about the problem you want solved. I 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, and for larger scopes I 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 code, the repository, the documentation and all access credentials are yours, and the transfer of rights goes into the contract before work starts. After launch you can stay with me for ongoing care (updates, monitoring, further development) or hand the system to your own team. I run projects so that both paths remain realistic at any point.

Yes, it is a common starting point. I 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.

Testing is 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. My QA and test automation background helps here: I look at my own code the way a tester looks at someone else's.

The contact channel is open 24/7. Companies on an ongoing support arrangement additionally get response times agreed in the contract: [TO BE PROVIDED: response times for standard and urgent issues]. Requests outside a standing agreement are handled as availability allows, and I always say plainly when I can realistically get to a problem.

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

We agree a scope that fits your company: day-to-day help for employees, care of hardware and software, backups, updates and purchase advice. Billing can be a monthly arrangement or based on hours worked; either way it is written into a plain agreement with no fine print.

Availability for requests and call-outs across Bydgoszcz and the Kuyavian-Pomeranian Voivodeship: 24/7. Every appointment is confirmed individually, so get in touch and we will find a time that works.

Get in touch straight away and briefly describe what is happening. Urgent requests are taken 24/7. I will tell you plainly whether and how fast I 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 I 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, I will say so. Paid work starts only after your go-ahead.

Your data is treated as confidential: I only look where the repair requires and never copy anything for my own use. Before touching the disk or the operating system we always discuss a backup; if you do not have one, I can make one before work begins.