One set of records from the indent to the invoice, built with a working factory
We build data, analytics and applications for manufacturers, and we make Uloborus, our own manufacturing system for Indian process plants. Buying, receiving, quality, stock, making, selling, dispatch and invoicing sit on one thread, with the GST paperwork that travels with it, built alongside Rajaram Consumer Care in Sangli rather than for a demo.
- Our product for this industry
- Uloborus
- Built for
- Batch plants, 20 to 300 people
- Modules
- Eight, one record set
- Design partner
- Rajaram Consumer Care, Sangli
On this pageWhat we hear in manufacturing
What we hear in manufacturing
Each of these comes from building Uloborus or from an article we wrote for manufacturers.
- 01A complaint arrives with a batch code on it
Whether you can trace that batch, and what went into it, within an hour was settled years earlier by how you record consumption.
- 02The plant head hears about a stopped line from someone on the stairs
The data was there the whole time, on a dashboard open in an office nobody was sitting in.
- 03Nobody fills in the form on the line
Capture at the machine fails for physical and social reasons long before technical ones. The designs that survive ask for less and give the operator something back.
- 04Two or three days a month matching despatch to invoices
The despatch register and the sales register have to agree, so somebody makes them agree by hand. The paperwork should fall out of the transaction instead.
- 05Yield is drifting and everyone has an explanation
Before funding an improvement project, check that input, output and the standard are still being captured the way they were four months ago.
- 06The ERP is frozen
Three extra fields on the batch release screen, and the answer is still no. The work still has to happen around it.
What you can inspect
What we have delivered
We have not published a manufacturing case study. What you can inspect is Uloborus itself, and the figures it publishes.
Buying, receiving, quality, stock, making, selling, dispatch and invoicing, seen from eight desks.
Today, Alerts, Stock, Orders, Money and Parties. Read only.
Batch plants in cosmeceuticals, food, speciality chemicals, pharma ancillaries and their contract manufacturers.
No card, so you can put a real purchase order through it first.
Read the full accounts
- ProductUloborus runs buying, making and dispatch on one set of records
Every module was built against how a working plant actually runs, then argued about, then changed.
See Uloborus ↗ - Where it does not fitDiscrete assembly, or a plant with no quality step
Batches and formulas run all the way into the data model, and half the value is holding material until somebody signs for it. If that is not your plant, Week 1 will say so.
Where to start
Four places a first engagement can begin. Week 1 tells you which one comes first.
- ProductUloborus, if you have outgrown the spreadsheet
For process plants that cannot stop for six months of implementation.
See Uloborus ↗ - ProductThe number on the plant head's phone
Glimvia: mobile-first KPI alerting for the people who need the number first and are not sitting at a desk.
See Glimvia ↗ - ApplicationsOff paper and WhatsApp
Registers, approvals and the forms on the line, moved into a system people actually use.
Process digitisation ↗ - AnalyticsThe screen a shift runs from
Exceptions rather than totals, an owner and a clock on each, and the action taken where the signal appeared.
Command centres ↗
How the first weeks run
The same three phases in every industry. What changes is what we build in them.
- Week 1, fixed feeAudit
Two calls and a written one-pager. Yours to keep whether or not you continue.
- Weeks 2 to 6Build
Something real in front of real users by week three. Median six weeks to the first production-grade artefact.
- Week 7 onwardOperate
Quarterly reviews and on-call governance. The people who built it pick up the phone.
Questions we get asked
Further reading
- A recall is a query, and you find out in an hour whether you can run itWhether you can trace that code in an hour was settled years earlier.
- The shop floor will not fill in a form it gets nothing back fromThe designs that survive ask for less and give the operator something back.
- Yield variance is usually a measurement problem before it is a process problemCheck the measurement before funding the improvement project.
Start with the Week 1 audit
Two calls and a written one-pager naming the first thing worth building, and who owns it. You keep it either way. NDA-friendly, fixed scope. Write to hello@woodfrog.tech.
