Author: Next

I remember the day clearly. A 55-person metal fabrication shop, run by two brothers who really knew how to weld, was staring at a job they thought was their best one. The CFO came to the weekly meeting with a printed job card, looked up, and said: “We billed 80 grand for this job, and I still can’t tell you if we made or lost money on it.” That’s the moment ERPNext Consulting gets invited into the room.

The problem wasn’t the workers, it was the data trail

The shop had a fine reputation in the town, but its costing was a disaster. Materials were pulled from the rack without any record, and the welders’ hours were marked down on paper at the end of the shift from memory. A job that looked profitable on the quote sheet was actually bleeding 11% of its value once every bolt, gas refill, and overtime hour was counted.

The fix started with three small habits, not a big dramatic rollout. Every material pull got logged against a job number. Every shift clocked labor hours into the same record. And scrap metal was weighed and tagged at the bin. That gave the brothers their first real picture of job-level profit in years. ERPNext Consulting has worked with plenty of shops like this, and the pattern is always the same: the data already exists inside the business, it’s just scattered across memory, notebooks, and spreadsheets.

What changed when the numbers finally lined up

• Quotes started from actual historical costs, not gut feel, which lifted the average profit margin on new work by 6.4 points within two quarters.
• The purchasing manager could see which steel grades were turning into scrap, so he stopped over-ordering the soft sheet stock that the painters kept rejecting.
• The owners finally had a weekly one-page report showing every open job, its costs to date, and its remaining budget. A meeting they used to avoid became the shortest one on the calendar.

Was it tedious in the first few weeks? Yes. The welders complained, the office manager complained, and one foreman swore he would quit rather than type a digital entry.

But the brothers held the line for a month, and the grumbling faded. The foreman who threatened to quit ended up being the one who showed new hires how to use the screens.

The real win appeared six months later

They took on a large, awkward architectural job that had gone through three quoting rounds already. The CFO opened the historical cost data on a similar job from the previous year, saw the hidden corners where that earlier job had lost money, and re-priced the new one accordingly. That single decision recovered more than the implementation fee.

If you run a shop that quotes jobs without knowing your true costs, do this tomorrow: pick the three biggest jobs from last year and reconstruct what they really cost you. If you can’t do it in an afternoon, that’s your first signal. The goal is not to get a nicer report, it’s to get a number you can trust before you promise a price to a customer.

There is a furniture maker I worked with whose sales team kept promising delivery dates that production had no idea about. Every Friday, the production manager would get a list of orders that were due soon, half of which required materials that were not even on site. The result was a permanent scramble: overtime, rushed purchases, and a 61% on-time delivery rate.

Sales had their own tracking spreadsheet, and purchasing had another one. Nobody was looking at the same number, so every department believed it was the only one doing its job properly. The owner summed it up better than any consultant could: we are all working hard — we are just not working together.

Making the production plan the single source of truth

ERPNext Consulting replaced the three spreadsheets with one production plan that everyone reads and writes to. When sales books a new order, it lands in the plan instantly. When purchasing sees raw material levels dip below the safety buffer, the system suggests a purchase order instead of waiting for someone to panic.

That sounds simple, and it is — but only if humans change their behavior too. The sales team had to stop promising custom lead times without checking the plan. The production manager had to enter completed work at the end of every shift, not on Monday morning. The discipline of daily updates was the hardest and most valuable part.

Three conversations that now happen daily

These are not meetings on a calendar. They are quick checks built into the daily routine:

• Sales reviews the production plan every morning and flags any promised date that conflicts with capacity.
• Purchasing checks the 14-day material shortage list, so long-lead items get ordered in time.
• Production updates actual completion numbers at day’s end, so everyone sees reality instead of hope.

Within five months, on-time delivery climbed from 61% to 89%, and overtime pay dropped by 30% because the scramble disappeared. The purchasing manager stopped making emergency calls to suppliers because the system flagged shortages two weeks earlier. The owner told me it was the first year they took a real family vacation in August, because for once, the factory did not require a hero to babysit it.

Take one look at your own sales-versus-production routine: if the agenda starts with what is the problem this week, you have a reactive culture. The fix is to make the plan the agenda. ERPNext Consulting can build the system that supports that conversation, but the conversation itself is on you to start tomorrow morning.

Picture this: five companies under one roof, five different ways of recording expenses, and a finance team that spent the first two weeks of every month glued to Excel. The group’s accountant called month-end the nightmare that never ends. Consolidated reports were delivered on the 22nd of the following month, which meant decisions were always made on stale data.

