Size Cloud Storage for Two Years Without Wasted Headroom

Zectron SEO

Published 6 November 2026

Most SMB cloud bills do not balloon in one dramatic purchase. They drift upward in unused gigabytes, oversized mailboxes, and spare capacity bought for a worst case that never arrived. With running costs already under pressure for many small businesses, idle headroom is a quiet tax on growth.

This guide shows you how to replace guesswork with evidence. Rather than buying for a hypothetical peak, you will size storage to measured demand (file volume, mailbox size and peak concurrency) and document a written scale-up trigger, so the decision to move tiers is deliberate, timely and defensible.

It focuses on capacity planning: how much storage and infrastructure to buy for the next two years. If you are still choosing a platform or weighing where your data should be hosted, start with our guide to business cloud storage in Australia, then come back here to size it.

You will learn why headroom is a decision, not a default; what to measure before you buy another gigabyte; how to complete a two-year sizing worksheet step by step; and how a sample 25-person office applies it. We also cover writing your scale-up trigger, spotting the signals that say move tiers now, avoiding the headroom trap, and turning the worksheet into a managed plan.

Why Headroom Is a Decision, Not a Default

Idle capacity competes with wages, insurance and marketing for the same dollar, yet it is rarely reviewed once it is on the invoice.

You can check your own position in ten minutes. Pull your last three invoices, compare provisioned capacity with peak usage, and note the gap. That gap is what you are paying for and not using.

Headroom usually accumulates in three ordinary ways: a migration sized for 100 users when the business had 40, a tier upgrade triggered by one busy month and never revisited, or a reseller bundle padded for a growth curve that never eventuated.

Headroom should be a decision with a number and a date attached, not a default setting. This guide gives you both: a two-year sizing worksheet and a written scale-up trigger.

What to Measure Before You Buy Another Gigabyte

Start with numbers that describe your business, not a vendor’s benchmark. Six inputs do the work.

File volume growth. Export 6 to 12 months of consumed storage from backup reporting or file-share tooling, then calculate gigabytes added per month. Strip out migrations, bulk imports and legacy archives so the trend reflects real growth, not a project spike.

Mailbox size trajectory. Record average mailbox size, growth per user per month, and what archiving removes. For example, 2GB per user per year across 30 staff is 60GB a year, which may be small next to the cost of a tier jump. If you are on Microsoft 365, mailbox and OneDrive reports give you these figures; our Microsoft 365 service can help you read them.

Peak concurrency. Measure simultaneous users and connections at your busiest hour, such as Monday morning, month-end close or end of financial year. Seat count alone inflates projections.

Non-file workloads. Databases, point of sale, accounting platforms and eCommerce checkouts during sales are sized by throughput and response time, not raw gigabytes. Count them separately or they distort your storage number.

Multipliers. Backup copies, snapshot frequency, version history and long retention can push stored data well above the raw source data. Work out your own multiplier from your backup reports rather than assuming an industry figure. Our guide to simple backup and recovery plans explains which copies you actually need.

Access and retrieval patterns. Track how often data leaves the platform and how that is billed. Many providers charge egress and retrieval separately, so a cheap storage tier can cost more if your team restores often.

Documented, these six figures give you a defensible basis for the projection that follows.

The Two-Year Sizing Worksheet, Step by Step

Once measured, those numbers become a decision. Work the worksheet in this order, and keep the whole thing to one page.

1. Baseline current usage. Export at least six months of consumed storage. Record the average and the highest observed figure: peak sizes performance, average sizes capacity.
2. Calculate monthly growth. Take current consumption minus consumption six months ago and divide by six. Express the result in gigabytes per month and as a percentage of current usage, using your own platform figures.
3. Project 24 months. If growth is a steady number of gigabytes each month, multiply it by 24 and add it to today’s figure. If growth is rising as the business grows, compound it instead: current gigabytes multiplied by (1 plus your monthly growth rate) to the power of 24. When you are unsure which pattern applies, run both and plan to the higher figure.
4. Apply multipliers. Multiply the projection by your backup, versioning and retention factor from step one, then add a buffer based on how long it actually takes your provider to deliver an upgrade. Resist the habit of simply doubling the number.
5. Map to a tier and price both sides. Find the tier your projection fits under, price the tier above and the tier below, and write down the dollar difference. That gap is your headroom bill, stated in dollars.
6. Make it a living document. Re-run the worksheet quarterly with fresh figures, and again straight after any hiring round, system migration or acquisition, because those events reset the growth rate rather than extending the old trend.

Keep the one-page record to current GB, monthly growth, 24-month projection, multipliers, buffer, target tier, adjacent tier prices and next review date. Anything longer will not be maintained.

Worked Example: Sizing Storage for a 25-Person Office

Consider a hypothetical 25-person professional services office with a 1.4TB file share growing steadily at about 18GB a month, plus 25 mailboxes that have never been archived.

The maths. Eighteen gigabytes a month over 24 months adds 432GB, taking the file share to roughly 1.83TB. Apply a measured retention and snapshot factor, in this example 1.5x, and the working figure is about 2.75TB. That is the number that should drive the decision, not the file share alone. Mailbox volume needs the same treatment: record-keeping rules require businesses to retain many records for five years, so unarchived mail tends to accumulate rather than recede.

