Autodesk x NTU Product Club PMC Hackathon 2026

Pre-Flight

autocad-translate-prototype.vercel.appchampion

Translating drawings through the Autodesk API was a black box: cost only appeared after the job ran, there was no time estimate, and broken sheets showed up afterwards as overflowing text and font issues to fix by hand. Users paid twice, once in tokens and once in rework. Pre-Flight opens the box before you commit. A side panel shows the unique string count so duplicates are not paid for twice, the estimated cost in Flex tokens, the estimated time, and the risks flagged upfront. Built with my team, The A Team, on the back of the Product Management Course: user interviews, surveys, competitor analysis, journey mapping and problem framing all fed straight into the product.

what it does

Pre-run estimates: unique string count, cost in Flex tokens, and time
Risks flagged upfront, such as text overflow and font readability issues
Preview risky samples and test one on the drawing, with undo
Select and deselect exactly which strings get translated
Double-click to edit any string the system cannot fix on its own
Click any string to jump straight to where it sits on the sheet
Progress bar that tracks the estimate against time remaining
Post-translation report comparing estimated against actual cost and time
Fix rewraps overflowing text or scales the font, and only hands a string back when neither works

built with

Product management
User research
Journey mapping
Prototyping
AutoCAD
Autodesk API