Managed services and project work are different jobs

Small businesses often buy "IT" as one blob. Something breaks, someone is called, and if a migration is needed it gets squeezed into the same relationship with no scope. Projects stall that way. Monthly service turns into a pile of unfinished changes.

Zesyo separates the two on purpose.

Managed services

Managed services are the environment as it is. Monitoring, administration, support, and the judgment to leave a stable thing alone.

The deliverable is continuity. Next quarter, someone who already knows the tenant is still there. Users, groups, policies, and the ordinary questions have a place to go. The hours and the response target are written down, because a very small company and a mid-size company do not need the same clock.

Professional services

Professional services are a change with an edge. A migration. A new tenant. A hardening pass. An identity cleanup. A review of Azure or AWS cost.

The deliverable is an outcome and a point at which the project is done. The scope says what is in and what is not. When the scope is finished, the project stops. It does not linger inside a monthly invoice under a vague name.

How to tell which one you need

• If the question is "who is watching this next quarter," that is managed services.
• If the question is "can we move, lock this down, or stop paying for that," that is a project.
• Most companies need both. They still should not be the same sentence. The project builds the thing the managed service then keeps.

If you cannot tell, say that. Sorting the question is part of the first conversation, not a fee for failing a quiz.

What this site will not pretend

A response time does not belong on a marketing page. Coverage is part of the agreement. Named customers do not belong here until they have agreed to be named. A rate card does not belong here until Zesyo chooses to publish one.

The descriptions of the work live on the services page. A note, if you want one read by a person, goes through contact.