OpenAI Travel and Hospitality Europe & UK

Plex Coffee

Document Processing · Enterprise Knowledge Search

As Plex Coffee expanded from one café to four, it needed a better way to train rotating staff, preserve service culture, and stop store managers from being overwhelmed by repetitive knowledge-sharing questions.

Expansion plan to 10 cafés while keeping operations lean
Onboarding time reduced from weeks to days
Operational questions on WhatsApp reduced by over 50%

Reported impact

Business outcome

Plex Coffee reduced operational messaging noise, accelerated onboarding, freed store managers for more guest and community engagement, and built a scalable knowledge-sharing model for future expansion.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

Plex Coffee uses ChatGPT Business to turn onboarding and store operations into conversational workflows that scale more cleanly than handbooks and messaging threads. The team first centralized knowledge in Notion, then enabled the Notion connector so staff could ask natural-language questions from an in-store iPad and receive answers grounded in the café’s documentation instead of flooding WhatsApp groups. For onboarding, founder-written training material was converted into a custom GPT that teaches company values, drink preparation, sourcing, and procedures in a more engaging conversational style than a 25-page manual. Once those flows stabilized, Plex extended ChatGPT Business into expansion research, demand analysis, and supply-order experimentation, using deep-research features and Agent workflows to estimate revenue, explain unusual demand patterns, and reduce repetitive vendor administration. The result is a lean hospitality operation where AI handles knowledge retrieval and prep work so managers can focus on guests and community.

Data flow

Operational documents from Notion are pulled into ChatGPT Business through the connector so staff can retrieve answers on demand. Handbook content is loaded into the onboarding GPT, while managers use the same workspace to analyze demand, research expansion, and experiment with supplier-order automation.

Solution architecture

3 components · 2 layers
  1. Ingest
    • Notion connector Grounds answers in Plex’s operational documentation so staff can ask questions in natural language.
  2. Serving
    • ChatGPT Business Provides the shared conversational workspace for operations, onboarding, research, and analysis.
    • Custom onboarding GPT Teaches company culture, sourcing, and procedures conversationally to new hires.

Architecture clues

  • Deep research is used for site-revenue estimation and demand explanations
  • Founders repurposed a 25-page handbook as a custom GPT
  • Staff access ChatGPT through an in-store iPad
  • Team is experimenting with ordering from suppliers directly through Agent

Evidence from the source

"I uploaded this handbook into a custom GPT"
"Onboarding time has gone from weeks to days."
"That has cut down our WhatsApp messages on certain issues by over 50%"
"The team enabled the Notion connector"
Transparency Evidence & methodology 90/100 reference value · 87% confidence · 1 source

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 value90/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/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

    Plex Coffee customer story

    First-party
    https://openai.com/index/plex-coffee/
    Source type
    Vendor-published customer story
    Published
    Oct 15, 2025
    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

Date evidence

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