AutoCAD and Revit workstation support for Dallas architecture firms

The short answer: yes, I support AutoCAD and Revit workstations in Dallas

I am Anthony Omini, owner of Cross River Tech, a small managed IT company in Dallas, and the person you deal with when you call. Architecture and design firms are one of the industries I work with most. That means the everyday reality of AutoCAD, Revit, SketchUp, Rhino, Enscape and the rest: workstations that used to be quick and are not anymore, a central model that takes ten minutes to sync, a rendering that locks up the one machine everyone shares, and licensing that somehow never matches who is actually sitting at the desks.

If your workstations are slow, the honest first answer is that the cause is almost always one of a short list of things, and most of them are cheaper to fix than a new computer. I go through that list below. If you are buying or upgrading, I describe what a drafting, BIM or rendering machine should have in general terms, without tying you to a particular brand or a marketing label. And because a CAD workstation is only as fast as the server and the cable behind it, I cover the network too.

Two things set my support apart for a design firm. First, I stay your point of contact for everything, so the person you call about a Revit crash on Tuesday is the same one who planned the file server and pulled the cable, with my team handling the routine monitoring and updates behind me. Second, I am honest about what needs money and what does not. If a memory upgrade will do, I will not sell you a workstation. You can read how I work with firms in general on the IT support for architecture and interior design firms page, or describe the slowness you are seeing and I will tell you what I suspect.

Why are our workstations so slow? The usual suspects

When a firm tells me every machine feels slow, I check the following in this order, because this is the order in which they turn out to be the cause. You can check several of them yourself.

1. Not enough RAM. Revit in particular loads the whole model, plus every linked model, into memory. A machine that was fine with 16 GB on small projects will crawl and swap to disk on a large hospital or multifamily model. Look at Task Manager while Revit is open: if memory sits near the top, this is your answer.
2. A spinning hard drive, or a slow SSD. Older workstations and cheaper builds still ship with mechanical drives or slow SATA SSDs. Moving the operating system and the local working files to an NVMe drive is the single biggest quality-of-life upgrade for the money.
3. Project files in the wrong place. Central models, Xrefs and sheet sets sitting on a consumer NAS, a synced OneDrive folder, or reached over Wi-Fi. The workstation is waiting on the network, not on itself.
4. A GPU that was never meant for this. Integrated graphics or an old card can make orbiting a 3D view feel sticky, and real-time renderers will refuse to run properly.
5. Something in the background. Antivirus scanning every file Revit touches, a cloud sync client indexing the project drive, a backup agent running during work hours, or Windows deciding to update at 2 PM.
6. Heat. A workstation full of dust throttles its own CPU. It is not glamorous, but it is real.
7. Age. Sometimes a machine has simply reached the end. A CPU from many generations ago with maxed-out RAM is not going to keep up with current Revit releases.

The fix for most firms is a mix: a few targeted RAM and NVMe upgrades, exclusions in the antivirus for CAD file types and project folders, updates scheduled for nights, and moving active project files onto a proper wired file server. That combination costs far less than replacing the fleet and usually feels like getting new machines.

What should an AutoCAD or Revit workstation actually have?

Every vendor publishes minimum requirements, and every experienced drafter knows the minimums are a joke. What matters is how the software really behaves. AutoCAD and Revit are still largely single-threaded for the everyday work of modeling and drafting, so a CPU with high per-core speed beats one with many slower cores. Rendering, on the other hand, uses every core and every bit of GPU it can find. Here is how I spec machines in general terms, by role.

A few notes on that table. Video memory matters more than raw GPU speed for real-time renderers working with large models and high-resolution textures; running out of it makes everything stall. For Revit, the difference between a modest and an expensive graphics card is small for modeling and large for rendering, so do not overspend on the GPU for a drafter who never renders. Two monitors are standard; a third is common for people who live in Revit schedules and sheets. And every machine gets a battery backup, because a power blip during a Revit save is how central models get corrupted.

I work with Dell and Lenovo business lines and I will spec from either. What I will not do is tell you a particular badge or marketing tier is required, because for most architecture work it is not.

Rendering: on the workstation, a render box, or in the cloud?

Rendering is where CAD-heavy firms burn the most time and money without noticing. The pattern is familiar: one designer starts a high-quality render, their workstation is unusable for an hour, and the whole studio has learned to schedule around it. There are three ways out, and the right one depends on how often you render and at what quality.

