Hey everyone,
I’m adapting an industrial airflow optimization workflow into cycling, and I’m looking for honest, analytical feedback from local road, TT, tri riders, fitters, and coaches.
The concept is straightforward: we bring the scanning rig to your garage or trainer setup. We capture a true 3D spatial scan of the actual rider on their actual bike in their real racing position. From there, we process that exact, unique geometry through a local OpenFOAM CFD pipeline to generate a practical, visual surface-pressure and airflow report.
To be clear right upfront: we are NOT taking 2D smartphone photos, moving digital sliders, or mapping you to a generic pre-built avatar. The pipeline runs fluid dynamics on the actual, high-resolution mesh of your body topology and physical bicycle components together.
My background is in motorsports airflow dynamics (specifically high-performance drag bike aerodynamics), and I’ve spent the last few months tailoring our local server processing loops, boundary layer constraints, and mesh resolutions specifically to the Reynolds numbers of a 25–30 mph cycling ecosystem.
The Aero-Tunes reporting covers:
- Actual surface pressure loading and localized drag tendency (Air P)
- Wake detachment boundaries and streamline velocity behavior (Air U)
- Left/right asymmetric pressure imbalances
- Lift, downforce, and high-speed stability indications
- Actionable, plain-English aerodynamic notes a rider or fitter can actually execute
Positions we are looking to validate and compare:
- Hoods vs. Drops (Road)
- Base bar vs. Aero extensions (TT/Tri)
- Micro adjustments: elbow width, shoulder turtle, helmet-to-back transitions
We are getting ready to roll this workflow out regionally, but first, I need to run a controlled smoke test on our automated pipeline processing times. I am looking for 3 to 5 beta testers located right here in the Raleigh/Research Triangle area (Wake/Durham/Orange counties) who care about the data and are willing to give brutal, honest feedback on our reporting layout.
In exchange for your time and feedback, the full 3D scan and custom CFD airflow report is completely complimentary.
I’m not here to make wild, unbacked wattage claims. I just want to put real physical geometry through the machine and see how riders interact with the report data.
If you are local to the Triangle and want to grab a beta slot, let me know:
1. What specific position or gear change would you most want to validate in a virtual tunnel?
2. What specific data layout would make a report like this fully credible and actionable for your training?
Drop a comment below or shoot me a DM if you’re in the area and want to get scanned!

