StuntIQ platform
AI-powered cheer stunt analysis built for the real practice-to-review loop.
The Figma Make direction is strongest when StuntIQ behaves like a product shell instead of a generic SaaS site. This landing page now mirrors that: capture-aware intake, visible AI processing, and coach-led review that stays connected from first clip to final follow-up.
How it works
Three concrete steps carried over from the Figma workflow.
The Make file describes a full StuntIQ journey, not just a splash page. The public experience now introduces the same sequence the product supports: capture or upload, visible processing, and review on the same surface.
Capture or upload with the right context
Authorized staff can start from a mobile-friendly practice flow or a structured upload route instead of scattered clips and text threads.
Track AI processing without losing visibility
Queued, uploading, processing, and preview-ready states stay legible so operators and coaches always know what happens next.
Move into coach-led review on the same surface
Results, history, and follow-up stay attached to the clip so the review loop feels like one product, not a handoff chain.
Why teams join
Built to reduce friction across the stunt review cycle.
AI assists coaching workflows, but the real product value is operational: fewer broken handoffs, clearer status visibility, and a system that feels aligned between public, customer, and admin surfaces.
AI supports analysis and triage, but final interpretation and athlete-safety judgment remain with people.
The Figma Make flow pushed mobile recording, upload queue visibility, and instant preview into the product instead of leaving them as afterthoughts.
The same design language carries from the landing page into admin, job monitoring, and customer history views.
Program-authorized participation, consent expectations, and data-use clarity are explicit throughout the experience.
Practice capture
The Figma mobile flow is now reflected in the marketing story.
StuntIQ is not just for after-the-fact uploads. The Make file pushed hard on coaches recording attempts during practice, tagging quickly, and seeing previews while the next clip is already moving. That direction is preserved here without inventing new routes.
Record another stunt attempt to compare performance while uploads continue in the background.
Beta and data use
Participation is structured, explicit, and limited.
StuntIQ is in closed beta. Participating programs may upload videos to evaluate the platform, and uploaded footage may be used internally to improve system quality during beta. Participation requires appropriate authority and consent.
Launch with intent
Ready to evaluate StuntIQ with your program?
This implementation keeps the current routes and app connections in place, then pulls the visual direction back toward the Figma Make source.