Build
Custom industrial software, written by people who have been in the panel
Plant operations are full of processes that run on spreadsheets, WhatsApp groups and paper because no off-the-shelf product fits them. We build the software that does — production tracking, quality, traceability, maintenance, energy — connected directly to machine data rather than to a manual entry step.
The problem
The spreadsheet that runs the plant
There is always one. It has forty tabs, three people can edit it, one person understands it, and the entire production planning process depends on it. It is fragile, it has no audit trail, and replacing it with an ERP module was quoted at a number that ended the conversation.
- 01
Critical processes run on a spreadsheet nobody wants to touch
- 02
The same data is entered into three different systems by hand
- 03
The ERP does not fit how the plant actually operates, so it is worked around
- 04
There is no record of who changed what, or when
- 05
Reports are assembled manually and are already out of date when they arrive
What we build
Concrete deliverables
Nouns, not adjectives. This is what actually gets handed over.
- 01
Production and order tracking
Work orders, schedules, actual versus plan, and progress driven by real machine data instead of by someone updating a status.
- 02
Quality and inspection
Inspection plans, in-process checks, non-conformance handling, SPC charts, and quality data linked to the process conditions that produced it.
- 03
Traceability and genealogy
Batch and serial-level traceability linking raw material, process parameters, operator, machine and finished output — with the recall query answerable in minutes.
- 04
Maintenance management
Asset register, preventive schedules, work orders, spares and history, fed by condition data rather than by calendar alone.
- 05
Energy and utilities management
Consumption by asset, shift and product, with cost attribution and anomaly detection.
- 06
APIs and integration services
Documented, versioned APIs so this system is a component of your landscape rather than another island in it.
How it works
The technical path, step by step
Where the engineering decisions actually get made.
- 01
Map the real process
Including the workarounds. The workarounds are where the requirements are; the official process description usually is not.
- 02
Design around the data that exists
Wherever a value can come from a machine, it comes from the machine. Manual entry is a last resort, not a default.
- 03
Build in slices
One usable slice at a time, in production, used by real people, reviewed. Not a twelve-month specification followed by a launch.
- 04
Integrate
ERP, SCADA, monitoring and third-party systems connected through documented interfaces with proper error handling and monitoring.
- 05
Hand over properly
Source code, deployment documentation, architecture notes and runbooks. You should be able to have someone else maintain it.
Protocols & technologies
Specifics, because vague answers cost you money later
Chosen per site according to what is installed, not according to what we would prefer to work with.
| Technology | Where it is used | Engineering note |
|---|---|---|
| Next.js / React / TypeScript | Web applications | Server-rendered where it matters for speed on a shop-floor tablet over patchy Wi-Fi. |
| Node.js / Python | Backend services | Python where the work is analytical or involves signal processing; Node where it is transactional. |
| PostgreSQL / TimescaleDB | Relational and time-series storage | One database engine covering both reduces operational burden significantly. |
| REST / OpenAPI | Documented external interfaces | Versioned, with a published contract, because integrations outlive the teams that built them. |
| MQTT / message queue | Event-driven ingestion | Decouples plant data flow from application availability. |
| Docker / on-prem or cloud | Deployment | The same build runs on a plant server or in your cloud account; you choose, and you can change your mind later. |
| Role-based access + audit log | Governance | Who did what, when, and what the value was before — non-negotiable for quality and compliance use. |
Brownfield
Alongside your ERP, not instead of it
We are rarely replacing an ERP and almost never recommending that you do. The usual, correct pattern is a focused application that handles what the plant actually does, integrated with the ERP for the transactions the ERP owns — material, orders, costing. Each system does what it is good at.
Works with
- SAP, Oracle, Microsoft Dynamics, Tally and Indian mid-market ERPs
- Existing SCADA and historian systems
- Existing quality and laboratory systems
- Spreadsheets, as a data source during migration
- Machine data from our own IIoT layer or from yours
Use cases
What people actually ask us for
Each one is a situation followed by the outcome it produces — not a feature list.
Replacing the critical spreadsheet
NowPlanning depends on a fragile shared file.
AfterA proper application with roles, validation, history and an audit trail — built around the same mental model people already have.
Recall readiness
NowTracing affected batches would take days.
AfterGenealogy queries answered in minutes, with the process conditions attached.
Paperless quality records
NowInspection records on paper, filed in a cupboard.
AfterDigital records with pictures, signatures, timestamps and searchable history.
Shop-floor data entry
NowOperators fill forms that get typed up later.
AfterTablet entry at the point of work, validated, with machine data filled in automatically.
Customer portal
NowCustomers call to ask about order status.
AfterA portal showing live order progress derived from actual production data.
Implementation
How a project runs
Eight stages, each producing something you own. Full detail on the process page.
- 01
Discover
1–2 conversations
- 02
Audit
1–3 days on site
- 03
Design
1–2 weeks
- 04
Engineer
2–8 weeks per phase
- 05
Integrate
1–2 weeks
- 06
Deploy
Your shutdown window
- 07
Monitor
First 4–6 weeks
- 08
Optimise
Ongoing, if you want it
Mixed-vendor machine monitoring rig
Three PLC brands and one machine with no controller at all, read through one gateway and normalised into a single tag model — the situation almost every Indian plant is actually in.
Read the write-upQuestions
Custom Industrial Software — common questions
Why build custom software instead of buying a product?
Buy where a product genuinely fits — ERP, CAD, accounting and most CMMS products are not worth rebuilding. Build where your process is either a competitive advantage or simply does not match any product, and where the alternative is a spreadsheet. The honest test is whether you would be changing your process to fit the product, and whether that change is an improvement or just a concession.
Will we be locked in to you?
You get the source code, the schema, the deployment documentation and the architecture notes, on infrastructure you own. We use mainstream technologies specifically so that another competent team could take it over. We would rather you stay because the work is good than because leaving is difficult.
How do you price software projects?
Fixed price for well-defined scopes, time and materials for exploratory work, and a monthly retainer for continuous development. For anything substantial we usually propose a paid discovery phase first — a few weeks producing a specification, architecture and realistic estimate — so the main quote is based on understanding rather than on guessing.
Can you integrate with SAP?
Yes, through the interfaces your SAP team supports — IDoc, BAPI, OData or an intermediate database, depending on your landscape and your basis team's preferences. In practice the integration design is agreed with whoever governs your SAP environment, and we work to their standards rather than around them.
Do you work on-premises or in the cloud?
Both. Many plants require production data to stay on site, and that is entirely workable — the same application deploys to a plant server. A common arrangement is on-premises for operational data with summaries replicated to the cloud for multi-site visibility.
Which spreadsheet is the problem?
Send us the one everybody is afraid of. It is usually a precise specification of what needs building.