From Product Design Agency to Client: 5 Rules for Building Your Own Product
About the Author:
Peter Deltondo is a Product Designer turned Product Founder who spent the last decade leading teams, Co-Founding Heyo, a design and development agency, and Co-Founding products, including Eventrise and Keyvo. The list of clients he’s worked with includes Figma, Adobe, Discord, Facebook, Merck, and Toyota. In his free time, he can be found in a river fly fishing or spending time with his family in the great outdoors.
As a product design agency, we’re usually working with a client who hands us a brief and we design and build under that framework. But because we’re problem-solvers, we became our own client a few years ago. We set out to build our own event management software, based on the pain points we felt with the major platforms in the space.
That project became Eventrise. We’ve shared why we built it, so now we talk about how we did it. The five principles that got us from a Figma file to a live product: the same ones we’d recommend to any brand, product or agency trying to do what we did.

1. Audit what competitors have quietly agreed not to solve
Most competitive research stops at “what do they do well.” But we knew that was the wrong question. The ones we asked were: what have they ignored? Where are they letting the user down? What are they doing entirely wrong?
We pulled up competing event platforms and analyzed them in Figma, screen by screen, every flow, checkout step, and piece of onboarding. We identified where the user flows broke down, where it felt like real event organizers or attendees would be left behind. What were the features, that we as event organizers desperately wanted, but were ignored by all these platforms?
The pattern was consistent:
- Every platform had solved event ticketing reasonably well.
- Almost none had solved the elements around it: workshops, add-ons, meet-and-greets.
- Those pieces lived on separate sites, checkouts, and made the platform more complicated and confusing.
If you’re auditing a crowded category and everything you find looks like a feature comparison, you’re not done yet. You’ve got to ask the right questions and look for the problems you actually need to solve.
This has sparked a lot of “Oh my gosh! This is what we’ve been wanting forever!” during calls with organizers and venues. They were all picking the platform that either checked the “most boxes”, but still wasn’t meeting their needs, or doing hacky things themselves to try and creatively solve these pain points. Who would have thought simply building what your audience has been begging for could work so well?…

2. Rebuild the whole thing when you need to
After some market research, we got to building. Part of why we built Eventrise for conferences, was because of our very own Heyo designer Mike Jones, has been running Creative South, a design conference coming up on 15 years. Heyo Co-Founder, Peter Deltondo has been volunteering alongside Mike for the past 13 years. Yet, as we worked, we realized we’d been building for a smaller opportunity: A conference happens likely once a year. A venue runs events almost every day.
So, we reworked navigation and checkout to genuinely serve two kinds of users, instead of just adding “venue mode” onto a conference tool.
We believe that this is the principle that differentiates a good product pivot from just making things look good: when the real opportunity turns out to be different from the one you started with, rebuild. Being flexible and moving when you need to is a superpower.

3. Know when to kick it into high gear
After piloting ticket sales at Eventrise at Creative South in early 2025 and seeing the massive excitement from other organizers in the crowd, we started investing in Eventrise on another level.
- We built dedicated teams around it
- We made our first full-time Eventrise hire, a Head of Marketing & Sales
The planning phase had done its job, but it was time to put some real weight behind it. A real team meant real requirements, real prioritization, and a process built for launch instead of exploration.
The shift from “we’re building this internally” to “we’re building for a global user base” was an important one for the future of the platform.

4. Keep one team for the whole build
The same team worked across brand, product, and engineering for the entire build. No re-explaining context between a brand shop, a design agency, and a dev contractor. Every handoff costs you consistency, time, and patches needing to be made later.
That’s part of why Eventrise feels coherent in a way that tools cobbled together from separate vendors often don’t. Every decision made in the brand system was made by people who also understood the checkout flow. Every product decision was made by people who understood what the marketing site needed to feel like.
If you’re a brand comparing service providers for a build like this, this is the question that matters most: who’s actually in the process for the whole thing, start to finish? It shows up in the final product more than almost anything else.

5. Design one flow, not a patchwork of flows
One of the early product solves was figuring out the checkout flow. Jumping around in a product is exhausting, especially when you’re trying to buy tickets. We built tickets, workshops, meet-and-greets and every type of “add-on” you can think of into a single checkout. We saw a big uptick in workshops purchased at Creative South this past year compared to years past, as this heavily reduced friction and made the workshops so much easier to find, rather than having to purchase a separate ticket from general admission sales.
Finding the gap isn’t the hard part, we recognized the challenge early in the research process. The hard part is designing the one flow that actually closes it, and helps every user have the best experience.

The Result
Eventrise is live online today. The web app is robust but we also have mobile apps for both attendees and organizers that are built out to do nearly everything the web app can do.
- Payouts land in one to one and a half days, directly into the organizer’s own Stripe account.
- Tax-exempt purchases are handled automatically, with approval typically landing in thirty to sixty minutes.
- Tickets, workshops, and add-ons run through a single, unified checkout.
Since launch, we’ve kept shipping: custom checkout questions, a Zapier integration, team roles, venue landing pages, attendee detail pages, a live multi-event dashboard, scheduled email reports, and pre-sale access codes. Merch sales and lanyard printing are next.
None of that came from a single good idea. It came from lots of small decisions, made in order, each one setting up the next.
You can follow the ongoing evolution of Eventrise on the website as well as right here on the Heyo team Dribbble page.






































































