ITM Case Study

The Problem

ITM is an all-in-one event and community platform for brands, creators, and their audiences, operating out of New York and San Francisco. It covers the full arc of an event — discovering it, buying a ticket, managing a membership, getting through the door, and revisiting the content afterwards. The premise is that an event is more than a ticket, and that everything happening before, during, and after a moment belongs in one place. That premise exists because organizers were living the alternative: separate tools for ticketing, payments, seating, memberships, guest lists, and door check-in, none of them talking to each other.

The founders had a second problem, closer to home. ITM was two people. Cam, the CEO, had carried the product through its initial design phase and needed to be out in the market building the business. Saarim, the CTO, owned the entire engineering surface, which meant he couldn't be anywhere else. Client requests arrived daily and each one landed on the same desk. Commercial growth was capped by engineering capacity, and engineering capacity was one person.

What We Did

Rather than take on a scoped project from the outside, Algorithm embedded engineers into ITM's team. Two of our engineers now work alongside Saarim — Safi leading web and Zakarya leading mobile, both full-stack, with Saarim leading backend. They own the path end to end: a request comes in from a client, and the same people scope it, build it, review it, and ship it to production. Nothing has to route through the CTO to move.

The product itself is three connected surfaces. Attendees use a mobile app to find events, buy tickets, hold passes and memberships, and revisit content afterwards. Organizers use a web dashboard to create events, configure tickets and seating, manage attendees, track sales, and run their communities. Event staff use a reader app to scan QR codes, verify tickets, and check guests in.

The engineering weight sits in keeping those three from ever drifting apart. A ticket sold in the app, a seat reconfigured in the dashboard, and a pass scanned at the door are all the same underlying record. A single shared backend keeps ticketing, payments, seating, memberships, notifications, and event data synchronized across all three, so a scan at the door reflects a sale made seconds earlier. Check-in is the least forgiving surface of the three — there is a queue of real people waiting, and no tolerance for a slow lookup or a stale ticket state.

Impact

The immediate change was structural: Saarim stopped being the bottleneck. With daily feature demand absorbed by a team instead of a single founder, he was freed to work directly with clients and take the product into its next phase, including fundraising. Cam could keep selling without worrying that every new client commitment would stall in the backlog.

The arrangement has held. Two Algorithm engineers remain embedded in ITM's team today, owning the full path from client request to production deploy, and the platform continues to expand across all three products.