One method, twelve companies, one baseline: getting ahead of the AI readiness gap
A single read answers one company’s question. A portfolio baseline on one method shows where AI can run across the fund, and where to fix first.
Read
Research and reports7 min read
Software, manufacturing, healthcare, retail and financial services: where each sector’s data tends to be strong, where it breaks, and what to check first.
Industries don’t start AI from the same place. A software company collects structured data by design; a manufacturer runs plant systems that were never built to talk to the CRM; a healthcare group joins patients, payers and sites across systems bought at different times. The question is the same everywhere, can the data carry the AI on the table, but the place to look first is not.
Understanding these industry-specific patterns helps organisations set realistic expectations, prioritise appropriate use cases, and benchmark their readiness against relevant peers. A manufacturing company should not compare itself to a tech company. A healthcare provider faces different challenges than a retailer.
This analysis examines AI readiness patterns across major industry sectors, identifying common strengths, hidden challenges, and priority focus areas for organisations in each sector.
Business-to-business software companies generally have the highest AI readiness among traditional industries. Their digital-native operations generate comprehensive data, and their technical teams understand data and AI requirements.
Product usage data is comprehensive. SaaS platforms capture detailed telemetry about how customers use the product. Feature adoption, usage frequency, workflow patterns, and performance metrics are automatically collected. This data provides rich signals for AI applications like churn prediction, upsell targeting, and product optimisation.
Engineering capabilities enable rapid experimentation. Software companies have technical teams who understand data pipelines, APIs, and machine learning infrastructure. They can build and deploy AI applications faster than organisations without this technical foundation.
Data-driven culture supports AI adoption. Software companies are accustomed to measuring everything and making decisions based on data. The cultural barriers to AI adoption are lower than in industries where intuition and experience traditionally dominated decision-making.
Customer data often fragmented across go-to-market systems. While product data is comprehensive, customer data may be scattered across CRM, marketing automation, support systems, and billing platforms. Integrating these systems for a complete customer view is often harder than expected.
Self-service and product-led growth models create data gaps. Customers who sign up and use the product without sales interaction may have sparse CRM records. The customers most likely to churn without warning, those who never engaged with success teams, are often the customers with the least data.
Rapid product changes invalidate historical patterns. Software products evolve quickly. Features are added, redesigned, or deprecated. Usage patterns that predicted churn in the old product version might not apply to the new version. AI models trained on historical data may not transfer to current conditions.
B2B software companies should focus on customer data integration across systems, establishing consistent customer identity across product, sales, and support data. They should also address the challenge of modelling through product changes, developing approaches that adapt to evolving product contexts.
Manufacturing companies often have rich operational data from production systems but struggle with the IT infrastructure and data integration required for AI applications.
Rich operational data from production systems. Modern manufacturing equipment generates extensive sensor data, quality measurements, and production metrics. This data can support AI applications in predictive maintenance, quality optimisation, and demand forecasting.
Clear ROI cases for AI. Manufacturing inefficiencies have direct cost implications. Reducing unplanned downtime, improving yield, and optimising inventory have quantifiable value that makes AI business cases straightforward.
Process discipline supports data governance. Manufacturing operations require process discipline for quality and safety. This discipline can extend to data governance when organisations make the connection.
Legacy OT/IT divide creates data accessibility issues. Operational technology systems on the factory floor often run on proprietary protocols with limited integration to enterprise IT systems. Getting data from machines into AI-ready formats requires bridging this divide.
Historical data may exist only in paper or disconnected systems. Older manufacturing data might be in paper logs, local databases, or obsolete systems. Digitising and integrating this historical data for AI training is often a major undertaking.
Data from acquired facilities may be incompatible. Manufacturing companies that have grown through acquisition often have different systems and standards at different facilities. Standardising data across sites is a prerequisite for enterprise-wide AI.
Manufacturing companies should prioritise OT/IT integration to make operational data accessible for AI applications. They should also focus on data standardisation across facilities to enable enterprise-wide AI rather than site-by-site solutions.
Healthcare organisations have strong data governance driven by regulatory requirements but struggle with data fragmentation across clinical and administrative systems.
Strong data governance driven by regulatory requirements. HIPAA and other healthcare regulations require careful attention to data handling. Healthcare organisations have established governance frameworks that can be extended to AI requirements.
Rich clinical data with potential for AI impact. Electronic health records contain detailed patient information that can support AI applications in diagnosis support, treatment optimisation, and population health management.
Clear value from AI applications. AI that improves clinical outcomes, reduces readmissions, or enhances operational efficiency has obvious value in healthcare. The case for AI investment is often compelling.
Data fragmented across EMR, billing, scheduling, and departmental systems. Healthcare data is notoriously siloed. A single patient might have records in the EMR, the billing system, the radiology PACS, the lab information system, and multiple departmental applications. Integrating this data for a complete patient view is extremely difficult.
Interoperability standards are improving but not solved. FHIR and other standards are making healthcare data exchange easier, but full interoperability remains aspirational. Data from different systems may have different formats, codes, and meanings.
Privacy constraints limit data use. Even with strong governance, privacy requirements may limit how data can be used for AI. Training models may require de-identification that reduces data utility. Some valuable data linkages may be prohibited.
Healthcare organisations should focus on clinical data integration, building comprehensive patient views from fragmented systems. They should also address the privacy/utility balance, developing approaches to use data for AI while meeting regulatory requirements.
Retail organisations have high transaction volumes providing ample data for AI but struggle with customer identity across channels.
High transaction volumes provide ample training data. Retail transactions number in the millions or billions, providing extensive data for AI applications like demand forecasting, recommendation engines, and pricing optimisation.
Digital commerce generates rich behavioural data. E-commerce platforms capture detailed clickstream data, search behaviour, cart activity, and purchase patterns. This behavioural data provides strong signals for personalisation and prediction.
AI directly impacts core business metrics. Better recommendations increase conversion. Better forecasting reduces stockouts and overstock. Better pricing improves margins. The path from AI to business value is direct.
Omnichannel creates identity resolution challenges. A customer who browses on mobile, researches on desktop, and purchases in store appears as three different people in channel-specific systems. Unifying these identities to build a complete customer view is technically challenging and often incomplete.
Anonymous and guest transactions limit personalisation data. Many retail transactions, especially in stores, are anonymous. Without customer identity, these transactions cannot contribute to individual-level AI applications like personalisation.
Seasonal and promotional patterns complicate modelling. Retail demand is heavily influenced by seasons, promotions, and events. Models must account for these patterns, which requires data spanning multiple seasonal cycles and comprehensive promotional calendars.
Retail organisations should prioritise customer identity resolution across channels and touchpoints. They should also focus on comprehensive promotional and pricing data to enable accurate demand modelling.
Financial services organisations have extensive data and sophisticated analytics capabilities but face complex regulatory requirements for AI applications.
Extensive transaction and customer data. Banks and financial services companies have detailed records of every transaction, balance, and customer interaction. This data can support AI applications in fraud detection, credit risk, and customer analytics.
Sophisticated analytics heritage. Financial services have long used statistical models for credit scoring, risk assessment, and fraud detection. The transition to machine learning builds on existing analytical capabilities.
AI directly impacts risk and revenue. Better fraud detection reduces losses. Better credit models improve risk-adjusted returns. Better customer analytics increases cross-sell success. AI impact is directly measurable.
Regulatory requirements for model explainability. Regulations like the Equal Credit Opportunity Act require that credit decisions be explainable. Black-box AI models may not meet regulatory requirements, limiting the techniques that can be applied.
Legacy core systems complicate data access. Many financial institutions run on core systems that are decades old. Extracting data from these systems for AI applications requires careful integration work.
Data from acquisitions may have different standards. Financial services consolidation has created institutions with multiple legacy systems from acquired companies. Data standardisation across these systems is an ongoing challenge.
Financial services organisations should focus on regulatory-compliant AI approaches that meet explainability requirements. They should also prioritise core system data integration to make legacy data accessible for modern AI applications.
Understanding industry patterns helps organisations benchmark their readiness against relevant peers. A manufacturing company in the bottom quartile of manufacturing AI readiness faces different challenges than a manufacturing company in the top quartile.
Benchmarking should consider both absolute readiness, measured against AI requirements, and relative readiness, measured against industry peers. Being above average in a low-readiness industry still means significant work to achieve AI success. Being below average in a high-readiness industry suggests the organisation is falling behind competitors.
Industry patterns also inform prioritisation. In industries where integration is the primary challenge, integration investments have the highest leverage. In industries where data volume is adequate but quality is poor, quality remediation is the priority.
The goal is not to excuse poor readiness based on industry challenges but to understand the specific obstacles to address. Every industry has organisations that have achieved AI success by addressing their sector-specific challenges. Understanding those challenges is the first step to joining them.
Insights by email
Short notes on what company data can and can’t carry, for CEOs, CFOs and investors weighing an AI decision. No vendor news, no sales sequence.
Exports from two or more systems, compared record by record. The gaps between them, and a verdict, in a signed memo within 5 working days of complete exports. From a firm with nothing else to sell you.
Starts with a 30-minute call. Commits you to nothing.