The conclusion. This office does not need a 5TB bundle. It needs a 3TB tier with a written trigger set at a sustained usage level that suits its upgrade lead times, in this example around 85% of provisioned capacity. That keeps roughly 250GB of genuine margin at the end of the period while flagging the upgrade well before capacity forces it.

The contrast. Suppose the same office had been sold a 5TB bundle sized for a much larger future headcount that no hiring plan supported. The difference between projection and purchase is the headroom bill, now a figure the owner can take to their accountant.

The lesson translates directly to your own numbers. The worksheet does not make you buy less. It makes you buy a specific amount for a specific period, with evidence you can defend at renewal.

Writing Your Scale-Up Trigger So You Never Guess

With a projected figure in hand, the trigger becomes arithmetic rather than judgement. The thresholds below are sensible starting points; adjust them to match your contract lead times and growth rate.

Set the threshold on sustained usage, not a single reading. For example, if usage holds above 80% of provisioned capacity for two consecutive months, you act. One busy day at 92% is noise, not a case for a permanent tier change.

Define a harder threshold for emergency action. For example, at 95% sustained, buy temporary burst capacity or accept a short-term overage while the permanent upgrade is arranged, so nobody is firefighting at midnight.

Name the owner and the escalation path in writing. Usually that is the operations or office manager working with your IT provider, so scaling arrives as a planned action with a purchase order behind it rather than a surprise invoice.

Match the review cadence to your renewal cycle. The quarterly worksheet re-run described above should land well before each renewal date.

Understand the contract before you need it. Check minimum terms, mid-term upgrade rules, downgrade options, notice periods and any fees for changing tiers. A provider that makes downgrades hard has effectively locked in your headroom.

Record the trigger on one page stored with your asset register: metric, threshold, action, owner and review date. A trigger that lives only in someone’s head is not a trigger.

The Signals That Say Move Tiers Now

With the trigger documented, the harder task is recognising when it has actually fired. Read these signals together rather than in isolation.

1. Sustained capacity above your threshold for two consecutive review periods. Take the reading from platform reporting, not from user complaints. Users rarely report filling a quota; they report the symptom after it hurts.
2. Backup windows that no longer complete. Jobs that used to finish overnight now overrun into the working day. That often means the platform is near capacity before any dashboard turns red.
3. Restores slowing, or failing outright. A restore that fails for lack of working space is the most expensive warning sign here, because it surfaces mid-incident when you have the least room to negotiate.
4. Slowdowns at peak concurrency. Slow logins, file locking, timeouts and sync conflicts clustering in your busiest hour point to performance limits rather than raw capacity.
5. Egress and retrieval charges climbing as a share of the monthly bill. Rising retrieval spend means your access pattern no longer matches your tier, even when stored volume looks comfortable.
6. A known event on the six-month horizon. A hiring round, a new practice management or ERP system, a digitisation project or an acquisition all reset your growth rate. Bring the review forward deliberately rather than reacting afterwards.

One signal is a conversation. Three is a decision.

When Not to Scale: Avoiding the Headroom Trap

A trigger tells you when scaling is justified, not that you must buy. Several situations look like growth but are not, and each is cheaper to handle without a permanent tier change.

Seasonality is not a trend. End of financial year, Christmas trade and single large projects spike usage and then recede. Cover those with a temporary burst plan or short-term overage, never a tier you pay for all twelve months.

Hypothetical headcount is not a plan. Without an approved hiring schedule and a date attached, capacity sized for that future is the definition of paying for headroom you never use.

Clean up before you upgrade. Duplicate files, orphaned accounts, departed staff mailboxes and obsolete backup sets can often reclaim a meaningful share of consumed capacity. Measure the reclaim first, then decide whether you still need the tier.

Diagnose the constraint. Capacity, performance and egress cost are three different problems with three different fixes. A tier upgrade addresses only the first, so confirm which one you have before spending.

Treat prepay discounts with scepticism. A discount on capacity you do not need is still a loss, and long prepay terms can lock in a size you want to reduce within twelve months.

Do not accept a provider’s recommended tier as the answer. Request the underlying usage data, run your own worksheet against it, and ask for the recommendation to be expressed as a number with a date attached.

Run each proposed upgrade through these six tests before you approve it.

Next Steps: Turn the Worksheet Into a Managed Plan

Knowing when not to scale is half the discipline. Keeping the model alive is the other half.

Run the worksheet this quarter using six months of real consumption data, then write down the dollar gap between your projection and your current tier. That figure is your opening position at the next renewal conversation.

File the one-page trigger with your asset register, and line up the quarterly worksheet review with your renewal dates so every renegotiation arrives with data.

Sizing cloud storage for two years is not about buying maximum headroom. It is about making headroom a deliberate choice, so every gigabyte you buy is one you planned to use.

Talk to Zectron. If maintaining the model is beyond your team’s capacity, our Norwest team can baseline your usage, build the two-year projection and run the review cadence as part of our managed cloud services. Book a free IT Health Check or call 1300 133 770.