Output / 01

Raven Tours

Aurora-tour operator out of Yellowknife.

In build · launches July 2026
Aurora over a frozen lake near Yellowknife
The problem

Elizabeth and James run Raven Tours out of Yellowknife, NT. Bookings, manifests, crew schedules — for years all of it lived in shared spreadsheets that worked right up until someone needed to know which row was current. The fix wasn't to throw the spreadsheet out. It was to put a real system underneath it, so the sheet stopped carrying the whole operation.

The system
intakebookingsmanifesttwo-way sync

Staff work a clean dashboard now. The data sits in a system Raven owns — on their own machine, not ours — and syncs both ways with the Google Sheet they already knew. The work still looks the way they're used to; the spreadsheet's just not load-bearing anymore.

Next.js 16local SQLiteself-hostedmagic-link authencrypted at rest
The shape
DashboardThe part Raven sees. Bookings, itineraries, the crew side of a tour day.screens unlock after launch
Folder OSThe part underneath. A folder-as-workspace running on Raven's own box — no rented SaaS account, theirs to keep.screens unlock after launch
Build log
  • First working loop intake → bookings → manifest → edit → Sheet push
  • Two-way sync validated Google Sheet sync, both directions, with a conflict log
  • Auth + encryption magic-link sign-in, data encrypted at rest, deployed
  • Next staff testing on a private network, then public launch in July

🔒 The walkthrough, the real screens, and the numbers go up after Raven’s live in July 2026.

Start a project