Skip to content

From one search to a working partner, in ten scenes.

Follow an agency in Toronto as it finds a sea kayak operator in Crete that is not on TravelHood yet, reaches it, and starts working together. About two minutes.

Start the tour

Use ← → to move between scenes. Space pauses.

  1. FindSay what you need, in your own words. · Every operator who runs it, not only who joined. · Your profile, drafted from your website.
  2. ReachNot on TravelHood? Write to them anyway. · This is the email they get. · They reply by joining. Their profile is already there.
  3. Work togetherYou're connected. · Agree the details in the same thread.
  4. Build on itAsk your AI assistant. It searches TravelHood. · Or call it from your own system.

Tour scenes

Every operator who runs it, not only who joined.

Operators not on TravelHood yet join the list, each with its source and date. More land while you look.

  • Source and date on every operator not on TravelHood yet
  • Change the place, the list re-sorts

Product preview

Preview: a search for sea kayak operators in Crete returns two operators on TravelHood first, then operators not on TravelHood yet, each with its source and date.

Your profile, drafted from your website.

Give us your site. We fill in what you run, where and in which languages, with the source of each line. Nothing is public until you validate it.

  • Five quick questions
  • You check every line

Product preview

Preview: a tour operator adds its website and gets a draft profile with its name, activities, places and languages, each with its source. It answers five questions and publishes only after checking it.

Not on TravelHood? Write to them anyway.

Write what you want to do together. We send that operator one email with your message, from your company, via TravelHood.

  • One email, sent once
  • You see exactly what we send

Product preview

Preview: an agency writes a message to a kayak operator that is not on TravelHood. The operator receives one email from the agency via TravelHood, with the message, why they got it, and a one-click way to stop all email.

This is the email they get.

Your message, who you are, why they got it, and one click to stop all TravelHood email. Nothing in small print.

  • Why-block always visible
  • Stop link always visible

Product preview

Preview: an agency writes a message to a kayak operator that is not on TravelHood. The operator receives one email from the agency via TravelHood, with the message, why they got it, and a one-click way to stop all email.

They reply by joining. Their profile is already there.

The operator opens the link, finds a profile ready to check, checks it and publishes. Your request becomes a conversation.

  • No form to fill from scratch
  • Claim or remove, their choice

Product preview

Preview: the kayak operator opens the email, finds a profile ready to check, checks it and publishes, and the agency's request becomes a conversation.

You're connected.

You get one notification. The conversation carries on in TravelHood, company to company.

  • One thread per pair of companies
  • Report or block from the conversation

Product preview

Preview: the kayak operator joins from the email, the agency is notified, and the two companies continue in a TravelHood conversation.

Agree the details in the same thread.

Dates, group size and what you will run together, written down in one place. Payment stays between the two of you: TravelHood does not handle bookings or hold money.

  • Proposed, then agreed
  • The terms are between you

Product preview

Preview: the two companies agree dates and group size in a proposal inside their conversation. No amount is shown.

Ask your AI assistant. It searches TravelHood.

We are building a TravelHood connection for AI assistants such as Claude and ChatGPT: one MCP link, then search, read profiles and prepare a request from the chat. Nothing is sent until you press Send.

  • Members first, sources included
  • You confirm every request

Product preview

Preview: TravelHood connected to an AI assistant by an MCP link. The assistant searches TravelHood, lists operators with members first, and prepares a request that is sent only after the person confirms.

Or call it from your own system.

We are building the same search as an API: members and operators not on TravelHood yet in one response, each with its source and date.

  • JSON over HTTPS
  • Keys from your account settings

Product preview

Preview: an API request for sea kayak operators in Crete and a 200 response listing members and operators not on TravelHood yet, each with its source and date.

Your turn.

Type what you need and where. We will write to you when TravelHood can answer it.