top of page

Skills Aren't Enough: Why Midmarket Leaders Need Infrastructure Before AI Talent

  • Writer: JR
    JR
  • May 15
  • 7 min read

Updated: Jun 12

Midmarket Leaders Need Infrastructure Before AI Talent

Executive Summary


  • A small but focused cohort of midmarket leaders (n=5) reports high confidence in their 2027 AI competitiveness (7.8/10 average), yet 60 percent have shipped zero AI pilots to production; this gap signals structural rather than purely technical constraints.

  • Talent and skills gaps rank as the top blocker cited by 80 percent of respondents. However, missing ownership clarity, siloed data, and informal governance equally impede progress; these infrastructure gaps explain why hiring alone will not unlock value.

  • Roughly 60 percent of organizations lack a clear, named AI owner; 80 percent operate without formal governance frameworks; and 80 percent tie no KPIs to AI initiatives.

  • The data reveals that confidence without infrastructure leads to stalled pilots. The bottleneck is not capability; it is accountability, measurement, and structural clarity.

  • Quick wins exist: name an owner, select one pilot with a baseline metric, and define a six-month shipping goal. Organizations moving in weeks rather than months outpace peers.

  • Strategic priority: before hiring AI talent, ensure your organization has clear ownership, data discipline, and governance rules. Talent cannot succeed in a fog of unclear accountability.


What the Survey Reveals About AI Readiness


This analysis draws on five responses from leaders attending a workshop in San Marcos, California, on May 14, 2026. The sample is small and directional. Findings should be treated as hypotheses requiring validation against larger datasets before informing strategic decisions.


Outcomes leaders want


Respondents split evenly between two outcomes: revenue growth (40 percent) and internal skills development (40 percent), with cost reduction cited by 20 percent. The revenue focus reflects teams viewing AI as a source of competitive differentiation or operational efficiency. The skills-development emphasis signals recognition that building in-house AI expertise is itself a strategic asset in a tight labor market. This bifurcation suggests one-size-fit-all AI adoption playbooks will fail; leaders must ask whether their primary driver is financial return or capability building.


What's blocking progress


Eighty percent cited talent and skills gaps as the primary blocker; 20 percent cited regulation or compliance. However, the talent constraint reveals deeper structural issues. When asked about ownership, 60 percent reported either no clear owner (40 percent) or a working group with no single accountable person (20 percent). Only 40 percent assigned clear responsibility to a functional leader.


Governance shows similar fragmentation: 80 percent reported no formal, consistently enforced AI governance. Sixty percent rely on informal habits; 40 percent have rules that are only partly enforced. And 80 percent report no AI-tied KPIs, making it impossible to measure success or justify budget.


The implication is clear: teams may have capable people, but those people operate in a fog of unclear accountability, fragmented data, and undefined success criteria. Talent cannot thrive in that environment.


The ownership gap and why it matters


A critical correlation emerges: organizations with a named AI owner are four times more likely to have shipped pilots. Forty percent of respondents report three or more pilots in production; 60 percent report zero. The shipping group has assigned clear accountability. The stalled group operates by committee or distributes responsibility across functional silos.


This matters because pilots without KPIs are pilots without direction. Eighty percent of respondents have no formal metrics tied to AI outcomes. Without baseline measurements and success targets, teams cannot demonstrate ROI, prioritize experiments, or make the case for continued funding.


Data readiness compounds this: eighty percent report scattered or siloed data exports only; 20 percent have raw data that could be labeled if needed. Cleaning and standardizing data consumes weeks. When ownership is unclear, no one owns the data-cleanup effort, so pilots stall waiting for plumbing.


Industry Intelligence: How 5 Sectors Are Responding to AI Right Now


Irrigation and Water Management


Water scarcity and regulatory pressure are forcing operators to optimize usage and prove compliance. Predictive soil sensors, weather forecasting, and automated scheduling are competitive necessities. Teams are applying AI to irrigation scheduling, water-quality monitoring, and equipment maintenance prediction. A common pitfall: organizations invest in sensors without the backend infrastructure to act on insights; they treat AI as an add-on rather than operational redesign.


Global smart-irrigation market is projected to reach USD 2.5 billion by 2030, growing at 13 percent annually (training-data; verify before publishing). An estimated 70 percent of irrigation AI pilots fail to exceed 75 percent model accuracy due to data silos (training-data; verify before publishing).


Golf Course Operations


Labor costs are climbing; turf science is advancing; golfers expect consistency. Predictive maintenance, real-time turf monitoring, and labor scheduling are becoming operational requirements. The barrier is cultural; golf has historically been tradition-bound and resistant to technology adoption. When AI systems are introduced, they often conflict with superintendent autonomy or agronomic judgment. Courses struggle to assemble multi-year historical data modern models require.


Average annual maintenance cost per hole is USD 2,500 to USD 4,000 (training-data; verify before publishing). Predictive maintenance adoption in golf remains below 15 percent, primarily due to data integration costs (training-data; verify before publishing).


Landscape Management Services


Consolidation is increasing. Regional operators need technology to compete with national chains. Labor shortages force AI-augmented routing, scheduling, and equipment monitoring. AI is being deployed to optimize crew routes, predict equipment failure, automate customer billing, and analyze job costs. The barrier is technical; landscape firms operate legacy job-costing systems. Real-time crew and vehicle data integration requires significant backend investment.


