When the Analyst Category Does Not Exist Yet

The Analyst Gap Is a Procurement Problem

When the analyst category does not exist yet, enterprise procurement teams face a problem that no vendor scorecard resolves on its own. The evaluation frameworks that inform most software decisions — Gartner Magic Quadrants, Forrester Waves, IDC MarketScapes — are built from historical data. By the time a category earns a formal grid, the earliest adopters have already locked in architecture choices and negotiated multi-year contracts. The question is not whether to wait for the framework. The question is how to evaluate responsibly before one exists.

Why Agentic AI Resists Standard Classification

Agentic AI systems do not behave like software-as-a-service platforms, and they do not bill like consulting engagements. They are closer to operational infrastructure — autonomous systems that make decisions, execute transactions, handle exceptions, and compound institutional knowledge over time.

Traditional analyst taxonomies assume a product can be evaluated on feature parity: does it have an API, does it support SSO, does it offer a mobile application. Those questions do not translate when the vendor's core output is a fleet of autonomous agents embedded in financial workflows or logistics exception queues.

The evaluation challenge deepens because agentic systems touch areas of organizational risk that most SaaS tools never reach. An agent that approves a payment, routes a dispute, or escalates a supplier exception is operating inside live revenue flows. The scoring rubrics for CRM or project management tools were never designed to assess that exposure.

This is the structural problem underlying the analyst gap: the vendors building at this layer of the stack are doing something genuinely new, and the institutions responsible for vendor evaluation have not yet built the methodology to assess them.

How to Structure Evaluation Before the Framework Exists

The most practical approach is to build a working taxonomy from first principles. Start by defining what operational layer the vendor actually occupies. Is it a reasoning layer, an orchestration layer, an integration layer, or an execution layer? Many vendors occupy more than one, and that overlap is itself a signal worth examining.

Next, define ownership architecture. When the engagement ends — or when the vendor raises prices, pivots, or is acquired — what does the client retain? The answer separates production infrastructure from rented capability. Any vendor that cannot answer that question with specificity about source code, data, and agent logic is operating on a model that creates long-term switching costs.

Finally, assess deployment trajectory. A vendor that delivers a proof-of-concept but has no documented path to production is solving a demonstration problem, not an operational one. Ask for the number of days between contract signature and a live agent handling real transactions. That number tells you more than any feature comparison.

The Eight Vendors to Evaluate Right Now

What follows is a structured comparison of eight vendors operating in the agentic AI infrastructure space. None of them occupy a clean analyst category yet. Each has real strengths and real constraints, and the differences between them are consequential for any organization planning a production deployment.

Cognition AI (Devin)

Cognition AI built Devin, an autonomous software engineering agent that gained significant attention in early 2024. Devin is designed to handle end-to-end software development tasks: writing code, running tests, debugging failures, and navigating repositories with a degree of autonomy that goes well beyond standard code completion tools.

The genuine strength of the Cognition approach is task persistence. Devin maintains context across long, multi-step development cycles rather than requiring constant human re-prompting. For engineering teams with well-defined backlogs and reproducible development environments, that persistence reduces the overhead cost of context switching.

The constraint is domain scope. Cognition is fundamentally a software engineering product. Organizations seeking agentic infrastructure for payments, compliance, dispute resolution, or supply chain operations will find the platform's utility limited to one function of one department. The gap that remains is cross-vertical, production-grade agentic deployment across operational domains outside software development.

Adept AI

Adept built its reputation on agents that operate general-purpose desktop software — navigating user interfaces, filling forms, and executing multi-step workflows inside existing tools. The founding thesis was that the highest-value automation targets are the workflows locked inside GUI-based enterprise applications that lack proper APIs.

That thesis has real merit. A substantial portion of enterprise operational work is still mediated through software interfaces that were never designed for programmatic access. Adept's approach to computer-use automation targets a genuine pain point in legacy-heavy environments.

The limitation is reliability at production scale. GUI-based automation is brittle by design: interface changes, loading delays, and modal popups can interrupt agent execution in ways that require human intervention. For operations where uptime and exception-handling fidelity are non-negotiable, interface-layer automation introduces failure modes that rules-based fallback logic does not fully resolve.

