raffle

Name: raffle
Brand: raffle
Rating: 4.5 (17 reviews)

Turn your website into an AI answer engine that gives visitors instant answers from your own content.

Est 2018|Valuation $5.2M|Raised $19.5M|31 Ref Customers

LinkedIn 3K|Website|Web traffic 3K|FTEs 20|HQ Copenhagen, Capital Region, DK

MarketsSelf-Service FAQ / Knowledge Base

Published Oct 12, 2026

01Common complaints

- When the primary requirement is enterprise internal search across dozens of applications with complex permissioning and ACLs - In such cases, an enterprise-purpose-built internal search solution (for example, Glean) may better address connector breadth and identity mapping needs. - When a highly customized, engineering-controlled search stack is required - For organizations that need developer-level control over ranking, retrieval, and UI pipelines, a developer-first platform (e.g., Algolia or a custom stack using vector databases) may be more appropriate. - When the underlying problem is content quality rather than discovery - If content architecture and information quality are the root causes of poor search outcomes, investment in knowledge-management processes and CMS improvements may yield higher ROI than adding an AI layer. - When cost-sensitivity at scale is a primary constraint - Volume-based pricing for conversations and indexed pages can increase total cost of ownership; validate projected usage and 12–24 month cost scenarios during procurement. - When independent proof of ROI is required before purchase - Vendor-published ROI figures are not independently validated in public materials. Buyers should request measurement plans, customer references, and pilot results. - Limitations cited by customers and reviewers - Analytics and reporting: difficulty with month-over-month comparisons and timeframe slicing in the dashboard (per available review excerpt). - User interface items: minor design and polish items were cited in reviews. - Vendor-stated roadmap and release notes - The vendor publishes release notes, but specific roadmap commitments and timelines were not extracted in this review; request current roadmap details during procurement. - Scale limitations - Pricing and practical scalability are tied to indexed page counts and conversation volumes; explicit limits on indexing size, update frequency, and concurrency are not broadly documented in public pages and should be clarified in sales discussions. - Security or compliance gaps - ISO certifications are not publicly documented; SOC 2 artifacts are available on request. Enterprise identity and audit controls (SSO/SCIM/audit logs) are not exhaustively documented publicly and should be verified. - API limitations or integration constraints - An API is documented, but production suitability requires review of authentication patterns, rate limits, and data governance policies.

Deal disqualifiers (poor fit)

Requirements for complex cross-application permissioning and strict ACL parity for internal content; dedicated enterprise internal search platforms may be more appropriate.
Requirement for a fully on-premises deployment (not indicated as a standard option publicly).
Need for extensive, developer-level relevance engineering and ranking controls beyond a managed offering.

02Why they buy

- Observed and partially validated strengths - Short deployment path for basic website embedding and a managed, lower-code experience for on-site Q&A. - Reported responsive customer support in the available review sample. - Multiple ingestion pathways (web crawl, direct integrations, and API index) that facilitate getting started with existing content sources. - Vendor-claimed items requiring verification - Performance and conversion uplift figures cited in vendor materials should be validated with customer references and measurement plans before use in procurement decisions.

03Field reports

