Software Maintenance and Support Services

Rates set and reviewed by Maciej Nasalski, Head of Commercial Department · Last updated: 5 November 2026 · Reviewed quarterly

Monthly maintenance or hourly support

The Care package is an example of a defined recurring scope, not four standalone hours priced at the hourly card rate. Hosting, licences and third-party services are agreed separately.

Taking over an existing application

You do not need to rebuild an app because its original supplier is leaving. Start by establishing what runs in production, how to reproduce a working build and who owns the code, hosting and deployment accounts.

Request the repository, environment and deployment notes, known issues, monitoring access and the main business flows to check. Agree the initial investigation and handover separately from recurring maintenance. Our software maintenance takeover guide gives the practical handover checklist.

PHP and WordPress security patching

A patch check starts with the PHP runtime and package actually serving your website. Ask your host for the active web PHP version, handler and vendor package or container revision, plus the advisory that confirms the relevant fixes. A version shown in a control panel alone may not identify every running worker or instance.

After an update, check that the website is running the intended package and that important business functions still work. For WordPress, that includes the affected forms, login, checkout or other flows your website uses. Our PHP and WordPress patch-check guide explains the evidence to request from your host.

Want a starting point? Request a free check and share the website URL and any version information your host has supplied. The check helps identify the next step; patching or repair work is scoped separately.

“A patch is only complete when the website is running it and the business functions still work. Ask for evidence of both, not just a message saying the update was installed.”

Bohdan Semenov, Head of Delivery at Powercode Group

How we start maintenance

1. Define the application and the work.

   Identify the product owner, business-critical flows, known issues, priorities and required support window.

2. Establish access and a working baseline.

   Review the repository, environments, release path and recovery arrangements. Separate missing handover work from the recurring scope.

3. Agree the first work package.

   Choose monthly or hourly support, define the included tasks and allowance, and record the approval and release responsibilities.

4. Maintain, check and report.

   Work through the agreed checks and backlog, verify affected flows after changes and keep the product owner informed of open issues.

Relevant experience: engineering inside an existing product

Powercode Group supplied four Full-Stack Engineers to extend CENDAS’s development teams. They worked alongside the client’s engineers within its existing architecture and development processes; CENDAS retained product and technical direction.

The CENDAS case study shows that team-extension engagement. Use the takeover brief to define the separate maintenance and operating responsibilities your application needs.

Software maintenance questions

What do software maintenance services include?

The scope can cover recurring production checks, updates, security patching, incident triage, bug fixes and small improvements. The proposal identifies the application, environments, responsibilities and included work. A takeover first establishes how the existing app is built, tested and released.

How much does software maintenance cost?

The Care package example is USD 550 per month for recurring production checks and four hours of investigation, small fixes, configuration changes and release support. Extra work uses the relevant approved role rate. WordPress/WooCommerce development starts at USD 33/h and PHP/Laravel at USD 36/h. The monthly package example has 30 days’ cancellation notice.

Can you take over software built by another team?

Yes. Start with the repository, build and deployment instructions, environments, access ownership, known issues and business-critical flows. Separate the initial investigation and handover from ongoing maintenance, then agree the responsibilities that transfer.

How quickly will you respond to an incident?

The first reaction is within eight business hours. That means an initial response and triage, rather than a promise that every incident will be resolved within eight hours. Agree the working window and reporting route in the proposal.

Do you maintain PHP and WordPress websites?

Yes. The scope can include PHP runtime and dependency updates, WordPress core and plugin updates, security patching, regression checks and small fixes. For a patch check, provide the website URL and the version or package information available from your host.

Can we book hourly work instead of a monthly package?

Yes. Hourly or ad-hoc work is an alternative to a monthly package. Choose the relevant role from the published rate card and agree the task, hours and access needed. Recurring checks and an included monthly allowance belong to the monthly package example.

Tell us what your app needs

Share the application URL, stack, current supplier or handover situation, and the first issue or change you want to address. Tell us whether you need a free patch check, an hourly task or a recurring maintenance scope.

Compare current developer rates · Cloud and DevOps engineers · Custom software development