Introducing the Civil Engineering Firm Tech Stack Map — an open reference for the six layers of technology every mid-market civil consulting firm runs, the typical vendors in each, and the integrations that separate working stacks from broken ones.
Walk into any mid-market civil engineering consulting firm and look at the technology. Civil 3D in some offices, OpenRoads in others. Revit on a few desks. ArcGIS for the GIS team. ProjectWise or BIM 360 for project collaboration. Bluebeam everywhere. Deltek, Unanet, or Ajera for project accounting. Some flavor of HRIS — BambooHR if the firm is smaller, Workday if it’s larger. Power BI or Tableau in the CFO’s office, often built by one heroic individual. Microsoft 365 for everything else. Azure or AWS underneath. CrowdStrike or Microsoft Defender keeping the lights on.
The stack is roughly the same at every firm because the stack is good. Each individual product has matured over decades, and the decisions about what to buy have largely converged. The problem isn’t the products.
The problem is that the same project gets set up three or four times — once in CRM when the pursuit was registered, once in ERP when the contract was signed, once in the CDE when the design team started work, once in a file share when the PM created a folder. Employee records live in HRIS, but their rates live in ERP, and their licensure lives in a spreadsheet. Hours worked in design tools never make it cleanly to project accounting. KPIs in the CFO’s dashboard don’t match the practice-area leader’s dashboard, and neither matches the PM’s dashboard. Data exhaust from every system stays locked inside that system.
We just published the Civil Engineering Firm Tech Stack Map to make this problem visible — and to give civil firm leaders a working reference for fixing it. It’s a single-page poster plus a 23-page companion guide that maps the six layers a mid-market civil consulting firm runs, the typical vendors in each, and the integrations between layers that separate firms with technology that compounds value from firms that own a portfolio of disconnected tools.
This post explains what it covers, the central insight (“the integration is the strategy”), and how it pairs with the Value Map we published earlier this year.
What the Tech Stack Map shows
The Map is structured as six horizontal layers, each containing four to seven categories of technology a typical civil firm runs:
Layer 1 — Strategy & Performance. How leadership sees and steers the firm. Executive dashboards, strategic planning and OKR tools, board / ESOP / owner reporting, pricing and multiplier analytics. The interface leadership uses to ask “where is the firm going?”
Layer 2 — Business Systems. Running the firm: time, money, people, work won and delivered. ERP / project accounting (Deltek Vantagepoint, Unanet AE, BQE Core, Ajera, BST). CRM (Deltek CRM, Cosential / Unanet CRM, Salesforce, HubSpot). HRIS (Workday, BambooHR, ADP, Paycom). Proposal production (OpenAsset, Unanet/Cosential). Document management for the business side (M-Files, OpenText, SharePoint). AP automation (Bill.com, Stampli, Tipalti).
Layer 3 — BI & Analytics. Making sense of the data the firm produces. AEC-specific dashboards (Deltek Clarity, Unanet Insights). General BI platforms (Power BI, Tableau, Looker, Qlik). Data warehouse / lakehouse (Microsoft Fabric, Snowflake, Synapse, Databricks). Predictive analytics and AI. Reporting automation and alerting.
Layer 4 — Project Collaboration. Connecting teams, partners, and clients around live project work. Common Data Environment (Autodesk Construction Cloud / BIM 360, Bentley ProjectWise, Newforma, Procore). PDF markup and review (Bluebeam, Adobe Acrobat). Project management and scheduling (MS Project, P6, Smartsheet). Communications (Teams, Zoom, Slack). File sharing (SharePoint, Egnyte, Box).
Layer 5 — Design, GIS & Production Tools. Where the deliverables are made. Civil design (Civil 3D, OpenRoads, OpenSite, OpenBridge, OpenRail). Structural engineering (Revit Structure, RAM, RISA, SAP2000, ETABS, STAAD, Tekla). Architecture and MEP (Revit, ArchiCAD). GIS (ArcGIS Pro, ArcGIS Online, QGIS). Hydrology and hydraulics (HEC-RAS, InfoWorks, SewerGEMS, WaterGEMS, EPANET). Survey and reality capture (Trimble, Leica, ContextCapture, ReCap, Pix4D, DroneDeploy). Specifications and estimating (MasterSpec, SpecsIntact, HCSS HeavyBid, Sage).
Layer 6 — Infrastructure & Security. The foundation: cloud compute and storage (Azure, AWS, GCP, M365), identity and access management (Microsoft Entra ID, Okta, Duo), endpoint management (Intune, Jamf), cybersecurity (CrowdStrike, SentinelOne, Defender XDR, Arctic Wolf), networking and zero-trust access (Cisco Meraki, Palo Alto, Zscaler, Cloudflare), backup and disaster recovery (Veeam, Datto, Cohesity, AvePoint), compliance and governance (Vanta, Drata, Microsoft Purview).
Under each category, the Map shows the vendors most commonly seen in mid-market civil consulting and — the central content — an integration insight: what good integration with the other layers should look like, and where the typical gaps are. The companion guide expands every category with watch-outs, vendor commentary, and the operating implications of the choices a firm makes at that layer.
The central insight: the integration is the strategy
The reason we wrote this resource is the central insight that emerges when you actually map a civil firm’s technology end to end: the layers individually are well-understood; the integrations between them are where firm-level competitive advantage compounds.
A firm that obsesses over which ERP to buy and treats the rest of the stack as a buy-and-forget exercise ends up with a five-product portfolio that doesn’t add up. A firm that picks reasonable tools at each layer but invests deliberately in the integrations — single source of truth for projects and employees, identity as the keystone, time entry as the operational discipline that feeds everything else, the CDE as the project’s spine, a data warehouse beneath the BI tools, AI models trained on the firm’s own data — ends up two or three years later with a meaningfully different operating capability.
Most strategy frameworks miss this. They treat technology as a single line item — “modernize the platform” — when in reality it is a layered system with very different economics, decision rhythms, and risk profiles at each level. Cloud infrastructure decisions live for five to ten years. Identity decisions live for the lifetime of the firm. ERP decisions live for ten to fifteen years. Design tool standardization lives for a CAD generation. BI investments compound over decades. Decisions at different layers should be made with different time horizons and different stakeholders at the table. The Map is built to make that visible.
Eight cross-cutting principles
The companion guide closes its main content with eight cross-cutting integration principles — the patterns that high-performing civil firms get right regardless of which specific vendor they pick in any given layer:
Single source of truth. ERP project IDs and HRIS employee IDs should be referenced by every other layer. When they’re not, you get parallel data sets, version drift, and reconciliation work that nobody owns.
Identity is the keystone. Layer 6 identity (Microsoft Entra ID, Okta) touches every other layer. Strong SSO, MFA, and lifecycle policies are the cheapest large-leverage investment in the stack.
Time entry is the bottleneck. Late time entry breaks BI, billing, multiplier discipline, and project forecasting all at once. Most stack-quality complaints trace back to a weekly habit problem, not a software problem.
The CDE is the project’s spine. Autodesk Construction Cloud, ProjectWise, or Newforma is where design hand-offs, submittals, and client deliverables live. The integrations around it determine the firm’s project-execution muscle more than any single tool choice.
Buy boring; build sharp. Use mature, vendor-supported tools for everything that isn’t a competitive differentiator. Build custom only where you can create durable advantage.
Pay attention to data exhaust. Every system produces telemetry. Treat that data as a strategic asset — feed it to the warehouse, build dashboards, train models. Firms that do this are noticeably ahead within 24 months.
Security debt is real debt. Mid-market civil firms are increasingly targeted as soft entry points to larger client networks. The cost of fixing security gaps after an incident is 10–20x the cost of preventing them.
The integration is the strategy. Buying the right tools in each layer is the entry ticket. The firms that get strategic value from technology are the ones who obsess over how the layers fit together.
Three ways to use the Map
Stack audit. Walk each layer with leadership and IT. For each category, ask: do we have a real solution? Does it integrate up and down? Where are the gaps that drag everything above and below? The companion guide’s vendor reference appendix doubles as a checklist for this exercise.
Roadmap planning. Use the Map to scope a multi-year technology roadmap. The foundation layers — L6 identity, cybersecurity, cloud, and L2 ERP — come first because everything else relies on them. BI, integration, and AI compound on top. Stretching the foundation decisions because they’re “infrastructure” is the most common roadmapping mistake we see, and it always costs more later.
Vendor selection. When evaluating any new tool, map it to its layer first and ask: how does it integrate up to BI, down to identity, and laterally to ERP and the CDE? The integration cost is almost always larger than the license cost, but rarely discussed in vendor demos. A tool that doesn’t integrate is a tool that creates a parallel data set, a parallel set of permissions, and a parallel set of operating habits that all have to be maintained forever.
Why we made it civil-specific
The technology stack of a civil engineering firm has features that distinguish it sharply from generic professional services or even from adjacent AEC sub-industries.
The design tooling layer (Civil 3D, OpenRoads, the Bentley stack, the H&H modeling tools, the survey and reality-capture chain) is unique to civil, deep in vendor specificity, and consequential in ways that horizontal IT frameworks completely miss. The CDE conversation is different from buildings-focused AEC because of how civil work intersects with construction (often via document-driven processes rather than IPD-style coordination). The ERP layer has its own dominant vendors (Deltek, Unanet) and its own configuration patterns built around utilization, multiplier, and project-margin discipline. The GIS layer is more central in civil than anywhere else in AEC.
Generic technology frameworks treat all of this as one undifferentiated category called “design tools” or “engineering software.” The Tech Stack Map treats it the way a civil firm’s CIO actually thinks about it — layer by layer, category by category, with the specific vendor choices and integration realities that matter at each.
How it pairs with the Value Map
The Tech Stack Map is the companion piece to the Civil Engineering Firm Value Map, which we published earlier and which covers how firm value is created — the four pillars of Revenue Growth, Operating Margin, Asset Efficiency, and Expectations, and the operating levers under each.
The two are designed to be read together because strategy and technology answer different questions about the same firm. The Value Map answers where does firm value come from, and where should we put our next move? The Tech Stack Map answers what is the system of technology that will execute that move, and where are the gaps that will stop us?
A specific Value Map lever — say, multiplier discipline, or reduced WIP days, or a higher hit rate — almost always traces down to one or two specific layers of the technology stack. Most of the time it’s L2 ERP and L3 BI; sometimes it’s L4 CDE; occasionally it’s L1 dashboards or L6 identity. Pairing the two maps is how leadership teams move from “we know what we should do” to “we know what to build.”
Where InfraTech fits
A few words on the connection between this Map and InfraTech’s work, since we built and publish both maps.
InfraTech Strategy Group is a technology partner to mid-market civil consulting firms. Our five service lines map directly to the layers of this stack. Enterprise Systems Deployment (ERP and CRM) is L2. Business Intelligence & Analytics is L3. CAD and Technical Integration is L4 and L5. Managed Technology Services is L6. Proprietary Software Development is where firms want to compete on something the off-the-shelf market can’t deliver — typically pricing tools, asset management platforms, or AI-assisted design utilities that turn institutional knowledge into a durable asset.
We don’t think of the Map as a sales tool. We think of it as the way we explain to civil firm leadership the architecture of the work we do. Some readers will use the Map as a strategic artifact and never speak with us. The ones who do reach out tend to be the firms who have looked at it carefully, recognized one or two specific integration gaps, and want help closing them.
Get the Map
The Civil Engineering Firm Tech Stack Map is available as a printable single-page poster (36 × 18 inch, designed for large-format printing) and a 23-page companion guide that walks layer by layer through every category — with vendor commentary, integration insights, and watch-outs for each. The guide includes a consolidated vendor reference appendix you can print as a quick lookup.
And if you haven’t seen it yet, download the companion Civil Engineering Firm Value Map — the two read best together.
If your firm is in the middle of a technology refresh, an ERP migration, a security maturity push, or simply a moment of asking “what should our stack actually look like five years from now?” — we hope it is useful. And if the conversation it starts leads to a question about how to close a specific integration gap, schedule a strategy session or calculate your ROI.
Independent reference work for the civil engineering consulting industry. Vendor names referenced for accuracy; no endorsements or affiliations implied.