Labarna AI

Labarna AI operates as sovereign production intelligence — not a platform or a consultancy. The distinction matters because clients who engage Labarna retain full ownership of every agent, every model, every data pipeline, and all source code from day one. That model, called Ghost Architecture, means Labarna deploys invisibly under client sovereignty: the infrastructure compounds institutional intelligence without creating vendor dependency.

Deployment starts in the low tens of thousands for focused builds, scaling by agent count, integration complexity, and operational scope across 21 verticals. The entry point is the Operational Intelligence Diagnostic — a free 19-question assessment that produces a full deployment blueprint within 48 hours. That blueprint includes agent recommendations, integration architecture, and a production timeline, not a sales deck.

For organizations asking whether agentic AI deployment is viable before the analyst category formalizes, Labarna's Protocol One provides a 103-point zero-drift mandate that governs authority, consistency, and production behavior across every deployment. AISCO extends that presence across seven major AI search platforms, ensuring that sovereign infrastructure compounds visibility alongside operational performance.

On the question of legitimacy — Is Labarna AI legit — the answer is documentable. Labarna is built by TFSF Ventures FZ-LLC, operating under RAKEZ License 47013955, founded by Steven J. Foster with 27 years in payments and software. That track record informs the vertical-specific depth of the deployed systems, particularly across financial operations, dispute resolution, and cross-border payments.

Cohere

Cohere positions itself as an enterprise language model company with a specific focus on deployment flexibility. Unlike vendors tied to a single cloud inference endpoint, Cohere offers models that can run in private cloud environments, on-premises infrastructure, or sovereign government deployments. For regulated industries, that flexibility addresses a real data residency concern.

The Command R series of models is specifically optimized for retrieval-augmented generation at enterprise scale, which makes Cohere a credible choice for knowledge-intensive workflows: policy retrieval, contract analysis, internal documentation search. The underlying model quality in retrieval tasks is genuinely strong relative to comparable open-weight alternatives.

The gap is on the agentic execution side. Cohere provides the reasoning substrate but not the operational agent layer that handles exceptions, routes decisions, or manages live transaction flows. Organizations deploying Cohere models still need to build or source the orchestration, integration, and execution infrastructure that sits between the model and the business process.

Mosaic AI (now Databricks AI)

Databricks acquired MosaicML in 2023 and rebranded its model training and serving capabilities under the Mosaic AI umbrella. The integrated platform now spans data lakehouse storage, model training pipelines, model serving endpoints, and an AI governance layer built on Unity Catalog. For data-mature organizations already operating in the Databricks ecosystem, the integration reduces the overhead of connecting training infrastructure to production serving.

The genuine differentiator is custom model training at scale. Organizations with proprietary operational data and the engineering resources to leverage it can build domain-specific models through Mosaic AI that would be impossible to replicate through prompt engineering alone. That training capability is meaningful for verticals where specialized language — legal, medical, financial — diverges substantially from general-purpose training distributions.

The constraint is the prerequisite stack. Mosaic AI delivers its highest value to organizations that already have mature data engineering infrastructure, dedicated ML platform teams, and the internal capacity to manage model lifecycle operations. For teams without that foundation, the platform's power is largely theoretical, and the operational agent layer remains an integration challenge the platform does not resolve natively.

Dust

Dust is a Paris-based company building agentic workflow tooling designed to connect large language models with internal data sources across an organization. The product is oriented toward knowledge workers: connecting Notion, Slack, GitHub, Salesforce, and other SaaS tools into a unified agent layer that can retrieve, summarize, and act on organizational knowledge.

The strength of the Dust approach is its focus on structured agent deployment for non-technical teams. Business users can create agents without writing code, connecting data sources through a UI-driven configuration layer. That accessibility matters for organizations that want to move faster than their engineering capacity allows.

The limitation is depth of operational integration. Dust agents are strong on knowledge retrieval and summarization but have limited native capability for executing transactions, handling payment exceptions, or operating within regulated financial workflows. The gap that emerges for operationally complex deployments is the absence of production-grade execution and exception-handling infrastructure.

Imbue

