Software maintenance & support

Launch is a milestone.Keep moving from there.

Once people are using your product, the work changes. We help resolve bugs, maintain the application and turn feedback into a sensible plan for what comes next.

See what’s included
Focus
Live applications
Work
Maintenance & improvements
Terms
Agreed to suit your product

Give the live product
the attention it needs.

Real use reveals things a prototype cannot: confusing interactions, uncommon edge cases and new demands on the application. At the same time, dependencies and connected services continue to change. Ongoing support helps you keep the product useful and maintainable.

We agree the support scope, responsibilities and priorities around your application. That can include maintenance of a product we built, or a takeover after reviewing an existing codebase and its deployment setup.

What we can help with

Bug investigation & fixes

Reproduce reported issues, identify their cause and implement fixes with checks around the affected user journeys.

Dependency & platform updates

Review relevant updates and plan changes to dependencies or integrations, considering compatibility and release impact.

Operational improvements

Improve error reporting, release checks and documentation so the application is easier to run and troubleshoot.

A practical next-release plan

Translate user feedback and business priorities into a manageable sequence of improvements and new features.

Maintenance and new features need different decisions

A defect in an agreed feature, a change to an external service and a new product request are different kinds of work. We make those distinctions clear so you can prioritise the budget and understand what is included.

Our product development package includes 30 days of bug fixing after launch. Work beyond that period, new features and any ongoing support arrangement are scoped separately. Support hours, response expectations and operational responsibilities are agreed explicitly; this is not an advertised 24/7 incident service.

How we move it forward

01

Understand the application

Review the code, hosting, known issues and any existing documentation before agreeing support.

02

Agree the priorities

Set the scope, communication arrangements and the order in which maintenance and changes will be handled.

03

Maintain & improve

Deliver the agreed work, verify releases and review the next priorities as the product evolves.

Let’s scope the right next step.

Tell us what the application does, how it is hosted and where you need help. We will propose a suitable maintenance or development scope after reviewing the setup.

Support scoped to your product
Responsibilities and response expectations agreed upfront
From our own portfolio

We build products, too.

Knowlith puts a help centre and support inside a product. We built it in-house, and use its widget on this website so you can talk to us without leaving the page.

Explore our work
Knowlith product website

Your questions, answered.

Can you support software another developer built?

Yes, subject to a review of the application, code access, hosting and dependencies. The review helps us understand the work and agree realistic responsibilities.

What is included after a new product launch?

Our product development package includes 30 days of bug fixing after launch. Ongoing maintenance, new features and further development are scoped separately.

Do you provide round-the-clock support?

We do not advertise 24/7 incident coverage. Support hours, response expectations and responsibilities are agreed as part of the engagement.

Can ongoing work include new features?

Yes. We can plan feature development alongside maintenance, with the scope and priority of each piece of work agreed before it starts.

You might also need

Your next chapter

Show us what you’re building.
Let’s take it from here.

An idea, a working prototype or a product that needs its next step. Tell us where you are and where you want to go.