Tripollon

The problem

One trip, scattered information.

An itinerary in a PDF, updates in a group chat, excursion sign-ups in a spreadsheet. When plans change, keeping those places in sync becomes another task for the agency and the guide.

Who it is for

What we're planning

• Tour details in one place

  A shared page for the itinerary, documents and useful contacts, reached through one link.

• Itinerary updates

  Update the tour page instead of sending a replacement PDF whenever the plan changes.

• Notices and read status

  Notices for the group, with a way for the agency to see which travellers have opened them.

• Excursion sign-ups

  A place for travellers to sign up and for the agency to keep track of registrations and cancellations.

• Language support

  Tour information in more than one language. The languages and translation options for the first version are still being defined.

• An overview for the agency

  A view of active tours and outstanding tasks, so the agency can see what needs attention.

Where it stands

1. Now

   First version in development

   We're building the core of Tripollon. The features above describe the intended direction; the scope of the first release is still taking shape.

2. Next

   First trials

   Once a usable version is ready, we plan to test it with agencies and guides. You can write to us if you are interested.

3. Next

   Refine for release

   Use what we learn from those trials to improve the product and decide what is ready for a wider release. We haven't announced a release date.

Why we build it

Keeping an agency's plan and a traveller's information in sync is a concrete problem to start with. Tripollon is our first product, and we're exploring how much simpler that coordination can be when it has a place of its own.