{"id":10176,"date":"2026-08-31T06:37:13","date_gmt":"2026-08-31T04:37:13","guid":{"rendered":"https:\/\/qdata.pl\/blog\/how-to-choose-managed-cloud-50-200-employees\/"},"modified":"2026-08-31T07:47:11","modified_gmt":"2026-08-31T05:47:11","slug":"how-to-choose-managed-cloud-50-200-employees","status":"publish","type":"post","link":"https:\/\/qdata.pl\/pl\/blog\/how-to-choose-managed-cloud-50-200-employees\/","title":{"rendered":"Jak wybra\u0107 zarz\u0105dzan\u0105 chmur\u0119, gdy macie 50\u2013200 os\u00f3b"},"content":{"rendered":"<div class=\"qdata-blog-tldr\">\n<h3>TL;DR<\/h3>\n<ul>\n<li>At 50\u2013200 employees you usually need <em>someone else<\/em> to run patching, backup and incident response \u2014 but you still own architecture and vendor choices.<\/li>\n<li>\u201cManaged cloud\u201d is not hosting with a logo swap: insist on SLAs, restore tests, security baselines and a named escalation path.<\/li>\n<li>Compare <strong>total cost<\/strong>: monthly fee + projects + egress + your internal time reviewing tickets.<\/li>\n<li>If a proposal cannot explain restore time, on-call coverage and who holds admin keys \u2014 keep shopping.<\/li>\n<\/ul>\n<\/div>\n<p>A manufacturing director called us last quarter with a familiar story. Revenue was growing, the ERP was creaking, and the IT manager \u2014 excellent at keeping the business running \u2014 was drowning in vendor tickets. \u201cWe need cloud,\u201d the board said. \u201cWe can\u2019t hire five DevOps engineers,\u201d the IT manager replied. Both were right. Companies with <strong>50 to 200 employees<\/strong> sit in an awkward middle: too big for \u201ca one-person IT shop\u201d, too small to fund a platform team that invents its own Kubernetes distributions on their own initiative.<\/p>\n<p>Managed cloud is often the rational answer \u2014 but the label is worn thin. Every hoster, MSP and integrator claims it. This article is for owners, CFOs and operations leads who need to compare offers without becoming cloud architects overnight.<\/p>\n<h2>What changes at your size<\/h2>\n<p>Below fifty people, a generalist plus a good MSP can still cover servers, mail and backups. Above two hundred, you often justify dedicated infrastructure roles and formal change management. In the middle band, complexity arrives faster than headcount: hybrid work, more SaaS, customer portals, maybe a warehouse system or production data \u2014 while compliance questions (NIS2, customer audits, insurance questionnaires) start landing in your inbox.<\/p>\n<p>You do not need a \u201cdigital transformation programme\u201d with steering committees that meet about meetings. You need <strong>predictable operations<\/strong>: known monthly cost, backups that restore, security that survives a serious questionnaire, and a partner who answers the phone when something breaks on a Sunday.<\/p>\n<h2>Managed cloud vs hosting vs \u201cwe\u2019ll figure out Azure\u201d<\/h2>\n<p><strong>Classic hosting<\/strong> gives you a VM or cabinet. You patch it, or you pay extra per ticket. Scaling and security architecture are mostly your problem.<\/p>\n<p><strong>DIY public cloud<\/strong> (you click in AWS\/Azure\/GCP) is flexible and can be cheap at small scale \u2014 until someone leaves the storage bucket public, nobody owns tagging policy, and three departments each spin up \u201ctemporary\u201d environments that run for years.<\/p>\n<p><strong>Managed cloud<\/strong>, done properly, means a provider operates a defined scope: baseline hardening, monitoring, backup and restore, patch cycles, incident handling within SLA, and often a landing zone or reference architecture so new workloads do not start from a blank account. You still decide <em>what<\/em> runs there and <em>what<\/em> it costs commercially; they own <em>how<\/em> it stays up and defensible.<\/p>\n<p>At QData we see the best fit when internal IT is strong on business applications (ERP, CRM, line-of-business) but thin on 24\/7 infrastructure \u2014 exactly the profile of many companies.<\/p>\n<h2>Five questions every serious proposal should answer<\/h2>\n<p><strong>1. What exactly is in scope?<\/strong> Patch management for OS only, or applications too? Database admin? Network firewall changes? List it. \u201cManaged\u201d without boundaries ends in disputes after the first outage.<\/p>\n<p><strong>2. What are the SLAs \u2014 and what happens when they break?<\/strong> Response time for severity-1, not just \u201cbest effort\u201d. Credit mechanics matter less than honesty: if they cannot do true 24\/7, say so and design escalation with your internal team.<\/p>\n<p><strong>3. When did you last restore a backup for a client like us?<\/strong> Not \u201cwe have backups\u201d. A date, a duration, a signed test report. RPO\/RTO in writing, tied to your tier-1 systems.<\/p>\n<p><strong>4. Who holds admin access?<\/strong> Break-glass accounts, MFA, PIM\/JIT if cloud-native. You should own the tenant; they operate it with least privilege \u2014 not the other way round.<\/p>\n<p><strong>5. How do you charge when we grow?<\/strong> Per VM, per workload, per project? Egress and storage growth destroy flat \u201call inclusive\u201d deals. Ask for a worked example at +30% capacity.<\/p>\n<h2>Red flags we see in RFP responses<\/h2>\n<p>Vague \u201ccloud transformation\u201d slides with no runbook. Unlimited support that somehow excludes databases, firewalls and \u201cthird-party software\u201d. No mention of data residency or subprocessors when you handle EU customer data. Proposals that list tools (Kubernetes, Terraform, AI ops) without saying who operates them day two. And the classic: monthly fee so low that migration is free \u2014 because the margin is hidden in professional services you cannot avoid.<\/p>\n<p>Another warning sign: they cannot explain what happens in the <strong>first 90 days<\/strong>. Good providers have onboarding: inventory, landing zone, backup proof, access review, then migrate workload by workload \u2014 not a big-bang weekend.<\/p>\n<h2>Compare total cost, not the cover page<\/h2>\n<p>Build a simple table. Columns: monthly managed fee, expected project days in year one, internal hours (your PM, app owners in testing), connectivity\/egress, licences you still pay directly, and exit cost if you leave. A higher monthly fee with fewer project days and a clear scope often beats a cheap base rate that invoices every change request.<\/p>\n<p>One logistics client saved money not by picking the lowest bid, but by choosing the offer that included <em>restore drills<\/em> and a single on-call path. Their previous \u201ccheap\u201d host had backups; nobody had tested restore in three years. That is not insurance \u2014 it is hope.<\/p>\n<h2>When managed cloud is not the first step<\/h2>\n<p>Sometimes the answer is boring on-prem hygiene first: AD cleanup, MFA on mail, offline backup, then migrate mail and file to SaaS, <em>then<\/em> lift a few workloads to managed cloud. If your ERP cannot tolerate downtime or your plant network is flat Layer-2 chaos, fix the riskiest items before marketing \u201cwe are in cloud\u201d.<\/p>\n<p>Equally, if you have no internal owner who can say \u201cyes, this application may move\u201d \u2014 pause. Managed cloud multiplies capability; it does not replace product owners.<\/p>\n<h2>A one-page checklist you can use Monday<\/h2>\n<ul>\n<li>Named internal sponsor (not only IT).<\/li>\n<li>List of tier-1 systems with RPO\/RTO expectations.<\/li>\n<li>Three vendor answers compared on scope, SLA, restore proof, admin model, growth pricing.<\/li>\n<li>90-day plan: onboard, prove backup, migrate one non-critical workload, review.<\/li>\n<li>Exit clause understood (data export, DNS, keys).<\/li>\n<\/ul>\n<h2>What to do next<\/h2>\n<p>If you want a second opinion on proposals you already have \u2014 or a neutral scope document before you send an RFP \u2014 our <a href=\"\/pl\/service\/cloud-services\/\">Us\u0142ugi chmurowe<\/a> team works from operations and architecture, not slideware. We help mid-market firms land managed environments they can actually run, audit and afford twelve months later.<\/p>","protected":false},"excerpt":{"rendered":"<p><span data-no-translation>Jeste\u015bcie po erze \u201eserwera w szafie\u201d, ale bez 15-osobowego zespo\u0142u platformowego. Poradnik bez \u017cargonu: co naprawd\u0119 obejmuje zarz\u0105dzana chmura, pi\u0119\u0107 pyta\u0144 do dostawc\u00f3w i jak por\u00f3wna\u0107 oferty bez informatycznego dyplomu.<\/span><\/p>","protected":false},"author":1,"featured_media":10158,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10176","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-guides"],"_links":{"self":[{"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/posts\/10176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/comments?post=10176"}],"version-history":[{"count":2,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/posts\/10176\/revisions"}],"predecessor-version":[{"id":10180,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/posts\/10176\/revisions\/10180"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/media\/10158"}],"wp:attachment":[{"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/media?parent=10176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/categories?post=10176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qdata.pl\/pl\/wp-json\/wp\/v2\/tags?post=10176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}