Tourist tax self service

What the company appears to be: Tourist tax self service is a platform designed to modernize tourist-tax registration for accommodation providers in Switzerland. The description states it aims to provide a shared digital layer between guests, landlords, tourism organisations and municipal legacy systems. It positions itself as a scalable solution that works with existing municipal backends rather than replacing them.

What changed: The project was submitted to the OpenAI 2026 hackathon on Devpost. The author describes it as a self-reported project built by one person (Roman Zoun) using various technologies including Next.js, React, Python, Docker, PostgreSQL, and OpenAI tools.

Single most important open question: Is there evidence of traction or early customer validation beyond the author's own experience and hypothesis?

The description states this is a self-reported, unverified project submitted to a hackathon. There is no evidence of revenue, customers, or adoption beyond what the author describes. The platform appears to be conceptual with no demonstrated market traction.

The description states that Tourist tax self service is:

• A shared digital layer between guests, accommodation providers, tourism organisations and municipal legacy systems
• A platform that allows landlords to create properties once and send guests registration links before arrival
• A system where guests enter information through a mobile interface that validates data, identifies missing information, applies municipality-specific rules, and prepares registration for existing backend processes
• A platform that can complete required workflows on behalf of landlords with explicit consent
• Designed as a scalable platform rather than single-purpose integration for one municipality

The product architecture is described as having three layers:

1. Shared User Experience (independent of municipality backend systems)
2. Municipality-Specific Business Rules (configurable requirements including mandatory guest information, tourist-tax rates, age-based exemptions, etc.)
3. Legacy Integration Layer (municipality-specific adapters connecting to existing systems)

The description states the company's positioning:

• Tourist-tax registration is fragmented, manual and locked into costly legacy systems
• They provide one scalable platform with a modern UX without replacing municipal backends
• The platform works with infrastructure municipalities already use
• It creates a consistent user experience across different municipalities
• It acts as a compatibility and orchestration layer around existing municipal systems

The claim evolution shows:

• Initial inspiration from personal experience of landlords in Leukerbad
• Recognition that the problem exists across multiple Swiss tourism destinations
• Shift from "building another tourist-tax system" to "creating a modern and scalable user experience while continuing to work with existing infrastructure"
• Emphasis on not replacing legacy systems but improving the interface around them

The description states:

• Primary customers are accommodation providers (landlords) in Switzerland
• Landlords who rent through platforms like Airbnb and Booking.com
• Municipalities that manage tourist-tax registration
• Tourism organisations that support accommodation providers
• Guests who must register for tourist tax

The target customer segments identified are:

1. Accommodation providers (landlords)
2. Municipalities managing tourist-tax systems
3. Tourism organisations
4. Individual guests

The description states:

• The business model must align pricing with measurable operational value
• Potential models include subscriptions per property, transaction-based fees per stay, and municipality-level platform agreements
• Revenue model could be expressed as: R = P · Sp + B · Sb + M · Sm where:
  • P is number of registered properties
  • Sp is subscription revenue per property
  • B is number of bookings or stays
  • Sb is transaction revenue per booking
  • M is number of municipal platform agreements
  • Sm is average municipal service revenue

The description states that the value is distributed across several parties:

• Landlords save administrative time
• Guests receive better experience
• Municipalities receive higher-quality data
• Tourism organisations reduce support work

The description states:

• Built with technologies including: codex, consent-management, data-privacy, docker, govtech, keycloak, legacy-integration, multi-tenant, municipalities, next.js, openai, playwright, postgresql, python, react, rest-api, rpa, saas, stripe, switzerland, tourism, tourist-tax, traveltech, typescript, workflow-automation
• Designed as a scalable platform with three architectural layers
• Separates shared user experience from municipality-specific business rules and legacy integration layer
• Uses configurable workflows and reusable integration components
• Supports different municipal rules through configurable requirements
• Works with APIs where available and supports controlled automation where modern interfaces don't exist
• Focuses on progressive validation of data

Not evidenced

The description states this is a self-reported project submitted to a hackathon. There is no evidence of:

• Revenue or financial performance
• Customer base or user adoption
• Product-market fit validation
• Market traction or growth metrics
• Any form of customer validation beyond the author's own experience

Not evidenced

The description does not provide information about:

• Direct competitors in the tourist-tax registration space
• Alternative solutions currently available
• Market size or competitive landscape
• Differentiation from existing systems
• Competitive positioning or market share

The description states several key risks:

1. Different rules in every municipality - Tourist-tax regulations vary significantly between destinations, making scalability challenging
2. Working with legacy systems - Legacy systems often have limited APIs, inconsistent interfaces, and workflows designed for manual administration
3. Data quality challenges - Balancing guest experience with municipal data requirements
4. Trust and consent requirements - Processing personal guest data and acting on behalf of landlords requires explicit consent and secure processing
5. Building a sustainable business model - Value distribution across multiple parties makes pricing alignment difficult

1. What specific municipalities have you identified as potential early adopters?
2. Have you conducted any market research or user interviews with landlords, municipalities, or tourism organisations?
3. What is your timeline for MVP development and initial customer acquisition?
4. How do you plan to handle the complexity of different municipal rules and regulations across Switzerland?
5. What are your specific go-to-market strategies for reaching accommodation providers and municipalities?
6. Have you identified any potential partners or stakeholders in the tourism industry who might support adoption?
7. What is your approach to data privacy compliance given the handling of personal guest information?
8. How do you plan to demonstrate value to municipalities who may be hesitant to adopt new technology?