Configured for your business
Agree who keeps the system working after launch.
Ongoing support should be as clear as the implementation itself. We define which workflows and systems are covered, how issues are reported, who manages infrastructure and what changes are included.
Discuss a support arrangementWebsite packages, automation implementations and complete business systems are separate offers. Existing package inclusions remain unchanged. Additional integrations, provider fees and ongoing management are included only when stated in your proposal.
How the process works
Illustrative process using fictional data. No messages, payments or live system changes are made.
- Monitoring: agree the checks, alert recipients and review frequency.
- Maintenance: define responsibility for updates, credentials, dependencies and backups.
- Incidents: agree working hours, response targets and escalation; response is not the same as resolution.
- Changes: distinguish fixes within scope from new processes, integrations and feature requests.
- Ownership: document access, exports, supplier accounts and the exit or handover process.
Monitoring: agree the checks, alert recipients and review frequency.
Outside the default scope
This is not an unlimited-development plan or a default 24/7 response promise. Existing Site Care, Store Care, Movelira and Nidomera plan inclusions remain unchanged.
Setup and ongoing management
One-time setup: quoted after scope.
Ongoing management: quoted separately where required or selected.
Software licenses, messaging, AI usage, payment-provider charges and hosting are included only when your proposal explicitly includes them.
Your proposal defines the channels, integrations, users, data migration, handover and support responsibilities. This page describes a solution approach, not an unlimited feature bundle.
Questions before you start
Can I buy one workflow without a full system?
Yes. Individual automation projects are independent offers. We assess the required connections and agree a scope for that workflow.
Are automations included in a website package?
Only where the published package or your written proposal explicitly includes them. The new catalog does not remove existing inclusions or silently add advanced automation to a basic website package.
Do I have to understand the technology?
No. Describe the work, the people involved and the tools you already use. We translate that into a proposed implementation.
Do you only work with n8n?
No. The implementation approach depends on the requirements, available interfaces, ownership model and applicable licenses.
Is monthly support mandatory?
It depends on the chosen deployment and responsibilities. A client-managed handover may use optional support; an operated service needs an agreed ongoing arrangement.
Does a demo show everything included in the price?
No. Demos illustrate journeys and possible scope. Your proposal identifies which features and integrations are delivered.
Tell us what you need to connect.
Describe your process in everyday language. Do not include patient records, identity documents, payment details, passwords or API keys.
Discuss this solutionWebsite packages, automation implementations and complete business systems are separate offers. Existing package inclusions remain unchanged. Additional integrations, provider fees and ongoing management are included only when stated in your proposal.