I open up in the morningand message three people.
We built a single operations board for a firm based in Istanbul and Melbourne that delivers turnkey construction, VIP transfers, private flights and security to corporate clients. The problem was not a missing tool; it was a missing shared discipline.
Sector
Construction and VIP services
Built
Operations board
Scope
Two cities, three channels
Status
Live
What the situation wasbefore the build.
The teams worked over WhatsApp, email and phone. Requests arrived, but which request was in which city, at which stage and under whose responsibility was invisible.
- When the Istanbul team opened at nine, they did not know what Melbourne had done overnight.
- Finding out the state of a job meant messaging three separate people.
- At handover, the information stayed on someone's phone.
The pieces builtfor Kora Partners.
- 01
One board
The board, built on Next.js, is fed by the WhatsApp business account and an email gateway. Work from both cities sits on the same screen.
- 02
Automatic classification
Every incoming request is classified on its own by type, city, stage and owner. The classification rule is written down and does not change from person to person.
- 03
Role-based access
Each team member sees the work in their own city and the work assigned to them. The permission structure was written during the build.
- 04
Handover is visible
When a job moves from one city to the other its history travels with it; the person taking it over does not start by asking.
The question got replacedby the answer.
No before and after measurement was taken on this build. The change the operations director describes is this: reading the state of a job off a screen instead of asking for it.
No before and after measurement was taken on this build. The items below are not a measured result; they are the way of working that changed with it.
- Less is lost in the handover between the two cities.
- Which stage a request is at, and who has it, is read off the screen.
- One common ground was built for a shared discipline.
The products usedin this build.
Request handling
Requests from WhatsApp, email and the phone land on the same board.
Repeatable decision support
Request type, city and stage are classified against written rules.
Web and mobile development
The board was written from scratch, and the permission structure was defined during the build.
Integrations
Two cities' channels were tied into one flow; the history used to be lost at handover.
The process first, the proposal after
In a short discovery call we map the process together and tell you plainly whether it is worth automating. If it is not, we say that too.
30 minutes · no preparation needed
