On-site IT: what a dedicated technician inside your offices actually does

Past a certain size — typically 80 to 150 staff on a single site — the “remote managed services with occasional on-site visits” model shows its limits. The organization needs an IT counterpart physically present: to prepare new joiners’ machines, to react fast on blocking incidents, to equip meeting rooms before a board meeting, to absorb the daily IT noise. That’s the role of on-site IT — a technician (or several) operated by Macinwork but physically present at your premises. Here is when this model makes sense, and how we run it.

The diagnosis that leads to on-site IT

An SMB’s internal IT team often runs at 1 or 2 people. When headcount moves from 80 to 200 staff on a site (or several Paris sites), the load grows non-linearly: more arrivals, more departures, more concurrent incidents, more meeting rooms to equip, more visitors, more ad-hoc requests. Hiring a third and fourth IT internally has a cost (recruitment, salary, charges, training, management) that doesn’t always pencil out, especially when load is variable.

The outsourced on-site IT model offers a different trade-off: Macinwork assigns a dedicated technician (or two) to your site, full-time or shared, with on-premises presence coupled to our full back-office (escalation, expertise, specialist teams on complex workstreams).

What an on-site IT actually does

On the sites where we operate on-site IT, the daily scope is:

• Onboarding / offboarding — new-machine prep, configuration, delivery to user, quick training; equipment recovery on departures, access deactivation, archiving.
• Level 1 and 2 user support — physical helpdesk (users come see the tech, day-to-day incidents resolved fast), troubleshooting, escalation to our teams when needed.
• Workplace — meeting room equipment and maintenance (Teams/Zoom videoconference, screens, audio, polycoms), collaborative spaces, IT signage.
• Internal coordination — interface with facilities, procurement, HR (for arrivals), external vendors (hardware repair, operators).
• Operational compliance and security — policy enforcement (MFA, updates, MDM), regular account audits, IT-related physical access management (badges, server rooms).

What it doesn’t replace

On-site IT replaces proximity IT, not strategy or specialist expertise. On the sites where we run on-site IT, behind the physically present technician sits our full back-office: security team, network team, ERP team, fractional CIO. The on-site tech is the interface, but when a topic exceeds their scope (a complex SSO issue, a cloud migration, an ERP integration, a security audit), they escalate.

Often misunderstood: on-site IT isn’t “less service”, it’s “more proximity with as much depth behind”.

Embedding with your teams

A sensitive point: the Macinwork technician on site works daily with your team. They have your badge, your internal email address, their seat on your Slack or Teams. From the outside, they’re a member of your IT team. But they remain a Macinwork employee, participate in our internal rituals, benefit from our continuous training, and can be replaced without service disruption if needed (vacation, internal mobility).

A delicate balance. Our approach: a tech dedicated to a client over the long run (typically 12-24 months minimum), who becomes a true context expert; with a backup partner trained to ensure continuity, and controlled rotation to avoid stagnation.

The on-site tech profile

Macinwork techs who succeed on-site share characteristics: high autonomy (they’re alone most of the time on site), interpersonal ease (they interface daily with leaders and business teams), technical versatility (Mac, PC, mobile, network, AV, SaaS), discretion (they see a lot of sensitive information), and ability to formalize (documentation, action tracking).

A demanding role requiring a senior profile, not a junior helpdesk. Our pricing reflects that.

The commercial model

For a full-time dedicated technician, annual Macinwork pricing depends on profile and scope, and includes:

• The person’s loaded salary;
• Back-office (escalation, expertise, supervision, tooling);
• Service continuity (replacement for vacation, sickness, departure);
• IT tooling we provide (tech laptop, MDM/EDR console access, etc.);
• Continuous improvement (training, certifications, practice sharing).

Compared to the all-in cost of an equivalent internal IT (salary + charges + recruitment + management + tooling + replacements), the gap is small — often in favor of on-site IT, sometimes neutral. The difference lies elsewhere: on-site IT buys flexibility (you can end the contract with notice if needs shift) and service guarantee (continuity doesn’t depend on a single person’s availability).

When it isn’t the right model

On-site IT isn’t always the right answer. For an organization under 60 people, managed services with occasional on-site visits is fine. For an organization over 300 with a strong internal IT department, on-site IT may be relevant on secondary sites (international subsidiaries) but redundant at HQ. For a very standardized, repetitive organization (chain of stores with strict process), a remote helpdesk + occasional on-site model can be more economical.

The conversation to have

If on-site IT is on your radar, it’s usually because the current friction is visible: users complaining about waits, poorly equipped meeting rooms, IT overloaded, leaders sensing they’re missing something. A free Macinwork initial IT audit sizes the right solution. The form at the bottom of the home is built to start the conversation.