Software

Goose Creek CRM

A client-facing itinerary page headed “Brennan Alaska — Three Ships Compared”, with a mountain photo and a letter laying out three cruise options.
The itinerary a client opens from a link. Demo data — the names and trips are not real.

The problem

A small travel agency runs on the same things every small business runs on: a spreadsheet, an inbox, and a folder of documents. Client details live in three places, a passport scan arrives by email and sits there, a final payment date is remembered or it isn’t, and every quote gets rebuilt from scratch.

Agency software exists. I tried PlanitEasy first, and the monthly cost didn’t make sense for an advisor just starting out — that’s the usual shape of it, priced for an agency with staff.

The approach

So I built what the agency needed. Clients and households, groups, bookings, and a day-by-day itinerary builder that produces both a PDF and a link the client opens on their phone.

The parts that matter are the ones that run without me. Reminders go out on their own: final payment at thirty days, seven days, and the day before, a pre-trip note a week out, and a follow-up three days after the client gets home. A log records every send, so a reminder can never go twice.

Client documents — passports, IDs — are encrypted the moment they’re uploaded, with a key that needs no password to seal. A client can send a document while I’m asleep, and reading it takes a passphrase that isn’t stored anywhere, not in the database and not in the code. Old documents purge themselves on a schedule.

The rest is the unglamorous half: a ledger with recurring entries, email templates with a log of what was sent, an audit trail of who changed what, and intake and payment authorization forms a client fills in from a link.

The outcome

It’s been the agency’s daily system since August 2026. Before that, bookings and payment dates lived in a Google Sheet I had to keep checking, and notes and booking numbers were in Discord threads.

It’s also the honest answer to “can you build something for my business?” I run a business on software I built, and I use it every week, which means I live with every decision in it.

The bookings list in the CRM: trips with travellers, departure dates, status badges, totals and commission.
Every booking with its status, total, and commission. Demo data.
A day-by-day itinerary view for a sixteen-night repositioning cruise, each day showing the ship and port.
The same itinerary day by day, built once and shared as a link or a PDF.
A new client registration form asking for traveller name, personal details and contact information.
The intake form a new client fills in from a link, straight into the database.

Built, hosted, and maintained by me, for my own travel agency. The screenshots are from a demo instance with sample data.

See more work Start a project About this service