The Small Shop's Guide to Going Digital (Without an ERP Budget)

The spreadsheet works. That is the trap. Your mold list lives in Excel, your maintenance history lives in a binder, and your PM schedule lives in someone's head. It all functions, right up until the day it does not: a mold gets double booked, a PM slips three months, or your best setup tech retires and takes the tribal knowledge with him. Then someone says the fix is an ERP, and the quotes start at five figures.

Here is the part most software vendors will not tell you: you probably do not need the ERP. Not yet, maybe not ever.

The ERP Math Rarely Works for a Small Shop

Full manufacturing systems such as Epicor, Made2Manage, or Plex are built for plants with hundreds of employees and a dedicated IT department. They track purchasing, inventory, scheduling, accounting, quality, and yes, tooling, all in one package. That breadth is exactly why they cost what they cost: implementations commonly run weeks to months, and the bill for licensing plus consultants plus customization lands firmly in five figures, often six.

A twenty person shop does not have a purchasing module problem. It has a much smaller set of problems, and all of them are about the molds.

The Three Things Worth Digitizing First

Almost every operational headache in a small molding or tool and die shop traces back to one of three gaps.

  • A mold registry with history. One place where every mold lives with its ID, location, shot count, and everything that has ever happened to it. Repairs, reworks, cavity changes, who worked on it and when. Not a spreadsheet that three people edit and nobody trusts. A record.
  • PM triggers that fire themselves. Maintenance due at shot counts or time intervals, tracked automatically, with overdue items visible without anyone walking the floor with a clipboard.
  • Findability. Can a new hire locate the right mold, its latest setup sheet, and its repair history in under a minute? If the answer requires asking the guy who has been here twenty years, that is a gap.

Everything else (quoting, accounting, shipping, CRM) can stay wherever it is today. Nail these three and the rest of the digitization conversation gets much easier, because you will have clean data to build on.

A Phased Path That Fits in Weekends

You do not need a go-live date and a consultant. You need a series of weekends.

  • Weekend one: List every mold. ID, location, shot count if you have it. Imperfect is fine; absent is not.
  • Weekend two: Backfill history for the ten molds that cause the most trouble. Failures, reworks, recurring issues.
  • Weekend three: Set PM triggers on those same ten. Shot count or calendar, whatever reflects how they actually wear.
  • Weekend four: Add photos of critical steel: cavities, cores, slides, shutoffs. Photos end arguments about what condition a mold was in.
  • Weekend five and beyond: One mold per week until the registry is complete. Then start logging every PM and repair as it happens, so the history builds itself.

Five weekends, and the backbone exists. No implementation project. No workflow redesign. The shop keeps running exactly as it did; the records just stop living in people's heads.

What You Do Not Need on Day One

Vendors love to demo the future. Resist most of it.

  • Tablets on every machine. A shared shop PC or the foreman's phone is plenty until logging becomes a habit. Hardware first is how projects die.
  • Sensor and IoT everything. Press data is genuinely useful, but only once someone is acting on the mold record. Instrument a shop that cannot find its molds and you get expensive silence.
  • Integrations. Until the mold data exists and is clean, there is nothing worth connecting. Import a spreadsheet, not an architecture.
  • Per seat licenses and modules. Pricing that penalizes the second user or gates history behind an enterprise tier is a small shop tax.

Every one of these can come later. None of them replaces the registry, the triggers, or the findability.

The Honest Cost Comparison

An ERP implementation for a small shop: months of discovery, five to six figures, and a real risk of stalling out before go live. The three things above: five weekends and a tool built for the job. MoldDB starts at transparent published pricing, because a shop owner should be able to see the number before sitting through a demo. If the registry is your bottleneck, start with what a mold record should contain and judge your spreadsheet against it.

« All articles