Fractal is an Indian-founded, publicly listed enterprise AI company that builds and operates large-scale AI, analytics, and decisioning solutions for Fortune-class enterprises; it exists to put AI into real business decisions (marketing, supply chain, pricing, risk, and care) so organizations run better and faster.


SECTION 1: Company Story

What the company is

  • Fractal is an enterprise AI and analytics company that designs, builds and runs AI systems and platforms for large companies across industries such as CPG, retail, financial services, healthcare, telecom and manufacturing. This is stated on the company site and investor pages.
  • It combines data science, software engineering, product design and domain expertise to deliver end-to-end solutions (from strategy to production) rather than only models or consulting.

Founding story

When it started

  • Fractal was founded in 2000 and later expanded to the US; founders include Srikanth Velamakanni and Pranay Agrawal among others.

Why it was created

  • founders saw that enterprises had growing amounts of data but lacked repeatable ways to convert that into operational decisions at scale; early Fractal focused on analytics to inform business choices.

Market problem that made it necessary

  • enterprises needed domain-aware analytics and operational systems (not just isolated models) that could be integrated and scaled across complex business workflows—Fractal positioned itself to bridge analytics → production value.

Mission and vision

Official mission (site language)

  • “Power every human decision in the enterprise” by leveraging AI and engineering.

Real-world mission (plain language)

  • help big companies make better, faster decisions by embedding AI into their daily operations (pricing, marketing, supply chain, clinical decisions, etc.).

Long-term ambition

  • to be the go-to partner and platform provider for enterprise decisioning and to create scalable AI products and IP (the company emphasizes R&D and product launches such as large reasoning models).

SECTION 2: Customer Problem Analysis

Before Fractal existed

Pain

  • enterprises had siloed analytics, slow delivery, limited productionization of models, and low adoption because tools weren’t designed for business workflows.

What they did instead

  • used internal BI teams, point analytics vendors, or consulting firms to build ad-hoc models that often stalled before production.

After using Fractal

What becomes easier

  • companies get integrated solutions—models + software + change management—that translate predictions into actions (e.g., optimized pricing rules, demand forecasts tied to supply chain execution).

Business value

  • faster time to impact, higher ROI from data, reduced waste in supply chains, improved customer outcomes; enterprises pay because these changes affect revenue, cost and risk materially.

Practical example

  • A retail client replacing manual markdown decisions with an AI pricing engine reduces inventory write-downs and increases margin; Fractal supplies models, integration, and operational workflows to enact those price changes across stores and channels.

SECTION 3: Product Portfolio

Major products/services (summary)

  • Enterprise AI Consulting and Transformation: strategy, operating model, change management for embedding AI.
  • Industry and function AI solutions: prebuilt and custom solutions for CPG, retail, FS, healthcare (e.g., pricing, personalization, supply chain AI).
  • Platforms and IP: enterprise AI platforms and production-grade ML engineering; company has launched large reasoning/search models and agentic AI platforms (e.g., Fathom-Deepsearch, Fathom-R1 as publicized).
  • Managed AI and AI-as-a-Service: hosting, operations, and ongoing optimization (focus on scalable deployment).
  • R&D and open models: investment into research and open-source reasoning models and IP (company states significant R&D spend).

For each product (short bullets)

Consulting & Transformation

  • purpose—help enterprise adopt AI
  • target—CIOs/heads of business
  • features—strategy, use-case prioritization, pilot-to-scale roadmaps
  • revenue—project/retainer
  • importance—core early engagement that leads to platform deals.

Industry AI Solutions (e.g., pricing, personalization)

  • purpose—solve repeatable business problems
  • target—business units in large enterprises
  • features—prebuilt models, integrations, dashboards
  • revenue—license + implementation + support
  • importance—primary sources of client value.

Platforms & Models (Fathom, agentic platform)

  • purpose—enterprise search/reasoning and automation
  • target—enterprise engineering & data teams
  • features—large reasoning models, agents, search and automation
  • revenue—product licensing, cloud marketplace, usage
  • importance—strategic for scale and recurring revenue.