The mess came from small differences nobody thought mattered. One entity categorized freight as cost of goods, another as a selling expense. Intercompany loans were tracked differently in every ledger, and reconciling them took the finance team three full days each month. Twelve days of value were lost every single month, and the whole group just accepted it.

Standardize first, automate second

ERPNext Consulting started with the boring stuff, which is where all the money was hiding. They created one chart of accounts that all five entities had to follow, with mandatory fields for cost center and project code. Then they mapped intercompany transactions so that when entity A invoiced entity B, the system recorded both sides in one step.

The finance team resisted at first, especially the accountant who had her own clever spreadsheet. But once the first automated consolidation ran without a single manual adjustment, she became the biggest supporter. Her team now closes the books by the 4th business day, and the consolidated view of the group is available the next morning.

What a smooth close actually requires

Here is the minimum standard:

• One shared chart of accounts, enforced by the system so nobody can quietly invent a new category.
• A fixed close calendar with named owners for each task, from bank reconciliation to intercompany matching.
• A golden rule that any unapproved expense from the previous month gets rejected, not tucked into next month.

The group eliminated about 120 hours of manual consolidation work per month. More importantly, the CEO started getting real answers — which entity was profitable, which cost center was bleeding, and which client segment deserved more attention. The culture changed from we’ll fix it later to it must be right today.

If your month-end takes more than a week, run a simple audit: list every manual step between the last transaction and the final report. Each one is a candidate for elimination or automation. ERPNext Consulting specializes in exactly that kind of cleanup, but you can start by simply asking each finance person what they spent Wednesday on.

I will never forget the meeting where a custom fabrication shop owner showed me a proposal from a giant enterprise software vendor. The implementation was going to take 18 months, cost more than their entire annual profit, and require four new hires just to keep it running. He was excited because it did everything. I asked him how many of those features he would actually use in year one. He could not name ten.

That is the trap that catches mid-sized manufacturers constantly. They think bigger software equals a better business. In reality, a system that fits 80% of your needs and goes live in four months will beat a system that fits 95% in four years.

The fit-gap exercise that saved him $400,000

Our team at ERPNext Consulting ran a fit-gap analysis before anyone signed anything. We listed every process that mattered: quoting, purchasing, job costing, delivery scheduling, and warranty tracking. Then we checked which ones were standard and which were honestly different.

The findings stopped him cold. Only six things in his operation were genuinely unusual, and all six could be solved with custom reports and a small workflow adjustment. The giant system would have installed 400 features he never needed just to get the six he did.

What you should do before you even look at software

Run these three tests first:

• Write down the 15 processes that consume 90% of your team’s time, and mark each as standard or different.
• Insist that every vendor demo shows how they handle your truly different process — not the standard one.
• Estimate full cost of ownership per year, including people, updates, and hardware, not just the license fee.

That shop went live on its new system in 14 weeks with one internal champion working part-time. The total cost was less than a tenth of the giant quote, and the annual maintenance bill was barely noticeable. The owner later told me the best money he spent was the fit-gap analysis itself, because it made him see how much of an ERP is just decoration.

Before you take another vendor meeting, steal this move: get a consultant from ERPNext Consulting to spend two days in your office mapping your real bottlenecks first. The answer might be a new system, or it might be a better process. Either way, you will spend your money with your eyes open.

An engineering services firm with 40 people and $8 million in revenue had a cash flow problem that made no sense. They were winning projects, clients were happy, and yet the owner was borrowing to make payroll. The culprit was hiding in the gap between finishing work and actually sending an invoice.

I asked when their invoices were issued. The answer: about 30 days after a project milestone, sometimes 60. One project had $140,000 of finished work sitting unbilled because the project manager could not compile the hours. This is an absurdly common problem, and ERPNext Consulting sees it in almost every services business we walk into.

The fix was not a software change — it was a habit change

We mapped the whole flow: quote, contract, timesheet, milestone approval, invoice. The system was not the bottleneck. The breakdown was that engineers recorded their hours two or three times a week, and the billing person then had to chase project managers for approval.

ERPNext Consulting set up a simple rule: timesheets must be submitted daily, no exceptions. Not weekly, not when the project ends — daily. Project managers got a weekly report showing which engineers were missing entries, and within three weeks the data started arriving on time.

The exact steps we used

Here is the sequence that worked:

1. Freeze project scope and milestones in the system before any work begins, so billing has a clear trigger.
2. Make timesheet entry a hard daily habit, with the manager’s approval happening the next morning.
3. Generate the invoice within five working days of the milestone approval, and track days-unbilled as a real KPI.

