Odeva № 026 Direct-booking setup
Vol. II Edition 21.05 Goes, NL
Founding partners wanted in Zeeland

Direct
bookings
without the spreadsheet
work.

app.odeva.app / dashboard
FIG. 01 — booking admin preview
FIG. 01 — Product preview Dashboard • Planning board • Reservation • Payments 00:00 / 01:32
Direct bookings from your website Built in Zeeland Mollie Stripe Guest confirmations Reservation admin Tourist tax reporting Live availability Mobile-friendly booking flow Founding-partner pricing Case study only if it works Direct bookings from your website Built in Zeeland Mollie Stripe Guest confirmations Reservation admin Tourist tax reporting Live availability Mobile-friendly booking flow Founding-partner pricing Case study only if it works
§ 01 The setup, front to back Four screens · one direct-booking flow

Connect the parts guests already touch.

§ 01 · 01 — Dashboard

See the booking day clearly.

Arrivals, departures, current guests, unconfirmed bookings, and recent payments in one place instead of split across inboxes and spreadsheets.

Answers — arrivals / departures / unconfirmed / paid Live data — updates as bookings land Owner-friendly — opens fast on desktop or phone
§ 01 · 02 — Planning board

Availability that does not live in your head.

See units and dates at once. Move a booking, block a stay, and keep the website flow aligned with the admin view.

Drag & drop — move a booking, availability follows Manual override — block maintenance or owner stays quickly Multi-unit rows — rooms, pitches, lodges, cottages in one view
§ 01 · 03 — Reservation

One reservation record, not five notes.

Guest details, dates, unit, payment status, confirmation history, and tax-relevant data stay attached to the booking.

Guest — contact, stay, preferences Money — deposit, balance, payment status Actions — confirm, message, invoice, check in
§ 01 · 04 — Actions

The next step is right there.

Stay details, payment status, guests, and quick actions sit on the same reservation screen. Add an accommodation or check the balance without losing context.

Status — checked in and paid at a glance Balance — subtotal, costs, total, paid amount Actions — add accommodation from the reservation
§ 01 · 01 — Dashboard
§ 01 · 02 — Planning board
§ 01 · 03 — Reservation
§ 01 · 04 — Actions
§ 02 A booking flow, not a software pitch Website, payments, emails, admin, tax

Replaces the manual steps after a guest says yes.

The first customer does not need an enterprise PMS migration. They need the direct-booking path to stop leaking work.

Availability RoomRaccoon Back-and-forth
Pricing Airbnb Needs explaining
Payments Separate processor Manual checking
Guest email Mailerlite Copy-paste
Reservation list Separate portal Always stale
Tourist tax Excel Rebuilt later
Setup DIY plugins Your weekends
Odeva Connects the flow. One setup. Builder-led.

Founding partners get the builder, not a helpdesk.

We start with a short audit of your current booking process. If Odeva can replace enough manual work, we configure the direct-booking setup with you.

  1. 01 Website booking flow for direct demand Founding partner
  2. 02 Live availability for roughly 3-30 bookable units Founding partner
  3. 03 Payments through Mollie or Stripe Founding partner
  4. 04 Guest confirmations based on reservation data Founding partner
  5. 05 Simple reservation admin for day-to-day work Founding partner
  6. 06 Tourist tax reporting data kept clean Founding partner
  7. 07 Case study only published if the setup works Founding partner
Make direct bookings
feel boringly connected.
— The first-customer wedge
§ 03 Practical questions Before we call it a fit

Questions, answered.

Q.01 What is Odeva?
Odeva is a direct-booking setup for small accommodations. It connects the website booking flow, payments, guest confirmations, reservation admin, and tourist tax reporting so the owner is not rebuilding the same booking in five places.
Q.02 What stage are you at?
The reservation admin, payment foundation, tourist tax tooling, and booking-widget foundation are in place. We are looking for a small number of founding partners where the setup can be shaped around a real local workflow.
Q.03 Who is this for?
A Zeeland minicamping, glamping site, small holiday-home cluster, B&B, or camper-pitch operator with roughly 3-30 bookable units and existing direct booking demand.
Q.04 How much does it cost?
Founding partners get reduced pricing after the setup review. The exact package depends on how much of your website booking flow, payments, confirmations, admin, and tax reporting we replace.
Q.05 Do I need to migrate everything first?
No. The first version should replace the highest-friction direct-booking steps. For customer one, a focused website booking flow is better than a full enterprise-style system migration.
Q.06 What integrations do you support?
The founding-partner scope is direct-first: payments via Mollie or Stripe, booking-widget flow, guest confirmations, reservation admin, and tourist tax reporting. Channel sync and larger-park features come later when the base flow is proven.
Q.07 What is the first step?
Start with a short audit. We look at your current website and booking process, then decide whether a founding-partner setup would replace enough manual work to be worth doing.

Start with the booking flow, not a PMS migration.

  • Zeeland-first local operators before generic SaaS
  • 3-30 units small enough for hands-on setup
  • Direct demand website bookings before channels
  • Case study optional only if the result is real
Start setup review No credit card. Short audit first.