Managed Services

  • purpose — run AI solutions for clients
  • target — enterprises lacking internal ops
  • features — SRE, MLOps, monitoring
  • revenue — subscription/managed services
  • importance—drives steady recurring revenue.

SECTION 4: Business Model

How the company makes money

Revenue streams

  • Professional services (consulting, implementation), product/platform licensing, managed services/subscriptions, and potentially cloud marketplace/usage revenue for models and agents.

Pricing model

  • mix of fixed-fee projects, time-and-materials, license/subscription fees for platforms, and usage-based charges for cloud/agent services (typical for enterprise AI firms).

Customer lifecycle & upsell

  • discovery through thought leadership & pilots → pilot to proof-of-value → scale to platform and managed services → cross-sell to other business functions and geographic expansion; retention through SLA, outcomes, and integration friction.

Why the business is attractive

Recurring potential

  • platform + managed services can create sticky, recurring revenue streams once AI is embedded.

Demand

  • enterprises need production-ready AI and operational integration; Fractal targets Fortune clients where impact is high.

Competitive advantage

  • deep domain engineering, end-to-end capabilities, and R&D investments create barriers to simple substitution.

SECTION 5: Growth Journey (timeline overview)

Stage 1 — Early days (2000–2010)

  • Started as an analytics firm founded in 2000 focused on customer analytics and decision science.
  • Early customers: large enterprises needing customer analytics; growth was organic and consulting-led.

Stage 2 — Product-market fit (2010–2018)

  • Expanded offerings to include more vertical-focused solutions and began acquiring specialized firms to broaden capabilities.
  • Built repeatable products around customer analytics and supply chain problems; secured marquee clients.

Stage 3 — Scaling and institutional investment (2019–2022)

  • Significant funding (e.g., large private equity investments) and acquisitions helped scale offerings and geographic presence.
  • Transition toward enterprise AI and heavier engineering and product investments; launched managed services and began building platform IP.

Stage 4 — Current position (2023–2026)

  • Public listing and continued productization (launch of large reasoning models, agentic AI platforms, participation in cloud marketplaces) mark a move toward product + platform revenue mix.
  • Strengths: large enterprise customer base, R&D emphasis, global presence and cross-industry solutions.

Major turning points

  • Raising institutional capital (boosted scale), acquisitions to add capabilities, and product launches such as open reasoning models and agentic platforms.

SECTION 6: Competitive Landscape

Direct competitors

  • Large global consultancies and systems integrators (Accenture, Deloitte) offering AI transformation and managed services; specialized AI vendors (e.g., Mu Sigma historically, other analytics boutiques); cloud vendors’ enterprise AI units (AWS, Google Cloud) offering platforms and managed AI services.

Indirect competitors

  • Point-solution SaaS vendors (for pricing, personalization), in-house analytics teams, and niche AI startups offering single-function solutions.

How they differ

  • Fractal differentiates with integrated domain + engineering + R&D, and by selling both services and platform IP; consultancies offer scale and breadth, cloud vendors offer infrastructure and managed ML tooling, startups offer focused products.

Why customers choose Fractal

Strengths

  • deep domain expertise, end-to-end delivery, enterprise integrations, strong R&D and product roadmap.

Why customers might leave

  • if cloud providers bundle competing managed services cheaper, if in-house teams mature, or if competitors deliver faster/cheaper vertical SaaS.

SECTION 7: Customer Perspective

Ideal customer profiles

  • Large enterprises (Fortune 500) in retail, CPG, financial services, healthcare, telecom, manufacturing that have complex operational decisions and data at scale.

Buyer personas

  • Chief Data Officer, Head of Analytics, VP Supply Chain, Head of Marketing, CIO — stakeholders who need measurable ROI from AI projects.

Common customer problems and desired outcomes

Problems

  • fragmented data, low model productionization, slow decision cycles, inconsistent adoption.

Desired outcomes

  • increased revenue, lower cost, faster decisions and better risk control.

