Application maintenance services for live SaaS products, new features included
With our application maintenance services, a team that learns your code first handles fixes, security patches and performance, while new features keep shipping.
2017
Founded
90+
Projects
19
Countries with clients
What you get from application maintenance
Ongoing care and change for a live web or mobile product, including code someone else wrote.
A review before the first fix.
Code, environments, release process and change history, read first, with what we find written down.
Fixes.
The agreed behaviour back, with a test to keep it there.
Updates.
Frameworks, libraries, APIs and security patches, with the features users rely on checked again afterwards.
Reliability and speed.
Slow pages and repeat failures, measured before the change and checked after it.
Improvements and new features.
Small improvements fit the regular flow of work. Larger features are planned and designed as their own piece of work, instead of being squeezed in as tickets.
A priority list you can see and change.
Each request sorted by kind and weighed for impact, with the reasons shown.
Releases with a way back.
Every change gets a test, a review and a release your team can see, and a way back if it misbehaves.
Mobile as well as web.
Operating-system updates, store resubmissions and older app versions kept working with the backend, with each API change tested on the phone and the web.
Who does the work
Engineers who learn the code first, and an account lead who keeps the queue moving. When a fix changes how a workflow behaves, our designers join in, so small improvements stay consistent with the rest of the product.
What we need from you
Access to the code, environments, release process and change history. Agreement on who raises requests and who approves releases.
Where our part stops
We agree at the start which kinds of change we own, so each area has a named owner. Features too large for the regular flow become their own project. Out-of-hours cover and infrastructure management are agreed separately if you need them.
Selected application maintenance work
The products we maintain, Vovisto's platform and the systems of Eagles Security Aruba and Hotel California Aruba, are the closest work to this service, and none has a case page yet. These three show how we change software that people already rely on.

Benchmark Gensuite: one shared control at a time
Customers have long-standing habits in Benchmark Gensuite's established safety and sustainability suite. We proved new shared patterns in coded prototypes its engineers reviewed, then tested them in the scope selector, and the work has continued from there.

Dealpath: one listing action changed, the rest left alone
Our redesign changed Add to pipeline, so people search existing deals before creating another. The other listing actions were left largely as users knew them, and Dealpath's team owned implementation.

OctiFi: a team that grew with the app
OctiFi tested us with one small design pilot. The work grew into onboarding, loan issuance, new features and adapting the app for a second market, each starting from what the team already knew about the product.
Legacy application maintenance: taking over a product someone else built
Older products often carry rules nobody wrote down, and finding them during that first review is part of the job.
From then on, the business rules, integrations, past incidents and the reasons behind key choices go into your code or your wiki. New people get up to speed from it, and so does your own team if you take the work back.
The oldest ticket is rarely the most important one. We weigh how many customers a problem touches, how often it recurs and how urgent any security risk is, then the effort, and whether a quick patch stores up a bigger problem. You see the order and the reasons, and you can change them.
A steady stream of urgent fixes is a signal in itself: the product may be ready for modernising.
Maintenance, warranty support or modernisation: which fits your product?
| Service | What it includes | Best for |
|---|---|---|
| Warranty support | Putting right delivered work that falls short of what was agreed at release | The weeks straight after a release, from whoever built it |
| Application maintenance | Fixes, updates, performance work and features on a live product, in an agreed order | Live products that keep changing and need a team that knows them |
| SaaS & Web Application Development | A large new module planned, designed and built as its own project | Features too big to fit into the regular flow of maintenance |
| Product Modernisation | Redesigning and rebuilding an ageing product one stage at a time | Products where patching costs more each month than it fixes |
What clients say
Three ways to work with us
Not sure which suits you?
Tell us about the product, and we'll suggest one.
Why founders and product teams choose Tcules
Fluent in SaaS
Roles, permissions and data-heavy screens need no explaining to us.
Idea to launch
Bring an idea or your own prototype. Designers lead it through to launch.
Craft people notice
Your product stands out from lookalike software and feels effortless to use.
Evidence before screens
We test your assumptions with real users before they become expensive mistakes.
Seen your problem before
Senior designers who've solved problems like yours lead your product and do the work.
Start small
An optional fixed-price pilot lets you try us first, and ongoing work has no minimum term.

Tell us what's running and who looks after it now
Tell us what's running, what keeps changing and who handles releases now. If the answer is ‘whoever's free’, start there.
Questions about application maintenance
What does application maintenance include?
Fixes, software and security updates, performance and reliability work, small improvements, new features and release management. We agree at the start which of these we own, so each area has a named owner.
Can maintenance include new features?
Yes. Small improvements fit into the regular flow of work, and larger features are planned and designed as their own piece of work, with designers involved where the feature changes a workflow.
How is maintenance different from warranty support?
Warranty support puts right delivered work that falls short of what was agreed at release, usually for a fixed period. Application maintenance is the ongoing care and change a live product needs after that, including work on code someone else wrote.
What does SaaS maintenance cost?
It depends on how much the product changes and which kinds of work we own, so the scope is agreed before any price. How We Work explains how ongoing work and fixed-price pilot projects are set up.