RetainerTSP-RET-02

Your internal systems, one team,and a roadmap somebody owns.

We run your internal systems together: fixes, small changes, the integrations between them, and a quarterly roadmap you sign off before it starts.

₹85,000per month

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

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

Every tool works. Together they do not.

You never planned this. You bought one tool, built a second, and inherited a third when the new plant opened. Each one works on its own. None of them agree on what a customer is, and nobody in the building owns the whole picture.

  • Dispatch data gets entered in the ERP, then again in the transport sheet, because the two were built two years apart.
  • Your ops head can name eleven improvements and cannot get a straight answer on which is a week and which is a quarter.
  • Three vendors, three response times, and every bug starts with an argument about whose bug it is.
  • The monthly MIS is one person merging four exports into one Excel file on the last night.
  • Changing the invoice format means changing it in two systems, and someone always forgets the second.
What you get

One team across all of it, and a plan you signed.

A small team that holds every system you put under the retainer, and the roadmap that decides what gets built next quarter.

  • A two-person engineering team with a named lead, plus design and QA hours drawn from the same block
  • A written quarterly roadmap, agreed with you before the quarter starts and reviewed at the end of it
  • A fixed monthly release train with a cut-off date your team can plan around
  • Integration work between the systems in scope, including the ones we did not build
  • Bug fixes on the tighter response window this tier carries
  • One reporting layer, so month-end stops being an Excel merge
  • Uptime, error and backup monitoring across every system in scope
  • A monthly hour statement split by system, showing which one eats the budget
  • A quarterly review call with whoever signs off, on your floor or on video
  • One WhatsApp group and one escalation number, not three vendor threads
Engineering hours
60 per month
Modules covered
3 live modules
Support response
same day
Bug fix turnaround
24 hours
Minimum term
3 months
How it runs

Two weeks to take over, then a quarterly rhythm.

Onboarding is longer here because there is more than one system to learn. After that the month has a shape and the quarter has a plan.

  1. Weeks 1–2 — Takeover

    We read every system in scope, run each one, and write down what is broken, undocumented or held together by a single person. You get that in writing before anything else starts.

  2. Week 3 — The first roadmap

    We rank what the takeover found against what your ops head has been asking for. You approve the quarter in writing before we build any of it.

  3. Every month — Release train

    Requests arrive through the month. Bugs get fixed as they land. Everything else ships on the release date, so your floor learns a screen once a month.

  4. Every quarter — Review and re-plan

    We show what shipped, what slipped and where the hours went. Then we agree the next quarter, in writing, before it begins.

Fit

Who should take this.

Take this if

  • You run more than one internal system and they need to know about each other
  • Change requests arrive faster than any single engineer can absorb
  • You want a quarterly plan you can put in front of a board before the quarter starts
  • Your MIS is assembled by hand every month and you want the assembly to stop
  • You are done managing separate vendors who blame each other

Skip this if

  • You run one system and your change list is short. Take the Operator retainer and keep the difference.
  • Software is now the operation and you need people in your daily standup. That is the Embedded Team tier.
  • You want a large new system built from zero. Buy that as a build, then bring it here to be run.
  • You cannot give one person authority to approve the roadmap. The quarter will stall in committee and you will pay for hours that sit waiting.
  • You want bodies on seats billed by the hour. A staffing agency does that cheaper than we ever will.
Pricing

What it costs, and what moves it.

One monthly fee across every system in scope, with the hours pooled, not split into separate vendor budgets. Billed monthly in advance.

₹85,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

  • More systems in scope than the tier carries
  • A system we cannot get source code for, which we can only support from the outside
  • Integrations against a vendor product whose API is paid or rate-limited
  • On-premise servers reachable only from inside your plant network
  • Response windows tighter than this tier, which point you at the Embedded Team

Included

  • The named lead, the engineering team and the pooled monthly hours
  • Fixes, changes, integration work, patching, monitoring and backups across every system in scope
  • The quarterly roadmap document and the quarterly review call
  • The monthly hour statement, split by system
  • A GST invoice raised on the first working day of each month

Quoted separately

  • A new system built from scratch, quoted as a build and then folded into the retainer
  • Data migration out of a system you are retiring
  • Cloud hosting, SMS, WhatsApp and payment gateway charges, billed at cost
  • Third-party licences bought in your name
  • On-site work outside Gujarat and the Mumbai region
Questions

Before you ask.

What changes the price?

Scope and access. How many systems sit inside the retainer, whether we can get at the source code, and where the servers live. Three systems on infrastructure we can reach is the standard tier. A fourth system, or a plant server we can only touch through your VPN, gets quoted before the quarter starts.

How does a month run?

Bugs are picked up as they land, inside the response window this tier carries. Everything else goes into the release train and ships on a fixed date each month, so your floor is trained once rather than every week. Requests arrive in one group chat. On the first working day you get an hour statement split by system.

What happens to hours we do not use?

Hours are pooled across every system in scope, so a heavy month on the ERP borrows from a quiet month on the dashboard. How unused hours carry is written into your agreement before you sign. You get a monthly statement showing where they went. If two quarters in a row finish well under the block, we will tell you to move down a tier.

What do you need from us?

One person with authority to approve the quarterly roadmap without convening a committee. Source access and server logins for every system in scope, and a staging environment for each. And one real user per system who will test a release before it reaches the floor, because we cannot verify a dispatch flow from a laptop.

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

You own every repository, database and server from day one, including work we do on systems we did not build. The minimum term is three months, and the notice period after that is set in your agreement. On exit you get the roadmap document, the handover pack, every credential, and a call with whoever takes over.

Do you invoice with GST?

Yes. We are GST registered and each 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. Hosting, SMS and gateway charges we pay on your behalf appear separately, at cost, with receipts.

Ready when you are

One team, one plan, one number in the budget.

Send a message listing the systems you run and who built each one. We will tell you within a day whether they fit under a single retainer.