I would suggest, with as generic the details provided are, that B2B to enable B2C is always going to trend on the maximum benefit to the C for the best balanced effort of the B.
So IMHO, your best bet is to get Product 2 out the door and crowdsource the value and best features to roll-out of Product 1 for your Product 2 customers.
"Lean in", "get'r done", and "just start" all are great statements that get to the point; your best place for you to start is where you can get to market fastest, and share with your customers your roadmap.
Since not all seats are sold for an equal price, the extra seats may have indeed increased revenue potential by allowing for more "premium location" seats on the plane.
There are a lot of factors and it would be silly to think that the airline didn't take more than we can come up with into account in their decision.
Great idea, but why do we require real-time and user-impacting statistics in the first place?
Why not place a AJAX script to a local session monitor that stores up details about a visit and flushes the results via hits to GA? That way, a user doesn't have to wait for GA to load on a page (I've see it be the majority of load time on many websites). The AJAX script could be tied to all types of events such as mouse movement (people hover over links, images, ect. without clicking so capture that as interactivity), onFocus events, and in future eye-tracking events.
This could be built up as a off-screen buffer that generates a more detailed session and fires it off to AG in near-real-time. One other important factor could be to label the events in a concatenated nomenclature so that home.hover, home.idle.30s, home.unFocus, home.gaze.rightMenu.17s, and home.scroll.down.x143 all make sense.
IMHO, sometimes we end working on things before the original concept of finished is achieved because those hacks are subconsciously self-serving and derive more personal-value in understanding everything about finishing than what we consciously believe the value of finishing is.
Tables are a tool. I think that most agree that it is best used for grid/tabular data representation.
Tables are similar to a club (caveman-style), it performs best at a particular task, such as knocking-off dinos, but it was quite often used as a hammer, paper-weight, table-leg, etc. Once specific and readily available tools came about, the club's value as a club didn't diminish, just its extended usability did.
CSS provided programmers the ability to not use a club as a wrench, but there will always remain a value for tables until something more efficient and effective comes about for the task that they serve.
So IMHO, your best bet is to get Product 2 out the door and crowdsource the value and best features to roll-out of Product 1 for your Product 2 customers.
"Lean in", "get'r done", and "just start" all are great statements that get to the point; your best place for you to start is where you can get to market fastest, and share with your customers your roadmap.
I hope that helps in some way.
Cheers