What the IT work during rollout consists of
Each client gets an isolated instance with its own database and its own email system, running in Docker containers, including on the client's own server. As a result, the IT department's work splits into several separate tasks: host preparation, network arrangements, sending email, user accounts, monitoring and rollout acceptance.
The IT scope does not cover application code or configuration. The configuration is described by an environment variable contract without values, so IT supplies the values and the environment rather than writing integrations from scratch. InnerWeb does not produce or replace access control readers, so replacing KD devices is outside the scope.
Cost structure: where the hours grow
The two factors with the largest effect on the number of hours are the choice of network architecture and the way accounts are entered. When the network blocks all outbound traffic from the host, alarm webhooks are stored permanently and a poller collects them through an inbound channel, so the acceptance design adds hours at the network stage.
Feeding accounts from the plant's user directory is not a standard, because the feature documentation does not describe it, and the described SSO covers entry from the qualification portal. It is an option to agree with IT and is counted separately. The calculation below assumes that accounts are entered from a list prepared by the plant.
- Host and containers: server preparation, Docker, disk space and backups.
- Network: DNS, firewall rules, certificate, possible inbound channel for alarms.
- Email: checking how the plant's mail system treats messages from the sending domain.
- Accounts: list of people, roles and possible MFA.
- Monitoring and logs: receiving error reports and reviewing the audit trail.
- Acceptance: collecting evidence for the audit.
IT hours per rollout task
Sample calculation of IT hours
The example concerns a medium-sized plant with one instance and one host. The assumptions are explicit so that the IT department can replace them with its own: the hours are sample values, not a promise of working time. The rate of 120 PLN per hour is a calculation assumption, not a price list.
In total this comes to 40 hours of one-off work, which is 4 800 PLN at the assumed rate, and 2 hours a month for maintenance, which is 2 880 PLN a year. In the first year the IT cost is therefore about 7 680 PLN, of which 62.5% is one-off work.
How to change the result: scenarios
Limited variant: a host without outbound traffic adds about 6 hours for the design and testing of the inbound channel. The variant with accounts fed from the user directory adds hours on the IT side depending on the structure of the directory and is set individually. The variant with MFA for all users adds hours for communication and training, but reduces the risk of account takeover.
In each case it is worth recording the assumptions in one document before go-live, so that a comparison with the time actually spent becomes possible after acceptance.
What the calculation does not include
The calculation does not cover hardware, system licences or the work of the implementation team. It also does not cover the costs of any replacement of KD readers, because InnerWeb does not replace them and integrates with the existing system. The pricing on the InnerWeb side is individual and depends on the scope.
Sample calculation of IT department work
| Parameter | Value |
|---|---|
| Host and containers | 8 hours |
| Network and DNS | 6 hours |
| Sending email | 3 hours |
| Accounts and MFA | 10 hours |
| Monitoring and logs | 4 hours |
| Acceptance and training | 9 hours |
| Sample rate | 120 PLN/h |
| Maintenance | 2 h/month |
Result: 40 hours one-off (4 800 PLN) plus 2 hours a month (2 880 PLN a year): about 7 680 PLN in the first year.
Note: Sample calculation on our own assumptions. Each plant enters its own hours and rate; InnerWeb pricing is individual.
Video
Frequently asked questions
Are 40 IT hours a norm for every plant?
No. This is a sample calculation for one instance on one host. The scope changes with the network architecture, the way accounts are entered and the MFA level.
Does IT have to maintain the application after go-live?
The scope of maintenance is set in the contract. The calculation assumes 2 hours a month for overseeing the host, the log and error reports.
Is replacing KD readers part of the IT work?
No. InnerWeb does not produce or replace readers; it integrates with the client's existing access control system.
Sources
Let's count the IT work for your plant
We will put your hours and rate into the calculation and show which tasks can be shortened. Let's arrange a conversation with the IT department.
Let's talk