IMDEX built a mining data platform in 8 months with Cursor
IMDEX, an Australian mining technology company, used Cursor to merge fragmented geological data products into one platform and to move a legacy Angular app to a React micro frontend. Cursor reports that the data platform landed in 8 months instead of an estimated 2–3 years, and the migration in 6 months instead of 3–5 years, with the existing team rather than new hires.
The problem
IMDEX sells 600+ mining technologies, from core scanners to IoT-connected drilling devices, and many were backed by separate applications with their own data models. Customers lost data fidelity moving from raw drilling data to analysis, and the old ecosystem made new features hard to build and old ones hard to maintain. IMDEX estimated the consolidation alone would need 20 additional engineers and two to three years.
How they did it
- Evaluate several coding agents on your own large codebase before standardising; IMDEX picked Cursor mainly for how its agent kept context across a large legacy codebase.
- Use the agent first to read the legacy code and draft a migration plan, then implement the plan in reviewed steps rather than one big rewrite.
- Match the model to the task. IMDEX developers use Auto for routine work, higher-thinking models for ambiguous design decisions and simpler models for contained implementation.
- Run a dedicated training month. IMDEX's "AI July" had 101-level sessions on context windows, model selection and token use, 201-level sessions on MCPs, skills, hooks and parallel agents, and hackathons on real product problems.
- Measure adoption with data. On Enterprise plans, Cursor's Analytics API (admin API key from the Cursor dashboard) reports active users, agent edits and model usage; IMDEX also tracks PR volume per developer.
- Widen use once engineering is moving faster, so product, legal, security, marketing and finance decisions keep pace.
From the official docs
curl -X GET "https://api.cursor.com/analytics/team/agent-edits" -u YOUR_API_KEY:
Results as reported by Cursor
- The data platform landed in eight months; without Cursor it would have taken 20 additional engineers, two to three years and millions of dollars, as reported by Cursor.
- The Angular-to-React migration landed in six months, versus three to five years without Cursor, as reported by Cursor.
- A 10x faster pace on legacy migration than IMDEX's pre-AI model, as reported by Cursor.
- IMDEX later built a customer insight app in less than 30 days and a sales training tool in just under two weeks, as reported by Cursor.
These figures are as reported by Cursor in Cursor customer story ↗ (Aug 25, 2026). Cursor sells the product used here. AgentGid did not measure or independently verify them.
This suits an established engineering team facing a long migration or consolidation of legacy apps, where the agent has to understand a large codebase before changing it. It suits less a small team on a fresh codebase, and the Analytics API that IMDEX used to track adoption is Enterprise-only per Cursor's docs. Per AgentGid's Cursor pricing and limits pages (checked Nov 3–5, 2026), there is a free tier with limited Agent and Chat requests; Plus is $8 a month but covers Grok models only, Premium is $30 a month with third-party models at API list price from prepaid credit, Teams seats cost $30, $100 or $200 a month by tier, and Enterprise is custom. Cursor is now owned by SpaceX. The "without Cursor" timelines are IMDEX's own estimates published on Cursor's blog, not measured comparisons. For an open-source route, OpenCode (MIT) is free with paid plans from $10 a month per its AgentGid page (checked Nov 17, 2026).
The agent used here
Similar use cases
Grab's designers and ops teams ship their own fixes with Cursor
Grab, the Southeast Asian rides, delivery and payments company, opened Cursor to people outside engineering as well as to engineers. Designers now merge their own production UI fi…
About 98% of employees in Grab's tech organization use Cursor monthly and about 75% weekly, as reported by Cursor.
How National Australia Bank sped up legacy migrations with Cursor
NAB engineers used Cursor to understand and migrate legacy Silverlight/.NET and Assembly systems, and to build a new payment app. As reported by Cursor, delivery was well ahead of…
As reported by Cursor: NAB 'originally scoped six months of work' for the BizCalc migration and now expects it to finish in two months, 'a 3x improve…
Cursor's planner-worker agents built a web browser from scratch in about a week
Cursor tested long-running autonomous coding with a hierarchy of planner agents that create tasks and worker agents that just complete them. The headline project was a browser eng…
The agents ran for close to a week, writing over 1 million lines of code across 1,000 files. (as reported by Cursor)
Guides
Malicious Claude Code 2.1.312 and 2.1.313 Extensions in Cursor: What It Did and How to Check
Tampered Claude Code extensions, versions 2.1.312 and 2.1.313, sat in Cursor's extension marketplace on October 29, 2026 and tried to plant an SSH backdoor. What Cursor's notice confirms, why the tunnel mostly failed, and how to check and clean a machine.
How to Cut Token Usage in Claude Code and Cursor (2026)
Practical ways to spend fewer tokens with Claude Code and Cursor: measure first, keep context small, match the model to the task, filter what the agent reads, and the open-source tools that help.
VoiceStudio: The Free, Local ElevenLabs Alternative
A viral post calls VoiceStudio a 100% free ElevenLabs replacement with 19.4K stars. We checked it against GitHub and the project's own pages: what it does, what is really free, the license catch in the default voice model, and how to plug it into Claude Code or Codex.
AI Coding Agent Pricing Explained: Claude Code, Cursor, Codex and Copilot (2026)
What Claude Code, Cursor, OpenAI Codex, GitHub Copilot and other coding agents really cost: plan prices, usage limits, subscription vs API billing, and how to estimate your monthly bill.