Daily Travel Briefing Trip planning, briefings and booking intake in one place
Daily Travel Briefing

Travel plans in one place. Daily briefings without manual overhead.

Plan a trip in clean date ranges, capture day-specific activities where needed, and let the system turn that plan into polished daily briefings with weather, context, places and booking intake.

Planning
Blocks first
Enter entire stays from one date to another instead of duplicating days by hand.
Briefings
Email-native
Daily summaries stay useful, timely and tailored to the actual trip context.
Ops
Invite-based
Friends get their own login, their own trip and their own preferences.
What it does

One workflow for trip setup, preferences and delivery

Trip planner

Range-based input

Add a full stay from May 3 to May 13 in one row. The app expands daily records internally, while still allowing day-specific overrides.

Preferences

Freitext works

Dietary preferences, mobility constraints, budget and travel style stay flexible. The LLM can handle nuanced text without forcing rigid schemas.

Delivery

Hosted email flow

Outbound sends run via Resend, with unsubscribe handling and account-aware recipient management.

Booking intake

Inbox to plan

Forward confirmations into the booking inbox, review extracted data, then import it into the right trip account.

How it works

Simple enough for friends, structured enough for reliable runs

1

Create or invite a user

Admins create the workspace once. After that, friends can join via invite link and edit only their own trip.

2

Plan the trip in blocks

Users enter location, accommodation and default activities for each stay, then add day-specific activities only where needed.

3

Send briefings automatically

The scheduler picks the right account, reads the plan, applies preferences and sends the daily travel briefing at the configured local time.

Why this setup

Cleaner than spreadsheets, safer than ad-hoc email scripts

Less manual upkeep

Long stays are entered once, not copied across ten rows.

Better context

Preferences and daily activity overrides are available directly in the briefing prompt.

Real product surface

Login, invites, account separation, delivery settings and booking review live in one coherent UI.

Production-ready path

Hosted on Railway, persistent in Postgres, with Resend for outbound email and room for Mailgun inbound.

Daily Travel Briefing

Travel plans in one place. Daily briefings without manual overhead.

Plan a trip in clean date ranges, capture day-specific activities where needed, and let the system turn that plan into polished daily briefings with weather, context, places and booking intake.

Planning
Blocks first
Enter entire stays from one date to another instead of duplicating days by hand.
Briefings
Email-native
Daily summaries stay useful, timely and tailored to the actual trip context.
Ops
Invite-based
Friends get their own login, their own trip and their own preferences.
What it does

One workflow for trip setup, preferences and delivery

Trip planner

Range-based input

Add a full stay from May 3 to May 13 in one row. The app expands daily records internally, while still allowing day-specific overrides.

Preferences

Freitext works

Dietary preferences, mobility constraints, budget and travel style stay flexible. The LLM can handle nuanced text without forcing rigid schemas.

Delivery

Hosted email flow

Outbound sends run via Resend, with unsubscribe handling and account-aware recipient management.

Booking intake

Inbox to plan

Forward confirmations into the booking inbox, review extracted data, then import it into the right trip account.

How it works

Simple enough for friends, structured enough for reliable runs

1

Create or invite a user

Admins create the workspace once. After that, friends can join via invite link and edit only their own trip.

2

Plan the trip in blocks

Users enter location, accommodation and default activities for each stay, then add day-specific activities only where needed.

3

Send briefings automatically

The scheduler picks the right account, reads the plan, applies preferences and sends the daily travel briefing at the configured local time.

Why this setup

Cleaner than spreadsheets, safer than ad-hoc email scripts

Less manual upkeep

Long stays are entered once, not copied across ten rows.

Better context

Preferences and daily activity overrides are available directly in the briefing prompt.

Real product surface

Login, invites, account separation, delivery settings and booking review live in one coherent UI.

Production-ready path

Hosted on Railway, persistent in Postgres, with Resend for outbound email and room for Mailgun inbound.