io.png

Introducing IO

This time last year, I started a new experimental project to re-implement some core Tito features using some modern web development techniques. 

Soon after starting this new project, we got the chance to work with an exciting customer with very specific needs. 

Before long, the new project became a new product for that use-case: bespoke invitations for high-end events.

Internally, I code-named this product “Tito 2”, but when we took a step back, we realised we had built something new. The app took something we had built in Tito—RSVPs—reimagined it from scratch, and implemented everything you would need to build a great invitation and RSVP experience. It would be the perfect app for invitation-only events. Invitation Only. IO.

We’ve spent the year since, in private beta, refining IO with some early customers:

  • Deutsche Filmakademie are sending bespoke, branded, personal invitations to the members, and managing the process in one app rather than multiple apps and spreadsheets.

  • For their Pioneer event, Intercom sent invitations with full control over the design. Invitations were customised to particular invitees, and guests had access to customised attendee hubs on the day

  • Product Marketing Alliance are sending invitations to their various VIP dinners using IO, with custom branded invitations and different domain names and email addresses for their individual communities.

IO is full of useful features for invitation-only events. Here are just a few:

  • Emails come from your address

  • RSVP links also use your own domain with SSL

  • Liquid allows custom email and HTML templates

  • Links are single-use, with authorization required once they’ve been used

  • You can control how many guests each attendee can bring

  • Apple and Google Wallet passes are customizable

  • Imports are lightning quick. You can selectively export, bulk update, and then re-import all the updates

  • Messaging is built in (again with custom templates)

The list goes on. It’s been a delight how often we can say “yes” to features that are specific to this particular use-case: creating the best RSVP experiences possible.

Three weeks ago we took some time to refine the UI, and yesterday I went looking for a domain name to host the new product (it’s been living on 2.ti.to all year). After a bunch of searching, I found a two-letter domain that felt like it was exactly what we were looking for:

io.rsvp

We put it live today, and it’s the perfect home and perfect domain name.

We're preparing for a full launch in February but we're eager to work with select partners now. It’s been gratifying to work closely with the customers above, refining and improving as we’ve solved real-world problems. If that sounds like something you’d be interested in, please get in touch.