For a long time, mid-size IT companies operated in a comfortable middle ground.

They were more agile than large enterprises.
More structured than small agencies.
And usually cost-effective enough to compete globally.

That advantage is starting to shrink.

Across the industry, many mid-size IT firms are facing a combination of pressure points at the same time - shrinking margins, AI disruption, slower client decision-making, rising delivery expectations, and increasing competition from both global consulting firms and AI-native startups.

What makes the situation difficult is that most of these problems are interconnected.

And many leadership teams are still trying to solve 2022 problems with 2020 strategies.

mid-sized IT firms, because many are still structured around large projects

1. Clients Still Want Digital Transformation - But Budgets Are Tighter

One of the biggest misconceptions in the market right now is that technology spending has stopped.

It hasn’t.

Companies are still investing in cloud migration, AI, automation, analytics, cybersecurity, and modernization.

But clients have become significantly more cautious about how they spend.

Earlier, many IT vendors could win projects based on technical capability and relationship strength alone.

Today, clients want:

• faster ROI visibility
• smaller delivery cycles
• measurable business outcomes
• flexible commercial models
• lower operational risk

This is creating pressure on mid-sized IT firms because many are still structured around large-project delivery models.

The market is slowly shifting toward outcome-driven engagements instead of pure resource augmentation.

Suggested Approach

Mid-size IT firms need to reposition themselves from “technology vendors” to “business problem-solving partners.”

That requires:

• stronger domain expertise
• consulting-led discovery workshops
• ROI-driven proposals
• smaller pilot engagements before large commitments
• industry-specific accelerators

The companies growing right now are not necessarily building more software.

They are reducing uncertainty for clients.

2. AI Is Creating Excitement - But Also Internal Confusion

Almost every IT company today claims to be “AI-powered.”

Very few have clarity on what that actually means operationally.

Inside many mid-size organizations, leadership teams are facing difficult questions:

• Should AI reduce engineering headcount?
• Should pricing models change if development becomes faster?
• Which internal processes should be automated first?
• How should AI governance work?
• Which AI investments are practical versus experimental?

At the same time, clients are asking AI-related questions in almost every discussion.

Even when the project itself is not AI-focused.

This has created a strange environment where companies feel pressure to “appear AI-ready” without having a mature execution strategy.

Suggested Approach

The smarter firms are treating AI as an operational capability, not a marketing slogan.

Instead of chasing every trend, they are focusing on:

• AI-assisted development workflows
• internal productivity automation
• intelligent QA automation
• knowledge management systems
• AI governance policies
• secure enterprise AI adoption

The real opportunity is not replacing engineers overnight.

It is improving delivery efficiency without compromising quality.

3. Talent Retention Is Quietly Becoming a Leadership Problem

Hiring pressure may have slowed compared to previous years, but retention challenges still exist - especially for experienced engineers and architects.

One issue many mid-size firms underestimate is career perception.

Good engineers today are not only comparing salaries.

They are comparing:

• learning opportunities
• technical exposure
• work flexibility
• leadership quality
• engineering culture
• long-term career relevance

If employees feel they are working on repetitive maintenance projects while the industry is moving toward AI, cloud-native systems, and automation, attrition eventually follows.

Suggested Approach

Compensation alone is no longer enough.

Companies need stronger technical growth ecosystems internally.

That includes:

• internal innovation programs
• AI experimentation labs
• certification support
• architecture mentorship
• modern engineering practices
• opportunities to work on high-impact systems

Many mid-size firms still operate with outdated hierarchical delivery structures that limit engineering ownership.

That model is becoming less attractive to strong talent.

4. Service Commoditization Is Hitting Traditional IT Models

Basic development services are becoming increasingly commoditized.

Clients can now compare vendors globally within hours.

AI coding tools are also changing client perception around development effort and timelines.

As a result, companies competing only on hourly rates are entering a dangerous race to the bottom.

Suggested Approach

Mid-size firms need stronger differentiation.

That differentiation can come from:

• deep domain specialization
• proprietary accelerators
• strong product engineering capabilities
• cybersecurity expertise
• compliance knowledge
• platform partnerships
• managed services models

The companies that survive in the long term will likely combine services with intellectual property.

Pure execution models will become harder to scale profitably.

5. Delivery Expectations Have Changed Permanently

Clients now expect:

• faster releases
• higher quality
• stronger security
• better communication
• real-time visibility
• proactive issue handling

At the same time, many delivery teams are already stretched.

This creates operational fatigue internally.

A major challenge for mid-size IT companies today is balancing speed with engineering discipline.

Because rushed delivery often creates technical debt, quality issues, and client dissatisfaction later.

Suggested Approach

Organizations need to invest more seriously in delivery maturity.

That includes:

• stronger DevOps practices
• automated testing
• platform engineering
• observability systems
• delivery governance
• engineering metrics
• better cross-functional collaboration

Operational maturity is becoming a competitive advantage.

Not just a technical necessity.

6. Many Companies Are Still Too Dependent on a Few Clients

This is one of the most dangerous, but least discussed problems in the industry.

A large percentage of mid-size IT firms still generate most of their revenue from a small number of accounts.

That model becomes risky during market slowdowns.

When even one major client reduces spending, the impact spreads quickly across hiring, cash flow, utilization, and business confidence.

Suggested Approach

Revenue diversification needs to become a board-level priority.

That means:

• expanding into new verticals
• building recurring revenue models
• investing in partnerships
• creating reusable solutions
• improving account expansion strategies
• developing stronger inbound marketing

Many IT firms still rely too heavily on relationship-driven sales.

That alone is no longer sustainable.

Final Thoughts

The current IT market is not collapsing.

But it is restructuring.

