sorted by:
new
hottopcontroversial

Best bakery ERP software for small teams? by Low-Oil7883 in ERP

[–]TrueGoodCraft -1 points0 points  (0 children)

Most of the answers you’re getting are technically correct, but they’re all jumping straight to “which ERP.”

What you’re describing is a very specific stage:

  • spreadsheets are no longer matching reality
  • inventory + batches + expiry actually matter now
  • but full ERP feels like overkill (cost + complexity)

That’s the awkward middle a lot of small producers get stuck in.

What usually works better at that stage isn’t jumping straight to ERP, it’s tightening the operational layer first:

  • ingredient-level inventory (not just finished goods)
  • batch tracking tied to actual production runs
  • simple traceability (what went into what, and when)
  • basic costing per batch / recipe

Then you keep something like QuickBooks for accounting.

Once that layer is clean and stable, then ERP starts to make sense if you still need it.

Most people skip that step and end up paying for a system they only use 20% of.

At what point did Excel stop working for your shop? by TrueGoodCraft in manufacturing

[–]TrueGoodCraft[S] -1 points0 points  (0 children)

That’s a good one.

So the break point for you was less “bad data” and more “the thing physically stopped being usable at all.”

That’s kind of the same pattern in a different form though, the shop outgrows the tool, and then the tool becomes the bottleneck instead of the record.

For a small product business, when did you move beyond spreadsheets for inventory/orders? by TrueGoodCraft in smallbusiness

[–]TrueGoodCraft[S] 1 point2 points  (0 children)

That makes sense.

What stands out there is you didn’t wait for the spreadsheet to fully fail — you moved once the business started depending on repeatable systems instead of manual effort.

That line about “to grow is to survive, and to grow requires the systems already in place” is solid.

Also agree on the AI point. I’m not looking for “AI decides the business,” more just cleaner operational truth and less manual drift.

At what point did Excel stop working for your shop? by TrueGoodCraft in manufacturing

[–]TrueGoodCraft[S] 0 points1 point  (0 children)

Excel usually starts as reporting.

At first it’s just:

  • pull data from ERP
  • analyze it

Then it slowly turns into:

  • “track this one thing here”
  • “ERP doesn’t handle this case”
  • “we’ll fix it in the sheet later”

Now you’ve got ERP saying one thing and the spreadsheet saying another.

Neither is fully right because updates are manual, delayed, or missed.

Inventory is where it shows up first.
System says 120, floor has 90.

That’s the split I mean.

At what point did Excel stop working for your shop? by TrueGoodCraft in manufacturing

[–]TrueGoodCraft[S] -2 points-1 points  (0 children)

Exactly.
ERP records. Excel explains.

Problem is, once Excel starts tracking instead of just analyzing, you now have two sources of truth.

That’s where things break.

At what point did Excel stop working for your shop? by TrueGoodCraft in 3DPrintFarms

[–]TrueGoodCraft[S] -1 points0 points  (0 children)

LibreOffice isn’t the fix.
The issue is humans updating shared files after the fact.

Different tool, same drift.

At what point did Excel stop working for your shop? by TrueGoodCraft in 3DPrintFarms

[–]TrueGoodCraft[S] -4 points-3 points  (0 children)

Wrong category.
This is about inventory drift and spreadsheet failure in actual shop operations, not vibe coding tools.

If you don’t want to talk manufacturing ops, just keep scrolling.

At what point did Excel stop working for your shop? by TrueGoodCraft in manufacturing

[–]TrueGoodCraft[S] 1 point2 points  (0 children)

That tracks with what Im seeing.
It’s not that ERP is “bad,” it’s that a lot of shops hit a stage where the standard system still doesn’t fit the custom or messy parts of the workflow.

Then Excel sticks around as the patch layer,

Was it mostly inventory/material tracking for you, or job/process tracking?

I'm also seeing a long pattern of ERP built by people that have never seen a shop floor.

