jugaad
studio
Manufacturing

Production, stock and dispatch — connected, and honest about itself.

You already know what your factory does. The problem is that no single place knows all of it at once, so every answer has to be assembled from three people and a spreadsheet.

How it runs today, and what changes.

Today
  • Stage status lives on a whiteboard and in supervisors' heads
  • Material goes out for job work and comes back as a note in a diary
  • Cutting can start before the trims have actually arrived
  • Rejections are counted at the end, when the shortfall shows up
  • Stock on screen and stock in the godown diverge until the next count
After
  • Every order's current stage visible without asking anyone
  • Vendor dispatch and receipt recorded with dates and quantities
  • A stage that refuses to open until the one before it is complete
  • Rejections logged at the stage they happen, so loss is traceable
  • Stock that moves when material moves, not at month end

What matters most here

Stage-wise production tracking

Your actual stages, in your actual order, with each one gated on the last. Not a generic three-step workflow that you then have to interpret.

Job-work and vendor register

What went out, to whom, when, how much came back and what was short. The single most common gap we see in manufacturing businesses.

Lot and roll traceability

Traceability that survives cutting, so a finished piece still maps back to the lot it came from when a customer raises a quality question months later.

Rejection and wastage capture

Recorded at the stage it occurs. Shortfall then has a location and a cause rather than appearing as an unexplained difference at dispatch.

A floor view and an owner view

The supervisor sees the queue in front of them. The owner sees what is stuck, what ships today and what will be late.

Questions people actually ask

We are a small unit. Is custom software overkill?
Sometimes, and we will say so. The test is not your size — it is whether your process is specific enough that products do not fit, and whether the time currently lost to coordination is worth more than the build. For a small unit running a standard process, a product is usually the better answer.
Our supervisors are not comfortable with computers.
That is a design constraint, not a blocker, and it is the main reason shop-floor screens fail. In practice it means very few fields, large targets, a phone rather than a desktop, and local-language labels where that helps. If the floor will not use it, nothing else about the system matters.
Can it handle job work sent to outside vendors?
Yes, and it is usually the first thing we build, because it is where visibility is worst. Material out, material in, ageing, and a clear list of what is sitting with whom right now.
Do you handle GST and invoicing?
We handle the operational side and connect to your accounting system for statutory work. Tally already does GST properly and we would rather integrate with it than rebuild it badly.
Let's talk

Tell us what wastes the most time.

Fifteen minutes is usually enough to know whether it's worth building. If it isn't, we'll say so.

No pitch deck. A 15-minute call to see if it's worth building.