Purchase, growth and control
Owner guide
Decisions worth closing before starting: scope, assets, responsibilities, support and exit.
- This guide is for
- Owners, general managers and investment approvers
- Expected outcome
- The proposal can be compared by outcome, dependency and responsibility, not just by screens.
Choose a starting point
Basic, Management and Intelligent are three commercial scopes; growth does not require rebuilding the identity.
- 1.1
Define the bottleneck: acquisition, coordination or deciding with more context.
- 1.2
Open the associated demo and compare the journey with the team that will use it.
- 1.3
Request a proposal separating launch, maintenance, improvements and integrations.
Keep control of assets
Domain, accounts and data should have understandable ownership from day one.
- 2.1
Confirm who owns the domain, DNS, email and provider accounts.
- 2.2
Agree administrative access, backups and data-export format.
- 2.3
Document which materials or licences the restaurant can reuse at the end.
Approve support and exit
The relationship is safer when maintenance and termination are described before they are needed.
- 3.1
Agree channel, hours, priority, maintenance and each party’s owners.
- 3.2
Define how an export is delivered and what happens to data on closure.
- 3.3
Do not assume a price, SLA or integration absent from the approved proposal.
Working rule
The restaurant owns business decisions and approvals. Logic2B owns only the implementation and service explicitly agreed in the proposal.
Proposal-dependent
