Skip to content
2good.dev

What we build

Maintenance and support

Fixes, updates and steady improvements for software you already run. Bug fixes, security and version updates, small features and takeovers of software another team built. Work is agreed in blocks with a clear list of tasks, and you pay after you accept each block.

Talk to usEstimate the hours
Code and a file tree in a code editor

The situation

The developer who built it has moved on

Plenty of businesses run on software that works well enough, yet nobody looks after it. The freelancer who wrote it has taken a full time job, the agency has gone quiet, and every small change feels risky. Meanwhile libraries go out of date, the Android app needs a new target version for the Play Store, and a report has been wrong for months. Maintenance is unglamorous work. Done steadily, it keeps the software safe, keeps users happy and stops small problems turning into a costly rewrite.

2goodThis month's blockAK

This month's block

ItemTypeHoursStatus
Upgrade framework versionUpdate18Done
Report runs slowlyFix9Accepted
Add GSTIN to invoicesFeature12Testing
Login timeout on AndroidFix6In progress
Representative screen with sample data. Client screens stay private.

What we build

Maintenance and support, in practice.

  1. Code review and takeover

    A review of the existing code, hosting and documentation, with a plain written note on what is sound, what is risky and what to fix first.

  2. Bug fixing

    Reported problems reproduced, fixed, tested and released, with a short note on the cause for each one.

  3. Security and version updates

    Frameworks, libraries, servers and mobile SDKs kept on supported versions, including Play Store and App Store target updates.

  4. Small features and improvements

    New reports, extra fields, screen changes and other requests from your team, taken in order of what matters most to you.

  5. Monitoring and backups

    Error tracking, uptime checks and backups that are tested, so problems are seen early and data can be restored.

  6. Documentation and handover notes

    Setup guides, deployment steps and notes on how the system fits together, so your next developer can find their way.

Typical sizes

Roughly how many hours.

Planning sizes only. The real number comes from a signed scope after the first conversation.

  1. 150HOURS

    A single maintenance block

    A code review, the most urgent fixes and version updates for one app or system. Roughly INR 29,850 before tax at INR 199 an hour.

  2. 150TO200HOURS

    A takeover with a backlog of work

    Taking over software another team built, fixing known problems and adding a few small features. Roughly INR 29,850 to INR 39,800 before tax.

  3. 200TO400HOURS

    Ongoing improvement across several systems

    A web app, a mobile app and their backend looked after together, with updates, fixes and planned improvements. Roughly INR 39,800 to INR 79,600 before tax.

Turn hours into a total

An example

Illustrative: a Vadodara manufacturer takes back control of its dealer portal

Suppose a manufacturer in Vadodara has a dealer portal and Android app built a few years ago by a freelancer who is no longer available. The first block starts with a code review and a written list of risks, then moves the hosting into the company's own account, updates the app for the current Play Store requirements and fixes the three bugs dealers complain about most. Later blocks take smaller requests from the sales team, each with its own task list and acceptance.

Technology we often use

  • TypeScript
  • JavaScript
  • PHP
  • Laravel
  • Python
  • React
  • React Native
  • MySQL
  • PostgreSQL
  • Docker

Chosen to fit the project and your team, and written into the specification.

Questions

About maintenance and support.

Can you take over code that another team wrote?

Usually, yes. The first step is a review of the code, hosting and access, so the specification is accurate about what can be kept and what needs fixing. You get the findings in writing before larger work is agreed.

How do maintenance blocks work with pay after acceptance?

Each block has an agreed list of tasks and what done means for each one. You test the finished tasks, accept them and then pay. Payment timing and any warranty on fixes are stated in your agreement.

What if something breaks urgently?

How urgent issues are reported and handled, and the response time you can expect, are agreed before each block starts.

Related

Related work and reading

What we buildCustom softwareBusiness software built around how your team already works.What we buildWeb applicationsWeb apps, portals and sites that your customers and staff use daily.What we buildMobile appsAndroid and iOS apps for customers, dealers and field teams.
GuideHanding over code, credentials and documentationA system is fully yours when you can run, change and move it without asking anyone. An Ahmedabad clinic chain shows what a handover should contain, with a checklist to work from.GuideWorking across time zones with an Indian teamA team in India can move your product forward while you sleep, if the handovers are written well. A clear written routine makes that work for London and US teams.ArticleFixed price, time and materials, or pay after acceptanceEach way of buying software puts risk somewhere. Fixed price, time and materials and pay after acceptance compared, with the trade offs for buyer and vendor.

Start with a conversation

Tell us what you want built. We will tell you plainly whether it fits.

The first conversation is free. You get a rough size in hours, the tier that suits the work, and what a first 150 hour block would cover.

Talk to usBook a 30 minute call
Or get a ballpark proposal in two minutes
Two young Indian colleagues working together on a tablet in a modern workspace
Chat with 2good.dev on WhatsApp