Haha, throwing the word "hire" around in a place like this is sure to grab some attention - I'm available too!
Anyways, I'm kind of thinking about this as a "Rolodex" kind of situation where you have a repeating section with several fields and a button in each one. What you could do is have a hidden field in the repeating section that would act as a "sentinel" and put code behind the button that would change the sentinel value to enable printing of the specific section (contact in the rolodex example). Say you have fields Name, Address, Phone, and Email, you would add one more - PrintEnable. Now the code in the button would put a true in the PrintEnable field (you could also do this with rules), switch views, print, and finally set PrintEnable back to false (you might even want to switch back to your original view). The other view that you would make would be a repeating section bound to the same nodes in the data source as the one on the main page where you have all of them, except you would filter the ones that it selects to display only the ones where PrintEnable == true. Since the only way PrintEnable will become true is when you press the button you know that this section will only have one contact in it.
I hope this makes sense.
---------------
Matt Faus
Matt Faus / Microsoft InfoPath MVPQdabra® Software / Streamline data gathering to turn process into knowledge