Many pilots, no shared decision standard
Different teams start assistants, automation and machine-learning experiments without consistent criteria for value, data, risk, ownership or readiness.
DataConsultant helps organisations determine whether their business priorities, use cases, data, architecture, controls, security, operating model and skills are ready for practical AI adoption. The result is an evidence-led view of what can advance, what needs preparation and what should wait.
Scope, evidence depth, timeline and commercial terms are confirmed after discovery. The service is vendor-neutral unless a specific platform decision is included.
AI readiness is most useful before substantial build, procurement or scale decisions—especially when enthusiasm is high but the conditions for reliable delivery are not yet clear.
Different teams start assistants, automation and machine-learning experiments without consistent criteria for value, data, risk, ownership or readiness.
Teams know data exists but cannot show whether it is accessible, current, permissioned, traceable, sufficiently representative or operationally usable for the intended AI workflow.
Privacy, security, human oversight, evaluation, third-party risk and evidence requirements are discovered late, forcing redesign or delaying release.
Business, data, technology, risk and operations teams each own part of the problem but no operating model defines who decides, builds, approves, monitors and supports AI systems.
Cloud, model, copilot or automation tools are being evaluated before priority workloads, data boundaries, interoperability, control needs and operating costs are sufficiently defined.
Leadership needs a defensible readiness position that separates viable near-term opportunities from initiatives that need foundation work or should not proceed yet.
An organisation is not “AI-ready” simply because it has a model licence, a cloud account or a prototype. Readiness means the intended use has a credible value case, suitable data and architecture, accountable ownership, proportionate controls, evaluation criteria, adoption capacity and a path to operate the capability after release.
Validate the business problem, accountable owner, evidence, feasibility, controls and acceptance conditions.
Expose data, architecture, integration, privacy, security, policy, skills and process prerequisites.
Identify common data, platform, governance, evaluation and operating capabilities that reduce duplicated investment.
Define owners, evidence, stage gates, exceptions, monitoring and review so readiness remains an operational discipline.
The depth of each domain depends on the use cases, risk profile, current technology estate and decisions required. The assessment can be enterprise-wide or focused on a business unit, portfolio or priority AI initiative.
Business objectives, decision rights, executive sponsorship, accountable benefit owners, AI principles and investment intent.
Problem definition, affected workflow, user needs, measurable outcomes, baseline logic, feasibility assumptions and prioritisation criteria.
Availability, quality, access, permissions, lineage, representativeness, retrieval content, labelling, retention and ownership.
System boundaries, APIs, data movement, cloud or hybrid constraints, identity, model access, interoperability and operational resilience.
AI inventory, risk classification, policy, transparency, human oversight, evidence, approval routes, exceptions and lifecycle accountability.
Sensitive data, access control, vendor dependencies, model and prompt exposure, residency, misuse, supply-chain and incident considerations.
Development practices, test strategy, acceptance criteria, evaluation data, monitoring, incident response, change control and service ownership.
Roles, capability gaps, change readiness, workflow redesign, training, support, communications and sustainable internal ownership.
The target is not “more AI”. It is a portfolio where approved initiatives have business ownership, suitable foundations, explicit controls, measurable acceptance criteria and an operating path.
The following maturity view is an illustrative assessment structure. Actual conclusions should be based on agreed evidence and use-case context rather than automatically assigning generic enterprise scores.
| Readiness domain | Foundation gaps | Emerging | Defined | Controlled | Scale-ready |
|---|---|---|---|---|---|
| Strategy & ownership | Ideas have no accountable sponsor or decision criteria. | Sponsors exist but priorities and ownership vary by team. | AI objectives, owners and portfolio criteria are documented. | Investment decisions use evidence, stage gates and review forums. | Portfolio governance is repeatable across business units. |
| Data & knowledge | Critical data, content, permissions or provenance are unknown. | Priority sources are identified; quality and access remain inconsistent. | Use-case data requirements, owners and acceptance criteria are defined. | Quality, lineage, access and freshness are monitored against requirements. | Reusable governed data products support multiple AI workloads. |
| Architecture & platforms | Pilots use disconnected tools with unclear integration or identity controls. | Preferred platforms exist but patterns and service boundaries vary. | Approved architecture, integration and deployment patterns are documented. | Security, observability, evaluation and change controls are integrated. | Standard patterns support governed reuse, portability and lifecycle operation. |
| Governance & risk | Risk, oversight and evidence expectations are addressed ad hoc. | Policies or review groups exist but coverage is inconsistent. | Risk tiers, roles, controls, records and escalation paths are defined. | Approvals, exceptions, incidents and evidence are traceable. | Governance is embedded in portfolio, engineering and operational workflows. |
| People & operations | No clear service owner, support path or adoption plan. | Specialists support pilots but ownership depends on individuals. | Roles, skills, handoffs, training and operational responsibilities are mapped. | Teams use defined runbooks, monitoring, review and improvement routines. | Capability, knowledge transfer and operating practices support sustained scale. |
Illustrative framework only. A real readiness position depends on the intended AI use, organisation, evidence, controls, jurisdictions and consequences of failure.
Readiness becomes useful when it changes a decision. A use case can move forward only when the evidence required for its next stage is sufficiently clear and material dependencies are understood.
Value, ownership, data, feasibility and control evidence are strong enough for a controlled pilot or next stage.
The opportunity remains viable but requires specific data, integration, governance, skill or operating prerequisites first.
Potential value exists, but assumptions or evidence need targeted discovery before funding or procurement.
Value is weak, dependencies are excessive, risk is disproportionate or the operating model cannot currently support the use case.
Deliverables are tailored during discovery. A focused assessment may use a subset, while an enterprise-wide review may require deeper evidence packs, business-unit views and implementation planning.
Decision summary, key findings, limitations, dependencies and recommended next actions.
Evidence reviewed, assumptions, gaps, owners and validation needs by assessment domain.
Current condition, material blockers, strengths and preparation needs across agreed domains.
Advance, prepare, explore or hold positions with rationale and required prerequisites.
Source, integration, platform, access, provenance, quality and operational dependency observations.
Ownership, policy, risk, privacy, security, evidence, oversight and escalation requirements.
Roles, decision rights, forums, service interfaces, skills, training and support implications.
Required evidence, technical checks, evaluation criteria, control gates and accountable approvers.
Sequenced remediation, shared capabilities, dependencies, owners, decisions and mobilisation actions.
Sequence and depth vary by scope. The process is designed to make findings reviewable, decisions explicit and implementation dependencies visible.
Confirm objectives, scope, decision requirements, sponsors, stakeholders and constraints.
Catalogue initiatives, use cases, systems, data, policies, vendors, evidence and known issues.
Review business, data, architecture, control, security, skills and operating readiness.
Challenge assumptions, identify missing evidence and calibrate findings with accountable teams.
Separate immediate opportunities from preparation work, discovery needs and deferred items.
Define pilot, release, control and evidence criteria with decision rights and escalation paths.
Sequence remediation, shared foundations, use cases, ownership and investment decisions.
The assessment can start with incomplete information, but unavailable evidence should be treated as a limitation and a preparation task rather than filled with assumptions.
Applicable frameworks depend on the organisation, intended use, jurisdictions and risk profile. They can provide useful control language and evidence expectations without turning a readiness assessment into a certification exercise.
A voluntary US framework structured around GOVERN, MAP, MEASURE and MANAGE. It can help organise risk, accountability and evidence questions for AI systems.
Open NIST AI RMF ↗NIST AI 600-1 extends AI RMF guidance for risks and risk-management actions associated with generative AI and can inform readiness questions for GenAI use cases.
Open NIST profile ↗An AI management system standard that can provide useful reference points for policy, roles, lifecycle management, risk, controls and continual improvement.
Open ISO reference ↗Privacy, data protection, sector rules and AI-specific requirements can affect readiness. For EU operations, AI Act obligations may be relevant; Indian organisations should also assess applicable data-protection duties.
EU AI Act enforcement update ↗Framework and regulatory references are planning inputs only. DataConsultant’s AI Readiness service does not itself provide legal advice, statutory certification or a guarantee of compliance. Applicability and interpretation should be confirmed with authorised legal, privacy, security, risk and compliance specialists.
Technology recommendations remain requirements-led. The assessment can work with existing enterprise investments, multiple clouds or a vendor-selection question when that decision is in scope.
A readiness review is not the right answer to every AI question. Clear fit boundaries help avoid paying for a broad assessment when a narrower delivery, quality, assurance or strategy service is more appropriate.
DataConsultant does not publish a fixed fee for this service. Public pricing reviewed for comparable AI readiness assessments in India can provide a planning reference while your exact scope, evidence depth and deliverables are being defined.
A defensible public-market planning band for enterprise-oriented AI readiness assessments, based on current published examples reviewed on 8 September 2026.
Public comparables used only for market guidance: Accucia AI Readiness Audit (₹2–₹5 lakh), IABAC 2026 India benchmark (about ₹3–₹8 lakh), and MLDeep published assessment pricing (₹6–₹8 lakh). Scope and provider models differ, so these figures should not be treated as quotations or like-for-like offers.
The service is designed for cross-functional enterprise decisions rather than a tool demonstration or checklist-only audit.
Readiness begins with the decision, workflow, user, value hypothesis and accountable owner—not with a preferred model or platform.
Findings identify documented evidence, assumptions, limitations and validation needs so executives can see confidence and gaps.
Existing investments and vendor constraints can be considered without treating procurement as a substitute for requirements.
Governance, privacy, security, human oversight and evaluation requirements are included in readiness and roadmap decisions.
Deliverables are structured to support pilots, architecture, governance setup, remediation, procurement and mobilisation where scoped.
Internal teams can be equipped with reusable decision criteria, evidence expectations, templates and operating guidance.
Use the readiness findings to choose targeted follow-on work instead of automatically expanding into a broad programme.
Practical answers on scope, sponsorship, evidence, pricing, deliverables, governance and what happens after the assessment.
AI readiness is the evidence-based assessment of whether an organisation can make, deliver and govern AI investments responsibly. It examines business objectives, use cases, data, technology, integration, security, privacy, governance, skills, operating model, change capacity, evaluation and operational support so leaders can decide what is ready now, what needs preparation and what should be deferred.
Scope can include executive alignment, AI initiative and use-case inventory, data and integration review, architecture and platform assessment, governance and responsible-AI controls, privacy and security considerations, operating-model and skills review, evidence-based readiness findings, dependency analysis, pilot entry criteria, prioritisation and a phased remediation or adoption roadmap. Final scope is agreed during discovery.
AI readiness answers whether the organisation has the foundations, controls and delivery conditions required to pursue specific AI ambitions. An AI strategy is broader: it defines where AI should create value, what portfolio and capabilities are required, how investment will be governed and how execution will be sequenced. A readiness assessment can inform an AI strategy or validate whether an existing strategy is executable.
Use case prioritization compares competing AI opportunities and helps decide which should advance, prepare, explore or defer. AI readiness evaluates the organisational and technical conditions required to execute those opportunities, including data, architecture, controls, security, skills, ownership and operational support. The two activities are often combined when a portfolio decision is required.
Sponsorship commonly comes from a CIO, CTO, Chief Data Officer, Chief AI Officer, COO, transformation leader or accountable business executive. Useful participation usually includes business owners, data and AI teams, enterprise architecture, security, privacy, legal, risk, compliance, finance, procurement, HR or learning teams, and platform owners where relevant.
Useful inputs include strategic priorities, current AI ideas and pilots, business process information, architecture diagrams, platform and application inventories, data-source and data-flow information, policies, security and privacy requirements, vendor contracts where relevant, model or prompt documentation, evaluation evidence, risk registers, skills information, delivery plans and access to accountable stakeholders. Missing evidence is recorded as a limitation rather than assumed.
Typical outputs can include an executive readiness brief, evidence register, domain-by-domain readiness profile, use-case readiness and dependency map, data and architecture findings, governance and risk-control map, target operating-model recommendations, pilot entry and exit criteria, prioritised remediation backlog, investment dependencies and a phased AI readiness roadmap.
A reliable duration is confirmed after scoping. Timing depends on the number of business units and use cases, stakeholder availability, platform and data complexity, evidence quality, workshop requirements, jurisdictions and risk depth, and whether detailed roadmapping, technical validation or implementation planning is included. Public market examples range from focused two-week audits to broader multi-workstream assessments, but DataConsultant does not promise a fixed duration before scope is agreed.
DataConsultant does not publish a fixed fee for this service. Current public India pricing researched for comparable readiness assessments shows enterprise-oriented examples around ₹2 lakh to ₹8 lakh, with lighter diagnostics below that range and broader programmes potentially above it. This is indicative market guidance, not a DataConsultant price. Final pricing is scope-led and confirmed through a quote.
Yes, when those use cases are in scope. Readiness can consider knowledge and retrieval quality, data permissions, model and vendor dependencies, prompt and application architecture, evaluation, hallucination and harmful-output risks, security, human oversight, tool access, workflow authority, monitoring, incident handling and operational controls. Requirements should be proportionate to the intended use and consequences of failure.
The assessment can map relevant policies, standards, privacy, security, recordkeeping, human-oversight and regulatory considerations into readiness findings and control requirements. It does not itself provide legal advice, statutory certification, penetration testing or a guarantee of compliance. Applicability and formal interpretation should be confirmed with authorised legal, privacy, security, risk and compliance specialists.
No. The service can remain vendor-neutral and assess the existing or planned technology ecosystem against business requirements, interoperability, security, data residency, operating skills, control needs and total operating implications. Vendor or platform selection can be added when procurement or architecture decisions are explicitly in scope.
Yes. Follow-on support can be scoped for AI strategy, use-case prioritization, data-quality improvement, governance and responsible AI, architecture, evaluation strategy, pilot mobilisation, implementation assurance, intelligent automation, training or managed data and AI operations. Accountabilities, acceptance criteria and commercial terms should be agreed before implementation begins.
Unless explicitly scoped, the service does not automatically include production AI development, full data remediation, platform procurement, legal opinions, statutory audits, formal certification, penetration testing, comprehensive model red teaming, supplier contract negotiation or ongoing managed operations. The readiness review identifies where specialist work may be required and how those dependencies affect the roadmap.
Share your current AI initiatives, business priorities, known data or control concerns, and the decision you need the assessment to support. DataConsultant can use that context to shape an appropriate readiness scope.
Required fields are marked with an asterisk. Please describe the decision, initiative or readiness concern in enough detail for a useful scoping response.