Smart Hands

A precise onsite task is easier to execute, verify and invoice.

Smart Hands is for physical technical work that requires a person at the equipment. The best request specifies exactly what may be touched, how success is measured and when the technician must stop.

Quick answer

Smart Hands is scoped onsite technical assistance for physical infrastructure. Typical work can include visual inspection, cable tracing and patching, power actions, rack-and-stack, approved component replacement, asset/serial verification, console connection and photo evidence — subject to site access and an approved task scope.

Typical tasks

Examples of physical work you can scope

Visual inspection

Check LEDs, display messages, cable state, physical damage, labels or other observable conditions and report evidence.

Cabling & patching

Trace, label, connect or replace approved network/power cables according to a port map or explicit instruction.

Power actions

Perform an approved physical power cycle or power-cable action when remote management is unavailable.

Component work

Replace approved RAM, disks, NICs or other compatible parts when access, parts and procedure are confirmed.

Scope template

Turn a chat message into an executable task

Identify equipment

Facility, rack/U, hostname, asset tag, serial number or another unambiguous identifier.

Define allowed actions

List exactly what the technician may disconnect, replace, power cycle, photograph or test.

Set stop conditions

State what must not happen and when the technician should pause and contact you.

Define evidence

Photos, serials, link state, power state, console output or another acceptance check.

Safety

What not to send in the first request

Never put privileged credentials or secret keys in an ordinary enquiry. If console or authenticated access becomes necessary, use a separately agreed secure exchange after the task is accepted.

No private keys

Do not paste SSH private keys, recovery codes or administrator passwords into contact forms.

No payment secrets

Do not send card numbers or other financial credentials as part of a technical ticket.

No ambiguous permission

Avoid “do whatever is needed.” Define permitted actions and escalation points.

FAQ

Questions to settle before deployment or onsite work

Technical request

Describe the hardware or onsite task

For faster scoping, include the equipment, location, requested action, maintenance window, urgency and any stop conditions.

Do not include passwords, private keys, recovery codes or other credentials. Access is arranged separately when a task is approved.

Turn the requirement into an executable scope.

Send the hardware, workload or onsite task. We will separate assumptions from confirmed availability before anything is deployed or touched.

Request a quote