Render on the workstation. Fine for real-time tools like Enscape and Twinmotion, which are built to give designers an immediate view rather than a final image. The workstation needs the GPU and video memory from the table above, and that is the end of it. Most small firms live here.

A dedicated render machine. When final-quality stills and animations are a regular deliverable, a single powerful machine in the office that takes render jobs from everyone pays for itself in freed-up designers. It sits on the wired network, has the biggest GPU in the building, and nobody sits at it. I set these up with remote access so a designer can start a job from their own desk and check on it later.

Cloud rendering. Several of the rendering products offer cloud rendering, and general cloud GPU machines can be rented by the hour. This is a good answer for a firm that renders in bursts, such as competition week, and does not want hardware idle the rest of the year. The costs are per job or per hour, so they need a little discipline, and uploading a large scene takes time on a slow connection.

Whichever you choose, the goal is that a rendering never holds a designer hostage. Talk to me about how often you render and how big the scenes are, and I will tell you which option fits, with an honest view of the hardware cost involved. Sometimes the answer is a modest upgrade to one existing machine and a schedule, not a purchase at all.

The network matters as much as the box

Here is something that surprises firms: the fastest workstation in Dallas will feel slow if it opens its models across a weak network. Revit worksharing keeps a central model on the server and each designer works on a local copy, synchronizing changes back and forth. AutoCAD Xrefs pull in referenced drawings live. Both patterns punish latency and small drops in throughput far more than an office full of spreadsheets ever would.

The rules I apply for a design office network:

• Wired, always, for CAD seats. Wi-Fi is for phones, laptops in the conference room and visiting consultants. A designer syncing a central model over Wi-Fi is asking for a corrupted file.
• Gigabit to every desk as the floor. For firms with large models and frequent syncs, 2.5 Gb to the desktop and 10 Gb to the file server is a sensible step up, and the cost difference at build-out time is modest.
• The file server on fast storage and a fast uplink. A server or NAS with SSD storage, or at least SSD caching, connected to the switch at 10 Gb, so five designers syncing at once do not queue behind each other.
• Cabling that was actually tested. A Cat6 run that was terminated badly will negotiate down to a slower speed or drop packets, and the symptom looks exactly like a slow computer.

For firms spread across offices or with people working from sites and home, Autodesk's cloud collaboration for Revit is often the honest answer for the central model, with the office server for everything else. I go into server and storage choices in the article on file servers, shared storage and backups for design firms, and I run the cabling and switching myself through my data cabling and IT room setup service, so when a firm tells me a workstation is slow, I can look at the whole path instead of just the computer.

Autodesk licensing without the headaches

Autodesk moved to named-user subscriptions some time ago, which is simpler than the old serial numbers and network license servers, but it still produces a steady trickle of problems in small firms: a new hire cannot open Revit, a departed employee still holds a seat, the renewal lapses on a Friday, or nobody knows which email address the account is under. All of it comes from the same root cause: nobody clearly owns the admin account.

What I do for the firms I support is take that role. One admin account, with your ownership, two-factor protected, with me as the day-to-day administrator. New hires are assigned a seat on their first morning; departures release one the same day. Renewals go on a calendar with a reminder well ahead. I keep a simple record of who has AutoCAD, who has the full Architecture, Engineering and Construction collection, and who only needs a viewer, so you are not paying for full seats for people who open a drawing once a month.

The same approach covers the rest of the software stack a design firm accumulates: Bluebeam for markups, Adobe Creative Cloud for presentations, SketchUp, Rhino, Enscape or Twinmotion, and the various plugins. Each one has its own portal and its own renewal date. Getting them all into one list with one owner is unglamorous and saves a surprising amount of money and frustration. If you use a reseller, I am happy to work through them; if you buy direct, I handle it in the portals.

One rule I hold firmly: I do not touch a firm's licensing in a way that could lock people out on a deadline. Changes are made at quiet times and confirmed with a test login before anyone goes home.

Updates, drivers and managing Revit versions across projects

Revit has a habit that people outside architecture do not understand: a project stays on the Revit version it started in. Upgrading a central model to a newer release is a one-way step that every consultant on the project has to take together, so a firm with several active projects is routinely running two or three Revit versions side by side. That is normal, and it is fine, as long as nobody lets an automatic update quietly change a machine.

