ERP implementation: what two weeks actually looks like

Most ERP implementations are measured in months. Discovery, blueprinting, setting up, moving data, running two systems side by side, training - the traditional sequence stretches to six months for a mid-sized business. Kinnow is designed to give first results in about two weeks. This is what those two weeks actually look like.

Week 1: your data comes across and your team is set up

Setting up starts with your data, not with settings. In the first week, the partner or Kinnow's own team imports the opening balances, the chart of accounts, the customer and supplier masters, the item catalogue and the outstanding invoices. The data comes from desktop-accounting exports, spreadsheets or a copy of the database from the previous system. The goal is that by the end of the first week, the trial balance in Kinnow matches the trial balance in the old system.

This is the foundation. Everything that follows depends on the numbers being right from the start. If the opening balances do not match, the team stops and fixes the import before moving on.

Still in week one: the first real transaction

Still in week one, the team processes the first real transaction: a sales invoice, a purchase order, a payment receipt - whatever happens most often in the business. This is not a practice entry in a test area. It is a live entry that goes into the books. The purpose is to prove that the steps work, that the GST treatment is correct, that the right people are asked to sign off and that the output document (the invoice PDF, the PO email) looks right.

If the first transaction surfaces a problem - a tax rate mapped to the wrong HSN code, an approval that should skip a step for orders below a limit - the fix is made the same day. In Kinnow, most changes to settings take effect immediately, with no wait for a software release.

Days 8–10: agents switched on for your two or three priorities

The partner identifies the two or three problems that the business most wants solved and focuses the first week on those. For a trading company, that might be the receivables ageing and the bank reconciliation. For a manufacturer, it might be the parts-list costing and posting goods receipts straight to the books. For a CA practice, it might be the multi-client view and the GST filing preparation.

Each problem is solved from start to finish: the data is in, the steps are set up, the agents are switched on for those priorities, and the team uses it for real work. First results come in about two weeks.

Week two: the team widens

In the second week, more people start using the system. The accounts team processes invoices and payments. The sales team logs orders. The warehouse team does goods receipts. Training is hands-on: a partner sits with each group for an hour, walks through their daily tasks in Kinnow and answers questions. There is no classroom-style training programme.

This is where having no per-user fee matters. Every person who needs access gets it - the warehouse supervisor, the field sales rep, the CA. There is no conversation about who gets a licence and who does not.

Week two: the close rehearsal

The partner runs a rehearsal of the month-end close. Even if the business has only been on Kinnow for ten days, this rehearsal is valuable because it surfaces the processes that have not been set up yet: accruals, provisions, taking out trades between group companies (for businesses with several companies), the GST return preparation. The Close Checklist agent runs and lists what is incomplete, what is unreconciled and what needs a person's decision.

This rehearsal is not about getting perfect numbers. It is about building the team's confidence that they know where everything is and how the close works in the new system.

End of week two: first results and handover

First results are not a big-bang event. By the end of week two, the team has been using the system for real work for over a week. Your accounting moves across at a month-end; until then the old system stays the primary record for it. Kinnow connects to your sales, payroll and support tools while you move. The old system stays accessible for reference - and Kinnow can display financial statements in the old system's format, so the team can cross-check without learning a new layout.

The partner hands over a short list of things that remain: agents that need adjusting, reports that need fine-tuning, edge cases that will surface in the first full month. These are addressed in the weeks after go-live, at the business's pace.

What makes two weeks possible

Three things make this timeline realistic. First, Kinnow includes all 49 applications with no per-user fee, so there is no haggling over which applications to buy. Second, Indian compliance - GST, TDS, payroll - is in the core product, not an add-on that needs a separate implementation. Third, changes are quick: most changes are live within a day; larger ones are agreed with you and delivered at a fixed date.

Two weeks is not a promise that every business will be fully optimised in fourteen days. It is a promise of first results - real transactions, real returns prepared and real decisions from real data - in that time. Optimisation continues for months. But the system earns its keep from week three.