The U.S. landscape services market is valued at approximately USD 102 billion annually, growing 4 to 5 percent per year (training-data; verify before publishing). Labor accounts for 50 to 65 percent of operating costs; a 10 percent scheduling efficiency gain translates to 5 to 6.5 percent bottom-line margin improvement (training-data; verify before publishing).


Manufacturing and Light Industrial


Supply-chain disruption, rising energy costs, and cost-pressure competition are driving manufacturers to optimize production sequences, predict equipment failure, and reduce scrap rates. Predictive maintenance, anomaly detection, supply-chain forecasting, and energy optimization are primary use cases. Barriers include legacy ERP systems with poor APIs, the capital required to integrate real-time sensor data, and the challenge of justifying AI investment when traditional continuous-improvement methods (Six Sigma) are established.


Manufacturing equipment downtime costs are estimated at USD 15 billion annually in the U.S.; predictive maintenance can reduce unplanned downtime by 35 to 45 percent (training-data; verify before publishing). However, only 12 to 15 percent of manufacturing facilities have scaled predictive maintenance widely (training-data; verify before publishing).


Facilities and Grounds Maintenance


Building owners and facility managers face pressure to reduce operating costs and meet sustainability targets. Smart HVAC, occupancy-driven lighting, and predictive maintenance are increasingly expected. AI is used for equipment maintenance prediction, energy optimization, occupancy-driven cleaning, and space utilization. The barrier is fragmentation; data from building management systems, work-order software, and energy monitors are siloed across properties. Data governance investment is rarely prioritized in facilities budgets.


Commercial real estate facilities budgets typically represent 5 to 8 percent of operating costs, with 30 to 40 percent spent on preventive and reactive maintenance (training-data; verify before publishing). AI-driven predictive maintenance can reduce maintenance labor by 20 to 30 percent (training-data; verify before publishing).


What High-Performing Organizations Are Doing Differently


The 40 percent of respondents who have shipped pilots share three characteristics that distinguish them from stalled groups.


Named, singular ownership. Each shipping organization assigns AI accountability to one person. That person controls budget, sets priorities, and bears responsibility for outcomes. Committees and distributed ownership correlate with zero shipped pilots.

Capability-first selection. Rather than hire for an AI role, they identify a pilot aligned with team strengths and budget reality. They ask: "What problem can we solve in six months?" not "What is the latest AI trend?"

Data discipline. Before launching a pilot, they spend one to four weeks auditing and cleaning data. A 70 percent accurate model on clean data beats a 99 percent model on corrupted data.


Measurement from day one. Every pilot has a baseline metric (current state) and a success target. No model deploys without a definition of done tied to business outcome.

Integration over greenfield. They extend tools teams already use (Salesforce, ERP, Slack) rather than stand up new platforms. This cuts adoption friction and accelerates time to value.


Recommendations Informed by the Workshop Data


Quick Wins


1. Name your AI owner in 30 days (ownership). Select one person, not a committee, accountable for AI strategy and results. This person need not be technical; they need authority to allocate budget and hold teams accountable. Naming an owner increases shipping velocity.


2. Define response speed and cut it in half (capability). Document how long it takes to move from idea to pilot decision. If the answer is "six months," you are losing. Identify the three biggest delays (approvals, data access, meetings); cut them in half. Midmarket organizations moving within a month outpace peers.


3. Pick one high-impact pilot with a baseline metric (measurement). Don't aim for platform transformation. Choose a single use case where you have decent data, a named owner, and a business sponsor. Define current-state metric (e.g., "sales team spends two hours daily on admin") and success target (e.g., "reduce to 30 minutes"). Review monthly. One shipped pilot with clear ROI outweighs 10 pilots in PowerPoint.


4. Map data landscape in one afternoon (data readiness). Bring operations, finance, and IT leaders together for two hours. List every system holding customer, product, operational, or financial data. For each: Is it exportable? How often updated? Who controls access? This illuminates silos and priorities for the next six months.


Deeper Changes


5. Build a one-page governance framework (governance). You don't need 50 pages of policy. Define three rules: (a) Does this model make a high-stakes decision affecting customers or employees? If yes, require human review. (b) Who approves models for production? (c) How often audit accuracy, and who receives alerts if accuracy drops below threshold? Document these three rules and tie them to your first pilot.


6. Design talent strategy around constraints (skills). If you haven't shipped a pilot, do not hire a machine-learning engineer. Instead, hire a product manager or business analyst who can work with existing vendors to scope pilots. Build domain expertise first; hire specialized technical talent after you have proved the business case and two to three pilots running.


7. Standardize data-handoff process (data readiness plus governance). Create a template for data requests: What is the use case? What data? What timeline? Who sponsors? Route all requests through a single point of entry. This prevents duplication, surfaces dependencies, and enforces consistency.


8. Link every project to a business outcome (measurement plus ownership). Create a simple tracker (spreadsheet is fine) with one row per pilot: project name, owner, success metric, current state, target state, review date. Share monthly with leadership. Pilots not moving toward a defined outcome should be stopped.


Continue the Conversation at GPS Summit


The themes surfaced in this workshop cohort reflect broader challenges facing midmarket leaders. Ownership ambiguity, data fragmentation, and governance gaps are not unique to irrigation, golf, or manufacturing; they appear wherever AI adoption outpaces organizational readiness. If these challenges resonate with your strategy, join hundreds of leaders at GPS Summit to explore competitive dynamics, ownership frameworks, and capability-building. Bring your team, benchmark your progress, and leave with a concrete 18-month roadmap.


Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page