Keep it running
Two short training sessions, the safety basics done properly, and one person to call, so what we built keeps working long after launch.
- What it is
- The part after launch: teaching your staff to run what we built, keeping access and backups in order, and a monthly plan with fixed response times and hours for improvements.
- Who it is for
- Any business that now relies on something we built, or that has an automation from elsewhere that nobody quite owns any more.
- What it typically returns
- Staff who run it without calling us, a quarterly check that finds problems before an auditor does, and a monthly note on what was fixed and improved.
Training your team
Short sessions in your office or on video, in Tamil or English, so your staff run it without us.
A system nobody on your team is comfortable with will be quietly worked around within a month. So we train the people who will use it, not only the owner, and we do it in the language they think in. Sessions are short, in your office or on a video call, and built around the real work: the actual WhatsApp orders, the actual month-end report, the actual approval step.
Every session ends with a written guide, one page per task, with screenshots from your own system. New staff learn from the guide. We come back for a refresher when you add a branch or the process changes. Training is part of the roll-out step in how we work, so it is never an extra.
What a session covers
- The three or four things the person will do every day, on real examples
- What to do when something looks wrong, and who to message
- How to approve, correct or reject what the system proposes
- Where the guide lives and how to find the page they need
How it runs
- Ninety minutes at most, never a whole day
- In Tamil or English, whichever the group prefers
- In your office, or on video for other branches
- Two sessions at launch, a refresher when you ask
- Who it is for
- The staff who will use the system every day, and the one person who approves what it does.
- What you receive
- Two short sessions at launch, with real examples
- A written guide, one page per task, with your own screenshots
- A refresher when staff or the process change
- How long
- Two sessions of about ninety minutes in the week of launch. Refreshers as needed.
- How it is priced
- Included in every Sprint and Project. Extra sessions, for new staff or a new branch, come out of the improvement hours in your support plan.
Keeping it safe and compliant
Access controls, backups and India's data protection rules handled, and checked every quarter.
The systems we build touch customer phone numbers, prices, invoices and sometimes health records. That brings three plain duties. Only the right people can get in. A copy exists if something is lost. And the personal details you hold are handled the way India's data protection law now requires.
We set all three up as part of the build. We write down what was done in a short document you can show an auditor, or a large customer who asks. Then, every quarter, we check that it is still true: who has access, whether the backups restore, and whether anything new has crept in.
What we set up
- Access: each person has their own login, and only to what their job needs. When someone leaves, their access goes the same day.
- Backups: a copy of your data every night, kept in a second place in India, and a restore test every quarter so you know the copy works.
- Records: a one-page list of what personal data each system holds, why, and for how long.
- Requests: a way to answer a customer who asks what you hold about them, or asks you to delete it.
- Who it is for
- Any business holding customer phone numbers, addresses, invoices or health records in a system, which is nearly every business.
- What you receive
- Logins and permissions set up per person, and a checklist for when someone leaves
- Nightly backups with a restore test every quarter
- A one-page record of what personal data you hold and why
- A quarterly check, with a short written result
- How long
- Set up during the build. The quarterly check takes about half a day of our time and an hour of yours.
- How it is priced
- The set-up is part of every Sprint and Project. The quarterly check is part of every support plan, from Basic up.
Ongoing support plans
One person to call, fixed response times, and a monthly note on what was improved.
Once your business relies on something, someone has to watch it. Orders keep arriving on a Sunday, Tally gets updated, a supplier changes their invoice format, a phone number changes. A support plan means one named person on our side and a promised response time. It also means a fixed number of hours each month spent making the system better, not only keeping it alive.
Three plans, priced by how fast you need us and how much improvement you want each month. All three include monitoring, fixes and the monthly note on what changed.
Scroll sideways to see all the columns: Basic, Standard and Priority.
| What you get | Basic | RecommendedStandard | Priority |
|---|---|---|---|
| Price | ₹15,000a month | ₹35,000a month | ₹75,000a month |
| We respond | Within 2 working days | Within 1 working day | Within 4 working hours |
| How to reach us | WhatsApp and email | Phone, WhatsApp and email | |
| Health checks | Monthly health check | Weekly health check | Daily automated checks, weekly review |
| Improvement hours | 4 hours a month | 12 hours a month | 30 hours a month |
| Monthly note on what changed | Included | Included | Included |
| Quarterly safety and access check | Included | Included | Included |
| Quarterly review meeting | Not included | Included | Included |
| Same-day fix for anything that stops work | Not included | Not included | Included |
| First call on new ideas | Not included | Not included | Included |
All three are the Ongoing plan at different levels, paid monthly in advance and ended with 30 days' notice at any month end. Improvement hours are for changes you ask for; fixes for anything that broke are always included.
Choosing is simpler than it looks. Basic suits a system that runs in the background and can wait a day or two, such as a monthly report. Standard suits most businesses whose orders or invoices now go through the system every day and who want a steady stream of small improvements. Priority is for anything that faces customers during business hours, where an hour of silence costs sales. If in doubt, start on Standard; you can move up or down at any month end.
Your first month on a plan
Handover call
Half an hour with your named contact. We list the systems covered, who on your side can raise issues, and what counts as work stopped.
Contact line and checks set up
The email, WhatsApp or phone line for your plan is set up, and the daily or weekly health checks start running.
Your improvement list
You tell us the five things you wish it did. We size each one in hours and agree the order.
First monthly note
At month end you receive a one-page note: what broke, what was fixed, what was improved, and what the hours were spent on.
- Who it is for
- Anything we have built that your business now relies on. Systems built by others, once we have reviewed them.
- What you receive
- One named person and a promised response time
- Monitoring, fixes and health checks
- Improvement hours every month, spent on your list
- A monthly note on what changed
- How long
- Month to month. Most businesses stay for as long as the system is in use.
- How it is priced
- ₹15,000 to ₹75,000 a month, paid monthly in advance. The table above has the three plans; the pricing page has the full picture.
How it fits together
From launch day to month twelve
Launch is the middle of the job, not the end. The first week is training and the written guide. From the first month, checks run on their own, fixes happen within the agreed time, and every quarter we look at access and backups together.
Scroll sideways to see the whole route. The list below says the same thing in words.
In words
- The system goes live on a date we planned towards together.
- In the same week, two short training sessions for the people who will use it.
- Each session ends with a written guide, one page per task, in Tamil or English.
- Your team runs it. You hold the logins and the code.
- From month one, checks run every day or every week and catch most problems first.
- Anything that breaks is fixed within the response time in your plan.
- At month end you receive a note on what broke, what was fixed and what was improved.
- Every quarter we review who has access and whether the backups restore.
For your technical teamAccess, backups, monitoring, data protection, handover
- Access
- One login per person, roles by job, two-factor on anything that can change money or data. Credentials live in a password manager you own; the leaver checklist takes ten minutes.
- Backups
- Nightly encrypted copies of the database and the files to a second location in India; a restore drill every quarter, timed and written down.
- Monitoring
- Uptime and error checks every few minutes, an alert on WhatsApp when a job fails or a queue backs up, and a weekly digest. Workers restart themselves; anything that fails twice pages a person.
- Data protection
- A per-system register of personal data (what, why, how long), data kept in India, calls to the rented AI services made with retention off and with personal fields removed where the task allows, and deletion requests handled end to end.
- Handover
- The code in a repository you own, infrastructure notes in one document, and the same guide your staff use. Nothing depends on our accounts.
The tools themselves are named on Keeping it safe and The AI itself.
Worksheet
How many hours does the system give back each month?
A support plan exists to keep those hours coming back. Put in the task we automated for you, or the one you are thinking about, and see how many hours a month depend on it running.
Hours a month given back
75 hours
That is about 9 working days a month given back.
An estimate, not a promise. We measure it properly before you rely on it.
Questions
What owners ask about support
Usually, after a review. We spend a few days reading it, note what we would change, and quote a plan from there. If it is in no state to support, we say so and suggest what to do instead.
One named person who knows your system, by email, WhatsApp or phone, depending on your plan. Not a ticket queue. If they are on leave, you are told who is covering before it happens.
Orders, invoices or replies not going through, or a report that is due and missing. On Priority we start on it the same day. On Standard we respond within 1 working day, and on Basic within 2 working days. Everything else is a fix within the normal response time.
Changes you ask for: a new column in a report, a new supplier's invoice format, a reminder at a different time. Fixes for things that broke never come out of them. Unused hours do not roll over, so we agree a short list at the start of each month.
Yes, with 30 days' notice, at any month end. Everything keeps running and stays yours, because you hold the logins and the code from day one.
Yes. Sessions run in Tamil or English, whichever the group prefers, and the written guide can be in either. Mixed groups usually get the session in Tamil and the guide in both.
A Sprint first, a plan once you rely on it
Most businesses start with one task and add a support plan when it is in daily use. The prices are on one page, agreed before we start.
Monday to Saturday, 9:30 am to 6:30 pm IST