DommoLabs.
Back to work
Product Tourism 2024

Sentya

A concierge platform that replaced the spreadsheets, WhatsApp threads, and stray emails running a small tourism operation.

  • StatusLive since 2024
  • ScopeSolo, end-to-end
  • Timeline~6 weeks to v1
  • UseDaily, full ops team
app.sentya.io/inbox
Inbox
14 open
Linnea Bergstrom9:42
Can we arrange a boat transfer for Friday afternoon?
EnquiryArr 14 Jun
Marco and Elena Russo8:10
Thank you for the welcome basket, such a lovely touch.
In stay
Kenji WatanabeYst
Flight pushed to Sunday, updating party of 4.
Rebook
The problem

Six spreadsheets. Three chat threads. By Friday, no one was sure who had promised what.

Bookings lived in a spreadsheet. Guest requests came in over WhatsApp, email, or a phone call someone had to remember to write down. Every handover was a prayer that nothing important had slipped.

What I built

One workspace. A guest, a booking, a message and a task — same object.

Sentya is a single workspace for small tourism operators — from the first enquiry through check-in, concierge requests, and the quiet bits after they leave. The first release was deliberately narrow: one workflow, done properly, instead of ten half-built ones.

Built with
  • Next.js
  • TypeScript
  • Supabase
  • Tailwind
  • Vercel
app.sentya.io/today
Today
Fri 14 Jun
Arriving3
In stay7
Open4
Arriving today
Linnea Bergstrom15:00
Party of 2 - Villa Oleandro - boat from Lipari
Transfer6 wks
Priya and Arun Shah17:30
Party of 2 - Villa Girasole - sunset dinner booked
Henrik Lund19:10
Party of 4 - Villa Azzurra - late arrival
How it works

Three decisions shaped it more than anything else.

1

Every thread, one object.

Enquiries, bookings, and messages collapse into a single thread per guest. The team stops stitching four systems to remember what was promised.

Mobile-first from day one — the people using it are on the dock, not at a desk.

Morning, Giulia
4 threads need you
Linnea B.
Boat - Fri 15:00
Now
Marco and Elena
Thank-you drafted
Priya and Arun
Sunset dinner - Thu
1h
2

Three columns. Never more.

The board is the team's shared nervous system — every request, every handoff, every “who’s got Thursday dinner?” lives in one place. Three design decisions made it actually work.

app.sentya.io/concierge
To do4
Boat transfer - Linnea B.
Fri 15:00
Sunset dinner - Priya and Arun
Thu
Welcome note - Watanabe party
Sun
In flight2
Skipper briefing - fish market stop
Fri AM
Airport pickup - Russo family
Tue 11:20
Done6
Basket delivery - Villa Oleandro
Done
Chef's table - Lund party
Done
1 2 3
  1. 1
    Guest-attached, not free-floating. Every task carries its guest record with it. Context travels with the work.
  2. 2
    Three columns. Always. To do · In flight · Done. Resisting the urge to add “blocked” or “later” was the whole design.
  3. 3
    Ownership is a face, not a dropdown. Avatars on every card. Who owns this is answered before you finish reading.
3

The note lives with the guest.

Handovers used to be voice memos. Now they sit on the guest record, where the next person actually looks.

One fewer system, one fewer place to forget.

app.sentya.io/guests/linnea-b
Evening handover
Giulia to Matteo13 Jun - 19:40
Follow-upFri 15:00
Where it is now

The first thing the team opens every morning since 2024. Replaced six spreadsheets and three chat threads with one workspace. Still shipping.

Status Live · daily use
Used by Full ops team
Cadence New work monthly
§ Stack and specifics for the builders in the room
Role Concept, UX, architecture, build, ops — solo.
Timeline ~6 weeks to v1 · live since 2024
Stack
Next.js 14TypeScriptTailwindSupabasePostgres · RLSEdge functionsResendVercelCloudflare
Access Private beta · NDA on request
Why this stack Supabase RLS let one person safely model multi-tenant data without a bespoke backend. Next.js + Tailwind bought shipping speed without punishing craft. Runs on free tiers at current scale — deliberate, for a tool this size.