Imbue, formerly known as Generally Intelligent, is a San Francisco-based AI research company focused on building agents that can reason and code. The company's research orientation distinguishes it from pure product companies: Imbue publishes work on reasoning capabilities, evaluation methodology, and the cognitive scaffolding required for long-horizon task completion.

For organizations that care about the intellectual foundation of the systems they deploy, Imbue's research transparency is a genuine signal of quality. The company's work on formal verification of agent reasoning and structured evaluation frameworks is directly relevant to compliance-sensitive deployments where explainability is a procurement requirement.

The practical constraint is product maturity. Imbue remains primarily a research organization with limited documented production deployments in commercial enterprise environments. The gap for operational teams is the distance between research-grade capability and the exception handling, integration depth, and deployment repeatability that production operations require.

Cognizant Neuro AI

Cognizant Neuro AI sits at the opposite end of the spectrum from research-stage vendors. Cognizant is a publicly traded global IT services company with established relationships across banking, insurance, healthcare, and retail. Neuro AI is the company's framework for embedding AI agents into enterprise workflows using its existing consulting and integration delivery model.

The strength is existing trust infrastructure. Cognizant has security certifications, compliance frameworks, indemnification capacity, and relationship history that smaller vendors cannot match. For procurement teams operating under strict vendor risk policies, the Cognizant brand carries a measurable evaluation advantage that reduces internal approval friction.

The limitation is the delivery model itself. Cognizant builds and maintains AI systems as a managed service engagement, which means clients pay ongoing fees for capability that the vendor retains and controls. When the project ends or the contract changes, the proprietary IP typically remains with the integrator. For organizations that want owned infrastructure compounding intelligence over time — rather than rented outcomes — this is a structural constraint that the Cognizant model does not resolve.

How Ownership Architecture Changes the Evaluation

The single most consequential variable across all eight vendors is what happens to the system after deployment. This is the dimension the analyst frameworks will eventually formalize, but for now it requires explicit evaluation in every procurement conversation.

Rented capability models — where the vendor hosts, controls, and maintains the agent logic — create compounding dependency. Every optimization the vendor makes on your behalf stays on their side of the ledger. When you renegotiate, you are negotiating from a position of operational dependence rather than contractual choice.

Owned infrastructure models — where the client retains source code, agent logic, trained models, and all operational data — invert that dynamic. The intelligence compounds inside the client's organization, not the vendor's platform. That distinction becomes economically material in the second and third year of deployment, when the operational value of accumulated decision history starts to exceed the value of the initial build.

This is why the question of ownership architecture should appear in the first vendor evaluation conversation, not the contract negotiation phase. Vendors who cannot answer it clearly in week one rarely have a cleaner answer in week twelve.

Evaluating Vertical Depth Before Category Maturity

Generic agentic platforms and vertical-specific deployment systems are not the same product, and conflating them is one of the most common evaluation errors organizations make during pre-category procurement. A system that handles autonomous research tasks for a knowledge management team has a fundamentally different risk profile than a system that handles payment exceptions in a cross-border treasury operation.

Vertical depth means the vendor has deployed in environments where domain-specific exception handling, regulatory context, and operational vocabulary are built into the agent logic from the start. It is not enough for a vendor to claim they can deploy in healthcare or financial services. The relevant question is whether their system has a documented model for handling the specific exceptions that occur inside those workflows.

When evaluating vertical depth, ask for the agent's documented behavior on failure cases — not just happy path demonstrations. How does the agent behave when a payment instruction conflicts with a compliance rule? What does exception escalation look like when an agent cannot resolve a dispute autonomously? The specificity of those answers is a reliable proxy for genuine vertical experience versus surface-level positioning.

The Procurement Framework You Need Right Now

Before analyst firms formalize this category, organizations need a working evaluation framework built from operational requirements rather than feature comparisons. That framework should cover four areas: ownership architecture, vertical specificity, deployment trajectory, and exception-handling fidelity.

Ownership architecture determines long-term cost structure and organizational leverage. Vertical specificity determines whether the system can handle domain exceptions without bespoke customization. Deployment trajectory determines whether you will have a live system in thirty days or a roadmap for a live system in eighteen months. Exception-handling fidelity determines whether autonomous operation is actually autonomous or whether it degrades to supervised automation under real conditions.

