From Tessera to Eventfold: Why We Rebranded Our Event Platform Mid-Flight

There is a particular kind of dread that comes from realizing your company name is wrong. Not wrong in an abstract, strategic sense — wrong in the way that becomes obvious the moment you say it out loud to someone who has never heard it before and they stare back at you with polite confusion.

That was Tessera.

I spent over a year building under that name. It was the name on the KTH Innovation paperwork, on the domain registration, on every email I sent. I had a whole internal story about it — a tessera is a small tile used in ancient mosaics, and events are made of many small moments that come together to form something bigger. I thought it was clever. I thought it communicated something.

It did not communicate anything to anyone except me.

What a Name Actually Does

Here is what I got wrong: I assumed people would learn the name, and that was enough. Names carry weight in a different way than I initially appreciated. They are not just labels — they are first impressions, they are the thing someone types into a search bar at midnight when they are trying to remember what tool their colleague recommended, they are what someone says out loud in a meeting room when they are trying to convince their manager to approve a new vendor.

If someone cannot say your name confidently, they will not say it at all. They will describe your product in vague terms instead. "That ticketing thing. The Swedish one." That is not how you grow.

The International Problem

Tessera is a real English word, but it sits comfortably in a very specific part of the vocabulary that most people never visit. Even for native English speakers, the pronunciation is uncertain. Is it TESS-er-ah? Tuh-SAIR-ah? The second syllable causes a small but real moment of hesitation.

Then there is the matter of existing brands. A company with the same or similar name already operates in the events and entertainment space in the US. Not directly competitive, but enough overlap to create confusion and SEO friction that I was not going to spend years fighting.

And then there is the Swedish angle, which might sound like a small thing but is actually not. I built this at KTH in Stockholm. A significant portion of my early customers, my support contacts, my partners — they are Swedish. "Tessera" does not sit naturally in Swedish pronunciation either. There is no clean way to say it that feels Swedish or that lands easily in a Swedish conversation.

I want a name that a Swedish grandmother can pronounce without thinking about it. That sounds like a low bar, but it filtered out a surprising number of candidates.

Finding Eventfold

The domain hunt is its own kind of suffering. You will fall in love with names that are taken. You will find names that are available but legally problematic. You will consider names at 1am that seem brilliant and are obviously terrible in the morning.

What I was looking for was something that described what the product actually does, was pronounceable everywhere, and had a clean domain available. Eventfold.com was there. It felt right immediately — not because it was clever, but because it was clear.

Fold. As in, you bring things together. You fold a community of people into one place for a shared experience. You fold the logistics — ticketing, check-in, seating, communication — into a single platform. It is not a metaphor that requires explanation. It is just a word that works.

And it is honestly just easier to say. Event. Fold. Two clean syllables each. No ambiguity.

The Emotional Part Nobody Talks About

Changing the name was harder than I expected emotionally. I do not think founders talk about this enough. There is a grief-adjacent feeling that comes from retiring a name you have been building under. All of the meaning you attached to it, all of the internal story — it does not transfer automatically. You have to let go of it and start building a new story.

I had introduced myself as "the founder of Tessera" hundreds of times. The name was part of my identity as a builder. Switching felt like admitting something had not worked. It required a certain humility to accept that the name I chose in the early days was not the name I should carry forward.

The honest reality is: I made a better decision at month fourteen than I made at month zero. That is fine. That is how building works.

The Practical Nightmare

If you think a rebrand is mostly a design exercise, you have not done one. Yes, there are visual assets to update. But the work that actually consumes your time is finding every single place the old name lives and updating it.

Config files. Email templates. Customer-facing documentation. Billing notifications. Legal documents. Social profiles. Domain forwarding. SEO metadata. Internal tool names. Support macros. Every onboarding email in the sequence.

And here is the part I want to be completely honest about: even now, there are internal code references to "tessera" that I have not changed. The old domain still exists. Some internal systems still carry the old name under the hood. That is the reality of a working product that you cannot freeze while you clean house. You do a migration, not a replacement, and the migration takes longer than you want it to.

This is not failure. It is just what it looks like when you rebrand a live product instead of a side project. The customer-facing surface got updated first because that is what matters. The internal archaeology continues in the background.

What I Would Tell Another Founder

If you are sitting with a name that is not working and trying to decide whether to change it, here is my honest advice:

Do it earlier than feels comfortable. The longer you wait, the more inertia you build. More customers to notify, more integrations to update, more places the old name lives. The "right time" to rebrand does not exist, but earlier is consistently better than later.

Prioritize pronounceability over cleverness. I loved the tessera metaphor. Nobody else cared about the tessera metaphor. A name that a stranger can say confidently on a phone call is worth more than a name that tells a clever story that only you know.

Run the domain test first. Before you fall in love with a name, find out if the .com is available. You can build something valuable on a .io or a .co, but the friction is real and persistent. If the .com is there, that is signal worth weighing heavily.

Protect your time. The rebrand will take twice as long as you estimate. Budget accordingly and do not let it eat every focused work session for a month. Chunk it: external surface first, internal systems over time, legal and technical last.

Tell your customers plainly. When I communicated the change, I was direct about it. "The product is the same, the team is the same, the vision is the same — the name is better." Nobody complained. Most people appreciated the clarity. The fear of customer confusion from a rebrand is usually larger than the actual confusion.

Where We Are Now

Eventfold is an AI-native event management platform. It handles ticketing, check-in, seating, AI-assisted email coordination, and analytics — built for event organizers who want to spend less time on logistics and more time on the experience they are trying to create.

The name reflects that now. When I introduce the product, people understand what it is before I have finished the sentence. That was not true with Tessera.

We are still a small team, still supported by KTH Innovation, still building from Stockholm. The ambition has not changed. The name just finally matches it.

If you are building something and the name is nagging at you — trust that feeling. It is usually telling you something true.