Support and development
Good software needs care and room to grow.
01 / POSSIBLE SUPPORT SCOPE
Keeping things running. Planning what comes next.
The scope depends on the system’s condition, documentation and the agreed way of working. Not every support service covers all the areas below.
- 01
CMS and component updates
Dependency checks, preparing changes and assessing their effect on the website or application.
- 02
Bug fixes
Reviewing the report, reproducing the problem and fixing it, with tests of agreed scenarios.
- 03
Feature development
New content types, views and tools planned around the existing architecture.
- 04
Technical modernisation
Assessing what holds development back and planning gradual modernisation or migration.
- 05
Performance
Finding bottlenecks and choosing improvements based on observed behaviour, rather than a list of metrics alone.
- 06
Monitoring and security
Within the agreed scope: monitoring, security, backups, recovery checks and restoration after a failure, depending on the available infrastructure.
02 / TAKING OVER AN EXISTING PROJECT
First, we understand what is already running.
We begin a website or application handover with access to the code, documentation and necessary environments. We review dependencies, startup procedures and areas needing particular attention. We also clarify responsibility for hosting, backups and other services.
We then propose priorities and an initial scope of work. That may mean updates and fixes or a separate modernisation plan. We do not promise to maintain any solution without reviewing it first.
Explore an application project: Ecotec03 / WORKING ARRANGEMENTS
Clear agreements instead of assumed promises.
Before support begins, we agree scope, availability, how to report issues and response arrangements. Everyone then knows who handles each task and how the work will be planned.
- 01
Assessment and priorities
We review technical condition and needs, separating issues requiring action from planned improvements.
- 02
Agreed scope
We define task reporting, availability, estimates, work approval and the scope of monitoring where needed.
- 03
Changes and review
We implement and check the agreed fixes. We organise further needs into a development plan that can change with your business.
04 / SUPPORT QUESTIONS
Let’s agree responsibilities and how we work.
Does support mean round-the-clock availability?
We agree support scope, availability and response times individually before work begins. We also define how to report problems and which tasks support covers.
What access do you need to take over a project?
We usually need the code repository, documentation and access to the relevant environments. We agree the exact list after an initial review. Permissions should match the agreed work and be shared through an agreed secure channel.
Does a CMS update need testing?
Yes. A version change can affect modules, the theme and custom features. We match testing to the update’s scale and risk. If the existing environment cannot safely support checks, we first agree how testing will be prepared.
Can support include new features?
Yes, but we distinguish keeping the system running from expanding it. We agree priorities and scope so new features are not automatically treated as fixes. A larger modernisation may need a separate research and delivery stage.
THE NEXT GOOD PROJECT STARTS WITH A CONVERSATION.
What can we create together?
↗Have an idea, a challenge or just a question? Let’s start by understanding what you need.
Tell us about your project