“Which tool should I use?” comes up repeatedly in AEC Office Hours and in conversations with firms of every size. One small-practice owner asked it three ways: What is the best app? Which one is worth paying for? What is best for a firm our size? Those are sensible questions. The honest answer depends on the work.
If you are starting, choose one general assistant—ChatGPT, Gemini, or Claude—and use it on real work long enough to learn. Add a specialized tool only when you can name the job it does better and why that improvement is worth another subscription.
The same AI can feel very different depending on where you use it
A model inside ChatGPT, Gemini, a rendering product, Photoshop, or another application may have different controls, limits, connections, and results. That is why “Which model is best?” rarely settles the decision.
Ask: Can it do the job with the files we have? Does it work with the software we use? What happens to our information? Who checks the result? Is it worth paying for?
Ask six questions before you add another tool
- What do we want help with? Name the repeated job, not “AI.”
- What information does it need? Know which files, emails, project records, or client information will go in.
- What can it do? Drafting is different from sending, changing, or updating something automatically.
- Who checks it? Decide who catches mistakes and owns the final result.
- Does it fit how we work? A good demo is not useful if it cannot work with your systems or your team.
- Who will take care of it? Someone must manage accounts, settings, training, support, and renewal.
You have four choices—and “buy” is only one
The existing system can support the job with better configuration, templates, training, or ownership.
A mature product already solves the job and fits the firm’s data and review requirements.
The value is in moving reviewed information between systems that already do their jobs well.
The workflow is distinctive, valuable, and stable enough to justify custom maintenance.
If the whole firm will use it, somebody has to own it
Decide who manages the account, adds and removes people, checks privacy settings, approves connections, answers questions, and decides whether to renew. Otherwise the “standard” becomes a collection of individual accounts nobody can see or support.
Teach people with examples from their own jobs. A project architect, designer, operations lead, finance person, and business-development team do not need the same lesson.
Keep the list small enough to maintain
Overlap creates confusion: people stop knowing where the accepted work belongs, which setting governs, or who supports the tool. Prefer a smaller, legible environment with clear exceptions over a crowded catalog nobody owns.
The best tool is not the one that can do the most. It is the one that makes a real part of your work easier—and that your firm can actually support.