Public sentiment themes (synthesis)

What customers love

  • domain expertise, ability to operationalize solutions, enterprise-grade delivery.

What customers dislike

  • cost and length of large transformation projects can be high; some customers prefer faster, lighter SaaS options (industry expectation).

What customers want next

  • more turnkey, faster-to-deploy products and plug-and-play models that still preserve enterprise control and privacy.

SECTION 8: Challenges Faced by the Company

Product challenges

  • Need to balance custom engagements with productization—too much customization slows margins; Fractal appears to invest in platform IP to address this. (Assumption: medium risk)

Customer acquisition challenges

  • Selling to large enterprises is long-cycle and relationship-driven; requires heavy sales and delivery investment. (Assumption: high confidence)

Competition challenges

  • Competing with BigTech cloud providers and large SIs that can bundle services; product differentiation is necessary. (Assumption: high confidence)

Hiring and scaling challenges

  • Recruiting and retaining specialist ML/engineers and domain experts at scale is difficult and expensive; R&D hiring is a priority. (Assumption: medium-high risk)

Technology challenges

  • Maintaining production reliability, model governance and explainability for regulated industries (e.g., healthcare, finance) is complex. (Assumption: medium risk)

Regulatory challenges

  • Data privacy, cross-border data rules, and model governance could constrain deployments in some sectors. (Assumption: medium risk)

SECTION 9: Organizational Understanding

Estimated team structure

Leadership

  • Group CEO/Executive Chairman and CEO for US; board with industry veterans.

Major departments

  • Product & Platforms, Engineering (MLOps), Data Science & Research, Industry Solutions, Consulting/Professional Services, Customer Success, Sales & GTM, Corporate functions (Finance, Legal). This mirrors typical enterprise AI firms and the company’s public descriptions.

Product organization

  • product managers for industry verticals and platform teams for models/agent tech.

Organizational maturity

  • mature — public listing, centralized R&D, distributed delivery centers, and structured investor relations indicate mid-to-high organizational maturity.

Possible gaps

  • need for standardized self-service products to complement custom services; more automation in sales-to-deployment to shorten cycles (assumption).

SECTION 10: Future Opportunities (3–5 years)

Product opportunities

  • Packaged vertical SaaS offerings that require less customization — would increase margins and speed to market. Impact: high; difficulty: medium.

AI opportunities

  • Enterprise reasoning/agent platforms and proprietary LRM models can be monetized via marketplace and cloud partnerships. Impact: high; difficulty: high.

Market expansion

  • Deeper penetration in healthcare, life sciences, and financial services where decisioning value is high and willingness to pay is strong. Impact: medium-high; difficulty: medium.

Partnerships and ecosystem

  • Cloud marketplace listings, alliances with platform vendors and system integrators to co-sell agentic AI and managed services. Impact: medium; difficulty: low-medium.

SECTION 11: Future Risks (ranked)

High risk

  • Competition from cloud providers and large SIs that can bundle AI tooling and services; can undercut price or scale faster.

Medium risk

  • Talent scarcity and wage inflation for ML/engineering talent; model governance/regulation raising compliance costs.

Low risk

  • Single-product obsolescence — mitigated by diversified vertical offerings and platform strategy.

SECTION 12: The Business Trajectory (narrative)

Fractal began two decades ago as an analytics boutique that helped big companies understand customers and make data-driven choices. As enterprise data volumes grew and the market demanded operational AI (not just insights), Fractal steadily extended from analytics into engineering and platforms—building the team and IP to take models into production reliably.

The founders observed that many analytics efforts stalled at pilot stages; Fractal’s response was to combine domain experts, engineers, and design to create solutions that deliver measurable decision value at scale.

Growth accelerated through targeted acquisitions, institutional funding, and investments in R&D, enabling the company to move from purely project-based revenue to product and managed revenue.

The company’s recent emphasis on large reasoning models and agentic AI reflects a strategic bet: enterprises will want reasoning/search/agent capabilities that can augment workflows and automate decisions, and those that supply secure, explainable enterprise-grade models will capture sticky, high-value relationships.

