We don't have a strong pairing culture, but we're trying to create one! It's a little harder to justify the price because we don't know how many people will use it yet. Besides, programmers are often not the ones who are in charge of approving expenses.

In any case, Tuple is really great. For us, I think it would become a no-brainer if it had a seat-based model. e.g., we pay for 4 pairing seats a month, and a max of 4 developer can use Tuple at any given time.