Let people explore.
Give the space a voice.

For space operators and teams that repeatedly explain a physical venue before a visit or enquiry.

• Start with a coworking space, showroom, or other venue with a defined visitor journey.
• Assign an owner who can approve imagery, venue facts, and the next action offered to visitors.

A visitor sees a room, but the relevant explanation, plan, or next step lives elsewhere.

• Connect the selected panorama with room descriptions and venue questions.
• Test whether visitors can find the information they need before handing an enquiry to your team.

Begin with material your team is authorized to publish and maintain.

• Panorama assets, named spaces, navigation links, and approved descriptions.
• Venue FAQs, facilities, plans, language requirements, and a content owner.
• For any operational action: the system owner, permitted actions, and a test environment.

Agree a reviewable scope around a tour and its visitor questions before adding operational actions.

• A navigable panorama tour with the agreed space labels and languages.
• A touring assistant using the selected view and approved venue knowledge.
• A review record of sample questions, observed answers, content gaps, and enabled workflows.

Choose one venue and one visitor journey, then review the source material and acceptance criteria together.

• Inventory imagery and knowledge; identify missing content and publication rights.
• Prepare the tour and answers, review them with the venue owner, then test representative questions.
• Agree who updates content and handles unresolved visitor requests before launch.

The public demo connects the tour and assistant. The protected operator demo illustrates feature activation using prepared demo data.

• Evaluate booking, CRM, payment, or access-control systems separately for APIs, permissions, and failure handling.
• A demo booking interface does not establish a working connection to your production calendar, payment provider, or door access system.

The demo is a prepared environment. Its quick prompts use prepared responses; free-form questions depend on the model and available knowledge.

• At the 11 September 2026 check, the first tour section was enabled; enhanced knowledge and the booking interface were disabled.
• Images and knowledge can become outdated. Review answers and confirm real availability with the operator.
• The demo does not establish customer outcomes, venue ownership, or a general document-ingestion service.

Request an estimate after reviewing the assets, visitor journey, and required integrations.

• Number of spaces, panorama preparation, language coverage, and knowledge cleanup.
• Integration work, expected usage, model operation, support, and content update frequency.
• Agree the first deliverables and ongoing responsibilities in the proposal; no fixed price or delivery period is published here.

Use an agreed checklist tied to your actual spaces and questions.

• Named views load and navigation reaches the intended space on agreed devices.
• Sample answers match approved venue facts in each agreed language; missing knowledge is identified for review.
• Any included action is tested with authorization in the target test system, with its result and failure behavior recorded.