Golf Club Analysis Application Needed

Hi, I please need a golf-related software program developed to accurately determine a rotation point location along the length of a golf club. The club movement in question takes place before a swing even begins, where golfers commonly move a club in a manner that creates a rotation point along the length of the club. In essence it divides the length of the club into two sections. The point location can vary significantly from golfer to golfer and is a crucial measurement that needs to be found. Club movements during the period can range from being much quicker than anticipated at first thought, to so small and subtle that they are barely noticeable unless specifically looking for them. The entire club as a whole is also generally moved around during the period, making it more difficult to accurately track and determine the rotation point location for any given golfer. Partially successful tries have been made in the past, the earliest attempts using an inertial-type sensor(s). But sensor reading drifting issues toward determining club positions were a major issue. An entire pre-swing period (though not necessarily needed) can last upwards of 10 seconds or more for some golfers, over which numerous relevant club movements (waggles) are often performed and separated by short inactive periods. A single waggle is generally less than a second, and with the most relevant portion being even less than that. Yet no two are ever exactly alike. Another attempt(s) used video frames and computer vision (only 2D video should be fundamentally needed). Simple conspicuous tracking markers were placed on the club. One contractor could not even come close to tracking the markers decently and determining any rotation point locations, though certain other needed parts of his application were okay. Another was essentially the opposite, tracking the club markers very well, but doing very poorly at the other parts needed to make the application function as a whole. Programming languages such as R (visually nice but unusable in other manners), Python, and perhaps some C have been used by various contractors. Inertial-type sensors and video tracking as examples should not both be needed simultaneously. One or the other should be fine for what is needed. A video-type application "might" provide information more useful for users and further application development. But I am not really certain of that right now, and I am open to any means. Unsatisfactory results and data thus far have prevented me from positively proving whether certain concepts are even correct yet. Thus, I am still somewhat at a prototyping stage. So I am first in need of a rudimental version of the application that can at least function properly, one that can be produced with hardware/software components that are as efficient as possible from time and cost standpoints (yet hopefully be able to get some decent results with it for further analysis). There is no set budget, yet I will spend little more on any further attempts unless and until certain anticipated elements are better proven first. Then I can take things from there toward potential commercialization. Additional information is available, including documentation of past attempts and the good and bad of those along with more details of what is needed for a next attempt. Various IP rights are in play, so an NDA will likely be required in order for me to release most additional details. I am open to considering project or hourly rates, though I cannot consider completely open-ended hourly rates. For hourly rates, before consideration a dependable estimate of hours needed will be required for what is needed next. Please feel free to throw any questions or comments my way, as I could have easily missed one or more even basic things that might be needed for your consideration. Thank you very much. I appreciate it.