Strawberry

Seven people, four origin cities, one hotel everyone can walk from

Constraints in, decision grid out: two flight options per traveler priced in your own session, three hotels inside a fifteen-minute walk, and total trip cost per scenario. Booking stays yours.

Someone volunteers, opens forty tabs, and spends two days reconciling "I cannot land after ten", "I am coming from the Berlin office" and "the venue is in an awkward part of town". Then one flight preference changes and half the grid recomputes.

A companion holds all seven sets of constraints at once and priced options come back as a grid. It runs in your logged-in session on the booking sites you already use, so your loyalty accounts and corporate rates apply. It stops before booking, because a wrong click there costs real money and somebody's Tuesday.

What is the exact prompt?

"Plan travel for our offsite: [dates], venue at [address]. People and constraints: [A] and [B] fly from [city 1]; [C] from [city 2]; [D], [E], [F] are local; [G] flies from [city 3] and needs step-free access throughout. Rules: nobody lands after 22:00 local; nobody departs before 09:00 on the last day; economy, one checked bag each. Flights: two options per traveler, cheapest-reasonable and best-times, with airline, departure and arrival times, and price as shown right now in my session on [booking site]. Hotels: three options within a 15-minute walk of the venue, one room per person, with nightly rate, breakfast included or not, step-free access confirmed on the hotel's own accessibility page for [G] rather than assumed from photos. Output: a grid, one row per traveler, columns option A and option B; a hotel table; and total trip cost per scenario (each hotel × cheapest flights, and × best-times flights). Note which prices looked volatile. Book nothing, reserve nothing, enter no payment or passenger details anywhere. Stop at the grid."

Prices move, so the grid is a snapshot with a short shelf life. Decide inside a day.

Why does accessibility get its own rule?

It is the constraint with the worst failure mode and the least reliable data.

Listings routinely imply accessibility the property cannot deliver, and discovering that at check-in leaves a colleague outside the lobby. The prompt demands confirmation from the hotel's own accessibility page, because "confirmed on their site" and "looked fine in the photos" are different classes of evidence.

The same verify-from-source rule applies wherever the grid drives a commitment. A "breakfast included" that means a paid buffet is annoying; a step-free claim that fails is a broken promise to a teammate. Where the page is ambiguous, the right output is "unconfirmed, call the property".

What happens after the grid arrives

Ten minutes of human work.

Post the grid in the team channel, let the two people with strong flight opinions claim their options, pick the hotel scenario, and book it yourself in the same session where the searches left the routes warm. Money-moving actions pause on an approval card anyway, and Ask Always in Settings → AI permissions forces a pause on everything.

The follow-through is more small prompts: "collect everyone's booking confirmations from email into one itinerary doc" is the same sweep pattern as invoice collection, and those confirmations feed next month's expense pass. Calendar holds, a venue-day agenda and a packing note are each one line once the grid is settled.

Recheck before anyone books

Recheck the two prices you are about to commit to.

Flight prices move between the grid's snapshot and your click, and the volatility notes tell you which rows to re-verify first. Then check the arrival constraint: a 21:55 arrival under a no-landings-after-22:00 rule is technically compliant and practically a gamble.

And ask the team. The grid optimizes the constraints people stated, and someone always holds an unstated one, a childcare handoff or a wish to arrive a day early, which surfaces the moment options become concrete. The grid makes that conversation ten minutes instead of two days. The operations teams page covers more of this shape.

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide

Frequently asked questions

It does the search-and-tabulate half in full: per-person flight options under stated constraints, hotels checked against real requirements, and total cost per scenario, all read from booking sites in your logged-in session. You pick and you book.

Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents

Experience Strawberry for free

Download

Trusted by fast-growing companies worldwide