Software maintenance and support
Keeping working systems working — including ones built by somebody else.
Kolkata and West Bengal
You own the source code
Support after launch
Software decays even when nobody touches it. Dependencies acquire vulnerabilities, browsers change, payment providers deprecate endpoints, certificates expire. A system that was solid two years ago needs attention to stay that way.
We take on maintenance for systems we built and for systems we inherited. Inherited work starts with an audit, so you get an honest picture of what you have before committing to a support arrangement.
Problems this solves
Dependencies with known vulnerabilities
Libraries left unpatched for years accumulate publicly documented security issues that scanners will find.
The original developer is gone
Systems with no documentation and no handover become risky to change and impossible to extend.
Gradual slowdown
Queries that were fast on launch-day data become the bottleneck once the tables have grown.
Silent breakage
Without monitoring, a failing integration can go unnoticed for weeks until someone reconciles the numbers.
What the work covers
Code audit
An honest assessment of structure, security and what it would cost to maintain.
Security updates
Dependency patching, vulnerability review and configuration hardening.
Bug fixing
Diagnosis and correction with a regression test so it does not return.
Performance work
Query optimisation, indexing, caching and front-end payload reduction.
Enhancements
Small, well-scoped improvements delivered on a predictable cadence.
Monitoring
Uptime, error rates and alerting so failures are noticed by us first.
The maintenance cycle
Maintenance is continuous rather than sequential. Monitoring both begins and ends the loop: it is how issues are found and how fixes are confirmed.
Monitor
Uptime, errors, performance and security alerts.
Identify
Reproduce, diagnose and establish the root cause.
Fix
Correct the cause, not only the symptom.
Test
Regression coverage so the issue cannot silently return.
Deploy
Released through the same pipeline as any change.
Deployment returns to monitoring — a fix is not finished until production confirms it.
What you end up with
Known vulnerabilities patched rather than accumulating
An honest audit before any commitment
Root-cause fixes with regression tests
Performance restored as data grows
Failures noticed by monitoring, not customers
Documentation improved as work proceeds
Technologies we commonly use for this
The stack is chosen per project — from your requirements, your existing systems and who will maintain it afterwards. This list is what we reach for most often, not a fixed answer.
Ways to work together
Model A
Fixed scope, fixed price
The scope is written down in detail before work starts, and the price is fixed against it. Changes are quoted separately as they come up.
Best for: Well-understood projects — a website, a defined module, a rebuild.
Model B
Monthly retained team
An agreed number of developer days each month, directed by your priorities. Scope can move without renegotiating a contract.
Best for: Products that will keep evolving after the first release.
Model C
Phased delivery
The system is split into phases that each ship something usable. Every phase is quoted before it begins.
Best for: Large ERP, SaaS and platform builds where the full scope is big.
Model D
Support and maintenance
Ongoing care for a system that already exists — ours or someone else’s — covering fixes, updates and small enhancements.
Best for: Live systems that need a reliable pair of hands.
Sectors we apply this in
Frequently asked questions
Yes. We start with a code audit so both sides understand the state of the system, then propose a support arrangement based on what we actually find rather than an optimistic assumption.
Typically security updates, bug fixes, monitoring, backups and an allowance of hours for small enhancements. Larger pieces of work are quoted separately so the retainer stays predictable.
Response times are agreed in the support arrangement and matched to how critical the system is. We do not publish a single figure that would be meaningless across very different systems.
Yes, though the audit takes longer. We document as we go, so the situation improves rather than staying dependent on one person’s memory.
Topics people search for
Related services
Cloud Solutions
Hosting designed around what your application actually needs, with the monitoring and backups that make it safe to rely on.
Custom Software Development
Software shaped around the way your business already works, instead of a packaged product you have to reorganise around.
Digital Transformation
Moving a business off paper and spreadsheets without stopping the business to do it.
Web Application Development
Applications that run in the browser, handle real workloads and hold up when several departments depend on them at once.
Talk through your project with a developer
You will speak to someone who writes the software, not a salesperson working from a script. Bring your requirements, or just the problem.