- Review platform coverage found during research - G2 - G2 listings show a small sample of reviews with generally favorable sentiment in the sample available during the review. - Gartner Peer Insights - No accessible product-specific reviews were located during this review run. - TrustRadius / Capterra - No product-specific review pages were found in the accessible crawl during this run. - Community forums - No substantive product-focused discussions were located on major public forums during this review; numerous search results relate to unrelated uses of the word "raffle." This limits community-level evidence. - Representative quotes (positive and negative) from public reviews (attributed to platform and reviewer role where provided) - Positive sentiment (ease of implementation and data value) - G2 reviewer (Enterprise user, listed role: Design Manager) — review titled: "Raffle is AI that you can actually use - easy implementation and a bunch of great data" (review date listed on platform): "I love how easy this has been to implement on our website." - Positive sentiment (customer experience) - G2 reviewer (Enterprise user, listed role: Digital Executive) — review titled: "Great service that is constantly evolving" (review date listed on platform): "The AI chatbot feature has enhanced our customer experience by enabling users to find answers to their questions without needing to call us directly…" - Negative sentiment (analytics/reporting limitations) - A G2 reviewer noted difficulty with month-over-month reporting and timeframe comparisons in the dashboard: "The dashboard offers great reporting ideas, but it is difficult to report month on month or compare to timeframes…" - Minor UX/design items - A reviewer cited small design adjustments that they expected to be addressed in future updates. - Common criticisms and complaints (from available review data) - Analytics and reporting: gaps in timeframe slicing and comparative reporting were noted in available review excerpts. - User interface and design: reviewers referenced minor polish items rather than major functional failures. - Price sensitivity: aggregated signals indicate cost may be a concern for smaller organizations as usage scales. - Why customers chose this product over alternatives (inferred) - Reported reasons include a relatively short deployment for basic website embedding and perceived responsiveness from vendor support in the small review sample. - Why some customers left for competitors (churn reasons to investigate) - No direct churn narratives were located. Likely reasons to validate in diligence calls include: - Need for broader enterprise connectors and permissions handling. - Requirement for fully custom UX or on-premise deployment. - Cost scaling as conversation and page volumes grow. - Specific outcomes customers achieved (notes on evidence quality) - The vendor publishes conversion uplift and engagement improvement claims (for example, modest conversion uplift figures). These are vendor-published and do not include transparent methodology or independent validation; treat such figures as claims that require verification via references and measurement plans.

Case Studies

- Third-party aggregations and vendor case materials - Third-party case study aggregators and vendor-hosted testimonials present quantitative claims (e.g., reductions in bounce rates, contact volume, and internal search time). These sources generally do not disclose full methodologies. - Vendor-hosted testimonials - Vendor-hosted testimonials describe ease of integration, improved searchability of content, and insights into user search behavior. These are useful qualitative data points but are vendor-controlled and should be corroborated with independent references when possible. - Critical evaluation of metrics - Conversion uplift figures and other specific improvement metrics are vendor-published. The underlying methodology, baselines, attribution model, and sample sizes are not publicly documented and should be validated via customer references and proposed measurement plans during procurement. - Recommendation for buyers - Request customer references in relevant industries, ask for reproducible pre/post measurement plans, and where feasible run A/B tests or controlled pilots to validate conversion and deflection outcomes.

04Best fit

Company sizes

Likely best fit
- Mid-market and enterprise websites with substantial support volume or conversion-sensitive user journeys.
Secondary fit
- Smaller organizations that prefer a low-code approach and can manage potential cost scaling as usage grows.

Industries and verticals where adoption is strongest (based on review sample and vendor materials)

Review sample and vendor materials indicate adoption across utilities, energy, communications, non-profit, banking, public sector, and education in specific examples.

Roles and personas

Decision makers
- Digital leaders, customer experience and support leaders, product and web owners.
End users
- Website visitors, support agents benefiting from deflection, and internal users for secondary internal search use cases.

Pain points addressed

Low-quality site search and high bounce rates.
Repetitive support inquiries and objectives to deflect tickets.
Lack of insight into search behavior and content gaps.

Qualification criteria (good fit)

Organizations with a coherent set of authoritative content (documentation, help center, product pages).
Organizations willing to invest in iterative content improvements informed by analytics.
Need for multilingual question-and-answer functionality in public-facing sites.

05The pitch

What the product does (core value proposition in objective terms)

- Raffle is a B2B SaaS platform that provides AI-assisted search and conversational assistants that can be embedded into a website, help center, or internal knowledge environment. The platform returns answers that reference the organization’s indexed content (web pages, documents, knowledge bases). It is implemented as a retrieval-augmented generation (RAG) style system with source references and controls intended to reduce model hallucinations. - Core modules commonly described - AI search widget and API for semantic/hybrid search and short-answer summaries from indexed sources. - Conversational AI assistant to answer questions using the organization’s indexed content. - Insights and analytics focused on queries, content gaps, trending questions, and user engagement.

Target market and market positioning

- Primary positioning is customer self-service and website conversion improvement (deflection of support tickets, helping visitors find answers faster, and improving lead conversion). - Secondary positioning is internal enterprise search and knowledge discovery across systems such as SharePoint and Confluence via integrations and an API-driven index. - Available adoption signals indicate usage in Europe (including Denmark/Nordics), with marketing activity directed at multiple markets including the UK and US.

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

Download full report →