managed IT services · monthly contract

Run by people who know your environment.

Managed IT services with 24/7 monitoring of servers, network and critical services. During business hours, the person who answers is the person who runs your IT. They know your ERP and which server went down last time.

RMM active
365days
human support
8h-18h
contract
tailored
anatomy of the contract

MSP tailored: human hours + a management platform.

Servers going down during business hours. An overloaded in-house team. Each engagement combines qualified human hours with the remote management platform that keeps your servers in order. No arbitrary minimum, no inflated scope, no surprises on the monthly invoice.

01
The core · human hours package

Qualified hours,
sized to your real needs.

Tier 1 · Support and operations
Support close to the user
Ticket management, first diagnosis, routine request resolution. Whoever answers already knows you: your environment, your ERP, your exceptions.
Tier 2 · Technical specialist
Infrastructure, networks and servers
Advanced configuration and troubleshooting for servers, networks, virtualization and integrations. Steps in when the problem goes beyond the obvious.
How many hours of each profile go into your contract comes out of the initial discovery. We have no off-the-shelf minimum package. We size it honestly, based on the real size of your operation, how critical your systems are and the profiles that make sense for your case.
02
The operation that never sleeps · RMM

A remote management platform
running directly on your servers.

RMM · Remote Monitoring & Management
Continuous environment monitoring, automated patching and remote management
Agents on servers and endpoints plus active monitoring of critical services (ERP, databases, internet links, network equipment) raise real-time alerts when something needs attention. OS, driver, agent and application updates are applied in agreed windows. Zulti operates, configures and fine-tunes. You never touch a console.
03
What is not in the MSP contract

Hardware and licenses stay in your name.

M365 / Workspace licenses licensed in the client's name
Hardware servers, laptops, switches, peripherals
Third-party software licenses ERP, management systems
— straight from the vendor
Zulti doesn't resell any of these three categories. You buy directly, in your name, through the best channel. Our team integrates, configures and runs it within the MSP.
who answers

It's not luck. It's organizational design.

Whoever answers knows who you are. Not because Zulti's team is "better" than a call center. Because the model is designed for it to work. Four organizational decisions make the difference every day.

01
— The whole team knows every client

It goes to whoever is free. And whoever is free knows you.

In a generic call center, the agent has never seen your environment. At Zulti, anyone on the team who picks up your ticket already knows your infrastructure, your history and even which users open the most tickets. It's not a dedicated allocation; it's knowledge shared across the team.

shared knowledge · everyone knows your environment
02
— Invisible escalation

Escalation happens in the background. You talk to one voice.

The team has Tier 1 and Tier 2. When a ticket needs deeper technical work, Tier 1 doesn't bounce you "to another level": they bring in Tier 2 in the background to solve it together. The person who took your call stays in charge, so you don't have to explain everything again or wait for a transfer.

one voice · invisible internal escalation
03
— Structured onboarding

When someone new joins, they start with the client's records, not from scratch.

Zulti keeps a runbook per client: environment history, technical decisions, operating standards, agreed windows. When someone new joins, this is their starting point instead of learning each client from scratch. Knowledge stays with the team, not in one person's head.

runbook per client · persistent records
04
— Effectiveness matters more than speed

Solving with effectiveness matters more than answering fast.

Where the metric is the number of tickets closed, the incentive is to close fast, even if the root cause comes back tomorrow. At Zulti the principle is different: work with effectiveness (actually solving it) and efficiency (with method), without trading quality for speed. Every ticket becomes a root-cause investigation, a runbook entry and a proposal for structural improvement.

effectiveness and efficiency beat a quick fix
Onboarding

The first 90 days.

Before operations become an invisible routine, there are 90 structured days: a clear goal, an agreed timeline and a visible deliverable at each stage. Each stage also says what changes on your side.

01
Week 1

Discovery

Inventory of the environment (servers, endpoints, networks, access, licenses, current contracts) and of known critical points. Meetings with leadership to align on the business's real priorities. Output: sizing of hours (Tier 1 + Tier 2) and RMM, turned into a signed contract.

02
Weeks 2 to 4

Transition

Most clients transition from a previous provider. Some come from ad-hoc support with no fixed provider. Zulti collects admin credentials, existing runbooks and configurations, installs RMM in parallel and opens the Zulti service desk. Output: a stable environment, RMM active on all agreed points, day-to-day technical operations already with Zulti.

03
Month 2

Calibration

First meeting with leadership after stabilization: what's working and what needs adjusting (sized hours, agreed windows, support channel). If something critical is still open, it gets prioritized here. Output: a tuned routine. Adjustments happen without you having to ask.

04
Month 3+

Routine

Support is answered by people who know you, RMM monitors, patches go out in the windows, the first monthly report is delivered. Operations have become invisible. Around month 9, if it makes sense, the first technical roadmap proposal comes out. A conversation separate from the MSP, with its own scope.

