Service
Business management systems
Work that is not recorded is not measured - and cannot be improved.
Off-the-shelf software forces the business to fit it; a system built for you fits the business. We build management systems around the real process - who opens a call, who executes, what closed and when; how a raw-material price cascades through the product tree - and we hold to the thing that decides whether an internal system lives or dies: it must be easier to work with than without.
Let's TalkPrefer to write? Send an enquiry through the form
What it gives you
- A full life cycle for every task - opened, assigned, executed, closed with a record
- The manager sees everything open on one screen instead of chasing updates
- Calculations that update themselves - one change cascades everywhere it touches
- Import from the existing Excel - the system starts from what exists, not from zero
Who this is for
- An organisation where the work is not recorded in one place, so there is no way to know what is open right now without calling to ask.
- A business running an entire process in a spreadsheet that has reached the size where a broken formula is no longer unusual.
- A business that looked at off-the-shelf software and found it would have to change its own process to fit inside it.
- A team with different roles that need to see different things - a technician in the field, a manager, bookkeeping.
How the work runs, stage by stage
Mapping the process and the roles
Who opens, who executes, who approves, and what exactly counts as "closed". It looks like an administrative question and it is the decision that determines the structure of the system.
Import from what exists
The system starts from what already exists rather than from zero. The current spreadsheet is imported, and what is in it is day-one data - otherwise nobody moves over.
Building the life cycle
Opened, assigned, executed, closed with a record. Any stage with no screen is a stage that will go back to WhatsApp.
Screens per role
A manager sees everything open on one screen; whoever is in the field sees what is theirs and nothing else. A system that shows everyone the same thing is a system nobody updates.
Running it in
The only test that matters is that it is easier to work with the system than without it. In the first weeks we fix according to what actually happens, and that is included.
What moves the price
A management system is priced by the number of processes it holds and by what it has to connect to. A project usually starts in the low thousands of shekels, and a system with several roles and integrations costs more; the range arrives in a written proposal. These are the things that move it:
- How many processes the system holds - work orders alone, or pricing, stock and reporting as well.
- How many roles there are, and how many different screens they need.
- How complex the calculations are. Cascading a raw-material price through a product tree is not one computed field.
- The state of the existing data: importing one tidy spreadsheet is different work from importing five files that disagree with each other.
- Integrations with systems already running in the business.
- The timeline: a system takes 4-6 weeks.
A work-order management system
A work order is the process in which it is easiest to lose work. It opens on the phone, moves through WhatsApp, gets done in the field and closes without anyone recording what was actually done. In that state there is no way to know how many calls are open now, who is handling what, or how long a call takes to close - and therefore nothing to improve. A work-order management system makes that cycle explicit: every call opens with the details needed to handle it, is assigned to whoever will do it, is updated from the field and closes with a record. Above that sits a single manager screen showing everything open. We have built this and are not describing it from theory: Air Manage is a work-order system in daily organisational use, with a full life cycle per call. Its case study sets out what was built there.
- A call opened with the details needed to handle it, rather than chased by phone afterwards.
- Assignment to a technician or a team, so the person responsible is on the call itself.
- Updates from the field, so the status is correct without a chasing call.
- A documented close: what was done, when, and by whom.
- One manager screen with every open call, ordered by what is urgent.
Systems we built
A work-order system in daily organisational use, and a costing system replacing an entire spreadsheet.
- BOM & RecipesBill-of-materials and recipe management with automatic costing - cost, retail and wholesale pricing - importing straight from existing Excel files.
- Air ManageTask management for maintenance, upkeep and cleaning teams - assignment, tracking and closing work orders. In daily use inside an organisation.
Common questions
Why not off-the-shelf software that costs less?
Sometimes it is, and we will say so. Off-the-shelf pays off when your process resembles the one it assumes. The gap opens when the process has to change to fit inside it - then the licence is cheap and the work around it is expensive, and that work comes back every month.
Can we import the spreadsheet we work with today?
Yes, and it is part of the process rather than an extra. A system that starts empty does not get adopted - nobody retypes three years of data. The import is the stage after the mapping.
What makes sure the team actually uses it?
Nothing except it being easier to work with than without. That is the test we hold every screen to. Screens per role are part of it: whoever is in the field sees what is theirs rather than a form designed for a manager.
Can it talk to our bookkeeping or ERP?
Yes, where there is something to talk to. If the system on the other side has a documented API it is days of work; if not, we look at what is possible - a scheduled export is sometimes the right answer. We built a two-way ODOO sync on another project, and its case study sets out how.
Who owns the system and the data?
You do. The code is transferred to you and the data is yours at any moment, export included. An internal system you cannot take with you is a dependency, and we sell the opposite of that.