The road ahead is promising but not guaranteed—success will depend on productizing core capabilities to increase margins, defending accounts against cloud and SI bundling, and executing the technical and regulatory aspects of enterprise AI.

If Fractal sustains R&D and converts platform IP into recurring revenue, it can become a dominant enterprise decisioning platform; if it remains too consultancy-heavy or loses ground to bundled cloud offerings, margin pressure and churn are real risks.


SECTION 13: Executive Summary (one page)

What they do

  • Fractal builds and runs enterprise AI solutions, combining analytics, engineering and product design to embed AI into business decisions across multiple industries.

Why they exist

  • To solve the problem that many enterprises cannot turn data and models into operational, repeatable decisions at scale.

How they make money

  • A mix of consulting/implementation fees, platform/product licensing, managed services subscriptions, and cloud/marketplace usage revenue.

What makes them different

  • Deep domain expertise + engineering + sustained R&D (publicized model and platform development) aimed at productionizing AI at enterprise scale.

Biggest strengths

  • Enterprise customer base, end-to-end delivery capability, R&D investment and product roadmap.

Biggest weaknesses

  • Historically consultancy-heavy model that must be productized for better margins; exposure to bundling by larger players.

Biggest opportunities

  • Productized vertical SaaS, agentic/ reasoning platforms, cloud marketplace monetization and expansion into regulated industry use cases.

Biggest risks

  • Competitive pressure from cloud giants and SIs, talent scarcity, and regulatory complexity for enterprise AI.

Most likely future direction

  • Continued shift toward mixed services + product model: more platform/IP monetization (reasoning models and agentic platforms), deeper managed services, and accelerated focus on scalable products to grow recurring revenue.

Key strategic takeaways

  • Accelerate productization of repeatable solutions to lift margins.
  • Prioritize platform monetization (marketplaces & cloud partners).
  • Strengthen governance and explainability for regulated sectors.
  • Keep investing in R&D that differentiates (reasoning/agent models) while shortening time from pilot to scale.

Confidence levels and assumptions

High confidence

  • Foundational facts (founding year, leaders, industries served, mission) — High confidence (sourced from corporate pages and public filings).
  • Recent product launches and R&D emphasis (Fathom models, agent platform) — High confidence (company announcements).

Medium confidence

  • Business model mix and revenue streams — Medium confidence (inferred from investor relations and product positioning).
  • Customer sentiment and precise strengths/weaknesses — Medium confidence (synthesized from company positioning and industry norms; direct customer reviews would refine this).

Low-medium confidence

  • Organizational gaps and exact internal structure — Low-medium confidence (estimated from public disclosures and typical enterprise AI firms).

  • Detailed revenue breakdown by product vs services and by geography (public filings may contain partial info but would need the latest annual report for exact figures).
  • Customer case studies with quantified outcomes (impact metrics) to verify value claims.
  • Employee sentiment, churn metrics and detailed product roadmap beyond public launches.

Would you like a focused deep-dive next on any of these areas:

  • Revenue breakdown and unit economics
  • Product monetization strategy (platform vs services)
  • Competitive win/loss analysis for a specific vertical (e.g., retail or healthcare)

Mozilor / CookieYes Task Reflection

  1. Task title: Fractal Company Story research note
  2. Objective of the task: Understand Fractal’s operating model and extract lessons that can improve Mozilor’s product, research, governance, and execution quality, especially for CookieYes.
  3. Date assigned and date submitted: Assigned during the Mozilor organization-building research cycle; submitted on 2026-06-26.
  4. Your submission / output: This research note, plus the supporting takeaways and operating ideas for Mozilor and CookieYes.
  5. Key learning or insight gained: AI becomes more useful when it improves decisions and workflows, not when it stays as a standalone capability.
  6. How the task connects to organizational thinking, execution, research, or role readiness: It trains me to convert external company research into operating principles that help Mozilor and CookieYes scale with clarity, trust, and repeatable execution.