Skip to main content
x

Interview with Jens Hagel, Founder & Owner, kjello

Interview with Jens Hagel, Founder & Owner, kjello

(Featured) - The Hamburg IT founder discusses integrating acquisitions, separating teams, documenting responsibilities, and using Microsoft 365, Intune and Autopilot.

Edited by Jenn Moon, Editor at Featured News · Nov 16, 2026

As founder and owner of a computer-networking firm in Hamburg, what kinds of business-change IT projects have given you the clearest view of what companies get right — and wrong — when their structure changes?

What I have learned from quick buyouts is this: A company that owned several properties in Hamburg had taken over 22 companies in the span of two years. Users had administrative rights, and two-factor authentication (2FA) was disabled.

We offered them a support package of around 20 hours a month to help them help themselves. Most of this time went towards configuring Autopilot and Intune, Microsoft’s way of deploying and managing devices. Once this was done, all users had 2FA enabled, and new starters could be configured in minutes.

What path led you to build kjello and become the IT partner companies call when they are acquiring, separating, merging or rapidly scaling their operations?

I started hagel IT from my living room in 2004. We migrated to the cloud in 2013. We moved away from hourly billing to a fixed monthly price in 2019. We are now a team of 32 supporting over 150 companies in northern Germany.

Whenever a company changes, staff join and leave. Devices and permissions need to follow suit. kjello was our answer to that. The company can choose a laptop from our portal, and it will be delivered to the employee and configured on first boot. If someone leaves, we can begin disabling their access through our system.

When a client buys another business, what is the first IT discovery step you take to reveal the risks that could disrupt the combined company?

I like to conduct a cyber risk assessment with the managing director and then review the company’s infrastructure to find out where they stand with their newly acquired company.

A company in Bremen bought a specialist company with 18 employees. All employees worked on private laptops with admin rights. The company had terabytes of data on network-attached storage (NAS) with no backups, which would have been difficult to recreate. We moved everything to SharePoint within four weeks and restricted access. The managing director stated that he did not know how close they were to disaster.

From your experience, what information should an acquiring company document before deciding which systems, networks and user accounts to integrate or retire?

Document who has admin rights, what licenses you're paying for and where data is stored. Having admin rights will cause you the most headaches.

An investment company in Hamburg was removed from the group IT department of a larger asset manager. Because the group could not give them access to their Microsoft tenant due to password restrictions, we created a new Microsoft tenant for them. Their IT is now around 40% cheaper than what the group charged them.

When a team is being spun out of a corporate group, how do you help preserve the team’s access to the tools it needs without leaving the former parent company exposed?

Have the company being spun out configured independently. If the two companies share logins, it will only cause headaches for both parties.

A consulting company that was taken out of a corporate group had employees working in Hamburg, Frankfurt and at home. All their laptops and email signatures were configured through the group’s IT department. We built them a serverless office using Microsoft 365, Intune and Autopilot. Even their private iPhones were included, and they pay us a monthly rate per person.

After a period of fast growth, what IT problem tends to remain hidden longest, and what review can a growing company perform now to uncover it?

Excessive admin rights and missing or untested backups. You may not know there's a problem until something goes wrong.

One of our clients in Hamburg had around four employees when we first started supporting them. They now have over 30. One of their employees did IT as their second job, and everyone had admin rights. Our client told me they did not know if their backups were working. We removed their unnecessary administrative rights, and no one noticed. Always check who has admin rights, and restore a backup from the previous week to see if it works.

Across acquisitions, carve-outs, mergers and growth cleanups, what is the one IT habit you would put in place early to make the next major business change far less risky?

2FA on all logins that support it. When we first start working with a company, they almost never have this enabled.

We started with a law firm that had 11 employees and did not have 2FA. It became one of their top security features. When you're buying a company, you will have multiple logins being created. Having 2FA can limit the damage if login credentials are compromised.

Thanks for sharing your knowledge and expertise. Is there anything else you'd like to add?

Know who is doing what when a group of companies buys a company and keeps its group IT involved. We support one of our clients that has group IT in another country. We are the first point of contact, but we do not have permanent admin rights. So, we had to pass any simple tasks on to the group IT. We felt like we were doing work for them.

We now have these responsibilities documented and have started using time-limited administrator credentials.

About the expert

Jens Hagel

Jens HagelFounder & Owner at kjello

This story was produced by Featured and republished with permission. Experts featured here are members of Connectively, Featured's expert network.

Article Link