Cursor

After Git training, Grab designers used Cursor to implement interface corrections directly in code. Design managers reviewed hundreds of merged fixes, often on the same day. Faster delivery is reported, but no controlled time-saving comparison is provided.

Money Forward QA teams feed Jira tickets and Notion documents to Cursor through MCP. One agent drafts test cases and another produces Playwright scripts. The vendor story reports 70% less test-generation time without publishing the measurement method.

Navan used self-hosted Cursor Cloud Agents to migrate eight applications and 15 libraries to Spring Boot 4 in about one week. A comparable earlier migration took over a month. These are company-reported project durations, not a controlled experiment.

A Schoo infrastructure engineer used Cursor Agent to investigate a manually maintained AWS account and import about 350 required resources into Terraform. The account contained more than 1,500 listed resources. The post provides technical steps but no measured time saving.

An Asahi Shimbun workshop demonstrated Cursor workflows for GitHub issue creation, project fields, deadline reminders and meeting documentation. Shell examples are provided. This was an internal hands-on exercise, with no measured productivity outcome.

Faire uses Cursor Cloud Agents and automations for migrations, CI failures, bug triage and code review routing. It reports more than 2,000 automated agent runs weekly and doubled PR throughput. The cited 18-month migration baseline was a prior estimate.

Wayfair researchers used Cursor agents to implement and evaluate 110 variants of a product-attribute validation model. The company reports a measured 94% inference-cost reduction, with the selected architecture entering production. A later sprint reported a further 90% reduction.

IMDEX used Cursor to rebuild fragmented geological data applications into an integrated platform delivered in eight months. Its comparison with two to three years and 20 additional engineers is a counterfactual estimate, not a measured alternative implementation.

National Australia Bank's merchant services team used Cursor to ship a hardware-independent payment application in three weeks. The original scope was four months. The story reports this delivery against a planning estimate, without a parallel comparison project.

Two Nokia engineers used Cursor to analyze more than 50 million lines of code in two weeks and prepare an architectural decomposition plan. The comparison with a dozen specialists working for months is an estimate, rather than an observed control project.