Support and development

What the project can include

• Availability and error monitoring.
• Backups and updates under an agreed plan.
• Small fixes within the selected allowance.
• A working communication channel, report and development plan.

Scope and timing

The base price covers one system and a limited amount of small fixes. Larger changes and response-time commitments are quoted separately.

Support starts after reviewing the system and access. 24/7 refers to monitoring; response coverage is agreed separately.

Features and timing are confirmed after discovery; the starting price does not include every possible option.

Start with your workflow.

What is in place today? Which response times and support hours do you need?

What we agree before work starts

• The main use case and a result you can verify.
• The data and access needed to connect your existing tools.
• First-release scope, milestones, cost and acceptance criteria.
• Team onboarding, access handover and ongoing support terms.

What to bring to the first conversation

Show us how the task is handled today: an enquiry, a report or a workflow example. List the tools you use and explain where your team loses time. You do not need a technical specification for the first conversation.