We solve 90 %
remotely

Q: Kommen Sie auch vor Ort, wenn wir es wirklich wollen?

Yes. We plan on-site visits around actual need - new premises, larger hardware rollouts, strategy workshops, annual reviews. At short notice in the Rhine-Main region, regularly in Tyrol (several times a year), project-based in the rest of DACH.

Q: Was kostet Anfahrt bei Ihnen?

No travel fee for existing clients inside the Rhine-Main region. Outside it: a fixed price per visit, usually bundled with other appointments, or shared. Never a mileage charge on top that exceeds the hourly rate.

Q: How do you solve problems that look like they need someone on site?

With remote access and good preparation. Cloudflare Zero Trust, TeamViewer Tensor or Splashtop for remote sessions. Screen sharing and session recording for documentation. For hardware faults we either keep spare hardware on site, or coordinate with service-technician partners and walk them through the work.

Q: Is not remote work impersonal?

Depends what you mean by personal. You get real contacts, actual names, direct phone numbers. Video calls happen regularly. What happens less is the weekly on-site chat over coffee - but the quality of the technical work does not suffer for it.

Q: Why do other IT firms bill travel as standard?

Because they can - clients historically expect it, competitors do it too, and every hour of travel is a billable hour. We do not think that holds up any more. If a problem can be solved in 15 minutes over remote access, you should not be paying for 90 minutes of driving.

Q: Wie funktioniert das bei Totalausfall - Server ist down, niemand kommt rein?

That is what the SLA protocol is for. First diagnosis remotely (out-of-band management via iLO, IPMI or iDRAC often works, where present). If hardware has to be swapped and time is critical, we activate our partner network for an on-site call. For critical systems we recommend high-availability setups where a single failure does not stop everything.

Q: Was, wenn wir Ihnen trotz aller Logik sagen: wir brauchen jemanden lokal?

Then we are not the right fit - and we will say so. There are good reasons to use a local provider: if your business needs someone physically present every day (production floor, showroom, publicly accessible hardware), our model does not suit you. We would rather recommend a good local provider than push you into the wrong setup.

Aus Prinzip, nicht aus Geldmangel.

Wir schicken keinen Techniker 90 Minuten auf die Autobahn, um einen 15-Minuten-Job zu erledigen. Remote ist Standard, Vor-Ort ist die Ausnahme - geplant, transparent, mit klarem Nutzen.

↓ How it works Kennenlernen

[K] Remote

90 %.

aller Tickets per Fernzugriff

[K] Reaktionszeit

< 2 h.

during business hours

[K] Anfahrt

0 EUR.

im Rhein-Main 50 km Radius

Remote-first is a quality choice, not a compromise.

The basic assumption of many IT firms comes from the reality of the 2000s: a technician turns up with a laptop and a tool bag, looks at the hardware on site, fixes it, then drives on to the next client. The hourly rate includes travel time.

Today that assumption holds for 5 to 10 percent of all IT work. For everything else, remote access tools, cloud dashboards, remote management and central configuration are not merely equivalent - they are often better. Weil Sie schneller reagieren können, Dokumentation systematischer anfällt, and fewer accidental problems arise from improvising on site.

Unser Modell nimmt die 90 Prozent, die remote gut laufen, und macht daraus den Standard. Für die 10 Prozent, die wirklich physische Präsenz brauchen, planen wir gezielt und transparent.

Was unser Modell anders macht.

Four ways our remote-first model differs from a traditional IT firm. Common practice on the left, our approach on the right.

Klassisch vs. Remote-first.

Klassisches IT-Haus

CAVORT Remote-first

Travel fee plus hourly rate for an on-site visit that remote would have solved in 15 minutes

Remote-First mit Cloudflare Zero Trust, TeamViewer Tensor, Splashtop - 90 % Tickets nicht vor Ort

Mileage charges on site visits that exceed the hourly rate

On-site visits bundled at a fixed price, no mileage charges

Kein Out-of-Band-Management, jeder Server-Reboot kostet einen Vor-Ort-Termin

iLO/IPMI/iDRAC dokumentiert und genutzt, Server-Restart aus 200 km Entfernung

Vor-Ort-Pauschale bei Standard-Tickets, weil Hersteller das verlangt

First diagnosis always remote, on-site only when needed - you pay for work actually done

What that means for your costs.

No travel fees for tickets that can be solved remotely. If we fix a problem over remote access in 20 minutes, you pay for 20 minutes - not an hour plus travel.

On-site visits by arrangement, with a clear framework. A day visit costs an agreed flat price that includes travel - no per-kilometre surcharges on top of the hourly rate.

Bundled visits. When several clients in one region need a visit, we share the travel. That lowers the cost for everyone.

Rhein-Main-Vorteil. Innerhalb 50 km um Neu-Isenburg keine Anfahrtspauschale für Bestandskunden. Erster Kennenlern-Termin immer kostenlos.

Where we are genuinely present.

Ninety percent of our work happens remotely. We show up in person where we spend time regularly.

Drei Geschwindigkeiten.

[HQ]

Rhein-Main.

Head office, regular on-site presence, short-notice visits possible.

Öffnen

[SP]

Tirol.

Zwischen Innsbruck und Serfaus-Fiss-Ladis. Mehrmals pro Jahr vor Ort.

Öffnen

[RT]

DACH-weit.

Alles andere - Remote-first mit geplanten Vor-Ort-Besuchen.

Öffnen

Common questions about the remote model.

FAQ.01Kommen Sie auch vor Ort, wenn wir es wirklich wollen?

Yes. We plan on-site visits around actual need - new premises, larger hardware rollouts, strategy workshops, annual reviews. At short notice in the Rhine-Main region, regularly in Tyrol (several times a year), project-based in the rest of DACH.

FAQ.02Was kostet Anfahrt bei Ihnen?

No travel fee for existing clients inside the Rhine-Main region. Outside it: a fixed price per visit, usually bundled with other appointments, or shared. Never a mileage charge on top that exceeds the hourly rate.

FAQ.03How do you solve problems that look like they need someone on site?

With remote access and good preparation. Cloudflare Zero Trust, TeamViewer Tensor or Splashtop for remote sessions. Screen sharing and session recording for documentation. For hardware faults we either keep spare hardware on site, or coordinate with service-technician partners and walk them through the work.

FAQ.04Is not remote work impersonal?

Depends what you mean by personal. You get real contacts, actual names, direct phone numbers. Video calls happen regularly. What happens less is the weekly on-site chat over coffee - but the quality of the technical work does not suffer for it.

FAQ.05Why do other IT firms bill travel as standard?

Because they can - clients historically expect it, competitors do it too, and every hour of travel is a billable hour. We do not think that holds up any more. If a problem can be solved in 15 minutes over remote access, you should not be paying for 90 minutes of driving.

FAQ.06Wie funktioniert das bei Totalausfall - Server ist down, niemand kommt rein?

That is what the SLA protocol is for. First diagnosis remotely (out-of-band management via iLO, IPMI or iDRAC often works, where present). If hardware has to be swapped and time is critical, we activate our partner network for an on-site call. For critical systems we recommend high-availability setups where a single failure does not stop everything.

FAQ.07Was, wenn wir Ihnen trotz aller Logik sagen: wir brauchen jemanden lokal?

Then we are not the right fit - and we will say so. There are good reasons to use a local provider: if your business needs someone physically present every day (production floor, showroom, publicly accessible hardware), our model does not suit you. We would rather recommend a good local provider than push you into the wrong setup.