Make the whole cost visible.

The displayed server price is a starting line, not the complete operating budget.

Use current quotes and your own workload; this worksheet does not predict savings or sales.

Budget from stored backup data rather than assuming it equals the live website size.

A human inbox and an order-confirmation sender are different services.

Compare the included allowance, overage rule and workload—not a bare monthly number.

A staging copy still consumes resources and can share the live server workload.

Separate capacity efficiency from ownership and recovery requirements.

A client can own the commercial relationship while granting you bounded technical access.

Reselling includes incident handling, exit work and billing administration—not just a markup.

Downscaling and disk changes depend on provider and operation; do not assume a reversible slider.

Keep an add-on only when its exact capability addresses a named task or risk.

Moving bytes is only one part of a migration; your business checks and handoff still need time.

Track recurring services, their owner and exit conditions together.

A capacity assumption can start a discussion, but only representative workload evidence can size a server.