However you like! We pride ourselves on our flexibility.

If you have workflow and project management tools in place, we’ll work with those. If you don’t, we’ll assign a project management tool that suits the scope of your maintenance work. Typically, we use Jira for larger maintenance plans, particularly ones that include significant ongoing application development. Freshdesk is our preferred tool for smaller maintenance plans, especially when our primary role is to offer support.

Retainer options work best for applications which require a fairly consistent amount of month-to-month support.

If your application requires more maintenance from time to time, you can save money by locking in a base-level monthly retainer, at a discounted rate, then covering the work spikes with on-demand maintenance.

If your maintenance needs are minimal and/or infrequent, on-demand support by the hour could be best for you.

That’s up to you. Or, more precisely, up to your application.

A few hours a year might be enough for a small application that is not currently being developed and doesn’t need end-user support. But a complex application which is continually being upgraded to include new features and capabilities will require significantly more maintenance time.

The main variables that determine maintenance requirements are the size and complexity of the application, the amount of ongoing development, and whether you’re looking for us to provide end-user support.

Most likely!

Taking over the maintenance of an application we didn’t help develop is sometimes quite straightforward. It can get more challenging if there’s little or no documentation available, if the original developer is not available to help facilitate the transition, or for other reasons.

But as long as an application is built in one of the languages that we work in, we can almost always help. Reach out and let us take a look, and we’ll put together a plan of attack.