OpenAI Software / SaaS North America

Asana

Application Refactoring

In order to modernize its frontend stack, Asana needed to finish a long-running code migration that was still years from completion. At its prior pace—with only a few engineers working on the migration incrementally alongside other priorities—Asana projected that it would take roughly five more years to complete.

After 1.5 weeks of engineering effort spread across two calendar weeks, Enzyme was fully removed. The work also delivered benefits beyond the framework migration itself, improving test coverage...

Reported impact

Business outcome

After 1.5 weeks of engineering effort spread across two calendar weeks, Enzyme was fully removed. The work also delivered benefits beyond the framework migration itself, improving test coverage, fixing poor-quality tests, and cleaning up legacy testing infrastructure.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

In order to modernize its frontend stack, Asana needed to finish a long-running code migration that was still years from completion. At its prior pace—with only a few engineers working on the migration incrementally alongside other priorities—Asana projected that it would take roughly five more years to complete. With Codex, Asana completed the project in about two weeks. Asana helps teams coordinate work. Its platform uses AI agents and automations to help customers manage, track, and execute that work. Asana brings the same approach to its engineering organization, where people use OpenAI Codex, powered by frontier models, to tackle large codebase changes, then review and approve each proposed change.

Data flow

Asana helps teams coordinate work. Its platform uses AI agents and automations to help customers manage, track, and execute that work.

Solution architecture

1 components · 1 layer
  1. Compute
    • Codex Implements, tests, reviews, or proposes code changes so engineers can move faster with human oversight.

Architecture clues

  • Asana helps teams coordinate work.
  • For this project, Codex helped Asana’s engineers remove Enzyme(opens in a new window), an outdated testing system that had made the company’s code harder to upgrade.
  • Implements, tests, reviews, or proposes code changes so engineers can move faster with human oversight.
  • In order to modernize its frontend stack, Asana needed to finish a long-running code migration that was still years from completion.

Evidence from the source

After 1.5 weeks of engineering effort spread across two calendar weeks, Enzyme was fully removed.
Asana helps teams coordinate work.
For this project, Codex helped Asana’s engineers remove Enzyme(opens in a new window), an outdated testing system that had made the company’s code harder to upgrade.
In order to modernize its frontend stack, Asana needed to finish a long-running code migration that was still years from completion.
Transparency Evidence & methodology 80/100 reference value · 89% 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 value80/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/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 scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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 provenance10/10
    The publication date comes from the source page or publisher.
  • 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

    Asana customer story

    First-party
    https://openai.com/index/asana/
    Source type
    Vendor-published customer story
    Published
    Aug 18, 2026
    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

  • Published on source page Aug 18, 2026 · OpenAI · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.