
Reflections on Life
Insights and Inspirations for Everyday Living
I write about what I'm actively building: AI integration, writing systems, and income transformation. Not theory—field notes from someone engineering multiple businesses while working as a practicing civil engineer.
Three focus areas: strategic AI implementation for technical firms, systematic craft development for writers, and positioning strategies for professionals breaking into seven figures.
My approach combines engineering precision with creative problem-solving, Stoic philosophy with entrepreneurial execution. I document the frameworks that work, the mistakes that cost time, and the positioning shifts that unlock leverage.
For people who value execution over inspiration, systems over motivation, and transformation over information.
Read what's relevant. Apply what works.
Why Standard AI Consulting Rates Don't Apply to Engineering Firms: A Response
January 9, 2026
Orient Software recently published a comprehensive breakdown of AI consulting rates, outlining the standard industry pricing: $100-150/hour for junior consultants, $150-300/hour for mid-level practitioners, and $300-500+/hour for senior experts. While these numbers accurately reflect the general AI consulting marketplace, they fundamentally misunderstand the value equation for architecture, engineering, and construction (AEC) firms.
Here's why: hiring a data scientist to implement AI in an engineering firm is like hiring a mechanic to design a bridge. They might understand engines perfectly, but they don't understand load calculations, soil mechanics, or the regulatory framework that governs every decision a civil engineer makes.
The Hidden Cost of "Affordable" AI Consulting
Let's do the math on what Orient Software's "affordable" hourly model actually costs an engineering firm:
The Traditional Model:
- Senior AI consultant at $400/hour
- Estimated 200 hours to implement a basic AI solution (their article suggests $10,000-$50,000 for simple integrations)
- Total cost: $80,000
But here's what they don't tell you:
- +40 hours of your senior engineers' time explaining domain-specific requirements
- +60 hours of back-and-forth because the consultant doesn't understand CAD workflows
- +80 hours fixing integration issues with your BIM software
- +120 hours of rework when the solution doesn't account for load factor calculations
Real cost: $200,000+ and 6-9 months of frustration
And you still don't have a solution that understands how engineers actually work.
Why Domain Expertise Changes Everything
Orient Software's article correctly identifies "industry-specific requirements" as a premium factor, noting that healthcare, finance, and defense command higher rates due to regulatory complexity. What they miss is that engineering is equally complex—it just doesn't advertise its sophistication.
Consider what happens when you implement AI in a structural engineering firm:
A general AI consultant sees:
- Data that needs to be organized
- Workflows that could be automated
- Models that could be trained
An engineer who understands AI sees:
- Load calculation patterns that predict failure modes
- Design iteration cycles that reveal optimization opportunities
- Specification checking processes that could eliminate 90% of RFIs
- Code compliance verification that could save weeks per project
The difference isn't marginal—it's the difference between automating the wrong things efficiently and transforming how your firm delivers value.
The Real ROI Equation
Orient Software's article focuses on cost predictability and pricing models. But here's the question they never address: What's the ROI of implementing AI that actually understands engineering?
Let's look at real numbers from an AEC firm perspective:
Scenario: Mid-size structural engineering firm (15 engineers)
Traditional AI Implementation (using Orient Software's model):
- Cost: $150,000 for project-based implementation
- Timeline: 6-9 months
- Result: Generic workflow automation
- Time savings: 5 hours/week across the firm (75 hours/week total)
- Annual value: $195,000 (at $50/hour average)
- Net first-year ROI: $45,000
Engineering-Specific AI Integration:
- Cost: $60,000 annually ($5,000/month retainer)
- Timeline: 2-3 months to first impact
- Result: Engineering-specific optimization
- Time savings: 12 hours/week per engineer (180 hours/week total)
- Annual value: $468,000
- Additional revenue from capacity: $280,000 (ability to take on 2 more projects)
- Net first-year ROI: $688,000
The difference? Understanding that engineers don't need faster spreadsheets—they need AI that understands structural analysis.
Why the Retainer Model Actually Works for Engineering Firms
Orient Software correctly identifies three pricing models but treats them as neutral options. For engineering firms, the retainer model isn't just preferable—it's essential. Here's why:
1. Engineering Projects Evolve
Unlike implementing a chatbot (Orient Software's example of a "simple" project), engineering AI integration touches every aspect of practice:
- CAD automation evolves as design standards change
- Code compliance requirements are updated quarterly
- Project types vary, requiring different optimization strategies
Hourly billing penalizes this reality. Every scope change becomes a negotiation. Every new requirement becomes a change order.
2. Engineering Firms Need Strategic Partnership, Not Task Completion
The project-based model Orient Software promotes assumes you know exactly what you need. But most engineering firms don't need a fixed deliverable—they need someone who understands both their technical work AND emerging AI capabilities to identify opportunities they didn't know existed.
This is why Salaam Integration Group operates on a retainer model ranging from $2,500-$7,500 monthly. Not because it's "better pricing," but because AI integration in engineering firms is an ongoing strategic process, not a one-time implementation.
3. Your Consultant Should Have Skin in the Game
Here's what Orient Software's article doesn't mention: hourly consultants get paid whether your implementation succeeds or fails. Project-based consultants get paid when they deliver what was specified, not necessarily what actually works.
A retainer model with an engineering domain expert means:
- Ongoing optimization as you discover what actually creates value
- No penalties for asking "stupid questions" (there are none when your consultant understands engineering)
- Continuous evolution as new AI capabilities emerge
- Strategic guidance that compounds over time
The Engineer's AI Advantage
Let me be direct about something Orient Software's article dances around: most AI consultants have never calculated a moment diagram, reviewed a construction drawing, or explained to a client why you can't just "make the columns thinner."
When you hire someone with 15+ years of civil engineering experience who has also mastered AI implementation, you're not paying for:
- ❌ Time spent learning what a shop drawing is
- ❌ Explanations of why load factors matter
- ❌ Education on the difference between design development and construction documents
- ❌ Clarification of why "just automate everything" doesn't work
You're paying for someone who already speaks your language and can immediately identify where AI creates value in YOUR specific practice area.
The Questions Orient Software Doesn't Ask
Their article provides a helpful checklist of questions to ask AI consultants:
- How do you price projects like mine?
- What are the hidden costs?
- Can you provide a cost breakdown?
- What happens when scope changes?
- How do you track progress?
These are good questions. But for engineering firms, here are the essential questions:
1. "How many engineering projects have you worked on?" If the answer is zero, you're about to pay someone $300/hour to learn your industry on your dime.
2. "Can you explain the difference between BIM Level 2 and Level 3?" If they can't, how will they integrate AI with your actual workflows?
3. "What's your experience with [your specific engineering software]?" Generic AI expertise means nothing if it can't interface with Revit, AutoCAD, SAP2000, or whatever tools your firm actually uses.
4. "Have you ever had to explain a design decision to a building official?" Because if you haven't navigated code compliance, you don't understand the constraints that make or break engineering AI implementations.
5. "What's the ROI timeline for engineering-specific AI integration?" If they say 12-18 months (Orient Software's implicit timeline for their project examples), they're not thinking like an engineer. Engineering firms need demonstrated value in 90 days or the initiative dies.
The Real Cost Comparison
Let's be transparent about what you're actually comparing:
Orient Software's Model (Typical AI Consulting Firm):
- Hourly rate: $300-500/hour for senior consultant
- Estimated hours for "medium project": 500-1,000 hours
- Total cost: $150,000-$500,000
- Timeline: 6-12 months
- Risk: You bear all risk of scope misalignment
- Ongoing support: Additional cost, usually hourly
The Engineer's AI Strategist Model:
- Monthly retainer: $2,500-$7,500
- Annual cost: $30,000-$90,000
- Timeline to value: 60-90 days
- Risk: Shared—if it doesn't create value, we adapt immediately
- Ongoing support: Included, with continuous optimization
The difference isn't just price—it's risk distribution and value realization timeline.
Why This Matters Now
Orient Software's article opens with a valid observation: AI is moving fast, and companies need to understand consulting costs to maximize ROI. But they miss the critical insight that ROI isn't just about cost—it's about alignment.
Here's the truth about AI in engineering firms:
Most AI implementations fail. Not because the technology doesn't work, but because:
- The consultant doesn't understand engineering workflows
- The solution optimizes the wrong processes
- The timeline is too slow for engineering firm decision-making cycles
- The cost structure punishes the iterative discovery process that makes AI valuable
The solution isn't cheaper AI consulting—it's properly aligned AI consulting.
The Path Forward
If you're an engineering firm evaluating AI consulting options, here's my honest recommendation:
Choose Hourly Rates If:
- You have a precisely defined, one-time technical problem
- You have strong internal AI expertise and just need execution help
- The project scope is truly fixed and won't evolve
Choose Project-Based If:
- You need a specific, bounded deliverable (like a chatbot or data pipeline)
- You have complete clarity on requirements
- The implementation doesn't touch core engineering workflows
Choose a Retainer with an Engineering Domain Expert If:
- You're serious about transforming how your firm works (not just automating current processes)
- You need strategic guidance on where AI creates value in engineering practice
- You want to minimize risk and timeline to value
- You value ongoing optimization over one-time delivery
The Bottom Line
Orient Software's article provides valuable market data on standard AI consulting rates. But "standard" rates assume "standard" implementations, and there's nothing standard about implementing AI in engineering firms.
The choice isn't between $300/hour and $5,000/month. The choice is between:
Option A: Hiring a brilliant data scientist who will spend 6 months learning your business while billing you $400/hour
Option B: Hiring someone who has already spent 15 years learning engineering and has also mastered AI implementation
One of these options costs less. The other creates value faster, significantly reduces risk, and transforms how your firm delivers projects.
Orient Software is right about one thing: AI consulting costs vary significantly based on expertise and industry requirements. They're wrong to assume that general AI expertise combined with time is equivalent to domain-specific AI expertise.
It doesn't.
And for engineering firms trying to navigate AI implementation without wasting hundreds of thousands of dollars and 12 months of time, that distinction matters more than the hourly rate.
Phillip Salaam
The Engineer's AI Strategist |15+ Years in Civil Engineering | AI Integration Consultant |Salaam Integration Group
#EngineeringFirms #AIIntegration #CivilEngineering #AECIndustry #EngineeringLeadership #BusinessStrategy #AIForEngineers
The $500K Question: Why Engineering Firms Can't Afford to Ignore AI in 2026
January 6, 2026
Last month, I watched a 50-person civil engineering firm lose a $2.3M contract to a competitor with half their staff. The difference? The smaller firm delivered proposals in 48 hours instead of two weeks. They weren't better engineers. They were just using AI.
The principal called me three days later. "How did they do that?" he asked. I told him the truth: "They've been doing it for eighteen months. You're just noticing now."
That conversation is the reason I'm writing this article. Because what the principal didn't realize—what most engineering firm leaders don't realize—is that the lost contract wasn't the real cost. It was just the visible symptom of a $500K problem that had been quietly bleeding his firm for over a year.
The Invisible Bleeding
Here's what keeps me up at night: the opportunities you never see.
There are RFPs you don't bid on because your team is already stretched thin, and a two-week turnaround is impossible. There are second-tier projects you pass on because "they're not worth the overhead" when overhead is the thing AI could eliminate. Some clients ghost after initial conversations, and you assume they went with someone cheaper, when really they went with someone faster.
I've been in civil engineering for over fifteen years. I've managed CADD departments, overseen multi-million dollar projects, and built my career on understanding how engineering firms actually operate—not how consultants think they should operate. And I'm telling you: most firms are hemorrhaging money in ways they can't see because they're looking at the wrong metrics.
Revenue looks stable. Maybe it even looks good. However, profit margins are eroding by 2-3% annually, whereas AI-integrated firms are expanding theirs by 15-20%. Your competitors aren't just working faster—they're working smarter, and the gap widens every quarter.
The $500K isn't a single catastrophic loss. It's death by a thousand paper cuts, and most firms don't realize they're bleeding until it's almost too late.
The Three Hidden Costs Nobody Talks About
Let me break down where that half-million dollars actually goes, because it's not where you think.
The Talent Drain
Your best young engineers know AI exists. They're using it in their personal lives. They see you ignoring it professionally. And here's what they're thinking: "This firm is dying, they just don't know it yet."
I'm part of group chats with younger engineers. I see the conversations. "My firm still uses the same workflows from 2015." "I mentioned AI in our last team meeting, and the principal literally laughed." "I'm interviewing at three places next month—all of them have AI integration plans."
The math here is brutal. Average cost to replace a mid-level engineer: $75K-150K. Lost productivity during transition: 6-9 months. Multiply that by 3-4 engineers over two years, and you're looking at $300K-600K in replacement costs alone.
But the real cost? The institutional knowledge that leaves the organization. The client relationships. The unwritten processes that only exist in someone's head until they no longer exist at all.
The Rework Cost
Manual processes mean human error. Human error means expensive fixes. It's that simple.
A typical engineering firm spends 12-18% of project time on rework. AI-integrated firms with proper quality control protocols? 4-6%. On a $500K project, that's $40K-60K in pure waste.
Let me give you a real example. A drainage calculation error identified during QC would cost approximately $800 to correct. The same error caught after construction begins? $47,000. I watched an AI-powered review system flag this exact issue on a project last year. The senior engineer had missed it. Not because he wasn't competent—he was excellent—but because humans miss things when they're reviewing their 23rd set of calculations that week.
AI doesn't get tired. It doesn't get distracted. And it certainly doesn't miss the same pattern it has been trained to detect.
The Opportunity Cost
This is the big one, and it's the cost most principals don't calculate.
What are you NOT doing while you're drowning in administrative work?
Business development that could land six-figure projects. Strategic planning that could reshape your firm's market position. Mentoring that could retain your best talent. Innovation that could differentiate you in an increasingly commoditized market.
I did a time audit with a firm last quarter. The principal was spending 23 hours per week on "tasks AI could handle"—proposal formatting, preliminary quantity takeoffs, routine correspondence, documentation review, and meeting notes compilation. At a $250/hour billing rate, this amounts to $299,000 in wasted principal capacity per year.
You're paying engineering partners to do data entry. Let that sink in.
The Competitive Reality Check
Let me tell you what's actually happening in the market right now, because the picture is clearer—and more urgent—than most people realize.
The Early Adopters (about 15% of firms) have been using AI for 18-24 months. They've automated proposal generation, turning 3-day processes into 3-hour processes. They're running AI-assisted design reviews that catch 40% more errors than traditional methods. They're using predictive project scheduling that's reducing delays by 30%.
They're winning bids you don't even know you lost.
The Fast Followers (25% of firms and growing rapidly) started 6-12 months ago. They're already seeing 10-15% efficiency gains. More importantly, they're marketing themselves as "innovative" and "forward-thinking." They're positioning AI adoption as a competitive advantage in their proposals. They're using the efficiency gains to either undercut on price or over-deliver on speed.
This is where the middle of the market is heading, and they're moving fast.
The Holdouts (60% of firms—probably you) are saying things I hear every week: "We'll wait and see." "Our work is too specialized." "AI can't replace engineering judgment."
All true statements. All completely irrelevant to the actual competitive threat.
Because here's what you need to understand: nobody is replacing engineering judgment with AI. They're replacing engineering busy work with AI, which frees up engineering judgment for the things that actually matter.
The 18-Month Window
I've watched this pattern play out three times in my career: CAD, BIM, and cloud-based project management. The pattern is always the same.
Months 0-12: Early adopters gain a quiet advantage. Their competitors don't notice because the advantage isn't yet overwhelming. They're learning, iterating, failing privately, and building systems that work.
Months 12-24: Fast followers scramble to catch up. They see the advantage and rush to implement. They make expensive mistakes because they're moving fast without a strategy. But even with mistakes, they're better off than waiting.
Months 24-36: Holdouts realize they're in crisis mode. The competitive disadvantage is now obvious. They try to implement, but they're doing it from a position of weakness, not strength. They're reacting, not leading.
We're at Month 18 for AI integration in AEC firms. The window is closing.
The firms that waited to adopt CAD? Most of them don't exist anymore. The ones that resisted BIM? They're struggling today. The pattern is consistent, and the timeline is always faster than people expect.
Why "Wait and See" Is Actually "Lose and Bleed"
I hear three common objections, and I want to address them directly because they sound reasonable but they're based on faulty assumptions.
"We're waiting for AI to mature."
The AI you're waiting to "mature" is already obsolete. GPT-4 to GPT-5 happened in 18 months. The tools available today are 10x better than they were two years ago. By the time you "feel ready," you'll be three generations behind competitors who are currently learning on fourth-generation tools.
Technology maturity isn't a destination; it's a moving target. The question isn't "Is AI mature enough?" It's "Am I learning fast enough?"
"We'll start when we have more time."
There is never a good time to integrate new technology. There's only "now" and "too late." The firms that successfully integrated AI didn't have more time than you—they made the time because they understood the cost of waiting.
The learning curve is real: 3-6 months to basic competency, 12-18 months to strategic advantage. Starting in 2026 means competitive advantage in late 2027. Starting in 2028 means you're in catch-up mode forever, paying premium prices for rushed implementation while competing against firms with two years of refinement.
"Our clients aren't asking about AI yet."
They're not asking about it. They're just noticing your competitors' faster turnaround times, more accurate proposals, and more responsive project management.
Here's the timeline of client expectations:
- 2024: Clients impressed by AI capabilities
- 2025: Clients curious about AI integration
- 2026: Clients expect AI-enabled efficiency
- 2027: Clients require AI as table stakes
Your clients might not use the word "AI" when they choose your competitor. They'll say "They just seem more responsive" or "They delivered exactly what we needed, faster." But make no mistake—AI is the engine behind that capability.
The Engineer's Unique Advantage
Here's something most AI consultants won't tell you, because they don't understand engineering culture: you're actually better positioned to lead AI integration than most other industries.
Why? Because you already think in systems.
You design drainage systems with multiple failure points and contingency plans. You manage complex workflows where one error cascades into expensive problems. You optimize processes while maintaining safety and quality standards.
The same analytical mind that designs a stormwater management system can design an AI integration system. The same attention to detail that catches calculation errors can catch AI implementation gaps. The same commitment to quality that guides your engineering work can guide your AI adoption.
The problem isn't capability. It's a translation.
Most AI consultants are tech people who don't understand engineering culture. They talk about "disruption" when you need to talk about "risk mitigation." They push tools when you need to understand systems. They've never dealt with PE stamps, liability insurance, or client specifications that run 200 pages.
Most engineering consultants understand your culture but don't understand AI deeply enough to implement it strategically. They know the problems but not the solutions.
I've spent fifteen years in civil engineering—managing CADD departments, coordinating with surveyors, dealing with city plan reviews, juggling client demands and project deadlines. I've also spent the last three years deeply studying AI integration, not from a tech perspective, but from an engineering systems perspective.
That combination is rare. And it's exactly what engineering firms need right now.
What Strategic AI Integration Actually Looks Like
Let me be very clear about what this is NOT:
It's not buying ChatGPT subscriptions for everyone and hoping something good happens. I've seen firms do this. They announce "We're adopting AI!" and give everyone access to tools with no training, no standards, and no integration plan. Six months later, adoption is 5%, ROI is zero, and leadership is frustrated.
It's also not "replacing engineers with robots." AI doesn't eliminate engineering judgment—it eliminates engineering busy work. Your engineers don't become less valuable; they become MORE valuable because they're freed up to do the work that actually requires their expertise.
Strategic AI integration is systematic and phased:
Phase 1 (Months 1-2): Assessment and Quick Wins
We identify the highest-impact, lowest-risk opportunities specific to your firm. Maybe it's proposal generation. Maybe it's preliminary quantity takeoffs. Maybe it's meeting notes and action item tracking. We deploy simple automations that deliver immediate ROI and build confidence among your team. We find your internal champions—the engineers who are excited about this—and we give them wins.
Phase 2 (Months 3-4): Process Integration
This is where most firms fail if they try to do it alone. We don't create parallel workflows—we embed AI into your existing processes. We develop firm-specific standards and protocols that match how your team actually works, not how some consultant thinks they should work. We train your team leads to become AI workflow experts within your firm, creating sustainable knowledge that doesn't leave when I do.
Phase 3 (Months 5-6): Strategic Advantage
By now, the efficiency gains are real and measurable. We use them for market differentiation. You're not just "faster"—you're positioned as an innovation leader. You're developing proprietary AI-enhanced methodologies that become competitive advantages. You're attracting better talent because talented engineers want to work at firms that are ahead of the curve, not behind it.
The ROI timeline looks like this:
- Month 1: 5-10% time savings on routine tasks
- Month 3: 15-20% faster proposal development
- Month 6: 25-30% efficiency gain on documentation
- Month 12: Measurable competitive advantage in win rates and margins
Most firms see positive ROI by Month 4. Full strategic advantage by Month 12. And the gap between you and non-adopting firms? It keeps widening.
The Decision Framework
Let me give you three questions to ask yourself, right now, honestly:
1. Can we afford $500K+ in hidden costs over the next two years?
Add up the talent replacement costs, the rework costs, the opportunity costs, and the competitive losses. Be honest about what "business as usual" actually costs when the market is shifting around you.
2. Are we okay being known as the firm that's behind the times?
Reputation moves slowly until it doesn't. You're "traditional" until you're "outdated." And once that perception sets in, it's incredibly expensive to change.
3. Do we want to lead this change or be forced into it by market pressure?
Leading means implementing from a position of strength—thoughtfully, strategically, at your pace. Being forced means scrambling to catch up, overpaying for rushed solutions, and implementing under crisis conditions.
The risk-reward calculation here is stark:
- Risk of acting: $15K-45K investment over six months, change management effort, learning curve discomfort
- Risk of waiting: $300K-800K in opportunity costs, talent drain, competitive disadvantage that compounds quarterly
The biggest risk isn't choosing wrong. It's miscalculating which risk is bigger.
What "Ready" Actually Means
You're waiting to feel ready. I understand that. Every principal I work with felt the same way.
But here's the truth: you'll never feel 100% ready. The firms that are winning today didn't feel ready when they started. They felt uncertain, uncomfortable, and concerned about all the same things you're concerned about.
Ready doesn't mean you have all the answers. Ready means you're asking the right questions. Ready means you're committed to learning, willing to invest, and humble enough to know you need guidance.
Ready means understanding that the cost of perfection is usually much higher than the cost of imperfect action.
Where You Are Right Now
You're probably doing fine financially. Your firm isn't in crisis. You're aware that AI is "important somehow," and you're thinking you'll "get to it eventually."
I meet principals every week who are exactly where you are. The ones who act are grateful six months later. Those who wait call me back in eighteen months, and the conversation is markedly different—more desperate, more expensive, more difficult.
This isn't a sales pitch. Whether you work with me or someone else or try to figure it out yourself, you need to address this. The $500K question isn't rhetorical—it's actuarial. The data from firms that delayed CAD adoption, BIM adoption, and cloud adoption is clear: waiting costs exponentially more than leading.
What Happens Next
You have three options:
- Option 1: Keep reading articles. Keep "meaning to look into this." Watch your competitors pull ahead while you convince yourself you'll catch up later. Hope that the market will somehow wait for you.
- Option 2: Have a conversation with someone who's been in your shoes—someone who understands PE stamps and project specs and client expectations, but who also deeply understands AI integration systems.
- Option 3: Try to figure it out yourself. It's possible. Some firms do it. But it's expensive in time, mistakes, and opportunity costs. The learning curve is steep when you're learning alone.
I offer free 45-minute strategic assessments. Not sales calls—genuine evaluations. We'll map your specific risks and opportunities. I'll tell you honestly whether AI integration makes sense for your firm right now, and if it does, what the path forward looks like.
You'll leave with clarity, whether we work together or not. At minimum, you'll know if you're sitting on a $500K problem. That's worth 45 minutes.
The Pattern Repeats
Fifteen years ago, I watched firms resist CAD because "hand-drafting worked fine." Then I watched them resist BIM because "CAD worked fine." Now I'm watching the same pattern with AI, and I'm watching the same firms make the same mistakes for the same reasons.
The firms that waited? Most of them don't exist anymore. The principals who led the change? They're running the most successful firms in the industry today. They're not smarter than you. They weren't more prepared than you. They just understood that leadership means moving before you feel ready.
The $500K question isn't whether AI will transform engineering firms. That's already happening. The question is whether you'll be leading that transformation or scrambling to survive it.
The window is closing. The cost of waiting is compounding. And the conversation you need to have is probably overdue.
Ready to assess if your firm has a hidden $500K problem?
Book a free 45-minute Strategic AI Assessment: Contact Now
Or connect with me here on LinkedIn—I share weekly insights on AI integration for engineering firms specifically.
Phillip Salaam
The Engineer's AI Strategist |15+ Years in Civil Engineering | AI Integration Consultant |Salaam Integration Group
#EngineeringFirms #AIIntegration #CivilEngineering #AECIndustry #EngineeringLeadership #BusinessStrategy #AIForEngineers
BLOG POST 1: AI Integration
Why Most AEC Firms Are Implementing AI Wrong (And How to Fix It)
I got a call last month from a structural engineering firm in Dallas. They'd spent $15,000 on AI tools over six months. ChatGPT Enterprise. Midjourney. Some specialized CAD plugin. Their team had attended webinars. Watched tutorials. Everyone agreed AI was the future.
Their actual AI usage? Maybe 10% of the team, sporadically, for tasks they could've done faster the old way.
"We're just not an AI company," the principal told me. "Our people are traditional engineers."
Wrong diagnosis. Expensive mistake.
Here's what actually happened: they bought tools before understanding workflows. Classic cart-before-horse. And now they're convinced AI "doesn't work" for their industry.
After fifteen years in civil engineering and the past year helping firms actually implement AI successfully, I can tell you: the problem isn't the technology. It's the sequence.
The Three Questions Nobody Asks (But Everyone Should)
Before you spend another dollar on AI subscriptions, answer these:
Question 1: What Takes Too Long That Shouldn't?
Not "what could AI theoretically do?" That leads to solution-in-search-of-problem thinking. Instead, look at your actual bottlenecks.
At CCI & Associates, where I've worked for 15+ years, we identified three massive time sinks:
- Preliminary design iterations (client changes mind, we redraw)
- Code research and compliance verification
- RFP responses and proposal writing
Notice what's NOT on that list? Complex structural calculations. Final design work. Site-specific problem solving. Why? Because those require engineering judgment that AI can't replicate reliably. Yet.
The Dallas firm? They'd bought tools for generative design and rendering—sexy stuff that looks great in demos but doesn't address their actual constraint: they were drowning in municipal permit applications that required reformatting the same information twelve different ways.
Action Step: Spend one week tracking where your team's time actually goes. Not where you think it goes. Where it actually goes. Look for repetitive, high-volume, low-judgment tasks. That's your target.
Question 2: What Could a Smart Intern Do With Perfect Instructions?
This is the AI sweet spot.
AI isn't replacing senior engineers. It's replacing the work you'd delegate to a really good intern if you had unlimited interns and time to write perfect instructions.
Examples from my own practice:
- "Take this geotechnical report and extract all bearing capacity values into a table organized by depth"
- "Review this drainage plan against local stormwater codes and flag any potential conflicts"
- "Draft three versions of this project description—one technical for engineers, one simplified for public meetings, one formatted for the planning commission"
Could a senior engineer do these tasks? Yes. Should they? No. That's $150/hour talent doing $30/hour work.
Could a junior engineer do them? Maybe, with supervision. But AI does them in 90 seconds, consistently, at 2am when you realize you need them for tomorrow's meeting.
The Framework: If the task has clear inputs, defined processes, and verifiable outputs—AI can handle it. If it requires site-specific judgment, creative problem-solving, or client relationship management—keep the human.
Question 3: What's the First Domino?
Here's where most firms fail: they try to implement AI everywhere at once.
The structural firm in Houston I worked with wanted to "transform" their entire operation. Noble goal. Impossible execution.
Instead, we identified one workflow: automatically generating preliminary foundation layouts based on geotechnical reports and building loads. One task. Clear success metric. Four-week pilot.
Results? 60% time reduction on prelims. Team saw the value immediately. Confidence built. Six months later, they've expanded to five AI-integrated workflows.
The secret? Start small, prove ROI, build momentum.
Don't ask "How do we become an AI company?" Ask "What's the single workflow that, if we improved it by 50%, would make everyone's life noticeably better?"
That's your first domino.
The Actual Implementation Sequence
Based on successful implementations across six firms:
Week 1-2: Workflow Audit
- Shadow 3-5 team members for full project cycles
- Document every repeated task
- Identify the bottlenecks that actually hurt (not theoretical inefficiencies)
- Build a prioritized list based on: frequency × time cost × implementation difficulty
Week 3-4: Pilot Design
- Choose ONE workflow (seriously, just one)
- Define success metrics (must be measurable)
- Select 2-3 team members as pilot group
- Design the before/after comparison
Week 5-8: Focused Training
- Not "here's ChatGPT, figure it out"
- Specific prompts for specific tasks
- Real examples from your actual projects
- Iteration and refinement as you learn what works
Week 9-12: Measurement & Refinement
- Track actual time savings
- Document quality improvements (or problems)
- Gather team feedback
- Adjust prompts and processes
- Calculate ROI
Month 4+: Strategic Expansion Only after the first workflow is running smoothly, proven valuable, and adopted by the team.
Why Engineering Firms Specifically Struggle
We're trained to be skeptical. To verify. To trust proven methods. These are strengths—until they become barriers.
I see this tension in myself constantly. Part of me wants to test every AI output against manual calculations. That's my engineering training protecting me from catastrophic failure. Smart.
But another part recognizes that AI excels at different tasks than precision calculations. It's brilliant at pattern recognition, information synthesis, and rapid iteration. Tasks where "approximately right, immediately" beats "perfectly right, eventually."
The key is knowing which tasks are which.
High-Stakes, Requires Precision: Keep the human in control. Use AI as a check, not the answer.
High-Volume, Requires Speed: Let AI handle it. Use human review for spot-checking.
Marcus Aurelius wrote: "The impediment to action advances action. What stands in the way becomes the way." Your team's skepticism isn't the problem—it's the design constraint. Build around it.
The Real ROI Calculation
Let's make this concrete.
Scenario: Mid-size civil firm, 15 engineers, average billing $150/hour.
One AI-Optimized Workflow: Preliminary site plan generation
- Current Time: 4 hours per project
- AI-Assisted Time: 1.5 hours per project
- Projects Per Month: 20
- Monthly Savings: 50 hours
- Annual Value: 600 hours × $150 = $90,000
Implementation Cost:
- ChatGPT Team: $600/year
- Training (my framework): 8 hours × $150 = $1,200
- Total First Year Cost: ~$2,000
ROI: 4,400%
And that's ONE workflow.
Scale that across 5-7 workflows? You're looking at 2-3 additional engineer-equivalents of capacity without hiring anyone.
What This Actually Looks Like In Practice
Real example from my own work:
Task: Respond to RFI (Request for Information) from the contractor about the drainage detail conflict.
Old Process:
- Pull up original drawings (5 minutes finding the correct file)
- Review conflicting details (10 minutes)
- Check code requirements (15 minutes)
- Draft response email (10 minutes)
- Have senior engineer review (5 minutes) Total: 45 minutes
AI-Assisted Process:
- Pull up drawings (same 5 minutes—AI doesn't help here)
- Prompt: "I have two conflicting drainage details [paste details]. Review against Texas stormwater code Chapter 15. Identify the conflict, recommend a solution, and explain code compliance." (2 minutes to write prompt)
- AI response in 30 seconds with code citations
- Senior review of AI output (3 minutes)
- Edit and send (2 minutes) Total: 12 minutes
Savings: 33 minutes per RFI. At 3-4 RFIs per week, that's 2+ hours weekly.
Is the AI perfect? No. Does it sometimes miss nuance? Yes. Does the senior engineer still review everything? Absolutely.
But we've compressed research and drafting time by 75%, and the AI often catches code requirements we might have missed.
The Question You're Really Asking
"Is this going to put engineers out of work?"
Wrong question. Better question: "Is this going to make good engineers unstoppable?"
Yes.
The firms that figure this out in the next 18 months will have an enormous competitive advantage. They'll respond to RFPs faster. Deliver prelims quicker and iterate designs with less friction. Bill the same rates but deliver more value in less time.
The firms that don't? They'll compete against AI-enhanced firms while using 1990s workflows.
Which side of that divide do you want to be on?
Start Here
If you're a principal or project manager at an AEC firm and this resonates:
- This Week: Do the workflow audit. One week. Track actual time usage.
- Next Week: Identify your first domino. The one workflow that's painful, frequent, and low-risk.
- Week After: Design your pilot. Two people. Four weeks. Specific success metrics.
Don't overthink it. Don't aim for perfection. Aim for "measurably better than current."
The firms winning at AI integration aren't the ones with the fanciest tools. They're the ones who started with the right questions.
Want help identifying your first domino? I offer AI Readiness Assessments specifically for AEC firms. Two weeks, comprehensive workflow analysis, and a custom implementation roadmap. Learn more about AI integration services.
Or if you'd rather explore on your own first, download my free guide: "7 AI Quick Wins for AEC Firms" — seven specific tasks with prompts you can implement this week. [Get the guide here].
Phillip Salaam
Civil Engineer | AI Integration Strategist | Building the future of AEC, one workflow at a time
Published: November 21, 2025 | Last Updated: November 21, 2025
