FairwayPal is built for the person who always ends up planning the golf trip.
The product focuses on one practical job: turn a messy golf-weekend conversation into a plan people can react to quickly, including the part of the trip that matters to non-golfing partners.
What the product is trying to solve
Most group golf trips break down in the same place: one organiser carries the logistics, the group reacts late, and partner plans get treated as an afterthought.
FairwayPal is meant to reduce that admin load by structuring the trip early, showing golf and partner plans side by side, and making review simpler before anyone starts booking.
What is live right now
- A public landing page that explains the product promise clearly
- A five-step planning flow for destination, dates, group size, budget, and vibe
- Metadata routes and deployment wiring for a production Next.js app
- Reusable affiliate surfaces that can later support hotels, flights, and partner activities
What comes next
- Generate a real itinerary from the planner input instead of ending at a structured brief
- Persist trips so organisers can return, share, and revise
- Add voting, comments, and conflict resolution for the group
- Layer in live partner and booking recommendations once destination data is ready
The current site is the first public product surface, not a generic starter. It explains the offer, captures the planning inputs, and sets up the next stage of itinerary generation.
FairwayPal is being shaped as a practical planning layer first. The point is not to publish generic travel content; the point is to help a real organiser get a group aligned faster.