// Case note · 07 min · 03.10.2026

What AIDA taught me
about local AI.

Rostock.ai reached the final nine from more than 150 submissions. The most valuable result was a clearer standard for what a useful destination-intelligence product must become.

The milestone

On September 16, 2026, I walked into AIDA’s headquarters in Rostock with ten minutes to explain a much bigger idea: local knowledge should be easier to access, more trustworthy, and more useful to the people arriving in a city.

Rostock.ai had been selected from more than 150 submissions as one of nine finalists in the first AIDA Innovation Hub. We were one of three projects in the “AI Tools & Smart Solutions” category. For an independent builder, simply reaching that room mattered.

A sharp use case makes the system visible

The cruise scenario forced the idea to become concrete. A guest has limited time ashore. Their needs may depend on mobility, language, weather, family, interests, and how far they can travel. A generic list of attractions is not enough.

The product must combine reliable local information with the visitor’s context, then explain a small number of useful choices. That is where an AI interface can add value—not by generating more content, but by reducing the distance between a question and a trustworthy local answer.

The model is not the whole product

A local assistant is only as good as the knowledge it can reach. Opening hours, accessibility, offers, event schedules, and business information change. The difficult work is therefore not only language generation. It is the information system behind the conversation.

Rostock.ai combines structured public and open sources with workflows that allow local organizations to contribute and maintain information. Public business information moves through review. The aim is a knowledge layer that is both useful to visitors and valuable to the local economy.

Independence can be a product advantage

I presented Rostock.ai as a solo founder among established teams and organizations. That can feel like a disadvantage. It also creates unusual speed: the research, product decisions, interface, data model, implementation, and pitch remain connected.

The goal is not to look like the biggest team. The goal is to understand the problem deeply enough to build the right next version.

What comes next

The finalist experience clarified three priorities: stronger data partnerships, clearer governance for contributed information, and product scenarios that serve visitors without disconnecting value from local businesses and institutions.

Rostock.ai is still a developing system. But the AIDA Innovation Hub showed that the underlying problem is real, the travel use case is credible, and a local approach to AI can earn a place in serious industry conversations.

See the system behind the pitch.

Read the full Rostock.ai case study, including its information model and destination use cases.

Rostock.ai case study