Describe the arrival pattern
Monthly volume matters, but bursts can matter more. Record typical request size, peak periods and how long work can wait before it affects customers.
- Typical volume
- Peak arrivals
- Waiting tolerance
Workload calculator
Explore the time.
Understand the assumptions.
Use an adjustable model to discuss potential scope. The result is an illustration of task-handling time, not a savings promise.
Interactive workload model
Make the assumptions.
See the difference.
Illustrative arithmetic, not a forecast or a client result. Adjust the inputs to explore task-handling time. Setup, monitoring and exception effort are excluded.
Formula: tasks × minutes ÷ 60 × automatic share. This assumes the selected share needs no manual handling. Actual savings require measurement.
60%modelled share
120hours potentially released / month
80hours of manual task handling remain
200 baseline hours · 120 potentially released · 80 remaining.
Capacity planning
Count the work behind the headline.
A client count alone does not describe a workload. Use the calculator above alongside the factors below to scope and test the service.
CAPACITY PLANNING / CONCEPT MAP
Conceptual structure · Explore the detail below
Include the hidden effort
Retries, long documents, multiple system calls and manual exceptions all consume capacity. Separate routine tasks from unusually expensive or consequential work.
- Task complexity
- Provider limits
- Exception effort
Leave room to operate
Allow for monitoring, backups, maintenance and recovery. Assess the actual deployment with representative workloads before promising a particular number of customers.
- Operating headroom
- Load testing
- Upgrade triggers
Useful details
Before the next step.
Can the VPS support a fixed number of clients?
There is no reliable fixed client count without knowing the workload. A small number of intensive workflows can demand more capacity than many light ones.
Keep exploring
Delivery approach ↗Prepare your inputs ↗Start a written brief ↗