Demo Sample property · not a real inn
The Larkspur Inn — a white clapboard Cape Cod inn with green shutters and flower boxes

Five days before arrival

It starts in the guest's inbox

No app to download. No website to find. The inn already has their email — this goes out automatically once the booking is made.

From  The Larkspur Inn, Brewster
To  Susan Whitmore
Sent  Sunday, five days before arrival

Susan, a few questions before Friday

Hi Susan,

We're looking forward to having you and Dave with us Friday and Saturday. Room 4 is yours.

Before you get here, would you take thirty seconds and tell us a little about the trip? We'll have some suggestions waiting — the kind of thing we'd tell you over coffee, not what you'd find on a search.

See you Friday,
Ellen & Tom
The Larkspur Inn · 6A, Brewster

The Larkspur Inn
Brewster · Cape Cod
Question 1 of 4

Save This Plan

We respect your privacy. Your information is only used to send your plan and is shared with The Larkspur Inn.

Now here's the part the innkeeper pays for

Everything above went to the guest. At the same time, one page goes to the innkeeper — built from these exact answers.

Friday, 7:00 a.m.

Arrivals briefing

One email. One page per arriving room. Built from what the guest actually told you — nothing here was typed by hand.

Want to change the answers and watch this page change with them?

In the room

The binder, retired

A small card on the desk and one on the breakfast table. Same guide, always current, and it already knows who they are.

Good morning, Susan
Saturday · Room 4

The same link the guest already used before they arrived. Nothing new to learn, nothing to install — and the innkeeper can update what it says from their phone.

For the operator

What actually has to happen

Four moving parts. Two of them the inn already owns.

1

The guest books

However they already do it — direct, or through a booking channel. Nothing changes about how the inn takes reservations.

2

One line in the confirmation

The inn already sends a confirmation email. It gains a single sentence and a link. No new system, no integration on day one.

3

The guest answers

Four questions, about thirty seconds, on their phone. They immediately get a plan for their stay, written for the way they actually travel.

4

The innkeeper gets the sheet

One page per arriving room, in the inbox the morning of check-in. Read it with coffee. That's the whole workflow.

Why not just put this on the inn's website?
Because almost nobody would use it. A small inn's website gets modest traffic, and a good share of bookings arrive through third-party channels anyway. A pre-arrival email reaches someone who has already paid, already committed, and is actively planning their trip. That is a completely different audience from an anonymous visitor browsing a homepage.
Does this replace anything the inn already runs?
No. It sits alongside the reservation system rather than replacing it. Version one needs no integration at all — the link goes in the confirmation email the inn is already sending. Connecting directly to the property management system is a later step, and only worth doing once the inn wants it to run entirely hands-off.
Who owns the guest information?
The inn. It is their guest and their relationship. The concierge collects only what the guest volunteers about their own trip, shows it back to the innkeeper, and does not sell it, rent it, or use it to market anything to that guest on anyone else's behalf. That should be written into the agreement rather than assumed.
Who keeps the recommendations current?
We do. That is most of the actual work and the reason this isn't just a form. Places close, change hands, and change hours, and a stale recommendation is worse than no recommendation. The innkeeper can also add their own — the neighbor's farm stand, the table they always ask for — and those get priority over anything general.
What does the innkeeper actually get out of it?
They stop answering the same question forty times a week, and they walk into a check-in already knowing it's a twenty-fifth anniversary and that one of them can't eat gluten. That is the difference between a pleasant stay and a review that mentions them by name.

This is a working demonstration built on a sample property. The Larkspur Inn is not a real business. The places recommended in the guest plan are real and were checked before this was built, but hours and seasons change — anything shown here would be verified again before it went in front of a paying guest.