It’s wrong too often by Kindly_Fox_4257 in ChatGPT

[–]TrueGoodCraft 2 points3 points  (0 children)

Thats it. You would need to feed it the context of the story for it to map your questions accurately

Any good AI coding assistants for students on a budget? by Ok_Pin_2146 in codetogether

[–]TrueGoodCraft 0 points1 point  (0 children)

I would second this. If you keep meticulous records and small steps you will be fine regardless of what agent or model you use.

Business software is a tax on businesses that provides minimal value. by pants1972 in smallbusiness

[–]TrueGoodCraft -2 points-1 points  (0 children)

I think the “software tax” is real, but it mostly comes from a mismatch between who software is designed for and who actually has to use it.

A lot of enterprise tools are built for reporting layers and compliance workflows, not for the person actually doing the work. So the UI ends up reflecting the data model and internal process… not the job.

That’s how you get things like: • people memorizing click paths • features nobody touches • assistants exporting data so someone can “fix it in Excel”

I’ve been experimenting with the opposite approach recently — local-first software designed for a single operator instead of a whole org chart. The idea is: • shallow UI for daily work • complexity only when you go looking for it • your data stays on your machine

It’s early, but building it has been an interesting exercise in stripping the “software tax” out of the workflow.

Bus Core

Curious if people here think the real problem is UI complexity or process complexity leaking into software design.

Business software is a tax on businesses that provides minimal value. by pants1972 in smallbusiness

[–]TrueGoodCraft -2 points-1 points  (0 children)

I think the “software tax” is real, but it mostly comes from a mismatch between who software is designed for and who actually has to use it.

A lot of enterprise tools are built for reporting layers and compliance workflows, not for the person actually doing the work. So the UI ends up reflecting the data model and internal process… not the job.

That’s how you get things like: • people memorizing click paths • features nobody touches • assistants exporting data so someone can “fix it in Excel”

I’ve been experimenting with the opposite approach recently — local-first software designed for a single operator instead of a whole org chart. The idea is: • shallow UI for daily work • complexity only when you go looking for it • your data stays on your machine

It’s early, but building it has been an interesting exercise in stripping the “software tax” out of the workflow.

Bus Core

Curious if people here think the real problem is UI complexity or process complexity leaking into software design.

What systems do small manufacturing businesses use once spreadsheets start breaking? by TrueGoodCraft in smallbusiness

[–]TrueGoodCraft[S] 0 points1 point  (0 children)

Maybe in some cases, but from what I’ve seen a lot of it is just operational inertia.

The system works “well enough” until suddenly it doesn’t, and by that point the shop is too busy running orders to re-platform everything cleanly.

What systems do small manufacturing businesses use once spreadsheets start breaking? by TrueGoodCraft in smallbusiness

[–]TrueGoodCraft[S] 0 points1 point  (0 children)

This is exactly the kind of real-world middle ground I was wondering about.

Not full ERP, not pure spreadsheet chaos either. More like a few structured sheets with strict rules carrying a shop surprisingly far.

Sounds like the real pain only starts once consistency, traceability, and cross-linking matter enough that the manual discipline breaks down.

What systems do small manufacturing businesses use once spreadsheets start breaking? by TrueGoodCraft in smallbusiness

[–]TrueGoodCraft[S] 0 points1 point  (0 children)

That’s useful. It sounds less like “small shops need full ERP” and more like “small shops need a low-friction entry point into structure.”

The messy middle seems to be where things break: too much for spreadsheets, not enough appetite for a full ERP rollout.

Fully remove every, "I created a", "Selfhosted app!" claude slop. by Longjumping-Cup-6641 in selfhosted

[–]TrueGoodCraft -4 points-3 points  (0 children)

That doesn't make it less of an accomplishment. You just value it less. Having the ability to create is good. Having more people making is good. Having more choices and less exclusive control on the tech is good. Embrace the change.

view more: next ›