Helpdesk
Operating systems, applications, accounts and access. Users know where to report a problem and when they will hear back.
ADMINISTRATION AND SUPPORT
Your IT department in one person.
Daily help for users combined with administration of the environment. A problem does not end at a quick fix — it goes back to the cause, and the environment becomes easier to maintain over time.
Ask about support- Response
- usually within hours
- On site
- Szczecin area
- Remote
- all of Poland
- Monitoring
- Zabbix
WHAT IT COVERSDaily care
Daily care
without the chaos.
The scope I run in practice for companies with a head office and branches.
Windows Server and Active Directory
Accounts, group policy, permissions, updates and domain health — the foundation everything else stands on.
Virtualisation
Hyper-V and Proxmox: deployment, machine maintenance, resources and a recovery plan that has been thought through.
Hardware and network
Diagnostics and repair of computers, network devices and printers. Configuration and rollout of newly purchased equipment.
Zabbix monitoring
Performance and availability of key services are observed — not checked only after somebody reports an outage.
Documentation
Configurations, licence records and user guides. Knowledge about the environment stops living only in somebody's head.
WHAT YOU GETSpecifics,
Specifics,
not just “IT care”.
Scope is agreed before we start, but these are the things that show up in almost every ongoing engagement. All of it stays with you — including after we stop working together.
- A ticketing system, or one agreed reporting path, instead of four chat apps
- An inventory of workstations, servers and network devices with their configuration
- Hardware and licence records kept in a dedicated tool, not a spreadsheet
- Documented administrative accounts and who has access to what
- Monitoring of the agreed critical services, with alerts reaching me
- An agreed backup plan and a check that the jobs actually complete
- Short guides for the repetitive tasks your staff handle themselves
- A priority list for the next quarter, kept up to date
WHAT I USUALLY FINDFive things
Five things
that repeat in every company.
These are not edge cases — they are the norm in companies that never had a permanent IT contact. None of them comes from incompetence; nobody simply had it in their job description.
Symptom
Requests arrive through three channels and some get lost.
Cause
No single place was ever agreed, so everyone writes wherever they happen to have a window open.
What I do
I put in a ticketing system, or one agreed reporting path at smaller scale. The phone stays for urgent matters, not for everything — a call leaves no record, and a month later nobody remembers what was agreed.
Symptom
Nobody knows how many licences the company holds or when they expire.
Cause
Software was bought ad hoc, alongside new computers, with no shared record.
What I do
I introduce a tool for hardware and licence records — past a few dozen workstations a spreadsheet stops keeping up. Where no records exist there are always licences paid for twice, or assigned to people who have left.
Symptom
Backups “are running”, but nobody checks whether they finish.
Cause
Backup was configured at rollout and never revisited; failure alerts were going to a mailbox that no longer exists.
What I do
I check whether the jobs complete successfully and route failure alerts somewhere a person actually reads them.
Symptom
Accounts of former employees are still active.
Cause
Leaving the company is an HR process, not an IT one — nobody passed the information on.
What I do
I clean up the accounts and agree a simple routine: one message when somebody joins and one when they leave.
Symptom
You hear about a server outage from your own staff.
Cause
There is no monitoring, or alerts go somewhere nobody reads.
What I do
We agree which services genuinely stop the business and I monitor only those. An alert everyone ignores is worse than no alert at all.
HANDLING A REQUESTFour steps,
Four steps,
the same every time.
Here repeatability matters more than raw speed.
Request
A short description reaches me directly, through one agreed channel.
Diagnosis
I check the user, the service and the wider context. The cause is often somewhere other than the symptom.
Resolution
I remove the cause, or present a plan if the fix requires an infrastructure change.
Record
The solution goes into documentation so the next occurrence takes minutes rather than hours.
QUESTIONS ABOUT SUPPORTWorth knowing
Worth knowing
before we talk.
Answers to the questions that come up most often about this service.
Will you take over an environment somebody else has been running?
Yes, and that is the typical case. I start with a review of the actual state: what runs where, who holds which access, what is still covered by warranty and vendor support. Only after that review do I say what can stay as it is and what needs changing. I do not criticise my predecessor — they usually worked under constraints I know nothing about.
What happens if a request arrives outside the agreed hours?
It reaches me and waits for the next support window, unless the contract says otherwise. I run Sailman IT alongside full-time employment and would rather say so plainly than promise a response at three in the morning. If your company genuinely needs round-the-clock cover, it is fairer if I point you elsewhere straight away.
Do I need a server to start?
No. Plenty of companies run perfectly well on workstations and cloud services, and a server can be a cost that solves nothing. If tidying up what you already have is enough, I will say so rather than propose a purchase.
How does on-site work look?
In Szczecin and the surrounding area I can come over when the task needs it — hardware replacement, a new workstation, a network problem that is invisible remotely. Everything else happens remotely because it is simply faster. Travel terms are agreed in the contract.
What if we stop working together?
You receive the full set of administrative credentials, the environment documentation and the licence records. Nothing stays only on my side — I treat that as obvious and put it in the contract.
NEXT STEPDescribe the problem.
Describe the problem.
You get a straight answer.
No specification required. A few sentences about your company and what currently does not work is enough to start.
Go to contact