A design practice is the case where per-user pricing fits worst. The cost sits in the workstation and the file store rather than in the person, and a practice of twelve can run more compute than an office of eighty. Of the 29 providers read for this record on 10 September 2026, seven publish a per-seat figure and six of those seven count by user. Only Powerful IT counts by machine, publishing $75 per workstation per month, $125 per server and $150 per location.
In architecture IT support, the unit decides whether the quote makes sense
Ask a provider to price a practice by user and it will quote the median shape of this record, which is $99.50 a user a month across the seven published figures, against a business whose real load is eight rendering machines, a model server and a file store measured in terabytes. The same practice quoted by machine looks entirely different. Powerful IT is the only provider in this record that publishes that structure in full, at $75 per workstation per month, $125 per server and $150 per location, and the value of it here is not that it is cheap but that it names the three units a design office actually consumes. Where a provider insists on a per-user rate, ask it in writing which of the workstations, servers and storage that rate covers and what is billed separately.
Workstations, specification and who owns the refresh
CAD and BIM machines are specified against the software vendor's requirements and the size of the models the practice actually opens, not against an office standard. Two questions settle most of the argument. First, who writes the specification, because a provider that supplies hardware on a standard office build will supply machines that open a model slowly and then treat the complaints as support tickets. Second, who owns the refresh cycle and its budget, because a five year replacement plan on a design workstation and a five year plan on a reception desktop are different amounts of money and only one of them is normally in a managed contract. Get the refresh out of the monthly fee and into a named schedule with dates, or get it explicitly excluded so the practice plans it itself.
The project file store, and whether it can live in a cloud at all
Project files are large, they reference each other by path, and design software opens them across the network rather than copying them down. That combination defeats a consumer file sync product, and it is where a cheap quote usually hides. The question to put to a provider is not whether it supports cloud storage but what it proposes for a live model file of the practice's actual size opened over the practice's actual connection, and what happens to linked references when the path changes. Ask for the answer as a design with a named product, a location for the data and a stated restore time, and ask separately what the backup covers, because a versioned archive of finished projects and a live working store are two different jobs with two different costs.
Licence servers and the consultants who are not your users
Design software is frequently licensed through a server that hands out seats, and when that server stops the practice stops with it, usually on the afternoon of a deadline. The contract has to say who patches it, who monitors it, who holds the vendor relationship and what the recovery step is, and it is reasonable to ask for that written down as a procedure rather than as a promise. Model coordination is the other access problem. Engineers, contractors and other consultants outside the business need to reach current models without becoming billable users of the practice's estate, so ask how external access is provided, how it is removed at the end of a stage, and whether those accounts are counted in the seat total.
Engineering IT support: deadline economics and what a response commitment has to say
An outage in an ordinary office costs a day of productivity. An outage in the week a package is due costs a fee stage, and possibly the relationship with the client who set the date. That asymmetry belongs in the response commitment: a stated number of hours to a first engineer, a named escalation to a person rather than a queue, and a written answer to what happens when the commitment is missed. Ask also about deadline weeks specifically, because a practice knows its submission dates months ahead and a provider that can accept a scheduled freeze on changes during those weeks is worth more than one promising a faster ticket. No provider in this record publishes a service credit or an out of hours rate, so both are quote questions rather than published facts.
Questions people ask about IT support for architects
Should a design practice be quoted per user or per workstation?
Per workstation is the better fit, because the cost is in the machines and the file store rather than in headcount. Six of the seven providers publishing a figure in this record count by user, and only Powerful IT counts by machine, at $75 per workstation per month, $125 per server and $150 per location.
Does any provider publish a rate for architecture or engineering practices?
No. Not one of the 29 providers read for this record publishes a rate specific to design practices. What exists is general per-seat publishing by seven of them, running from $10 a user a month to a band topping $300, with a median of $99.50.
Can project files live in cloud storage?
Sometimes, and it depends on file sizes, linked references and the office connection rather than on the provider's preference. Ask for a proposal naming the product, where the data sits and how long a restore takes, and treat the live working store and the archive of finished projects as two separate requirements.
How should external consultants get access to models?
Through a named mechanism that grants access to project data without creating an ordinary user account in the practice's estate, with removal at the end of a stage written into the process. Confirm in writing whether those accounts count towards the seat total on the invoice.
Are IT services for engineers priced the same as for an office?
They should not be. The cost sits in the workstation, the licence server and the project file store rather than in the person, so a per-user quote for a practice running heavy compute is the wrong unit before it is the wrong number.