📝
A single logging form
Sometimes one good form is the whole solution — for an operator to capture process details into a spreadsheet, your server, or your ERP.
- Built around one real task
- Standalone or into your ERP
- No new system to learn
Built around your process, not a product
We scale the solution to the problem — never the other way around. A digital system is only as good as its understanding of the real one.
What we build
From the smallest useful tool to a full integrated suite — what we build depends entirely on where your pain is.
💬
Chat-based logging & alerts
Log data or receive alarms through WhatsApp or Telegram — into a text file or a custom ERPNext doctype, with scheduled or alarm-driven notifications.
- WhatsApp / Telegram
- Scheduled & alarm scripts
- Into ERPNext v15
🌡️
Machine & environment logging
Continuous capture from critical equipment — for example, chiller-room temperature logged into a spreadsheet, MySQL, or an ERPNext doctype.
- Workstation data capture
- Cold-chain monitoring
- Standalone or integrated
📊
Dashboards & monitoring
From a simple spreadsheet pivot chart to integrated Metabase, Grafana, or Tableau — with alarms when a metric drifts out of range.
- Live reporting
- KPI visualisation
- Drift alarms
🏭
A complete ERP suite
Built on ERPNext v15 by Frappe, with your manufacturing process at the centre — and full access to both the platform code and our customizations.
- ERPNext v15 (Frappe)
- Production-first
- No vendor lock-in
🤖
AI chat over your own data
Ask questions of your production database in plain language, inside a defined, trustworthy scope — scripted and semi-scripted queries you can rely on.
- Plain-language queries
- Linked to your database
- Bounded & reliable
Built for the hard kind of factory
We specialise in non-discrete manufacturing — plants where one unit of input doesn't cleanly become one unit of output. It's where recipes don't behave like Lego, and where generic systems quietly break down.
🍶
Food & pharmaceutical
Recipe-driven batches where a correctly weighed input can still yield a variable output — and where storage, sequencing, and line setup all have to be planned together.
🪑
Furniture & assembly
Made and bought parts, shared sub-assemblies, and variable inputs — four metres of beam should make four legs but often takes six. Batching has to balance lead time and setup.
🔁
Work-in-progress reality
Sub-recipes that must finish together or wait in storage, bottlenecks that move, and decisions about what to release next — the messy parts we model rather than ignore.
How an EmpiFlow project works
Deliberate, evidence-first, and staged — so you adopt the system gradually, never in a risky overnight switch.
1
Discovery
We interview the people who run the system and review the data, KPIs, and structures you already have. This is the base of every quote.
2
Design the data structure
We design how data is captured and documented, shaped around your specific pain point — so the system can answer your real questions.
3
Build the business rules
We encode the rules that reflect how your process actually behaves, with the assumptions and limits documented in plain language.
4
Dashboards & support
We add reporting and monitoring where it helps. For large, integrated systems, ongoing technical support is available on an annual basis.
What you can count on
- ✓ A project plan with milestones you sign off before the next begins.
- ✓ Payment tied to delivered milestones, agreed up front in the contract.
- ✓ Gradual rollout of sub-systems — no sudden migration off what you use today.
- ✓ Training for your users and administrators before each sub-system goes live.
- ✓ A user guide and a system guide documenting the assumptions and limits we coded.
- ✓ Full access to the code when we use ERPNext — Frappe's and ours. No lock-in.
Not sure which of these you need?
That's what the discovery phase is for. Tell us what's slowing you down and we'll scope it together.
Talk to us about your plant