Model A
Local PC
Software and files live on every person's workstation. Simple, well understood and largely indifferent to whether the internet is up.
In most small and mid-sized firms nobody ever designed the infrastructure; it simply accumulated. There is a server bought when the company had ten staff, a network drive a former colleague picked up, wireless access points from the shop round the corner and a handful of cloud subscriptions nobody can trace to a budget. When things slow down, the reflex answer is new equipment. Apply works in a different order. Step one is a full record of what you own. Step two is watching the systems when the pressure is highest. Only then comes the question of spending money. The fix may turn out to be one database parameter, a backup rescheduled to run overnight, or hosted desktops for the summer crew. We do all of it at a distance, and since there is no hardware catalogue behind us, nobody earns a commission on what we recommend.
The health check tells you where the risk sits, tuning tells you why things drag, and virtual desktops settle where programs and data should run. Begin with whichever matters most and bolt on the others later.
Ahead of switching IT provider, renewing cover with your insurer or a customer's supplier audit. You get a to-do list ordered by risk and by cost.
When raising an invoice takes a minute and opening a project gives everyone time to brew coffee. Instruments, not hunches, show whether storage, RAM, the LAN or the database is to blame.
Useful for summer staff, a branch that has just opened or people who mostly work from home. The device can be anything; the files stay put on the hosted server.
Our engineers dial in; your people give up perhaps an hour of conversation in total. Nothing in your configuration is altered during the review. Any change waits until you have read our findings with us and said yes.
Every server, workstation, switch, licence and warranty date goes on one list. For many owners it is the first complete picture they have had, and it nearly always surfaces a couple of boxes nobody remembered buying.
A small collector runs quietly for a fortnight or three weeks. We schedule it so that it catches the pressure points: closing the books, a filing deadline or a web shop's sale weekend.
Red items need attention within weeks. Amber items belong in the coming budget. Green items simply get watched. Each finding comes with the engineering time it should take and, where relevant, an equipment price.
We can do the work, your existing provider can, or your own staff can. The document is yours to use as you see fit, and commissioning it commits you to nothing further.
Hosted desktops earn their keep by solving specific headaches, and trendiness is no reason to adopt them. Below, five everyday scenarios are run through both set-ups.
Model A
Local PC
Software and files live on every person's workstation. Simple, well understood and largely indifferent to whether the internet is up.
Model B
Hosted desktop
Windows itself runs on a server elsewhere, and whatever the user holds, laptop, thin client or tablet, just displays it.
In practice
A mix of the two
Decide job by job rather than for the company as a whole. Plenty of offices run both without friction.
“The server can't cope any more” often hides a different culprit. Typical discoveries include a nightly backup that drifted to mid-morning long ago, whole departments working on large spreadsheets directly across the network, a power-saving profile throttling server CPUs, a database engine hoarding every gigabyte of memory, and branch office traffic looping through headquarters for no reason. A few hours of remote work fixes each one. Fresh hardware fixes none.
Usually. Measuring for a couple of weeks shows whether the existing machine has genuinely run out of headroom. When it has, we write the specification, CPU, RAM and disks, that you then hand to your supplier, which stops you overbuying. When it has not, tuning tends to fix the symptoms and the replacement can wait another year or more.
Plan on two to three weeks of elapsed time. Your involvement amounts to a kick-off, a wrap-up and a handful of short queries. We bill €50 per hour plus VAT, and you see an hours forecast, derived from staff, server and site counts, before anything starts; a fixed fee is possible for a narrow scope. Running over the forecast requires your go-ahead.
Inside the EU. We use Microsoft Azure's EU regions or European hosts like Hetzner, OVHcloud and IONOS, and we write down exactly which provider and location hold your data so the details can go into your processing register. As your processor we sign the necessary agreement and handle encryption and access logs. Questions about informing employees or clients belong with your DPO or lawyer.
Far from it. Start with one clearly bounded team: say, seasonal reception staff at a hotel in Kranjska Gora, a pair of bookkeepers at a Savinja valley exporter who work from home half the week, or a fresh branch with nobody technical on site. Let it run for a few months, look at usage and cost, then decide on the next group.
Possibly. The Slovene Enterprise Fund, SID banka and EU-funded calls run digitalisation schemes from time to time, including vouchers, but the rules change frequently. Ask the body running the scheme whether your project qualifies. We make no promises about funding and hold no official consultant status; what we can supply is a quote, a scope of work and a written report laid out so they can accompany your application.
Visibility only. Our review accounts cannot change configuration or remove data. Each engineer uses a named login protected by multi-factor sign-in, connections run through an encrypted tool, and sessions are logged. The data processing agreement precedes any connection, and write permissions arrive only alongside your sign-off for a particular fix.
Share your headcount, servers and sites and the thing that frustrates you most. Within one working day you will hear our suggested starting point and a rough time estimate.
Enquiry received
An engineer will write back no later than the following working day. Faults that leave your staff unable to work are always looked at first.
No town by that name here. Check the letters, or settle for the nearest larger place. Our engineers work only over the internet, so Kočevje and Koper get precisely the same treatment.