Software support

Keep the software you depend on usable as your team, vendors, and business processes change. Start with the issue you’re seeing.

When the software slips

Software support helps businesses maintain and improve applications already in use. It’s for teams that have an issue to diagnose, an update to plan, or a system they want someone to look after on an agreed basis.

A supervisor notices the weekly report leaves out work closed after a recent update. The entries are still there, but the team can’t use the report to plan the week. The first job is to follow an affected record and find where it drops out. That gives us a better starting point than changing the report and hoping.

What support can cover

Fault finding

Work through a problem your users can describe. We look at the affected records, actions, and conditions so we can reproduce the issue and understand what a repair has to fix.

Planned updates

Identify updates that affect the application or the services it relies on. Test the parts of the business that depend on them before agreeing when the change should go live.

Connection repairs

Investigate missing or incorrect information between tools. Work out whether the problem is access, a changed data field, or something earlier in the process, and identify which records need attention.

Practical improvements

Scope changes to a report, screen, or workflow when the current version slows people down. A feature that changes several parts of the application can be planned and quoted as its own project.

How a fix moves

1

Get access and context

Tell us what the application does and which people depend on it. We check access to the relevant code, hosting, and connected services before agreeing what we can support.

2

Record the behavior

Describe what the user did, what they expected, and what happened. We identify whether the issue can be reproduced and how widely it affects the work.

3

Check the correction

Test the change against the task that failed and nearby tasks it could affect. Agree on what a suitable test looks like and who is responsible for approving the release.

4

Close the loop

Tell the people using the system what changed and whether any records need correction. For ongoing support, agree how issues are reported and how planned changes fit around everyday work.

Who needs ongoing care

This service fits a business running an internal tool, customer portal, or app that people rely on. It also suits a team inheriting software after a developer leaves, where the first question is whether the system is in a condition to maintain. Bring whatever documentation and access details you have.

Services that fit

Custom software

Consider a focused replacement if the current application cannot support the work your team needs it to do.

Software integrations

Scope a replacement connection when the one carrying important records between tools has reached its limits.

Software support questions

Can you work on an app someone else built?

Yes, if an assessment shows it’s a fit. We need to understand how it’s hosted, whether we can access the source, and which services it depends on. Sometimes the application needs an initial repair or better documentation before we can set up ongoing coverage.

Can we ask for a single repair?

Yes, you can start by describing the issue you want us to assess. Tell us who sees it, what task is affected, and when it started. We’ll discuss the access we need and whether there’s enough information to scope a specific fix or an investigation first.

How do you decide if a change is safe to release?

We agree on what needs to be checked before the change goes live. That includes reproducing the original issue, exercising the affected workflow, and checking related steps where the change could matter. We also agree on who approves the release and who carries it out.

Are new features included in ongoing support?

Coverage depends on the agreement for your application. A small adjustment and a new feature can have different design and testing needs. We’ll clarify what belongs in regular support and what needs its own scope so you can decide when it makes sense to take it on.

How much does software support cost?

We scope and quote each engagement after a call. The quote depends on the applications covered, the condition of the code, the tools it connects to, and the coverage you need. If an assessment or initial repair is needed, we’ll discuss that work as part of planning.

Tell us what changed

Share the issue, the people it affects, and anything that changed before you noticed it.

Discuss your project