There's a version of this conversation that happens in every small architecture firm at some point. A principal or PM decides the current system, some combination of shared drives, email, and a spreadsheet someone made four years ago, isn't cutting it anymore. They start researching software. They demo a few things. And then one of two things happens:
They buy something they don't end up using, because it required a full-time admin to maintain. Or they get overwhelmed by the options and do nothing.
This guide is an attempt to cut through that. Here's what a small A&E firm, somewhere between 5 and 25 people, actually needs to manage projects well, and what you can skip.
The Core Jobs That Software Needs to Do
Before you look at any software, get clear on what you're actually trying to accomplish. For most small A&E firms, project management software needs to handle some combination of:
- Document management, where do current drawing files and specifications live, and how does the team know what's current?
- Task tracking — what needs to happen, who's responsible, and when is it due?
- Team communication — how do team members and consultants coordinate day to day?
- Client access — how do clients receive information and review progress?
- Time and fee tracking — how is project time recorded and compared to budget?
The mistake most firms make is trying to solve all five with a single tool. And usually getting something that does all of them adequately but none of them well.
A more effective approach: prioritize the jobs where your current system is failing most badly, and solve those first.
What You Actually Need
Document Management — Non-Negotiable
For most small A&E firms, this is the highest-leverage investment. Where do files live? Is "current" actually current? Can consultants access what they need without you having to email it to them?
At minimum: a shared drive with a consistent folder structure and naming convention, maintained by someone with actual ownership. Google Drive or SharePoint, maintained well, beats an expensive system maintained poorly.
Better: purpose-built document management that tracks versions, controls access by role, and keeps an audit trail of what was issued and when. For design-phase work specifically, version control is the critical feature, not storage.
Task Tracking — Usually the Second Priority
If you're managing tasks in email and meeting notes, things fall through. The question is what falls through and how much it costs you.
A simple task tracking tool with due dates and owners is the minimum. The feature that makes the biggest difference in practice: automated reminders. Not "send yourself a task to check tasks" — actual reminders that go to the person responsible when a deadline is approaching.
For small firms, the task system doesn't need to be sophisticated. It needs to be used. A simple system used consistently beats a complex system used intermittently.
Communication — More Nuanced
This is where small firms have the most options and the least clarity. The honest answer: most small firms don't need dedicated project messaging software. What they need is to stop using email for project coordination, and to have a consistent protocol for where project conversations happen.
If your team is genuinely committed to a simple communication tool (not Slack with fifty channels), it helps. If you're going to default back to email anyway, the tool won't fix the problem.
The more important question is how you handle communication with external parties. Consultants and clients. Having a clear, dedicated channel for each project, accessible to the right parties and nobody else, is worth more than any internal communication tool.
Client Access — Often Overlooked
Most small firms share information with clients via email attachments or shared drive links. This works until it doesn't. Which is usually when the client saves the wrong version of a pdf, or when you need a formal record of what you shared and when.
A dedicated client access layer, where clients can see exactly what you give them access to, organized by project, without seeing anything else, solves this cleanly. It's not glamorous, but it prevents a surprising number of problems.
Time and Fee Tracking — Separate Problem
This guide is focused on project management, not accounting. Time tracking and invoicing are their own category, and there are good specialized tools for them (Monograph, BQE Core, and others built specifically for A&E firms).
Don't try to solve time and fee tracking with your project management tool unless it was specifically built for it.
What to Skip
Full-featured enterprise platforms. Procore, Autodesk Construction Cloud, and similar platforms are built for general contractors and large-scale construction management. They handle procurement, RFIs, submittals, financials, and much more. They're also expensive, require significant setup, and are designed for firms with dedicated PM staff. Unless you're managing large construction projects with complex GC coordination, they're overkill.
All-in-one project management tools not built for AEC. Asana, Monday, ClickUp, these are capable tools that work well for software teams and marketing departments. They don't have the terminology, the document handling, or the external access model that design project teams need. You'll spend as much time configuring them as using them.
More tools than your team will actually use. The highest-cost mistake isn't choosing the wrong software. It's choosing software that your team doesn't adopt. A tool that two people use and six people work around doesn't solve anything.
A Realistic Small-Firm Stack
For a 5-15 person architecture firm managing design-phase work, a functional stack looks like:
- Project management (documents + tasks + communication + client access): One purpose-built tool for AEC design phase work — something like Olumba, which covers these jobs in one place without requiring a full-time admin to maintain. Purpose-built for design teams, not adapted from something else.
- Time and fee tracking: A dedicated A&E accounting tool (separate from PM)
- Accounting: Whatever you're using — this shouldn't change
- Design software: Revit, AutoCAD, SketchUp, separate, not integrated into PM
Four tools. Not fourteen. Each doing one job well.
The Question Worth Asking
The most useful question to ask before buying any software: what, specifically, is falling through the cracks on your current projects? Document version confusion? Tasks without owners? Clients surprised at presentations? Team members missing deadlines because nobody reminded them?
Whatever the specific failure mode is, that's where you invest. Not in a comprehensive platform that promises to solve everything, but in a targeted solution to the actual problem.
