Anagog

Name: Anagog
Brand: Anagog (Acquired by Intent HQ)

Enhance mobile customer engagement with true moments of delight, based on a customers’ Real-World journey

Est 2010|Valuation $22.8M|Raised $28.1M

LinkedIn 3K|Web traffic 2K|FTEs 123|HQ London, England, GB

MarketsMobile App Engagement Customer Engagement Platforms (CEP)

Published Sep 19, 2026

01Common complaints

1. The procurement process requires abundant third-party validation on mainstream review sites before purchasing. - Anagog has limited presence on mainstream review platforms; if procurement policies require such coverage, alternatives may be easier to justify. 2. The purchasing organization cannot support ongoing SDK integration and maintenance. - If mobile engineering resources are unavailable for integration and updates, a turnkey engagement platform with lower engineering overhead may be more appropriate. 3. There are strict restrictions on background sensing, location-adjacent inference, or behavioral profiling. - Even designs that limit cloud transfer may trigger legal or reputational concerns in some jurisdictions or verticals. 4. The organization is small (early-stage) and price-sensitive. - Enterprise licensing and integration costs can outweigh expected benefits for very small teams or early-stage startups. 5. The primary need is email-first marketing automation. - An on-device mobile context SDK may not address core email automation needs; email-centric platforms or marketing automation specialists may be a better fit.

Deal disqualifiers

No ability to modify the mobile app or add SDKs.
Strict prohibitions on collecting or processing sensor-derived signals or on behavioral profiling.
Requirement for transparent, self-serve pricing and immediate trials with no sales engagement.

Limitations evident from public artifacts

The SDK is commercial and proprietary rather than open source; use requires a license agreement.
Integration and configuration complexity across multiple frameworks and OS versions.

Roadmap visibility

No clear public roadmap specifically for Anagog was found; product planning and releases are likely managed under Intent HQ post-merger. Prospective buyers should request roadmap details and support horizon commitments.

Scale limitations

No independently verified information on scale limits was found. Vendor statements about large-scale event processing are vendor-published and should be validated.

Security and compliance gaps

A SOC 2 logo appears on the redirected site, but public details about scope and report type are insufficient to satisfy enterprise due diligence without additional documentation.

02Why they buy

Unique selling points that appear plausible (require validation)

On-device behavioral inference: the product emphasizes inference on the handset to limit transfer of raw personal data to cloud services.
Timing-based/contextual triggers: the solution emphasizes engagement triggered by real-world contextual signals rather than only app events.

Where competitors may have clearer advantages

More mature ecosystems, broader integration catalogs, stronger third-party review footprints, and clearer public security and compliance documentation.

03Field reports

Review platform presence

The vendor does not have meaningful coverage on mainstream SaaS review platforms such as G2, Capterra, or TrustRadius in a way that provides buyer-grade sentiment and a balanced review distribution. Some search results returned unrelated entries rather than product-specific reviews.

Implication for procurement: the absence of review-platform coverage increases due diligence burden; prospective buyers should request customer references and consider a structured pilot.

Community and social sentiment

Direct community discussion on public forums about the product was not prominent in surfaced results. This may indicate enterprise-focused sales or a shift of brand discussion to the parent company.

Available quotes (limited and vendor-provided)

The most accessible testimonial-like statements appear in vendor-issued press releases and partner materials. For example, a vendor press release quoted an app creator expressing strong positive sentiment about mobility capabilities. These statements originate from vendor channels and should be treated as marketing material rather than independent verification.

Inferred reasons customers may select the solution

Based on vendor messaging and technical artifacts such as SDK packages, likely motivations include:

The need for contextual triggers based on signals beyond standard app events
Desire to reduce reliance on persistent identifiers or cookies and to limit data sent to cloud systems
Intention to improve timing-based engagement and conversion through contextual signals

Inferred reasons customers might not buy or may leave

Common enterprise risks for this category include:

Perceptions of the solution as a "black box" if model decisions lack explainability
Integration complexity and ongoing SDK maintenance burden
Concerns about battery impact and operating system background processing restrictions
Procurement and security friction if compliance artifacts are not readily provided

Case study signals found

- Vendor-published marketing highlights a case study claiming a substantial revenue uplift for a beauty retailer in Brazil. Critical evaluation: - The claim is vendor-published and lacks an associated methodology in the publicly captured snippet. Procurement should request: - Time window for the reported result - Whether reported revenue is incremental and how that was measured - Control group setup and statistical controls for confounders - Any campaign mix changes that might explain the result

Older product-era use cases (CrowdPark / mobility)

Early press coverage positioned the vendor around crowdsourced parking intelligence and documented initial investment activity. This demonstrates technical heritage in mobility inference but also indicates product evolution risk: the vendor has shifted from early mobility/parking applications to broader on-device AI and engagement use cases.

04Best fit

Company size

Best fit typically:

Mid-market to enterprise organizations with significant mobile monthly active users and large retail/telco apps.

Industries

Telecommunications, retail/e-commerce with strong mobile engagement, financial services, travel/hospitality, and consumer subscription businesses.

Roles and personas

Decision makers: VP/Head of CRM, Growth, Lifecycle Marketing, Heads of Data/AI, and privacy or security leadership.
Operational users: lifecycle marketers, campaign operations teams, mobile product managers, and data analysts.

Pain points addressed

Timing-based relevance is missing from personalization approaches that rely only on app events.
Regulatory and privacy constraints reduce available external identifiers for targeting.
Rising cloud compute and data transfer costs for centralized inference or large-scale analytics.

Qualification criteria

The organization can run controlled experiments (holdouts) to validate incremental lift.
Mobile engineering bandwidth and a mature release process are available for SDK integration and maintenance.
Operational processes exist to manage consent and user-facing disclosure of sensor-derived features.

05The pitch

What the product does (objective value proposition)

Anagog is an on-device (on-handset) AI software development kit (SDK) and a set of mobile engagement capabilities that analyze mobile sensor and behavioral signals to support timing-based personalization while limiting the transfer of raw personal data to cloud services. Historically the vendor marketed its JedAI SDK (on-handset mobility/context inference) and related analytics capabilities; more recently the product has been merged and rebranded under Intent HQ and the company website now redirects to Intent HQ. In practical buyer terms, the product category overlaps with: - Mobile customer engagement and personalization (push, in-app, segmentation) - Mobile intelligence and sensor-derived context (mobility status, predicted intent) - On-device processing approaches intended to reduce cloud data transfer

Target market and positioning

Target users: mobile app owners (consumer brands, telcos, financial services, retail) that seek improved conversion and retention through more accurate timing and context for engagement.
Positioning: emphasizes on-device processing and contextual signals obtained outside of standard app-event streams, with the intent of reducing cloud data collection and associated compute costs.

Get a comprehensive analysis of Anagog including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →