1. Define demand
Describe outcomes, scope, volume, complexity, roles, and dependencies.
Managed-service planning tool
Configure a practical managed service before procurement begins
Translate outcomes, scope, workload, coverage, controls, service levels, and commercial preferences into an indicative service model, staffing profile, governance cadence, and transition plan.
Transparent and non-binding. Results depend on user-supplied information. No external API or fabricated live data is used.
How it works
2. Set conditions
Choose coverage, SLA, governance, security, compliance, and reporting.
3. Review
Assess effort, staffing, risks, assumptions, exclusions, and consultation questions.
Configure the service
Methodology, limitations, and responsible use
Methodology
Effort starts with a non-linear volume baseline, then adds scope, roles, tools, integrations, locations, languages, and dependencies. Multipliers reflect complexity, coverage, security, governance, and capacity.
How to use the result
Use it for an RFP, business case, vendor briefing, discovery agenda, or service design workshop. Validate demand, seasonality, rework, incidents, dependencies, and controls before fixing capacity or SLAs.
Limitations
The calculation excludes pricing and cannot infer hidden technical debt, undocumented processes, data sensitivity, stakeholder responsiveness, or change complexity.
Data-quality notice
Confidence reflects input completeness and complexity signals only. It is not a statistical prediction or guarantee.
Related tools
Frequently asked questions
Is this a binding quote?
No. It is an indicative planning output requiring discovery and commercial validation.
How should volume be defined?
Use one consistent unit such as tickets, reports, pipelines, datasets, models, or cases.
Why use a non-linear volume factor?
It reflects some scale efficiency while retaining management, quality, and exception effort.
What does the risk score mean?
It is a planning indicator, not a certification or probability of failure.
What does confidence mean?
It indicates input completeness, not accuracy.
Can this configure 24×7 service?
Yes, but final design must define severity, on-call, handover, escalation, maintenance, and communications.
How should compliance be handled?
Map obligations to controls, evidence, owners, retention, access, incidents, subcontractors, and audit rights.
What is included in staffing?
An indicative role mix; seniority, shifts, location, leave cover, and segregation require further design.
Why is there an effort range?
It provides tolerance while rework, technical debt, exceptions, and dependency delays are validated.
Can I export the result?
Yes. JSON, CSV, and print outputs are generated locally in the browser.
Does the page store information?
No persistent storage is implemented.
What should happen before procurement?
Validate baselines, scope, ownership, systems, controls, dependencies, acceptance, SLAs, reporting, commercials, and exit provisions.