Three transparent starting points for one restaurant. Monthly pricing and launch are visible; providers, migration and custom integrations are quoted separately.
Intelligence and automation are demonstrative: there is no external model, charge or autonomous action.
Prices exclude VAT, per restaurant. No Logic2B booking commission. Payment provider fees, messaging, migration and custom integrations are quoted separately. Six-month minimum term for Basic; other terms are agreed in the proposal.
Try the demos with fictional data. A working restaurant service requires an agreed implementation.
Functional ladder
Compare what you need.
Each plan adds to the previous one. Start with your website and expand later.
CapabilityStarts inEvidence
01Brand and owned websiteBasicBrasca website, menu and enquiry journey
02Booking and availabilityManagementVedra widget and shared booking state
03Floor, waitlist and groupsManagementVedra service, floor plan and group journey
04Events, deposits and private hireIntelligentSolane shared inventory and simulated commercial rules
05Explainable decision supportIntelligentSolane deterministic reports and visible factors
Getting started
Launching, caring and improving are different jobs.
We review setup, support and any separately quoted work with you.
Launching, caring and improving are different jobs.
01
Launch services
Turning a demo into an owned system requires context, configuration and shared validation.
Inventory of data, channels, domain, providers and owners
Configuration, agreed migration and team testing
Publication, handover and acceptance criteria
02
Maintenance and support
Agreeing who handles incidents, what is monitored and how updates work avoids unclear dependency.
Agreed support channel, hours and priority
Technical maintenance and compatibility review
Backups, exports and continuity according to scope
03
Development and improvements
New rules, views or connections are prioritised with operational evidence, not as implied promises.
Shared backlog and verifiable objective
Estimate and approval before development
Testing, documentation and handover for each change
Shared responsibility
What each party needs to bring.
Restaurant
Business rules, content and authorised users
Ownership or authorised access to domain, DNS and provider accounts
Validation of data, privacy basis, payment rules and acceptance
Logic2B
Discovery, configuration and agreed implementation
Technical documentation, testing and handover
Maintenance and support only within the approved scope
Defined per proposal
Migration volume and historical data
Payment, POS, messaging or other integrations
Timeline, service level, maintenance, price and exit support
Inspect before deciding
Find your starting point.
Let’s talk
More time for your guests.
Tell us how you take bookings. We’ll help you find a simpler way to run your day.
