RetainerTSP-RET-01

The system your operation runs on,with somebody responsible for it.

We take over one internal system: fixes, small changes, backups, monitoring, and the call when it breaks at eight at night. One fixed monthly fee.

₹40,000per month

All prices exclusive of 18% GST. GST invoice issued against every payment.

  • Minimum term 3 months, then month to month.
The gap

Somebody built it, then left.

The system works. It has worked for two years. But the person who wrote it is gone, nothing has been touched since handover, and every small change now needs a quote, a wait and an argument.

  • A field on a form needs renaming. It takes three weeks and a purchase order.
  • The freelancer who built it replies on WhatsApp when he feels like it.
  • Nobody has checked whether the backups restore. Nobody has tried.
  • A certificate expired on a Sunday and the plant ran on paper until Tuesday.
  • Your ops head has a list of eleven small improvements, and none of them are worth a fresh quote.
What you get

A named engineer who knows your system.

Not a ticket queue. The same two people every month, who have read your code and sat on your floor.

  • A named engineer and a backup engineer, both onboarded onto your codebase
  • Bug fixes inside the response window on this tier, clocked from your message
  • Small changes and new fields, shipped in the month they are asked for
  • Nightly backups with a restore actually tested once a quarter
  • Uptime and error monitoring, alerting us before your floor notices
  • Dependency and security patching across the framework, database and server
  • One WhatsApp group with your ops head, our engineer and nobody else
  • A monthly hour statement showing where every hour went
  • A short written handover pack, updated as the system changes
Engineering hours
25 per month
Modules covered
1 live module
Support response
next business day
Bug fix turnaround
48 hours
Minimum term
3 months
How it runs

One takeover week, then a monthly rhythm.

The first week is us learning your system. Every month after that runs the same way, so your team always knows when things happen.

  1. Week 1 — Takeover

    We read the code, run it ourselves, and write down what is broken or undocumented. You hand over repository access, server logins and whatever notes exist.

  2. Week 2 — Stabilise

    We fix what the takeover found: dead backups, expired certificates, missing monitoring. This comes out of your first month of hours, before any new work starts.

  3. Every month — The cycle

    Requests come in through the month. Bugs get picked up as they land. Small changes are batched into two releases, mid-month and month-end.

  4. Every month — The statement

    On the first working day you get last month itemised, plus a short note on what is worth doing next.

Fit

Who should take this.

Take this if

  • You run one internal system that the operation genuinely depends on
  • It was built by somebody who is no longer available to you
  • Your change requests are small and constant, not big and rare
  • You want a fixed monthly number in the budget instead of a quote every time
  • You need one person to call when the screen goes white at shift change

Skip this if

  • Nothing is built yet, so there is nothing to maintain. Take the Operations Audit first.
  • You run three or more systems that have to talk to each other. That is the Partner retainer, and this tier will run out of hours by week three.
  • You want a new system built from zero. Buy the build, then put it on this retainer afterwards.
  • You want engineers seated in your office on your attendance system. Hire them directly, or use a staffing agency.
  • The system is a licensed product from another vendor and you cannot give us the source. We can only maintain code we are allowed to read.
Pricing

What it costs, and what moves it.

One monthly fee, one system, a fixed block of hours held for you. Billed monthly in advance, with a minimum term so the takeover week is worth doing properly.

₹40,000per month

All prices exclusive of 18% GST. GST invoice issued against every payment.

  • Minimum term 3 months, then month to month.

What moves the price

  • A second or third system on the same retainer, which moves you to the Partner tier
  • On-premise servers we can only reach through a plant VPN or a site visit
  • A framework or database outside our usual stack, which adds ramp-up in month one
  • Response windows tighter than this tier carries

Included

  • A named engineer, a backup engineer and the monthly block of hours
  • Bug fixes, small changes, patching, monitoring and backups
  • The monthly hour statement and release notes
  • A GST invoice raised on the first working day of each month

Quoted separately

  • A new module or a rewrite that does not fit inside the monthly hours
  • Cloud hosting, SMS, WhatsApp and payment gateway charges, billed at cost
  • Third-party licences bought in your name
  • On-site visits outside Gujarat and the Mumbai region
Questions

Before you ask.

What changes the price?

Three things: how many systems sit under the retainer, where the servers live, and how fast you need us to answer. One system on infrastructure we can reach is the standard tier. A plant server behind your VPN, or a stack we have never worked in, adds ramp-up in the first month. We quote that before we start, never after.

How does a month actually run?

You raise everything in one WhatsApp group. Bugs get picked up as they land, inside the response window on this tier. Small changes are batched into two releases, mid-month and month-end, so your floor staff learn a screen twice a month at most. On the first working day you get an itemised statement of where the hours went.

What happens to hours we do not use?

You get a monthly statement showing where the hours went, line by line. How unused hours carry is written into your agreement before you sign, so there is no argument about it later. If two months in a row finish well under the block, we say so and suggest you drop scope or add a system. We do not invent work to fill the sheet.

What do you need from us?

One person who can approve a change without calling a meeting. Repository access, server logins and any documentation that exists, even if it is a WhatsApp thread. A staging environment, or permission to build one. And somebody who will confirm a fix works on the floor, because we cannot test a weighbridge from a laptop.

Who owns the code, and what happens if we stop?

You own the code, the database and the servers from day one. We hold no licence over any of it and nothing is locked to us. The minimum term is three months, and the notice period after that is set in your agreement. On exit you get the handover pack, every credential, and a call with whoever takes over.

Do you invoice with GST?

Yes. We are GST registered and every month gets a proper tax invoice against our GSTIN, raised on the first working day. Every price on this page is exclusive of 18% GST. Billing is monthly in advance, by bank transfer or UPI against the invoice. Hosting and SMS charges we pay for you are billed at cost, with receipts.

Ready when you are

Your system should outlive the person who built it.

Send a message saying what the system does and what it was built in. We will tell you within a day whether we can take it over.