OpenAI Software / SaaS New Zealand

Yabble

Document Processing · Enterprise Knowledge Search

Yabble needed to turn large volumes of survey answers and customer feedback into actionable insights faster, because manual coding and analysis could take days or weeks and users were asking increasingly complex questions about their data.

days or even weeks translating data sets
thousands of customer data points
translated into meaningful themes in minutes

Reported impact

Business outcome

Yabble cut insight generation from days or weeks to minutes, delivered more nuanced answers to customer questions, and turned Query from a helpful feature into an essential part of customers' business strategy workflows.

  • Customer Experience
  • Productivity Improvement

Solution

Yabble layered GPT-3 into its customer-insight platform to automate the hardest part of feedback analysis: converting large, unstructured datasets into themes, subthemes, and usable answers. The platform already collected survey responses and customer feedback forms at scale, but analysts still had to spend days or weeks coding results and assembling insights. With GPT-3, Yabble Query can interpret more nuanced natural-language questions from users and return answers grounded in the relevant dataset, while Yabble Count analyzes thousands of comments, tags sentiment, and organizes the data into themes and subthemes. The workflow starts with survey and feedback data entering Yabble, continues through GPT-3-based classification and question answering, and ends with business users consuming richer insight outputs inside Yabble's existing experience. That architecture lets Yabble spend less time on manual analysis and more time helping customers make business decisions.

Data flow

Survey answers and customer feedback forms flow into Yabble, where GPT-3 classifies comments into themes and subthemes, powers Yabble Count sentiment analysis, and supports Yabble Query so users can ask natural-language questions and receive insights tied to the underlying dataset.

Solution architecture

3 components · 2 layers
  1. Compute
    • GPT-3 Provides the natural-language understanding that turns unstructured feedback into themes and answers.
  2. Serving
    • Yabble Query Lets users ask questions about their own data and receive dataset-aware insight outputs.
    • Yabble Count Categorizes comments by sentiment and organizes them into themes and subthemes.

Architecture clues

  • The platform was already ingesting survey and feedback data before GPT-3 was added
  • Yabble Count analyzes unstructured comments for sentiment and themes
  • Yabble Query answers questions about a customer's own dataset

Evidence from the source

Beginning in 2017, Yabble created a platform where organizations could easily analyze thousands of customer data points
Query went from helpful to our customers to absolutely essential to their business strategy
Using GPT-3, data sets that would usually take Yabble teams days to code and develop insights for, were now being translated into meaningful themes in minutes
Yabble Query... uses AI-powered algorithms to provide relevant insights
Transparency Evidence & methodology 75/100 reference value · 92% confidence · 2 sources

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence92%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    2 source references document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. OpenAI

    Yabble customer story

    First-party
    https://openai.com/index/yabble/
    Source type
    Vendor-published customer story
    Published
    Jan 4, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. GetLatka

    Yabble Revenue 2024: $2.7M, $3.1M Raised

    Independent secondary
    https://getlatka.com/companies/yabble

    The Organization JSON-LD lists addressLocality 'Auckland', addressCountry 'New Zealand', and numberOfEmployees value 28; fewer than 250 employees maps to SMB.

    Source type
    Structured company profile
    Supports
    • Company size
    • Region

Date evidence

  • Published on source page Jan 4, 2024 · OpenAI · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.