April is when leftover budget finds a vendor
India’s financial year starts on 1 April. By the first Monday, accounts have a new voucher series, a new company year in Tally, and a software line that either rolled over or appeared because last year’s unused amount would have looked bad. That is a real calendar, not a marketing season. It is also how businesses buy the wrong thing: a portal nobody asked for, a dashboard that reprints the spreadsheet, a “digital transformation” that starts with a logo on a slide.
The useful job in the first fortnight of the year is not spending. It is writing down what already runs the firm — including the workbooks you are embarrassed by — and naming one slice worth funding. Cost bands belong on a different page. This page is the audit you do before anyone opens a quote.
We work with Kerala and wider-India SMEs that already live in Tally, WhatsApp, and a folder of Excel files named after a person. The pattern in April is the same every year. Finance wants the books clean. Operations want last year’s workaround to stop hurting. Someone in the family or the board wants a new system because a competitor “has an app”. Those three wishes are not one project. Treat them as one project and you will still be reconciling Tally to a sheet in September.
What “old software” actually means in this office
It rarely means a mainframe. It means Tally as the books, a billing or weighbridge package from 2014, a website that is really a brochure, and five workbooks that have become the system of record for orders, stock, jobs, or dealer claims. WhatsApp is the exception channel and, often, the real dispatch list. None of that is shameful. It is how a firm that grew on relationships keeps moving. It becomes expensive when two people cannot agree which file is true, and when hiring another person to copy between them is the current plan.
Old software is also the custom Access file on one desktop, the desktop .exe whose vendor stopped answering, and the shared drive with three copies of every rate card. You do not need to replace all of it this year. You need to know which of those objects is the one that will break a GST filing or a customer promise if the person who understands it takes leave in May.
Write the list on one page. Name the owner. Name what happens when that owner is away. If you cannot name an owner, that item is already a project — even if you spend nothing on software this quarter.
The audit before the shopping list
Sit with the people who do the work, not only the people who approve the budget. Photograph the screens, the sheets, the printed checklist, the WhatsApp group titled after the workflow. Ask what they retype. Ask what they do not trust. Ask which number they use when Tally and the sheet disagree. That last answer is the system of record, whether or not it has a licence.
- Books. What must stay in Tally this year? Year lock, GST, auditor comfort. Write it down so nobody “replaces Tally” in a kickoff that finance will refuse.
- Operations facts. Orders, stock, jobs, tickets — where is yesterday’s record actually found? If the answer is a person’s laptop, that is the slice candidate, not a new homepage.
- Side channels. Spreadsheets “just for this month”, groups, a whiteboard. If you fund a system and leave those alive, you funded a museum exhibit.
- Integrations that already exist. Bank files, a supplier portal, a scale, a payment gateway, email that is already the inbox of record. List them. Guessing here is how April quotes move in June.
- The one painful retype. The job that happens every weekday and still requires a human to copy a field. That is usually the first slice, not the “full platform”.
This is IT systems consulting when you want a second pair of eyes. It is also something a sharp operations lead can start this week with a notebook. The deliverable is not a tool recommendation. It is a page that a vendor cannot waffle past.
Spreadsheets that have become the company
A workbook is fine when one person uses it and the facts are not needed elsewhere. It stops being fine when three branches edit copies, when a formula is the only place a rate lives, or when accounts retype the same totals into Tally because nobody trusts the export. April is a good time to admit which sheets are products. Products need owners, backups, and a plan. A sheet that invoices customers is a product, even if Microsoft Excel is the runtime.
Do not start by “building a portal to replace Excel”. Start by listing the columns that are true, the columns that are calculated, and the columns that are someone’s opinion. The opinion columns are why custom software projects stall. If two supervisors cannot write the same rule for a discount or a job status, software will not invent the rule. You will encode a guess and fight it at month-end.
Look at last year’s month-end. The files that were emailed as “final_v3_use_this” are the map. The person who sent them is the product owner whether their visiting card says so or not. Budget their time this quarter, or do not budget a build. A vendor that needs nothing from you will guess, and you will pay for the guesses after the year is no longer new.
- Sheets that only one person understands — document or replace the dependency, do not wrap it in a login.
- Sheets that contradict Tally — decide which number wins before you buy a connector.
- Sheets that are really a workflow — status columns, “pending with”, dates. Those are the first-slice shape.
- Sheets that are a report — those can wait. Reports are cheap once the facts are in one place.
Tally gaps that are not a Tally problem
Tally is good at books. It is a poor warehouse, a poor dealer portal, and a poor job card. Firms get into trouble when they force those jobs into ledger names, or when they keep a parallel universe in Excel because Tally “cannot do it”. Sometimes Tally can do a version of it and the firm never learned the feature. Sometimes the job is not accounting and should never live there. April is when those two cases get mixed into one purchase order for “ERP”.
A Tally gap is: invoices and receipts are clean, but the operational fact — the dispatch, the batch, the claim, the appointment — never had a home. Funding a new accounting package to fix that is how you get a second set of books and the same WhatsApp group. Funding a small operational system that posts into Tally, or drops a file Tally can import, is the shape that survives a GST quarter.
We would not rip Tally out in April because a brochure said “cloud ERP”. Auditors know Tally. Your accountant knows Tally. Year one of a new operational system is late enough to prove the numbers. If someone is selling you a cutover of the books in the same sprint as the warehouse screen, they are selling a festival date, not a phase.
Ask a narrower question: which voucher or report is currently a lie because the operational fact was typed twice? That is the integration to price. Not “Tally to SAP”. Not “Tally replacement”. The lie, named.
What is worth funding this year — and what is shopping
Worth funding: the weekday job that already has a rule, an owner, and a cost you can feel without inventing a rupee total — overtime, retyping, a missed dispatch, a claim that sat in mail. Shopping: a mobile app because the competitor’s nephew built one, a chatbot on a site that has four pages, an AI layer on a process that is still a photo in WhatsApp. Those can be next year’s sentences. They are not this year’s first slice.
Also shopping: a full module list copied from a vendor deck. “Sales, inventory, production, CRM, HR, analytics” is a catalogue. A first slice is one sentence. “Warehouse staff will record dispatches in the system instead of WhatsApp.” “Dealers will raise claims here instead of email.” If you cannot write that sentence, you are not ready to spend the software budget. You are ready for a week of discovery, which is a smaller spend and a better use of April than a twelve-module hope.
The MVP page is the longer version of that discipline. Use it. Do not rename a festival deadline an MVP so the leftover budget can be parked against a date. An MVP you cannot put in front of staff without you in the room is a prototype. Call it that and keep the rest of the money.
Keep, wrap, or replace
| What you have | Usually do this | April tell |
|---|---|---|
| Tally, trusted books, known auditor | Keep. Integrate later. | Finance will not attend a rip-and-replace kickoff |
| A desktop package that still invoices | Wrap: export, API, or a sidecar for the new job | Vendor still answers, data is ugly but complete |
| A workbook that is the only order book | Replace the workflow, not “Excel” as a religion | Two copies already disagree on Friday |
| WhatsApp as the dispatch list | Replace the path. Software cannot retire the group for you. | The group name is the workflow name |
| A brochure site with a contact form | Leave it. That is a website job, not this budget. | Nobody works in it all day |
The table is a decision aid, not a score. A desktop package whose vendor has vanished may still be cheaper to wrap for a year than to replace during peak season. A workbook that only the founder trusts may need a process conversation before it needs a login. Honesty here saves more money than a discounted quote.
A first slice you can defend in June
Write the slice so a sceptic can attack it. Name the users. Name the Tuesday job. Name what is out: the portal, the second branch, last year’s analytics, the bilingual help site. Name the systems that stay. Name the parallel run if money or stock is involved. Name who will sit with the build one day a week. That paragraph is what you fund. Everything else is a backlog you can sequence after the test.
June is when the leftover-budget glow fades and someone asks what shipped. If the answer is workshops and a Figma file, you bought discovery at build rates. If the answer is “staff completed the job in the system four days out of five”, you have something you can extend. If the answer is “they went back to the sheet”, you learned cheap — provided you kept the slice small. That is the only April spend that still looks smart at Diwali.
How much that slice costs is a scoped estimate after someone has seen your data, not a number we will invent here. Read how much custom software costs for the shape of a serious quote. Bring them the audit page, not a wish list. The 3× gap between vendors usually collapses when the slice is a sentence and the systems that stay are named.
What to leave on last year’s stack
Leave the books. Leave the site if it is only publishing. Leave the HR portal if it is not the pain. Leave the idea of unifying every login this year. Unification is a programme. April money is usually a project. Mixing them is how you get a year-end slide that says “phase 1 ongoing”.
Leave the vanity report. Directors ask for last year’s charts because charts feel like control. Charts on top of two disagreeing sources are decoration. Get one weekday job into one place. The report becomes a query. Paying for a BI tool in April because the sheet is ugly is how you fund a prettier lie.
Leave the mobile app unless the job is already done on a phone in the yard or the counter, and the phone is how the job fails today. A responsive screen on a phone the supervisor already has is often the first slice. A store listing is a different product. Do not buy both because the budget line said “app”.
A week in April that is not a build
Monday: list systems and owners. Tuesday: sit on the floor or at the counter; photograph the real path. Wednesday: write the keep / wrap / replace table with the people who will live with it. Thursday: write the first-slice sentence and the out-list. Friday: decide whether you are buying a small paid discovery, a fixed first slice, or nothing this quarter. Nothing is an allowed outcome. Spending leftover money on a vague portal is not a fiduciary duty.
If that week produces an argument, good. April is the cheap time to argue. July is when the same argument becomes a change request. Put the argument in email: Tally stays; the group chat closes when the path is live; the second branch waits. Silence in that email is how festival dates eat backups.
We will not pretend every firm should hire us for this. A competent internal lead can run the week. Hire a consulting week when the argument is stuck, when nobody owns the sheets, or when two vendors have already quoted “the system” on a one-line brief. The point of April is to stop being that brief.
The meeting before anyone quotes
Get finance, operations, and whoever will actually click the thing in one room for an hour. Not a webinar. Not a vendor demo. Walk the audit page. Force the first-slice sentence onto a whiteboard. If a director adds a module, ask which item leaves the in-list or which month moves. Doing that in April is kinder than doing it in a demo in week ten.
Send the same page to every vendor. Same systems, same slice, same “done”. Ask for assumptions in writing. A vendor that replies with a technology list and a module grid has told you they did not read the page. A vendor that argues with your out-list might be useful — provided they write the argument down and do not quietly put the module back into a fixed price.
Then wait a week before you sign. The new year makes people hurry. Hurry is how you buy last year’s leftover problem a second time. The software you already have is old. The budget is new. Only one of those should move in the first month, and it is not the stack.
If you want a partner for the week itself, start with consulting, not a build. If you already know the slice and need it built as a real test, start with the MVP definition and a quote that can move without a fight. Either way, spend April on the sentence. The purchase order can wait until the sentence can survive a sceptic.