How it works
From operational chaos to a connected business system
Five steps, in this order, every time. The first two produce no software at all — and they are the ones that decide whether the software gets used. This page describes what each stage produces, what we need from you, and the ways these projects fail.
- Understand and Map are priced separately — and the map is yours
- Built in phases, so something is in real use within weeks
- No big-bang go-live
- Documented and handover-ready from the start
The five steps
What each stage actually produces
- 01
Understand
We sit with each department and learn the process as it is actually run — including the workarounds, the informal exceptions and the things people do because the official way does not work. This is where most of the value of the project is decided.
You getA written map of your current processes, departments and bottlenecks
1–2 weeks
- 02
Map
We trace how information moves between people, departments and systems: where it is created, where it is re-entered, where it is lost, and where a decision waits on something nobody can see. The re-entry points are almost always the expensive ones.
You getAn information flow map, with every handoff and duplication marked
1–2 weeks
- 03
Design
We design the target workflow — owners, rules, gates, automations and the screens each role needs — and agree it with the people who will live in it. We also agree what we are deliberately not building yet, and say so plainly.
You getA workflow design, screen list and phased build plan with scope you have signed off
2–3 weeks
- 04
Build
We build in phases, so one department is genuinely using something early rather than waiting for a full system. Each phase is delivered, tested with real data and put into use before the next begins — which is also how the awkward details get found while they are still cheap.
You getWorking software in real use, phase by phase, with integrations and reports
Phased, typically 4–12 weeks per phase
- 05
Optimize
After go-live we look at what is actually being used, which alerts are being acted on and which are being ignored, where people are still keeping a parallel sheet, and what the data now reveals that nobody could see before. Then we improve it.
You getUsage review, workflow refinements, new reports and ongoing support
Ongoing
What we are changing
Not the tools. The joins between them.
How the work moves today
Eight handoffs, four tools, no record
Sales team
Confirms an order with the customer
WhatsAppData lost here
Tells production — nothing is recorded
Excel
Someone re-types the same order by hand
Production
Starts work from a printout
PaperData lost here
Actual output stays on the shop floor
Purchase
Learns material is short — late
Phone calls
Everyone chases status
Management
Asks four people for one report
Every tool in this chain works. The chain does not — because nothing carries forward, and no one can see the whole of it.
One connected workflow
One entry, seven departments, nothing re-typed
Sales
Order confirmed — once, in one place
Production
Work order created automatically
Purchase
Shortages raised before work starts
Inventory
Consumption and stock update themselves
Quality
Inspection triggered on completion
Dispatch
Only passed material can be packed
Finance
Invoice raised from what actually shipped
Management dashboard
Every step visible as it happens
The same eight steps — but each one hands the next its data, and every one of them reports to the same dashboard.
What we need from you
Four things, and none of them are documents
- 01
Time with the people who run the process
An hour each with the store keeper, the line supervisor, the purchase person and whoever compiles the reports. Not documents, and not only managers — the people who actually do the work know where it breaks.
- 02
A decision-maker who can settle rules
Approval limits, who may override, what counts as confirmed. These are business decisions, and a project stalls when nobody is empowered to make them.
- 03
Honesty about the workarounds
Every operation has informal practices that keep it running. If we design around the official process and not the real one, the system will be abandoned within a month.
- 04
Willingness to switch off the old way
Running the spreadsheet in parallel forever guarantees the system stays second. At some agreed point the new way has to become the only way for that process.
Being straight about it
Five ways this kind of project fails
Trying to build everything at once
We phase deliberately. One department in real use beats six departments in review. It also surfaces the awkward details while they are still cheap to change.
Designing for managers, not for the floor
Shop-floor screens are designed separately and tested with the people who will use them. If entering a shift's production takes more than a few seconds, the data will be late and the project will fail quietly.
A big-bang go-live
We sequence by process rather than switching everything on one Monday, and run old and new in parallel where the risk warrants it.
Automating a process that should be removed
If a step exists only because of a limitation that no longer applies, we will say so. Digitising waste just makes it faster.
Dependence on one developer
Data model, integrations and deployment are documented as part of delivery. You should be able to hand the system to your own team or another vendor.
Capabilities
Everything your operations need to run with less manual work
How do we stop chasing approvals and handoffs?
Work moves without being pushed
- Workflow automation
- Multi-level approval systems
- Task management and assignment
- Notifications and alerts
- Automated reminders and escalation
- Department-to-department handoffs
How do we stop entering the same thing three times?
Data is captured once, where the work happens
- Digital forms and data capture
- Form builders for new processes
- Shop-floor and mobile entry screens
- Validation at the point of entry
- Document management and attachments
- Barcode and QR support where labelling exists
How do we know what is happening without asking?
Management can see the operation
- Custom role-based dashboards
- Real-time operational reports
- KPI and exception reporting
- Scheduled automated reports
- Drill-down from any number to its transactions
- Multi-plant consolidated views
Can the system represent how we actually produce?
The operational core is modelled properly
- Production and work-order workflows
- Inventory and material workflows
- Purchase and vendor workflows
- Quality and inspection workflows
- Job work and subcontracting
- Lot, batch and grade traceability
Who did what, and can we show it?
Responsibility is clear and provable
- Role-based access control
- Field-level permissions
- Complete audit trails
- Approval history on every decision
- Employee and HR workflows
- Back-dated entry control
Do we have to replace our existing software?
It works with what you already run
- API development and integration
- ERP integration and extension
- Accounting software integration
- CRM integration
- Data migration and cleaning
- Reconciliation reporting between systems
Before / after
What changes after your operations become digital?
Before
After
Excel everywhere
One system, one record
WhatsApp communication
Workflows with owners and a clock
Manual approvals
Digital approvals that escalate
Employee dependency
Process consistency the system enforces
Delayed reports
Real-time dashboards
Disconnected departments
Connected departments
Repeated data entry
Centralised data, entered once
Management asking for updates
Management seeing what is happening
Why Nij Web Solutions
We don't start with software. We start with your process.
Process first
We map the workflow before we write software. If we find a step that should be removed rather than digitised, we say so — digitising waste just makes it faster.
Custom built
The system is designed around your process, your identifiers and your definitions. Where a package would genuinely serve you better, we will tell you that instead of building.
Operations focused
We work in the vocabulary of departments, approvals, lots, shifts and dispatch. You should not have to translate your business into software terms for us.
Automation first
Before adding a screen we ask whether a person needs to be involved at all. The best workflow step is the one nobody has to perform.
Data visibility
Every project is judged on whether management can see something it could not see before — and whether the number can be traced to the transaction behind it.
Scalable systems
Built for the second plant, the tenth user role and the process change you have not had yet. Configuration over code, documented and handover-ready.
Questions
How we work — the practical questions
Still unsure whether your processes are a fit? Walk us through one of them.
Book an Operations Automation ConsultationDo you work on fixed price or time and materials?
Usually fixed price per phase, because the phases are small enough to scope honestly. The mapping and design stages are fixed price on their own, and they are deliberately separable — you can stop after them and take the process map elsewhere if you want to.
What if we do not know what we need yet?
That is the normal starting position, and it is what the first two steps are for. The output of Understand and Map is a written picture of your own operation, which is useful to you whether or not you build anything.
Can we stop after the mapping stage?
Yes, and the map is yours. We price it separately for exactly that reason. It would be a strange incentive if the only way to find out what you need was to commit to us building it.
How do you handle changes during the build?
Small refinements inside an agreed phase are normal and expected — operational detail surfaces once people use something real. A change that alters the shape of the phase gets re-scoped and priced openly rather than absorbed quietly and delivered late.
Who tests the system?
We do, and then the people who will use it do, with real data from your own operation. Testing with invented data is how systems reach go-live looking correct and failing on the first genuine edge case.
What does support look like after go-live?
Defect fixes, process changes as your operation evolves, new reports and new units. We also review which alerts are actually being acted on — an alert nobody acts on should be deleted rather than tolerated.
Next step
Start with step one
An hour on a call, walking through one process end to end. You will get a clearer view of your own bottleneck whether or not anything comes of it.