And mid-size IT companies are under pressure because they sit directly between two extremes:

large enterprises with massive scale,
and smaller AI-native firms with high agility.

The next few years will likely reward companies that can balance:

efficiency with innovation,
AI adoption with governance,
speed with quality,
and growth with operational discipline.

The firms that adapt early will not just survive this transition.

They will emerge significantly stronger.

Curious to hear how others in the industry are seeing this shift.

Which challenge do you think is hurting mid-size IT companies the most right now?

I am curious to know how many users is an average amount to be directly responsible for supporting these days.

I work as a desktop support technician (tier 2, also handle helpdesk escalations and accounts for users assigned to me) at a university. I have a little over 450 assigned users, so I am responsible for creating, maintaining, and decommissioning their accounts. I am also responsible for maintaining their hardware and handling any purchase requests. In addition to that, I receive around 10-20 tickets a week from students when the helpdesk escalates to me.

I’m wondering how this workload compares to others in similar positions, both public and private sector, as I have not worked in IT anywhere else.

I work in DevOps, I have a couple years of experience and have been trying to transition specifically into infrastructure within the finance space.

I left my last longer term 2+ year role back in early 2025. Since then, I've bounced around quite a bit. A very short time in a senior systems engineer role (team fell apart), took a Support Engineer role for a security/networking product for 6 months.

Semi-recently I managed to get a role doing exactly what I wanted most FinTech/Infra, for a cool company, except it was 3rd shift. I only lasted a couple of months before I was burnt, it really didn't mesh with my health well.

So at this point I no longer have a coherent story or resume, I've bounced around a ton and because of it, I don't know how to even list the experience on resume, so I've just been leaving off the short-term roles, but I need to somehow illustrate I have some experience in Low-latency trading environments, think algo trading. It's pretty niche and even a little would make a huge difference. Breaking into the industry is incredibly hard IME.

I'm happy to answer any questions that might help.

Not an event planner, I work in IT.
But every time our company hosts a major event, suddenly I’m dealing with crm sync issues, registration data not transferring properly, broken email automations, badge printing issues, and login problems.
And somehow all of this happens right before the event starts.
Are event platforms just messy by nature or are we using the wrong tools?

I came across a moment recently that kind of sums up the weird tension around AI right now.

At a university commencement speech, the speaker (an exec at a real estate company) said that AI is the next industrial revolution. Big, optimistic, “this will change everything” kind of message.

And the crowd… booed.

Apparently one guy even yelled “AI sucks.”

At first that sounds harsh, but the more I think about it, the more it makes sense.

You’ve got someone established in their career, probably benefiting from AI as a productivity tool, telling a group of new grads that this shift is a good thing. Meanwhile those grads are walking into a job market where entry level roles are getting automated, the “boring work” that used to be a stepping stone is disappearing, and expectations are rising faster than opportunities. So yeah, of course the reaction is different.

I use AI a lot myself, and I can see both sides. On one hand, it does feel like a huge leap forward. On the other, if I were just graduating right now, I’d probably be more anxious than excited.

It feels like we’re in this strange moment where people further along in their careers are optimistic, and people just starting out are not so sure.

Curious what others think. If you were sitting in that audience, would you have booed?

I am curious to know how many users is an average amount to be directly responsible for supporting these days.

I work as a desktop support technician (tier 2, also handle helpdesk escalations and accounts for users assigned to me) at a university. I have a little over 450 assigned users, so I am responsible for creating, maintaining, and decommissioning their accounts. I am also responsible for maintaining their hardware and handling any purchase requests. In addition to that, I receive around 10-20 tickets a week from students when the helpdesk escalates to me.

I’m wondering how this workload compares to others in similar positions, both public and private sector, as I have not worked in IT anywhere else.

Something I've been thinking about after a few months of evaluating AI options for our service desk and basically the title.

Every vendor demo looks impressive. The AI intercepts the message, classifies it, maybe asks a clarifying question, routes to the right queue. Fast, clean, "intelligent." But then almost every case what we're watching is triage. The AI organizes the work. A human still does the work.

The vendors calling this "autonomous resolution" are mostly showing you demos where the request is something simple like a password reset and even then, the AI is logging the ticket and asking the human to click approve before anything happens.

The cases where AI actually resolves something end-to-end and not routes, not suggests, not creates a ticket... seem to require the system to already know a lot about the employee before the conversation starts. Role, permissions, what they have access to, who approves what for them. Without that context layer, the AI can't make decisions. It can only gather more information, which is still triage.

Is anyone running something that's past the triage stage? What does the employee data layer look like in those setups?

I have a PDF file that opens normally on my local computer. However, once I place/upload the same file on our network server, it no longer opens and shows this error in Adobe Acrobat:

“There was an error opening this document. Access denied.”

Possible things I’m thinking about:

• File permission/restriction on the network folder
• Server security settings or antivirus blocking the file
• Read/write access issue
• File path or mapped drive problem
• Adobe protected mode/security settings
• The file may be marked as blocked after transfer
• Possible issue or restriction on the server itself

Is there a possible reason the server may have an issue causing the file to be inaccessible? Has anyone encountered this before? Any suggestions on what to check or fix would be appreciated.

Had a technical support interview recently. The scenario was: a user says they can’t access a shared drive that other people on the team can still open.

I knew a few things to check: network connection, VPN status, drive mapping, permissions, group membership, and whether the share path was correct. But I answered too fast and basically listed all of them.

After the interview, I checked the notes from real-time meeting assistant and realized I skipped the reasoning part. I didn’t explain what I would ask first, what each answer would rule out, or why I would check one thing before another. That made my answer sound memorized, even though I understood the basic troubleshooting areas.

I wonder what is a good structure for answering scenario questions like this?