Hour package
priced per hours
On-demand support settled against a monthly pool of hours.
- Remote helpdesk and consulting
- Care for workstations and accounts
- Transparent settlement of unused hours
SCOPE OF WORK
User support, systems, mail, hosting and security handled by one person in one consistent model. Scope can grow with the company — you do not have to buy everything on day one.
Ask about scopeI do not offer everything. I offer the areas I work in daily and take responsibility for.
Helpdesk, care for workstations, network and servers, monitoring and documentation that keeps knowledge inside the company.
See details↗[365]Deployments and migrations, Exchange administration, order in accounts, licences and permissions, plus secure sign-in.
See details↗[SEC]Endpoint protection, DLP, MFA, mail hardening and log analysis — layers that genuinely reinforce each other.
See details↗[NET]Servers, websites, applications and mail with real ownership of configuration, updates, backups and migrations.
See details↗An engagement starts with terms in writing, not with the first request. These are the things that have to be clear on both sides — without them I do not begin, because each one can turn into a dispute later.
Scope and price depend on the number of users, the infrastructure and the agreed response time.
priced per hours
On-demand support settled against a monthly pool of hours.
monthly rate
Monthly administration of the environment with monitoring and docs.
fixed for the scope
A closed implementation with defined scope and deadline.
I reply to requests within a few hours as a rule, and by the next working day at the latest; the binding response time goes into the contract. Technical monitoring can run around the clock, but I run Sailman IT alongside full-time employment and do not promise availability I cannot keep.
The questions that come up before we agree scope.
If you do not know how much work you actually need, start with an hour package. Two or three months of usage shows it better than any estimate on paper. Where the scope is steady and predictable, ongoing care works out cheaper and gives me a reason to prevent problems rather than firefight.
Yes, and that is the usual path. Companies tend to begin with an hour package and move to ongoing care after a few months, once it is clear the same requests repeat every month. The change needs an amendment, not a new contract.
No. A common arrangement is user support only, or Microsoft 365 only, with the rest added later. I take on exactly what we agree — I am not responsible for areas outside that scope, and I say so plainly so there is no argument later about who was supposed to be watching the server.
Sometimes it does. It happens that somebody handles workstations and users well but is not confident with Microsoft 365 or security — then I take that narrow area and we work in parallel. I do not step into the role of replacing your person if that is not what you are after.
I do not use long commitments. Ongoing care normally runs monthly with short notice — if the arrangement is not working, nobody should be held in it by a clause. Project work ends when the work is accepted.
No specification required. A few sentences about your company and what currently does not work is enough to start.
Go to contact