Company origin / imagined world
Haamer Ventures OÜ was originally called Basil Harem Ventures OÜ. The name came from an imaginary character I had invented, because I wanted the company to begin with storytelling rather than a standard business category.
“I did not begin with a market category. I began with a character.”
Why such a strange name?
Basil Harem Ventures was deliberately theatrical, slightly excessive, and hard to flatten into a single service description. That was the feature. It gave the company permission to move between media, technology, culture, and experiments while keeping a recognizable point of view.
01
Basil Harem was an imaginary figure before it was a business name. The point was not to sound like a conventional consultancy or holding company. It was to create a name that suggested a world, a personality, and stories still waiting to happen.
02
The early idea was that a company could behave like a narrative container. Projects, websites, films, events, and experiments could belong to the same expanding story without needing to fit one narrow category.
03
Basil Harem Ventures OÜ later became Haamer Ventures OÜ. The legal name became more direct, but the original impulse remains visible in HAAM: build distinct worlds around ideas, give projects memorable identities, and use design to make people curious enough to enter.
From Basil Harem to HAAM
Today, Haamer Ventures OÜ operates through HAAM. The name is shorter and closer to my own, but HAAM still treats identity as more than decoration. A project can have a voice, a cast of characters, an atmosphere, a mythology, and a reason for people to care.
That approach now appears in more practical forms: interaction design, products, research, cultural projects, events, and AI systems. The output changes. The underlying question does not: what story makes an idea feel real enough to enter?
Optional Google Analytics and Microsoft Clarity measure content performance and usability. They load only if you allow them. Form values, email addresses, and chat messages are never included in analytics events.