The conventional wisdom in the ERP industry is that implementation takes 6-18 months. For large enterprises running SAP or Oracle across multiple countries and thousands of users, that timeline is real. For an Indian manufacturing SME with 20-100 people, it is absurd.
A fabrication unit in Ahmedabad does not need 18 months to start tracking quotations and job costs. A machining shop in Pune does not need a 6-month "discovery phase" before someone enters the first product into the system. The 12-month implementation timeline exists because enterprise ERP vendors sell consulting hours, and more months mean more revenue. It is not because the work requires it.
We have implemented QuoteERP at over a hundred manufacturing units across India. The playbook below is the distillation of what works. Four weeks. Not four quarters. The factory goes from zero to live in 30 days — with quoting, BOM costing, inventory, production tracking, and job costing running on real transactions.
This is not a magic trick. It requires discipline, a champion inside the factory, and a willingness to start imperfect and iterate. But it works. And it works because Indian SMEs do not have the luxury of a year-long project. They need results this quarter, not next fiscal year.
Why 30 days is realistic
Before you dismiss this as marketing, understand why the traditional timeline is inflated.
Traditional ERP projects spend 40% of the time on requirements gathering. For a 50-person manufacturing SME, the requirements are not mysterious. You quote, you produce, you dispatch, you invoice, you track costs. The process variations between a sheet metal shop in Rajkot and a machining unit in Coimbatore are surprisingly small. A well-designed manufacturing ERP has already solved these patterns. You configure — you do not custom-build.
Traditional projects assume zero data readiness. Most Indian factories have their customer master in Tally, their product catalogue in Excel, and their BOMs in someone's head. Preparing this data takes 3-5 days of focused effort, not 3 months.
Traditional projects plan for full organisational change management. In an SME, the owner decides, tells the team, and things move. You do not need a steering committee, a change management consultant, and a quarterly review board. You need the owner's commitment and one champion who drives adoption.
Traditional projects aim for 100% coverage from Day 1. The 30-day playbook aims for 80% coverage. The remaining 20% — edge cases, rarely-used workflows, advanced reporting — is handled in the weeks after go-live through iteration.
The role of the champion
Before we get into the week-by-week plan, this is the single most important success factor: you need one person in the factory who owns this rollout. Not the ERP vendor's consultant. Not the owner (who is too busy). One person from your team.
Who should be the champion?
Ideally, someone from the sales or operations team — not from accounts. The reason: the ERP's first and biggest impact is on quoting and production, not accounting. You need someone who understands these processes from inside and has the respect of both the sales team and the shop floor.
What does the champion do?
- Coordinates data preparation in Week 1
- Makes configuration decisions in Week 2 (with the owner's input for policy questions)
- Drives the parallel run in Week 3 (making sure every transaction goes into the ERP)
- Handles questions and resistance in Week 4
- Owns post-go-live issue resolution
How much time does the champion need?
In Weeks 1-2: about 3-4 hours per day. In Weeks 3-4: about 2 hours per day plus availability for questions. After go-live: about 1 hour per day for the first month, then it becomes part of normal work.
This is a significant time investment. The owner needs to protect the champion's time — which means temporarily offloading some of their regular duties. If the champion is also handling their full workload, the implementation will drag beyond 30 days.
Week 1: Data preparation (Days 1-7)
This is the week where most implementations either succeed or stall. Data preparation is not glamorous, but it is the foundation. An ERP without accurate master data is a beautiful building on a cracked foundation.
Day 1-2: Customer master
Task: Export your customer list from Tally and clean it up.
What you need for each customer:
- Company name (as it appears on GST registration)
- GSTIN
- Billing address and shipping address (if different)
- Contact person name, phone, email
- Credit limit (if applicable)
- Customer category (dealer, OEM, retail, institutional)
- Payment terms (advance, 30 days, 60 days)
Common problems and fixes:
- Duplicate entries (same customer with slightly different names) — merge them
- Missing GSTIN — look up on the GST portal
- Outdated contact details — call and verify the top 50 customers, mark the rest for gradual cleanup
Target: Clean customer master for your top 100 active customers. Do not try to migrate every customer from the last 10 years. Start with active ones. Add others as transactions happen.
Day 2-3: Product catalogue
Task: Create a structured product catalogue with consistent naming, HSN codes, units of measurement, and base pricing.
What you need for each product:
- Product name and code (use a consistent naming convention)
- HSN code
- Unit of measurement (nos, kg, metre, sqft, set)
- Base selling price (before discounts)
- Product category
- Standard lead time
Common problems and fixes:
- Same product called different names by different salespeople — standardise
- No HSN code mapping — use the government's HSN lookup tool or ask your CA
- Pricing inconsistency — document the current price list; do not try to fix pricing strategy during implementation
Target: Catalogue for the products that account for 80% of your revenue. For a typical SME, this is 50-200 products.
Day 3-5: Bills of Materials (BOMs)
Task: Document the BOM for your top products — every raw material, component, sub-assembly, labour operation, and bought-out part.
What you need for each BOM:
- List of materials with grade/specification, quantity per unit, unit of measurement, wastage factor
- Labour operations with estimated hours per operation
- Outside processing steps (if any) with estimated cost
- Bought-out components with vendor and cost
- Overheads allocation method (percentage of material, fixed amount per unit, etc.)
This is the hardest part of Week 1. In most factories, the BOM lives in the production manager's head. Getting it documented and into a structured format takes focused effort. Start with your top 10-15 products. For each one, sit with the production manager for 30-45 minutes and document everything.
Common problems and fixes:
- "Every job is different" — true for custom manufacturers, but 70-80% of the BOM is usually common. Document the common base and allow customisation of the variable portion
- Inaccurate wastage factors — use your actual consumption data from the last 3 months, not theoretical values
- Missing labour hour estimates — start with rough estimates and refine based on actual data in the first month
Target: Documented BOMs for the top 10-15 products that drive the majority of your quotations.
Day 5-6: Rate cards and pricing rules
Task: Document your pricing logic — who gets what discount, at what quantity, under what payment terms.
What you need:
- Standard price list (base price for each product)
- Customer category discounts (dealer: 15%, OEM: 10%, retail: 0%)
- Quantity slab discounts (100+ units: 3%, 500+ units: 6%)
- Payment term adjustments (advance: extra 2% discount, 60-day credit: 3% premium)
- Approval thresholds (discounts above X% need owner approval)
Target: A documented pricing rules matrix. This probably exists in the owner's head — the goal is to get it written down and configured into the system.
Day 6-7: Opening stock
Task: Take a physical stock count and enter opening balances for raw materials, work-in-progress, and finished goods.
What you need:
- Physical count of all raw materials (with batch details if applicable)
- WIP — list of jobs currently on the floor with material already issued
- Finished goods inventory with quantities and locations
Common problems and fixes:
- Stock in Tally does not match physical stock — use physical count as the truth. Reconcile with Tally separately; do not let Tally discrepancies delay the ERP rollout
- Multiple godowns — count each location separately and enter location-wise
- No time for full count — count the top 50 materials by value (which typically cover 80% of inventory value). Add the rest over the next 2 weeks
Target: Opening stock for the materials that account for 80% of inventory value.
Week 1 day-by-day checklist
| Day | Task | Owner | Deliverable |
|---|---|---|---|
| Day 1 | Export customer list from Tally, start cleanup | Champion + Accounts | Raw customer export file |
| Day 2 | Complete customer master cleanup (top 100) | Champion | Clean customer master ready for import |
| Day 2-3 | Product catalogue with HSN, UoM, pricing | Champion + Sales head | Structured product list (50-200 items) |
| Day 3-4 | BOM documentation — top 5 products | Champion + Production manager | 5 documented BOMs |
| Day 4-5 | BOM documentation — next 5-10 products | Champion + Production manager | 10-15 total documented BOMs |
| Day 5-6 | Pricing rules and discount matrix | Champion + Owner | Pricing rules document |
| Day 6-7 | Physical stock count and opening balances | Champion + Store manager | Opening stock sheet |
Week 2: Configuration (Days 8-14)
With data ready, Week 2 is about setting up the ERP to match your business rules. This is where the ERP vendor's implementation team earns their fee.
Day 8-9: Master data import
Task: Import customer master, product catalogue, and BOMs into the ERP. Verify the import by spot-checking 20 random records.
What to watch for:
- GST rates should auto-calculate correctly based on HSN codes
- BOM costs should match your manual calculations (within 1-2%)
- Customer categories and payment terms should be reflected in credit limit settings
Day 9-10: Quotation template and branding
Task: Configure the quotation template with your company logo, standard terms and conditions, bank details, and format preferences.
Key decisions:
- What information appears on the quotation (some companies include BOM details, others show only line items)
- Payment terms default (can be overridden per quotation)
- Validity period default
- Signature block format
Test: Generate 5 sample quotations for real customers. Print them. Show them to the owner and sales team. Get feedback. Adjust.
Day 10-11: Pricing rules and approval workflows
Task: Configure the discount matrix, quantity slabs, customer category pricing, and approval thresholds.
Key decisions:
- What discount level requires owner approval? (Typical: anything above 10% from standard price)
- Who can approve? Just the owner, or also the sales head?
- How does the approval notification reach the approver? (WhatsApp link, email, in-app notification)
Test: Create a quotation with a discount above the threshold. Verify that the approval request reaches the owner's phone. Approve it. Verify the quotation status updates and the customer gets the PDF.
Day 11-12: Production workflow setup
Task: Define work centres (cutting, welding, machining, assembly, painting, QC, packing), operation sequences for standard products, and job status tracking steps.
Key decisions:
- How granular should tracking be? (Per operation vs per major milestone — start with milestones if the team is not used to digital tracking)
- Who updates job status? (Supervisor vs operator)
- What triggers the "job complete" status?
Day 12-13: User setup and roles
Task: Create user accounts for everyone who will use the system. Assign roles with appropriate permissions.
Typical roles:
- Owner/Director: Full access, approval authority
- Sales engineer: Quotation creation, customer management, order view
- Production supervisor: Job status updates, material issue, shop floor view
- Store manager: Inventory management, purchase requisitions, goods receipt
- Accounts: Invoice generation, payment tracking, Tally sync
- Dispatcher: Packing, dispatch, delivery challan, e-way bill
Key principle: Start with more restriction, not less. It is easier to grant additional access than to tighten it after people are used to seeing everything.
Day 13-14: Integration and testing
Task: Set up Tally integration (if applicable), test the complete flow from quotation to invoice, and fix any issues.
The end-to-end test: Create a quotation for a real customer, convert it to a sales order, generate a production order, issue material, update job progress, mark job complete, create a dispatch, generate the GST invoice and e-way bill. Every step should work without manual workarounds.
Common Week 2 issues:
- BOM costs do not match expectations — usually a wastage factor or UoM conversion error. Fix the BOM, re-test.
- GST calculation is wrong — check HSN mapping and place of supply configuration.
- Quotation format does not look right — usually a template adjustment, takes 30 minutes.
- Approval notifications are not reaching the owner — check WhatsApp number configuration or notification settings.
Week 2 day-by-day checklist
| Day | Task | Owner | Deliverable |
|---|---|---|---|
| Day 8 | Import customer master and product catalogue | ERP vendor + Champion | Verified master data in system |
| Day 9 | Import BOMs, verify costing accuracy | ERP vendor + Champion | BOMs live with accurate costs |
| Day 9-10 | Configure quotation template and branding | Champion + Sales head | Branded quotation template approved |
| Day 10-11 | Set up pricing rules and approval workflows | Champion + Owner | Working approval flow tested |
| Day 11-12 | Configure production workflow and work centres | Champion + Production manager | Production tracking configured |
| Day 12-13 | Create user accounts and assign roles | Champion + ERP vendor | All users set up with correct access |
| Day 13-14 | End-to-end testing and issue fixing | Champion + ERP vendor | Complete flow working |
Week 3: Parallel run (Days 15-21)
This is the week that builds confidence. Every transaction goes into both the old system (Excel/Tally) and the new ERP. It is extra work — the team will complain — but it is essential.
Why parallel run matters
The parallel run serves three purposes:
- Data validation. You verify that the ERP produces the same numbers as your manual process — or better numbers, if your manual process had errors.
- Team training. People learn by doing, not by watching demos. The parallel run is real-world training on real transactions.
- Confidence building. The owner sees the system handling actual business. The sales team sees quotations going out correctly. The production manager sees job tracking working. By the end of the week, the question shifts from "will this work?" to "why are we still doing it the old way?"
How to run the parallel week
Quotations: Every new enquiry gets a quotation in both Excel (the old way) and the ERP. Compare the two. If the ERP quotation is different, find out why. It is usually a pricing rule misconfiguration or a BOM error — fix it immediately.
Purchase orders: Every purchase requisition goes through the ERP. The actual PO can still go through the old process, but the ERP captures the requirement, tracks it, and matches it against the BOM.
Production orders: Every new job gets a production order in the ERP. The supervisor updates status daily — even if he also updates the whiteboard. By mid-week, the whiteboard and the ERP should show the same information.
Inventory: Every material receipt and every material issue gets recorded in the ERP. At the end of the week, compare ERP stock with physical stock. Discrepancies reveal either data entry misses or the process gaps that the ERP is designed to fix.
Managing the extra workload
The parallel run doubles data entry for one week. Your team will resist this. Here is how to handle it:
- Acknowledge the burden. Do not pretend it is not extra work. Say: "This week is the hardest week. After this, we stop the old system and the workload goes down."
- Provide immediate support. The champion should be available on the floor for questions. The ERP vendor's support team should respond within 30 minutes to any issue.
- Celebrate small wins. When the first quotation goes out from the ERP and the customer approves it, make it known. When the first production order is tracked to completion, acknowledge it.
- Do not extend it. One week of parallel run. Not two. Not three. The longer you run parallel, the more the team believes the old system is still the real system.
Week 3 day-by-day checklist
| Day | Task | Owner | Success Metric |
|---|---|---|---|
| Day 15 | First live quotations in ERP (parallel with old process) | Sales team + Champion | 5+ quotations created in ERP |
| Day 16 | First purchase orders and material receipts in ERP | Purchase + Store | GRN entries matching physical receipts |
| Day 17 | Production orders created for all active jobs | Production supervisor | All current jobs visible in ERP |
| Day 18 | Daily status update routine established | Production supervisor | End-of-day job status updated for all jobs |
| Day 19 | First dispatch processed through ERP | Dispatch team | Delivery challan and e-way bill from ERP |
| Day 20 | Week comparison: ERP data vs old system data | Champion | Discrepancies identified and resolved |
| Day 21 | Go/no-go decision for cutover | Owner + Champion | Decision documented |
The go/no-go decision
At the end of Week 3, the champion and owner make the cutover decision. The criteria are simple:
- Can quotations be generated accurately from the ERP? (Yes/No)
- Is the customer master and product catalogue 90%+ complete? (Yes/No)
- Can production orders be tracked to completion? (Yes/No)
- Does the team know how to enter data without constant hand-holding? (Yes/No)
- Are there any blocking issues without a workaround? (Yes/No)
If four out of five are yes and there are no blockers, go live. If there are blockers, extend the parallel run by 3-5 days — not more — and fix the blockers.
Week 4: Go-live and stabilisation (Days 22-30)
Day 22: Cutover
This is the day the old system stops being the primary system. From today, every quotation, every production order, every material receipt, and every dispatch goes through the ERP first.
Important: Tally continues for accounting. The cutover is for operations, not for financial reporting. Invoices generated in the ERP flow to Tally through the integration. The accountant's workflow changes minimally.
Announce it clearly. The owner should tell the team: "From today, all transactions go through the ERP. If it is not in the system, it did not happen." This statement, from the owner personally, matters more than any training session.
Day 22-25: High-support period
The first 3-4 days after cutover are the most critical. Issues will come up. Some will be data problems (a product missing from the catalogue). Some will be process problems (the team does not know which screen to use). Some will be genuine bugs.
The champion's role is to be available. Every question gets answered within 15 minutes. Every data issue gets fixed the same day. Every process gap gets a workaround immediately and a proper fix within 48 hours.
The ERP vendor's role is responsive support. During go-live week, the vendor should provide same-day resolution for any reported issue. If the vendor's support is slow during go-live week, it will be slower later. This is your test of the vendor relationship.
Day 25-28: Routine establishment
By the end of the first week of go-live, the daily routine should be established:
Morning: Production supervisor reviews today's job list on the ERP, checks material availability for upcoming jobs.
Through the day: Sales engineers create quotations in the ERP, share with customers via WhatsApp. Production supervisor updates job status as operations complete. Store manager records material receipts and issues.
End of day: Champion reviews pending items — unapproved quotations, unresolved material shortages, overdue jobs. Flags issues for next-day resolution.
Day 28-30: Post-go-live measurement
The first measurement cycle happens at the end of Week 4. This is not a comprehensive audit — it is a pulse check.
Metrics to capture:
| Metric | Before ERP (estimate) | After ERP (Week 4 actual) |
|---|---|---|
| Average quotation turnaround time | ___ hours | ___ hours |
| Quotations generated per day | ___ | ___ |
| Active jobs visible in system | 0 (whiteboard only) | ___ |
| Material issues tracked by job | Not tracked | ___ jobs |
| Dispatch documents generated from ERP | 0 | ___ |
| Data entry issues reported | N/A | ___ (should be declining daily) |
These numbers serve two purposes: they validate the implementation and they provide the baseline for ongoing ROI measurement.
Week 4 day-by-day checklist
| Day | Task | Owner | Success Metric |
|---|---|---|---|
| Day 22 | Cutover — ERP becomes primary system | Owner + Champion | Owner's announcement to team |
| Day 23 | High-support: resolve all Day 1 issues | Champion + ERP vendor | Zero unresolved blockers by end of day |
| Day 24 | High-support: address workflow questions | Champion | Issue volume declining |
| Day 25 | Review first week's data quality | Champion | Spot-check 20 transactions for accuracy |
| Day 26 | Routine check — are all transactions being entered? | Champion | No transactions bypassing the ERP |
| Day 27 | Identify gaps for Phase 2 improvement | Champion | Gap list documented |
| Day 28 | Compile post-go-live metrics | Champion | Metrics dashboard populated |
| Day 29 | Team feedback session (30 min) | Champion + all users | Feedback collected, top 5 issues identified |
| Day 30 | Go-live review with owner | Champion + Owner | Implementation status report |
What to do when the team resists
Resistance is guaranteed. Do not be surprised by it. Plan for it.
The "This is extra work" objection
Reality: In Week 3 (parallel run), it is extra work. After cutover, it should not be — the ERP replaces the old process, not adds to it. If someone is doing double data entry after cutover, the process is not configured correctly. Fix the process, do not blame the person.
The "Excel was faster" objection
Reality: For someone who has used Excel for 10 years, the first week on any new system will feel slower. This is the learning curve. By Week 3, the ERP will be faster for most tasks because it eliminates the searching, cross-referencing, and manual calculation that Excel requires. Acknowledge the short-term pain, but hold the line.
The "The system does not handle our process" objection
Reality: Sometimes this is legitimate — a genuine gap that needs configuration or customisation. More often, it is resistance dressed up as a technical issue. The way to tell the difference: ask the person to show you the specific step that does not work. If they can demonstrate a real gap, fix it. If they cannot articulate it beyond "it just does not feel right," it is comfort zone resistance. Address it with patience but do not redesign the system around feelings.
The silent boycott
The most dangerous resistance is the person who says nothing but quietly continues using the old system. The champion's job is to catch this by monitoring usage — which users have created transactions this week? If someone has not logged in for 3 days, that is a conversation to have immediately.
Post-go-live: the first 90 days
The 30-day playbook gets you live. The next 60 days are about making the system stick and expanding its value.
Days 31-45: Stabilisation. Fix the remaining issues from the go-live gap list. Complete the product catalogue for the long-tail items. Train anyone who was not part of the initial rollout.
Days 46-60: Optimisation. Review quotation conversion rates. Analyse job costing data from the first month — where are the biggest variances between estimated and actual? Refine BOMs based on actual consumption data.
Days 61-90: Expansion. Add any deferred modules — detailed production scheduling, advanced reporting, dealer portal. Start using the data for strategic decisions: which products are most profitable? Which customers are most expensive to serve? Where are the operational bottlenecks?
Day 90: Business review. Present the ROI data to the owner. Quotation turnaround time, quote volume, job cost accuracy, on-time delivery, material waste — compare these against the pre-ERP baseline. This is when the ERP investment is validated with hard numbers.
The complete 30-day timeline
| Week | Focus | Key Activities | Output |
|---|---|---|---|
| Week 1 (Days 1-7) | Data preparation | Customer master, product catalogue, BOMs, pricing rules, opening stock | Clean master data ready for import |
| Week 2 (Days 8-14) | Configuration | Data import, template setup, pricing rules, workflows, user roles, testing | Fully configured system, end-to-end tested |
| Week 3 (Days 15-21) | Parallel run | All transactions in both old and new system, team training by doing | Team confidence, data validated, go/no-go decision |
| Week 4 (Days 22-30) | Go-live | Cutover, high-support, routine establishment, first metrics | Live system, baseline metrics, gap list for Phase 2 |
Start your 30-day rollout
This playbook works because it is designed for how Indian manufacturing SMEs actually operate — fast decisions, lean teams, practical priorities. You do not need a year. You need 30 days and one champion.
QuoteERP is built for this implementation model. The system is pre-configured for Indian manufacturing — GST, BOMs, job costing, WhatsApp sharing — so you are configuring, not building from scratch. Our implementation team has run this playbook at factories in Ahmedabad, Pune, Bengaluru, Hyderabad, Ludhiana, Rajkot, and Coimbatore. We know what works, what breaks, and how to fix it fast.
Start your 30-day implementation. We will assign an implementation partner, map your data requirements in the first call, and have you quoting from the ERP within two weeks. No 18-month project plan. No steering committee. Just a system that works, configured for your factory, in 30 days.