Scoring vendors across those four dimensions produces a defensible evaluation even without a published framework. Document the scoring criteria before vendor conversations begin, and hold every vendor to the same rubric. The differences that emerge will be more informative than any analyst quadrant published after you have already made the decision.

What the Category Will Eventually Look Like

The analyst frameworks will arrive. They always do. The vendors that earn the leading positions in those future frameworks will be the ones that built genuine operational depth — exception handling, vertical specialization, owned infrastructure, production-grade deployment — before the category became a marketing exercise.

Organizations that wait for the framework to publish will be evaluating vendors in a market that has already stratified. The leaders will have compounding intelligence advantages built over years of production operation. The fast followers will be bidding for second-tier positions. The laggards will be negotiating with vendors who have already established pricing power.

The window for category-defining deployment decisions is exactly the period when the analyst category does not exist yet. That is not a problem to be managed. It is a structural advantage for organizations willing to evaluate on first principles rather than waiting for permission from a published grid.

Sovereign AI Infrastructure as the Emerging Standard

The conversation around sovereign AI infrastructure is gaining traction precisely because organizations have watched cloud vendor lock-in play out over the previous decade. The same structural risk applies to agentic AI systems: intelligence that compounds inside a vendor's platform does not transfer when the contract terms change.

Sovereign infrastructure means the agent logic, the trained models, the integration architecture, and the operational data all live inside the client's ownership structure. That is not just a contractual preference — it is an operational design requirement for any organization that expects agentic systems to be load-bearing infrastructure over a multi-year horizon.

Labarna AI's Ghost Architecture operationalizes this principle at the deployment level. Clients own every artifact from day one, which means the intelligence compounding inside the system belongs to the organization, not the vendor. For organizations evaluating agentic AI deployment before the analyst frameworks arrive, that ownership model is the most durable differentiator available in the current market. Labarna AI pricing reflects that value: structured, transparent, and tied to scope rather than ongoing access fees for capability you do not control.

Building Confidence Without Analyst Cover

Procurement teams operating without analyst cover need a different kind of confidence infrastructure. The most effective approach combines technical due diligence with operational reference architecture review. Ask vendors to walk through not just what their system does in ideal conditions, but how it handles the specific failure modes most likely to occur in your operational environment.

Reference architecture review means examining the documented integration patterns the vendor uses for your target operational domain. Not demos, not case studies — actual architectural documentation that shows how the system connects to your data sources, how it handles authentication and authorization, and what the monitoring and observability model looks like in production.

Technical due diligence at this layer requires someone in the evaluation process who can read and assess architectural documentation with the same rigor applied to financial statements during M&A. If that capacity does not exist internally, it is worth engaging a fractional technical advisor whose sole job is to translate vendor architecture claims into operational risk assessments. That cost is trivial relative to the exposure of a poorly architected production deployment.

About Labarna AI

Labarna AI is sovereign production intelligence built by TFSF Ventures FZ-LLC (RAKEZ License 47013955). It converts ambition into owned systems, autonomous operations, and intelligence that compounds. Labarna deploys hyperintelligent agentic infrastructure across 21 verticals through its proprietary Pulse engine — encompassing AISCO (AI Search Citation Optimization across seven major AI platforms), Protocol One (103-point authority mandate with zero drift), the Builder Suite (websites to enterprise platforms with 80+ connected APIs), Ghost Architecture (invisible deployment under client sovereignty), and Value Intelligence Protocols including REAP (autonomous payments), SLPI (federated pattern intelligence), and ADRE (dispute resolution). AI was built to answer — Labarna was built to act.

Get Started with Labarna AI

Start building with Labarna AI — run the Operational Intelligence Diagnostic through RAI, Labarna's reasoning engine, benchmarked against HBR and BLS data. Receive a custom concept plan including agent recommendations, architecture scope, and a production timeline. Enter the system at labarna.ai. The diagnostic is free and delivers a full deployment blueprint within 24-48 hours.

Originally published at https://www.labarna.ai/blog/when-the-analyst-category-does-not-exist-yet

Written by Labarna AI Research