Management · Terrava
How could my accommodation look?
Explore the design, the rooms and the enquiry entry. Fictional website: no messages or live availability.
Explore this fictional website Assess whether this scope fitsFor rural stays with an identity of their own
Your rural stay, from website to an enquiry with context.
Show what makes your stay special and explore how to review an enquiry before replying. Start with a website or management according to your needs, with guided implementation and an agreed scope.
Assessment: an on-screen plan recommendation, without contact details. Demo: fictional data, no live bookings or messages.
Request a conversation
Management · Terrava
What does this enquiry need?
Compare dates and an alternative before replying. Fictional data: no replies or real bookings.
Inspect the sample enquiry Assess this management needThe journey of a rural stay booking
From discovering your story to preparing the arrival.
One flow, with human decisions and context that stays intact.
Illustrative workflow for your operation
Starting plan · ManagementHuman supervision
- 01Attraction
They discover you
Story, imagery and SEO turn interest into intent.
- Input
- Search or referral
- Output
- Qualified visit
- 02Enquiry
They ask about a stay
Dates, group and needs arrive together.
- Input
- Direct form
- Output
- Structured request
- 03Human decision
You review and propose
Check the case and offer an alternative when needed.
No fit → another stay or date- Input
- Context and calendar
- Output
- Clear proposal
- 04Follow-up
You confirm the next step
The conversation keeps decisions and ownership.
- Input
- Accepted reply
- Output
- Simulated booking
- 05Operations
You prepare the arrival
Guest, property and tasks share the same context.
- Input
- Agreed details
- Output
- Stay prepared
Illustrative resultDirect relationship · context through the stay
01
Logic2B configuresBrand, content, permissions and agreed flow.
02
You stay in controlAvailability, alternatives and confirmation need human judgement.
03
Demo boundaryNo live payments, inventory or channels.
Main flow Human decision Requires real integration
A managed service, with people behind it
We set it up with you. We stay alongside you.
Logic2B adapts and configures everything agreed in scope to fit the way your business actually works. Our job is to help you get value from it—not simply hand over access.
Tell us how you work- 01
We understand your operation
We follow a real booking, identify the friction that costs you most and agree what should stay, change or connect.
- 02
We configure it for you
We prepare your website, content and workspaces, and review the result with you before launch.
- 03
We stay involved after launch
Hosting, security, technical maintenance and base support are part of the service. We review how it is working and scope improvements when the business needs them.
Verifiable status
Explore the features for your accommodation.
“Visible in the demo” never means “active in production”. Every capability keeps its evidence, status and boundary in view.
View features and demo availability
Modular brand website
Design, content and SEO foundations adaptable to the stay.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Responsive editorial website with content and navigation for a fictitious brand.
Boundary: It collects no enquiries, queries no inventory and includes no workspace or live editing.
Email enquiries
Visual representation of the context a property could receive in a direct enquiry.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Three fictitious enquiries show the context an email could contain and thirteen delivery conditions that remain unvalidated.
Boundary: It only changes an in-memory preview and retains 0/13 validated conditions: it collects no personal data, sends no email, does not query or hold inventory and creates no booking; reloading restores the fixture.
Enquiries and bookings
Represents an enquiry and its alternative with shared context.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Preloaded fictitious case that keeps context and compares an alternative in read-only mode.
Boundary: It does not create, convert or confirm bookings and sends no communication.
Planning and rates
Represents stays, units, guests and pricing in a shared calendar.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Read-only fictitious calendar with units, stays and a prepared alternative.
Boundary: It changes no inventory or rates and connects no PMS, availability or payments.
Guests and arrivals
Fictitious stay context available to prepare an arrival.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Read-only fictitious table with two sample guests, source and status.
Boundary: It creates no profile, reports no traveller, stores no visitor data and sends no communication.
Supervised website editor
Visual editing of a fictitious draft with local human approval.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Terrava lets users edit a fictitious headline, discard the draft, approve a local preview only from Direction and review twelve unvalidated publication conditions.
Boundary: State only lasts for the visit and local approval validates 0/12 conditions: there is no CMS, repository, deployment, provider or HTTP write, and reloading restores the fixture.
Basic reports
Booking, occupancy and revenue reading with sample data.
Fictitious visual representation; it does not imply live activation.
What is evidenced: Visual reading of occupancy and revenue from a sample dataset.
Boundary: It uses no live accounting, payment or operational data.
Guide for this journey
Keep context from enquiry to arrival.
Reservations and reception clarifies sources, minimum data, exceptions and actions that still need authorisation.
Website and style
Terrava Collection
Eight homes, one enquiry and an alternative that keeps its context.
Management
Sample enquiry and alternative. The demo confirms no booking and prepares no real stay.
Explore the design →Questions from rural stays
Resolve the boundary before changing tools.
Do I need a booking engine to start?
Not necessarily. If you need to explain the stay better and receive direct enquiries, Basic may be enough. A booking engine or connected management is considered only when the real scope justifies it.
Can I keep the platforms I already use?
Yes. The project does not assume you should abandon a channel that works. We review the role of each platform and the relationship you want to regain under your brand.
Does it work for one rural stay?
Yes. Size helps scope implementation, while capabilities determine the plan. One stay may start with a website and enquiries; a collection may need planning and management.
A recommendation before a proposal
See where rural stays should start.
The assessment uses capabilities; size only helps scope implementation.
Start the assessment →