The result: unbilled work dropped from $400,000 to $140,000 in four months, and days sales outstanding fell from 58 days to 34 days. For a typical project, the full quote-to-cash cycle now runs about 21 days from signed contract to money in the bank. The owner stopped borrowing for payroll and started funding growth from cash flow. ERPNext Consulting‘s involvement ended with a simple dashboard the office manager updates every Monday.

If you run a services business, do this one check today: list the last five completed milestones and write down today’s date versus the invoice date. If you spot a gap longer than a week, you have already found the money leaking out of your company.

A $25 million industrial parts distributor came to our team at ERPNext Consulting with a brand new problem: business was growing, but customers were complaining more than ever. They had three warehouses in three states, 11,000 SKUs, and every location ran its own spreadsheet. One branch would order 200 units from a supplier while another branch sat on 500 identical units that nobody could see.

The stockout rate had crept up to 15%, which means almost one in every six orders was missing something. The owner told me the most painful part was the phone calls from sales reps in the field asking warehouse staff to check inventory manually. Sales reps were becoming stock-checkers, and they hated it.

Visibility is not a screen — it is a discipline

ERPNext Consulting started by putting all three warehouses into one system with a shared product master. That sounds boring, but it was the turning point. Every bin got a code, every transfer between warehouses got a document, and every location became answerable for its own count.

Suddenly the branch that needed 100 units could see in real time that another branch had 380 and could transfer them overnight instead of ordering new stock. Inter-branch transfers increased by 40% in the first three months, and the company avoided about $60,000 in duplicate purchases.

What every distributor should measure weekly

Stop waiting for monthly reports. Track these three numbers every Monday morning:

• Stockout count in the last seven days, broken down by warehouse — not a monthly average.
• Transfer-on-time rate, because a transfer that takes four days defeats the purpose.
• Slow-moving inventory over 180 days, which is cash sleeping in a corner.

After six months the stockout rate dropped from 15% to 6%, and inventory turnover improved from 3.2 to 5.1 turns per year. The cash released was roughly $800,000, which the owner used to open a fourth branch. ERPNext Consulting also set up a simple alert so purchasing sees a supplier delay before it becomes a customer disappointment.

One honest warning: no system will fix a warehouse where staff do not update counts. If you walk the floor and see handwritten sticky notes on bins, fix that habit first, then bring in the software.

I sat down with a food manufacturer who proudly showed me a product margin report. It said her jam line was making 34%. Then I asked two questions: did that figure include the extra sugar wasted in changeovers, and did it cover the additional freight from split shipments? She went quiet. Her spreadsheet did neither.

That spreadsheet was actually a 40-column Excel monster, and the cost column was mostly a guess. Here is what ERPNext Consulting discovered during the first week: six of her 28 products were losing money while the report showed a profit. She had been subsidizing them for two years without knowing it.

Where the real cost hides

Here is where the true costs were hiding:

• Material waste on the production floor that never got recorded back into the product cost.
• Changeover time — switching from one flavor or size to another eats hours that nobody bills to a product.
• Freight and returns, which accountants often drop into a giant overhead bucket.

ERPNext Consulting rebuilt the costing model so every production order captured actual materials issued, actual hours worked, and actual waste. The team stopped relying on average costs and started comparing each batch against a standard. The numbers were uncomfortable at first, and that is exactly the point — an uncomfortable truth about cost is worth more than a comfortable guess.

What the fix was worth

Within two months the owner repriced six products, one of them by 19%. She also redesigned the changeover schedule, grouping similar products on the same production day to cut setup time by a third. The margin report now tells her team what is really happening.

Here is a useful test you can run tomorrow: pick your top five products and write down what you think each one actually costs. Then check whether waste, changeovers, and freight are part of that number. If they are not, your margin report is lying to you too — and ERPNext Consulting will tell you the hard truth instead of a pretty one.

It was a Thursday afternoon when the owner called. His inventory report said they had 3,400 units of a best-selling part, but the warehouse manager swore the shelf was nearly empty. That gap between screen and reality was costing them about $38,000 a month in rush orders and missed deliveries. If this sounds familiar, keep reading, because that business is not unique.

The ugly number: 18% of stock records were wrong

The first thing ERPNext Consulting did was not install software. They ran a full physical count in two of the three warehouses and compared everything to the spreadsheet records. The result: 18% of the items had incorrect quantities, and some had been wrong for over a year.

The owner told me he was shocked. I told him he should be — 18% error means nearly one in five decisions about buying or selling was based on fiction. We wrote off the ugly differences, set a fresh baseline, and only then started the implementation.

