Sizing and architecture
NAS or SAN selected on capacity, performance and how it will be accessed.
Raw disk totals mislead. We size on usable capacity after protection overhead, against the performance your applications need and the growth you expect, so the first expansion is planned rather than forced.

This distinction causes more data loss than any technical failure. RAID keeps a volume online when a disk dies. It does nothing about accidental deletion, file corruption, ransomware or the loss of the array, the rack or the building. Every storage design we produce treats protection and backup as two separate requirements with two separate budgets.
NAS or SAN selected on capacity, performance and how it will be accessed.
RAID levels and storage pools configured deliberately, with the trade-offs explained.
Shared folders with role-based permissions rather than inherited sprawl.
Disk health and utilisation tracked, with alerts before thresholds become incidents.
Replication to a secondary location where the recovery requirement justifies it.
Where remote access to storage is required, configured without exposing it to the internet.
For most organizations of this size, a well-specified NAS is sufficient and far simpler to operate. SAN becomes worth its complexity when you have virtualization hosts needing shared block storage or performance requirements a NAS cannot meet. We will say plainly which applies.
It depends on capacity efficiency, rebuild risk and the performance profile. With large drives, rebuild times matter more than people expect, which affects the answer. We explain the trade-off rather than defaulting.
Less than the raw total, and the design states the real number. Protection overhead, filesystem overhead and the headroom needed for performance all reduce it.
Tell us roughly how much data you hold, how fast it grows and what has to be kept.
Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.