AWS Software / SaaS New Zealand

Thematic

Real-time Analytics

Thematic needed to turn large volumes of unstructured customer feedback from multiple channels into accurate, reliable intelligence that could explain customer-experience metrics such as Net Promoter Score and help clients act on them quickly.

Millions of customer feedback data points
test more than 10 LLMs

Reported impact

Business outcome

Thematic uses generative AI to transform millions of customer feedback data points into actionable customer intelligence, helping large enterprises such as Atlassian, DoorDash, and Woolworths derive more accurate and reliable insight from qualitative feedback.

  • Customer Experience
  • Productivity Improvement

Solution

Thematic uses generative AI on AWS to convert large-scale customer feedback into business intelligence for enterprise clients. Feedback from multiple channels is fed into Thematic’s analysis workflow, where the company uses Amazon Bedrock to evaluate and compare large language models and to generate curated, reliable customer-intelligence outputs. This builds on Thematic’s earlier NLP-based feedback analysis by adding a simpler way to experiment with and operationalize modern foundation models for qualitative insight generation. The platform connects themes from unstructured comments to business metrics such as Net Promoter Score and helps clients understand what is driving satisfaction or dissatisfaction at scale. With AWS, Thematic can analyze millions of feedback data points and continuously tune its approach across more than 10 LLM candidates.

Data flow

Customer feedback from multiple channels is ingested into Thematic's analytics workflow, processed with Amazon Bedrock to identify themes and generate insights, and then connected back to customer-experience metrics such as Net Promoter Score.

Solution architecture

1 components · 1 layer
  1. Compute
    • Amazon Bedrock Provides the large language model layer Thematic uses to analyze customer feedback and generate reliable intelligence.

Architecture clues

  • Explicitly compares more than 10 LLMs when designing solutions.
  • Extends an earlier NLP-based feedback-analysis workflow with foundation-model experimentation.
  • Links qualitative feedback themes to customer-experience metrics.

Evidence from the source

Thematic partnered with Amazon Web Services (AWS) to use generative AI to turn customer feedback data from multiple channels into curated, accurate and reliable customer intelligence.
Using Amazon Bedrock is just so easy. Whenever we design a solution we do test more than 10 LLMs.
developed a NLP-based prototype that analyzed unstructured customer feedback, connected themes from qualitative feedback to metrics, and generated insights that explained the drivers behind the Net Promoter Score.
Transparency Evidence & methodology 71/100 reference value · 83% 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 value71/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 specificity16/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 confidence83%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability23/25
    11 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    Thematic customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/generative-ai-thematic/
    Source type
    Vendor-published customer story
    Published
    Jan 1, 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

    Thematic Revenue 2024: $3.1M Est.

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

    The public company profile lists 'Employees 32' with 'Oct 2024' and says, 'Thematic has 32 employees (October 2024, LinkedIn).'

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

Not separately sourced Industry, Region. Treat these normalized attributes as lower-confidence until a dedicated source is added.