Three numbers that moved in the first 90 days

Here is what changed fastest:

• Stock accuracy climbed from 72% to 96% by making every pickup and put-away a required entry.
• Purchase orders started using real reorder points, and rush freight dropped by two-thirds.
• Sales staff finally saw live inventory at order time, so they stopped confirming dates they couldn’t meet.

The money showed up quickly. With fewer emergency orders and smarter planning, the business freed about $210,000 in cash that had been sitting in duplicated and slow-moving stock. That cash alone paid for the entire implementation effort in about five months.

The one thing that made it stick

No one likes entering data. Staff found excuses for the first three weeks, and the old spreadsheet habit was hard to break. ERPNext Consulting kept the go-live simple, with a rule that nobody touches the same transaction twice. Once people saw their own reports improve, the resistance melted.

If you take one action this week, do a cycle count of your top 50 items before you even talk to a consultant. The numbers you get will tell you how much chaos you are really dealing with — and that single count will make every future decision clearer.

The finance manager at a 22-person clothing exporter kept 14 spreadsheets for orders, fabric purchases, shipping, and invoices. Every month-end, she spent nine days reconciling them, and every month the numbers disagreed somewhere. When she asked the owner for help, the owner asked ERPNext Consulting to look at the mess. The first meeting lasted two hours, and the most useful thing said was: “Stop counting all the spreadsheets and start with the order file.”

Why spreadsheets fail exactly at the moment you grow

A spreadsheet is fine when you handle 30 orders a month. This exporter was handling 220, with fabric bought in bulk and split across multiple orders, and shipping costs that varied by port. The moment one order contains fabric from three purchases, a spreadsheet forces someone to become a human database. That someone was the finance manager, and she was exhausted.

The staged approach that made adoption painless

1. Week one to four: sales orders and a single customer list, replacing two spreadsheets.
2. Week five to eight: purchase orders linked to those sales orders, so fabric costs attached themselves automatically.
3. Week nine to twelve: invoices, payments, and the shipping log, with the finance team reviewing one live dashboard every morning.

Each stage let people keep their old habit until the new one proved itself. By the end of week twelve, the owner could see the profit on every order without asking anyone. Month-end closing dropped from nine days to three, and the finance manager stopped working the first weekend of every month.

What the first spreadsheet to kill is

It is not the biggest one. It is the one that everyone copies from and that nobody owns — for this exporter, it was the order log. The ERPNext Consulting team’s rule of thumb is simple: find the spreadsheet that gets emailed around most often, and that is your starting point. Replace that one file with a shared record and you immediately remove the worst bottleneck — the waiting for other people to send you the latest version.

If you are drowning in your own spreadsheets this month, pick the one file you resent most. That is the one to fix first, and it is the exact move that turned nine-day month-ends into a long weekend for this exporter’s finance team — with ERPNext Consulting guiding the sequence at every step.

They paid for the old system, hired consultants for six months, and still everyone used spreadsheets on the side. That is the story a 50-person machinery parts importer told when they came to ERPNext Consulting. They had run the old “go-live” but the data was full of mistakes, staff hated it, and the finance team reconciled everything in Excel anyway. They were 11 months in, and the system had become an expensive way to store bad information.

How to know your ERP is actually failing

Nobody will announce it. You know it when you see people exporting data from the system just to re-enter it into their own spreadsheets. This importer had exactly that: eleven departments, eleven private spreadsheets, and zero trust in the shared records.

The ERPNext Consulting team’s first move was not to promise a better system. It was to sit in the importing office and watch how orders actually moved from supplier to customer.

• Ask your warehouse team what number they trust more: the system’s stock figure or the notebook on the desk. That tells you everything.
• Check how long month-end closing takes. If it is more than a week, the system is not your source of truth.
• Look at the last 5 invoices: how many times did someone manually edit a price or a date because the system got in the way?

The restart that worked

ERPNext Consulting cut the scope down to three things: purchase orders, stock, and sales invoices — nothing else for the first two months. They made the warehouse staff responsible for the stock counts and gave them the authority to correct errors on the spot. Within four weeks, the private notebooks started disappearing. Six months later, month-end closing went from nine days to three, and the managing director could finally see the gross margin on every single order.

What saved this project was humility

The biggest mistake on the first attempt was trying to automate everything at once. This time, the team took eight weeks just to fix one process the way everyone actually worked, and only then added the next.

If your company is in a similar mess, do not pay for another big launch. Pick the single pain point that hurts the most, run it properly for a month, and make that your proof of concept. That is how a failed project became a working one.