Discuss

04 / Software maintenance & product improvement

Product support. Keep moving forward.

We take on existing websites, services and apps. Understand unfamiliar code, fix problems and give product development a clear rhythm again.

  • Technical maintenance
  • Product improvements
  • Supplier handover
Discuss my projectExplore scenarios
The project journeyClick or turn the cube
PROJECT STAGES01 / 04
Rotate the cube.
Click the cube or an arrow.
01 / Discover

Review the code, infrastructure and current problems.

  • Understand the code first
  • Agree on priorities
  • Show the impact of changes

01 / Scenarios

What is holding the product back?

An existing product has a history. Start there and choose the right format, from a single fix to ongoing development.

Team handoverBugs & performanceNew features

Illustrative workflow / 01

The product is here. The team is gone.

The developer has left, documentation is incomplete and new requests keep coming. You need to understand the system and its risks.

  1. Inventory

    List repositories, environments, services and required access.

  2. Understand

    Check project setup, dependencies and critical user journeys.

  3. Take over

    Agree on handover, priority work and day-to-day communication.

What changes

A clear picture of the product and a way to move forward.

How to assess value

Reproducible setup · risk map · agreed plan

Illustrative workflow / 02

Users find the bugs first.

A payment fails, a screen loads slowly or the latest update breaks a familiar workflow.

  1. Reproduce

    Gather symptoms, logs and the conditions behind the problem.

  2. Fix

    Find the cause and prepare a change that accounts for related parts of the product.

  3. Verify

    Check the fix, add relevant tests and plan release with a rollback option.

What changes

The issue is resolved and easier to detect if it returns.

How to assess value

Issue recurrence · response time · core journey success

Illustrative workflow / 03

The ideas grow. Releases do not.

Features keep slipping, requests are mixed with bugs and no one knows what the next release will contain.

  1. Prioritise

    Separate defects from improvements and agree on scope and capacity.

  2. Build

    Work through the change, implement it and share progress.

  3. Release

    Check related workflows, prepare the release and record the next priorities.

What changes

An agreed scope for the next release and visible progress.

How to assess value

Completed priorities · release quality · user feedback

02 / The deliverables

More stable today. More capable tomorrow.

Solve current problems and create a foundation for the next changes.

  1. An informed starting point

    Components, known limitations and risks prioritised by their business impact.

  2. A near-term plan

    What to fix first, what to improve next and the expected outcome of each stage.

  3. Controlled changes

    A process for requests, review, acceptance and releases.

  4. Clear support terms

    Working hours, communication, response expectations and capacity agreed before starting.

03 / An easier place to start

Get to know what already works.

Show us the product and the main problem. We review the code and infrastructure, then suggest a one-off change or an ongoing arrangement.

Discuss my project

For our first conversation

  • A link to the product
  • What is blocking users or the team
  • Known technologies and access arrangements

What happens next

A condition assessment, priorities and a proposed working format. Diagnostic costs are agreed first.

Cost depends on code condition, change complexity, workload and incident response requirements.

04 / Questions

Before we begin

Budget, data and the details worth discussing early.

Will we need a complete rewrite?

That cannot be decided from a description alone. We first review the code and constraints, then compare targeted improvements and rework in terms of cost and risk, including what can be retained.

Do you offer 24/7 support or an SLA?

Working hours, response times and escalation are agreed separately. Round-the-clock coverage is not included by default. Availability of your required setup is confirmed before signing.

Can you work on an AI-built prototype?

Yes, starting with a review of the code, access controls, data handling, dependencies and core workflows. We then plan the work needed to turn it into a usable product.

How do we hand over a website or app from another supplier?

Inventory repositories, environments, domains and third-party services. Confirm who can deploy and how to verify a restore from backup. A first step can focus on one priority issue and a plan for the rest of the handover.

What affects the cost of maintenance?

Code condition, integrations, response requirements and the volume of recurring work. A one-off change can be scoped separately. If you need an SLA, agree on incident response terms before work begins.

What should we prepare for a first estimate?

Share the product link, known issues and examples of expected behaviour. For a specific bug, include reproduction steps and what changed recently. Discuss access separately.

Already have a prototype? Explore project improvement

Good projects
start with hello.

Tell us a little about your project.
We’ll figure out the rest together.

Discuss a project
A QUICK INTRODUCTION

What would you
like to build?

Leave your contact details and tell us about your project.

Choose a service
What do you need?
Add a budget, deadline or link Optional +

Demo: nothing is sent. Please use fictional details.