MAKIN ERP implementation that maps your process before configuring it
What’s included
01- ✓Process mapping before configuration
- ✓Master data setup and validation
- ✓Location and warehouse hierarchy
- ✓Purchase to payment workflow
- ✓Phased go-live per site
- ✓Super-user training programme
- ✓Hypercare for the first 30 days
The details
02Why map the process before configuring anything?
Because an ERP configured around assumptions reproduces the old arguments in a new system. Process mapping comes first: how stock is received, stored, moved and issued at each location, who raises a purchase and who approves it, and when payment is released. Configuration starts from that map, and anything you want to change about how you work is decided on paper, where changing it is cheap.
Master data is the other half. Items, units, vendors and locations are set up and validated before go-live, because a wrong unit of measure or a duplicated vendor shows up in every report afterwards. The location and warehouse hierarchy is built to match your real sites and stores, not an idealised chart.
Why go live one site at a time?
A phased go-live per site means one location moves onto the ERP while the others carry on as before. Problems found at the first site are dealt with before the next one moves, and later sites can learn from the ones that went first. Once a site is live, its purchase-to-payment workflow — requisition, order, receipt, invoice and payment — runs through the system the same way as everywhere else.
Who keeps it running after go-live?
Your own people, with us alongside for the first 30 days. The super-user training programme prepares people at your sites to answer everyday questions and train new joiners. Hypercare for the first 30 days means we stay close to the live system while its first real month of transactions goes through.
After hypercare, fixes, iterations and the roadmap can move to Managed Support & Growth, a retainer that starts at ₹14,000. Whether you need that, or whether your super-users can carry the system on their own, is much easier to judge once the first month is behind you.
What is not included?
This is a rollout of stock, purchase and production visibility across locations, not a deep production system. Multi-level BOMs, job cards, quality checks and batch costing belong to Manufacturing ERP (₹2,18,000). Trip planning, proof of delivery and freight costing belong to Distribution & Logistics ERP (₹1,60,000). A Tally sync is not listed here and is scoped on the call.
If you are not yet sure an ERP is the answer, because the real problem may be that your existing systems disagree with each other, the Drift Audit (₹49,000, 2–3 weeks) maps your systems, analyses where their records fail to reconcile and sets out the priority fixes. We diagnose. You get clarity. We quote only after that.
How it works
03- 0115-min callTell us what’s breaking. We ask the questions that change the price.
- 02Scope in writingA fixed quote and a written scope: what’s in, what isn’t.
- 03Build & reviewWorking software early, with review rounds on real screens.
- 04LaunchWe go live with you, train your team and hand over access.
- 05SupportFixes, changes and growth on a retainer, if you want one.
FAQ
04What does an ERP implementation cost?
ERP & Inventory Rollout starts at ₹1,75,000 and takes 3 months or more. The work is the implementation itself — mapping, master data, configuration, training and 30 days of hypercare — so the scope call starts with how stock and purchase run across your locations today. Your fixed price arrives in writing after a 15-minute scope call.
Which ERP do you implement?
The stack on the package card is Odoo, Postgres and Node, and the rollout is built on Odoo. Any Odoo subscription your setup needs, and where the system is hosted, are discussed on the scope call and written into the proposal, so those costs are known before you sign.
Will the business have to stop while we switch over?
Not all of it at once. Sites move over in turn, so the rest of the business keeps working on its current system while one location cuts over. How each cut-over is handled — opening stock, open orders, the last day on the old system — is planned with you before it happens.
How many sites can the rollout cover?
The package is built for businesses with more than one location; the warehouse hierarchy and the phased go-live exist for exactly that reason. The number of sites and the order in which they go live are set on the scope call and written into the proposal.
Does our data need cleaning before we start?
Master data setup and validation is part of the package, so items, units, vendors and locations are checked before any site goes live. If the data sits in an old system and needs a larger move with proof that nothing was lost, Data Migration & Quality (₹15,000, up to 30 days) covers that as a separate package.
More in ERP
05Also see
0615 minutes.
One quote.
Tell us what you need. We reply on WhatsApp or email with a time, and a written quote after the call.
Re: ERP & Inventory Rollout