Tigmus was in some senses a data catalogue for live music

A searchable interface describing what data were available for our different music industry personas:

• players (“where should I tour?”)
• punters (“which tickets should I buy?”)
• promoters (“which acts should I be booking?”)
• services (“need a lightshow / poster design / mixing?”)
• Tour Managers (TM: “what hotels can I book in 10km radius?”)

… so that these members of the community didn’t have to resort to traditional, “tribal knowledge” approaches in order to address information asymmetries and get the live music experience working for all.

There’d already been a wave of tech adoption through the live touring circuit in terms of TM-assistant apps, notably MasterTour. The data architectures behind touring are some of the most exciting, as you get to see down to the granular data points of “what time the bass player needs to arrive on site for dinner”; all visualisable in apps like MasterTour and Tigmus. However, being an industry geared toward Openness and much less Conscientiousness, the use of those data architectures — even when facilitated through the most intuitive UI and simple workflows — was (and continues to be) slower than necessary for generating a profit for the developer. Even those TMs who conscientiously carry around a Google Sheet of all the carefully assembled info around each day’s journey, soundcheck, hotel check-in, performance, etc, don’t stand a chance: the chaotic lifestyle lends itself to unkempt tourbuses rather than consistent developer-friendly data structures.

Still, a really fun project to have co-developed and a great Rails On Rails showcase.