My approach is boring on purpose. Autodesk updates are set to notify rather than install. Windows updates run on a schedule at night, with a reboot, and never during the working day. Graphics drivers are updated deliberately, on one machine first, then the rest, because a driver update is the most common reason a rendering tool suddenly misbehaves. Antivirus is configured with exclusions for CAD file types and project folders so it stops scanning a 400 MB model every time it is saved.

When a project does move to a new Revit release, I make sure the version is installed on every machine that needs it before the upgrade day, the add-ins that team relies on are compatible, and the old version stays put for the projects still on it. When a project closes, the old version stays until the archive is confirmed, then goes.

The result is that your designers stop being part-time IT people. A Revit crash still happens now and then, because Revit, but the environment around it stays consistent, which is most of what stability means in a design office. All of this is standard work inside my managed IT services, where updates for computers and servers are part of the monthly fee.

Buy new or upgrade? Dell and Lenovo workstations in a design firm

Not every slow workstation needs replacing, and not every old one is worth saving. The test I use is simple. If the machine has a CPU from the last few generations, it is almost always worth upgrading: RAM to 32 or 64 GB, an NVMe drive for the system and working files, and a better graphics card if rendering is the complaint. Those three changes together cost a fraction of a new workstation and can be done in an afternoon.

If the CPU itself is the bottleneck, which shows up as Revit being slow even with plenty of free memory and a fast drive, it is time to replace the machine. Motherboards, memory generations and power supplies change together, and chasing a CPU upgrade in an old chassis rarely ends well.

For new purchases I spec from the Dell and Lenovo business and workstation lines, with next-business-day onsite warranty, and I set every machine up before it reaches the desk: operating system clean, software installed, licensing assigned, security tools enrolled, monitors and dock working, and the designer's profile and settings migrated. Site-visit laptops are a separate conversation: a mobile workstation that can genuinely run Revit is heavier and dearer than an ordinary laptop, and many firms do better with a strong desktop plus a light laptop that remotes into it from the site.

Whatever you decide, I put together a written plan showing which machines to upgrade, which to replace, and in what order, so the spend is spread across quarters rather than landing all at once. I describe how I handle business computer purchases and support more generally in buying and supporting Dell and Lenovo business computers.

How I support a CAD-heavy firm in Dallas

Most architecture and design firms I work with are between five and forty people, somewhere in Dallas or the surrounding metroplex, with a mix of desktop workstations, a couple of laptops, a file server or NAS, a plotter that everyone hates, and a lot of software. Here is what working with me looks like.

Per device, month-to-month. For a design firm I usually quote managed IT per device rather than per user, because a workstation with a big model on it takes more looking after than a laptop that only runs email. The plan includes updates, unlimited remote support, onsite visits when remote cannot fix it, antivirus and email security, managed backup, and management of the firewall, switches, access points and printers. No long contract. The price is quoted after a short conversation about your machines.

Remote first, onsite by appointment. The overwhelming majority of workstation problems, from a licensing error to a slow sync, get fixed remotely while the designer keeps working on something else. When a machine needs a memory upgrade or a plotter needs hands, I schedule an onsite visit, and same-day onsite visits are often possible.

No contract needed to start. If you only want the slowness diagnosed, or three workstations upgraded, I do that as an hourly project through my hourly IT support and break/fix service at $100 per hour remote and $150 per hour onsite during business hours, with a one-hour minimum.

One contact, whole picture. Workstations, the server, the switch, the cabling, the licensing and the backups all sit with Cross River Tech, and I stay your contact for every one of them, so nobody points at anybody else. Tell me what your studio runs and what is annoying you, and I will come back with a plain-language diagnosis and a quote.

Questions people ask

Written and reviewed by

Anthony Omini, founder of Cross River Tech

Over 15 years in IT across many industries, now running Cross River Tech, a small owner-led managed IT company in Dallas. Every article is written from his own client work and checked by him before it is published.

Slow workstations? Let me look before you buy anything. Tell me how many CAD seats you have, what software you run and where your project files live. I will tell you what is actually slow and what it would cost to fix, usually the same day.

Ask Anthony(214) 612-7080About Anthony