the operations curve

MSP is not a one-off service. It's a continuous service.

The value of an MSP doesn't show in the first month. It builds over time, through gradual, guided progress with minimal impact on day-to-day work. No big-bang switch.

↑ HIGH ↗ MEDIUM ↘ LOW 6 MONTHS 9 MONTHS + 1 YEAR
6 months — Stabilization complete

IT is out of "firefighting" mode.

— What happened

Discovery done, transition from the previous provider closed, RMM active, a single Zulti service desk in production. First calibration done in month 2.

— What the client feels

Patch windows respected, tickets no longer get lost, the monthly report is a habit. No more "chasing" the provider.

9 months — Calibrated operations

The same problems don't happen anymore.

— What happened

Full command of the environment, a consolidated runbook, standards adjusted to the real profile, recurring tickets fixed at the root cause. Here, when it makes sense, comes the first annual technical roadmap conversation led by our CTO as a Service.

— What the client feels

Response time dropped with no contract change. Leadership starts taking IT off the weekly agenda and thinking mid-term.

+ 1 year — Invisible operations

Leadership forgot what IT used to be like.

— What happened

A standardized environment, growth without drama (new sites, new users, new systems), RMM warns before things break. Technical investments in planned cycles.

— What the client feels

IT is off the CEO's radar. Proportional cost went down, the effect of good decisions repeated over time. Zulti stopped feeling like a vendor. It became part of the routine.

Continuous operations, a tailored contract. The people who run it are the people who answer you.
Book a call →
Frequently asked questions

Before outsourcing operations, every CEO asks the same things.

How a real MSP works, what's in and what's out, no fine print.

Is there a lock-in period?+
For new clients, the initial cycle is 3 months, a period to validate the fit, with setup concentrated in it (the same 90 days described in "The first 90 days"). After that, the contract moves to 12 months, the MSP market standard, with one difference: you can leave at any time, with 30 days' notice and no penalty. Zulti doesn't need to lock clients in. Most have been with us since their first contract.
What if I want to leave?+
You can leave at any time after the first 3 months, with 30 days' notice, no penalty. The 30 days are for an organized transition: Zulti hands over the whole environment, documented (inventory, credentials, configurations, contracts, incident history), transitions with whoever takes over (in-house or another MSP) and keeps operating until the last day. The idea is that clients own what is theirs, not forced dependency. And no disappearing on the last day.
I already have an in-house IT technician. Does an MSP make sense?+
Yes, it's one of the most common models. Your technician handles what's closest, and Zulti adds hours (Tier 1 and/or Tier 2) to cover what they can't handle alone: peak periods, support outside their hours, technical specialties (servers, networks, virtualization) and running the RMM on the servers. Sizing is agreed together: what makes sense to keep in-house and what makes sense to hand to Zulti.
How does day-to-day communication work?+
All support happens through a ticket, no unrecorded "quick favors". The channel is email or WhatsApp (a single team number, not an individual agent's), and the ticket opens in Zulti's own service desk, where everything is documented: request, response, attachments, resolution and a visible timeline (what happened, how long it took and who solved it). Occasional exceptions (a real emergency, a quick operational question) are fine, but a ticket is opened right after to keep the history.
Do you serve clients outside Piracicaba?+
Yes. The vast majority of tickets are solved remotely (RMM, service desk, secure access to environments), so the client's location rarely matters. Zulti serves clients in Piracicaba, across São Paulo state, in São Paulo city and in other Brazilian states. On-site presence happens when it makes sense (initial setup, a critical situation that requires being there), agreed in the contract with a clear scope. The team is based in Piracicaba, São Paulo.
Who it's NOT for

There are cases where
in-house IT fits better.
And we'll tell you when.

Commercial honesty has kept us going for almost a decade. If you fit any of the scenarios below, it's worth looking elsewhere. Zulti isn't the right partner for that case.

✕
You need a fixed 24/7 on-call human team (structural, not occasional). Zulti provides human support during business hours and runs occasional on-call shifts agreed in a separate proposal, but doesn't keep fixed night shifts. For a fixed on-call model, look for a specialized provider.
✕
You prefer pure break-fix, paying only when something breaks. Zulti's MSP is a tailored monthly contract; separate one-off projects exist with their own scope, but the contract itself doesn't work per ticket.
✕
You need a high-volume end-user support (call center, 500+ tickets/month). Zulti's MSP is designed for companies that want close support, not ticket volume.
✕
Your operation is very small, with nothing critical: few devices, nothing that stops the company if it goes down, no need for RMM or operational standards. In that case, an occasional technician solves it without a structured MSP.
More from Zulti

Services designed to cover every aspect of your IT.

Next step

Operations that care are quiet. 15 minutes to get to know yours.

A direct 15-minute conversation. No off-the-shelf package, no forty-page proposal. The person you talk to makes the decisions.

or if you prefer
or tell us briefly