Keep the environment dependable between projects.
Managed Technology gives your organisation a written operating boundary for support, monitoring, maintenance, supplier coordination and continued improvement.
Sufrone accepts defined responsibility—so the next incident, request or maintenance decision has a known channel, owner and escalation path instead of another informal message.
No universal 24/7 promise: support hours, response targets, onsite work and exclusions remain written terms.
- Planning entry
- From KSh 25K/month
- Billing cadence
- Monthly in advance
- Service rule
- Hours, targets and exclusions are written
When something breaks, the next owner should already be clear.
Choose an example to see the operating pattern. The exact authority, response target and escalation route are always determined by the accepted agreement.
A user cannot reach an important system.
The support path should begin with a defined channel and enough context to verify the user, the affected system and the business impact.
Actual response targets, supported users, access authority and after-hours handling are set in the agreement.
- 1Receive
Record the request through the agreed support channel.
- 2Triage
Verify scope, identity, priority and the affected service.
- 3Resolve or escalate
Act within the accepted authority or coordinate the responsible supplier.
- 4Close with evidence
Record the outcome, remaining risk and any follow-up work.
Choose by responsibility, not organisation size.
The tiers are planning signals for increasingly broad operating ownership. They are not checkout packages: final scope follows the environment, service expectations and responsibility Sufrone accepts.
- 01Managed Essential
Essential monitoring, maintenance and support for a bounded environment.
Planning rangeFrom KSh 25K/month - 02Managed Business
Broader operational ownership across users, endpoints, systems and suppliers.
Planning rangeKSh 40K–50K/month - 03Managed Operations
High-touch managed operations for complex, multi-system or multi-site environments.
Planning rangeKSh 60K–100K+/month
What changes the monthly fee.
These factors change the environment Sufrone must operate and the level of responsibility the agreement must define.
- Users
- Endpoints
- Sites
- Servers and cloud services
- System complexity
- Response expectations
- On-site requirements
Responsibility is accepted line by line.
Depending on the accepted environment, Sufrone can continuously own these operating responsibilities rather than leaving them between projects or individual suppliers.
- Remote support and technical escalation
- Infrastructure, server and backup monitoring
- Patching, account and endpoint administration
- Vendor coordination and incident management
- Preventative maintenance and monthly reporting
- Quarterly technology and improvement reviews
- Advantage Engine care where it forms part of the managed environment
The agreement removes the grey areas.
A tier name does not replace written boundaries. The accepted agreement records what is covered, how service operates and where another owner or project begins.
- Covered environment
- The users, endpoints, sites, systems, servers, cloud services and suppliers inside scope.
- Service operation
- Support channels, operating hours, request priorities, response targets and escalation paths.
- Onsite and emergency work
- Visit expectations, emergency handling, after-hours coverage and related charges.
- Responsibility boundary
- Exclusions, client dependencies, third-party control and work that requires a separate project.
Support becomes an operating rhythm, not a rescue call.
The cadence keeps evidence, incidents, maintenance and improvement connected without implying every environment receives the same hours or response model.
- 01
Observe agreed signals
Keep the systems, services, infrastructure and backup evidence named in scope visible.
- 02
Respond through one path
Route requests and incidents through the defined channel, priority and escalation model.
- 03
Report the evidence
Summarise support activity, service concerns and maintenance evidence each month.
- 04
Improve deliberately
Use quarterly reviews to turn recurring issues and changing needs into an agreed roadmap.
Start with the environment you want someone to own.
Tell us which systems, users, sites and suppliers are involved, what repeatedly fails and what support exists today. We will recommend a responsible boundary before proposing a tier.