OpenAI Healthcare Asia-Pacific & Oceania

cult.fit

Application Refactoring · Customer Service Automation · IT Operations Automation

cult.fit wanted teams to solve operational and product challenges without adding process complexity. Fragmented developer tools hindered shared engineering practices, data requests bottlenecked at a central analyst team, and the company sought more personalized member experiences and lower-cost customer support.

$100,000+ annual software savings
20+ internal applications built by non-engineering teams in recent months
50%+ reduction in customer support costs
Around 20% of cult.fit's gym users currently utilize the AI Trainer product

Reported impact

Business outcome

cult.fit reports more than 20 internal applications built by non-engineering teams in recent months, over $100,000 in annual software savings from rebuilding an internal capability, and a 50%+ reduction in customer support costs. It also reports shipping a social feed in two months instead of the more-than-a-year estimate for the previous approach.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

cult.fit standardized software development around Codex, with shared repository structures, skills, testing, code review and feedback loops; its SRE agent aggregates observability-platform and log information, investigates incidents and can prepare a pull request for engineer review. Security agents address vulnerabilities, while on-call agents investigate recurring production issues. Beyond engineering, teams use Codex with company data to analyze information and build internal applications and workflows, including HR performance-review coordination. The OpenAI API and GPT Realtime support the AI Trainer's two-way voice coaching and workout logging. For customer support, AI agents are built into Sprinklr and connected to backend systems to assess penalty-waiver requests using local weather and class-attendance signals. The page does not identify underlying storage or deployment topology.

Data flow

For workouts, members interact by voice with the AI Trainer, which uses GPT Realtime through the OpenAI API to provide coaching cues and support workout logging. For support, Sprinklr-hosted agents check local weather and class-attendance patterns against cult.fit backend systems to assess a member's penalty-waiver request. Codex also works with company data for team analysis and app building.

Solution architecture

4 components · 2 layers
  1. Compute
    • Codex Provides the shared development platform teams use to build software, analyze company data, and create internal applications and workflows.
  2. Serving
    • OpenAI API Connects the AI Trainer experience to OpenAI models for personalized member experiences.
    • GPT Realtime Enables two-way voice coaching and workout logging in the AI Trainer.
    • Sprinklr Hosts cult.fit's AI customer-support agents within its existing support platform.

Architecture clues

  • GPT Realtime is used through an OpenAI API integration for two-way voice interaction.
  • Support agents are embedded in Sprinklr and connected to backend systems.
  • The SRE agent aggregates information from observability platforms and logs and can create a pull request for engineer review.

Evidence from the source

Cult.fit built these agents into its existing Sprinklr support platform and connected them to its backend systems.
Cult.fit now runs the capability on its own application, avoiding more than $100,000 in annual software costs.
More than 20 internal applications have been built by non-engineering teams in recent months.
The latest version is designed around a voice-first workout experience. Using GPT Realtime through an OpenAI API integration, the trainer can provide coaching cues and support workout logging through two-way voice interaction.
Transparency Evidence & methodology 100/100 reference value · 95% 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 value100/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 impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • 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 transparency10/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

    Cult.fit builds operational muscle with Codex | OpenAI

    First-party
    https://openai.com/index/cultfit-builds-with-codex/
    Source type
    Vendor-published customer story
    Published
    Nov 5, 2026
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • Publication date

Date evidence

  • Published on source page Nov 5, 2026 · OpenAI · First-party
    Open date source