01
Support & escalation
Agree on support hours, contact channels, urgency definitions, and who takes an issue after hours.
Put in writing: Named owner, escalation path, and written coverage terms.

Build a managed-IT scope around a named owner, documented coverage, and the systems your team depends on. The audit defines what LUCA operates, what remains with you, and how the work is checked.
Samuel Mfinanga · Named engineer · 20+ years infrastructure
Start with your operation
Answer what you know; every question is optional. Your choices prepare an editable draft on Contact. Nothing is sent from this page; review the contact options there. Your answers do not produce a price or promise a service level; scope and terms are agreed after review.
Continue now, or add a few details first.
Before the agreement
A managed IT proposal should show what is covered, what is separately quoted, and what remains yours. These are decisions to make together, not a list of pre-included services or a promised service level.
01
Agree on support hours, contact channels, urgency definitions, and who takes an issue after hours.
Put in writing: Named owner, escalation path, and written coverage terms.
02
Count the users, locations, devices, and systems in scope; identify what stays with your team.
Put in writing: Current inventory and a responsibility map.
03
Identify what must be protected, who runs restore tests, and who decides when to recover.
Put in writing: Backup ownership, test cadence, and recovery priorities.
04
Decide who approves access, reviews exceptions, responds to alerts, and coordinates incidents.
Put in writing: Approval authority and an incident handoff path.
05
Name the owner of connectivity, equipment, cloud accounts, and third-party tickets.
Put in writing: Vendor contacts and the boundary between teams.
06
Separate ongoing support from new projects, hardware purchases, and the provider handover.
Put in writing: Quoted exclusions, transition checkpoints, and sign-off owners.
Replacing a provider?
A switch is more than installing new tools. Use these four checkpoints to ask for a written transition scope before anyone changes access or support ownership.
Who owns every account, device, vendor relationship, backup, and open issue today?
Ask for this recordA buyer-owned inventory with the current owner, missing access, critical dependencies, and the people authorized to approve changes.
What must keep working while responsibility changes hands?
Ask for this recordA handoff order for business-critical systems, support contact path, change window, validation checks, and a named rollback decision-maker.
When can the incoming team enter, and when should the outgoing team lose access?
Ask for this recordApproved access steps, least-privilege assignments, tool changes, evidence of removal, and an exception owner—not credentials in a public form.
What shows the buyer that support and recovery now have an owner?
Ask for this recordA checked support route, tested handoffs, known exceptions, agreed reporting, and an exportable environment and exit record.
These are buyer checkpoints, not a promise that every activity, tool, coverage hour, or transition period is included. The actual responsibilities and terms belong in the reviewed proposal. Do not send credentials or sensitive environment details through this site.
Book a callStill comparing providers?
Compare ownership, coverage hours, security, transition, and exclusions before you compare the monthly number.
Read the managed IT buyer guide →Managed services
Managed Services & Support: what this includes
Managed Services & Support: the practical distinction
A ticket number, then a stranger who has never seen the office.
Name the account owner, backup contact, and escalation path in the scope.
A backup job is green, so it must be fine.
Define a restore test, its cadence, and the evidence you will receive.
A portal full of charts, and a quarterly meeting to explain them.
Agree on a useful reporting cadence: what is healthy, what changed, what is next.
After hours, you start the explanation over.
Write down staffed hours, monitoring, on-call coverage, and who gets the alert.
Leave, and the picture of your environment stays in their tool.
Specify the environment record, asset list, backup design, and exit handoff.
The workflow
Before the quote
A monthly agreement should follow the real environment, the people who use it, and the hours when a failure matters. Bring the facts you have; unknowns belong in the audit.
How many people, locations, devices, and critical applications need support? Separate remote coverage from work that requires a person on site.
If you have an IT lead, name what they keep and what LUCA would run. Include vendor access, joiners and leavers, and who authorizes a material change.
Identify the systems whose outage stops the business, the after-hours contact, and the recovery you expect. A backup status is not the same as a tested restore.
Office moves, migrations, and major security redesigns are projects, not invisible additions to the monthly account. Ask for a written line between them.
What gets scoped
The audit sets covered users, devices, systems, support hours, on-site geography, ownership, escalation, reporting, and separately quoted projects before a monthly account is priced.
Read the primary guidance
These sources help frame the questions. They are not a LUCA certification or a promise that every control is included in a service quote.
Before you choose
Choose the right next step
NEXUS MSP Edition is a separate software discussion. Availability is not confirmed; this is not LUCA's managed-services labor.
Book a callA full access rebuild is Zero-Trust Security. The monthly account keeps the doors that are already there.
See the related serviceHow we quote
For
Owners who need day-to-day technology support, internal IT leads who need extra capacity without giving up decisions, and teams planning a provider change.
Other work in Technology & Software Engineering
Tell us what you need done and what success looks like. The contact page also gives you LUCA's direct phone and email.
Book a call