One system for projects, budgets, payments and people.
Like every Ektra project, this one began with a question, not a feature list: what is the one thing holding this business back? The fix came after the answer, and the result was judged by what it removed.
A machinery company ran its operations on spreadsheets and chat groups.
Project budgets in one file, payments and collections in another, HR requests by message, fleet bookings by phone.
We built an in-house operations system with 31 modules, the ones the company lives in.
Projects and project logs, budgets with role based permissions, payment tracking and collections, quotations and revenue reports, dashboards, HR with announcements and open positions, fleet vehicles with requests and a schedule, boards for team work, chat, business documents and presentations, access requests, and a modules and roles admin.
From the first meeting to the work it does today
Each department’s sheets and the decisions they fed.
Modules in order of pain, budgets and payments first.
A dark, card based workspace with a home page per role.
31 modules on one data model, with live updates and notifications.
Module by module with the people who use it, real data imported early.
Rolled out team by team, the old sheets retired.
New modules as departments asked, each with a written guide.
Tell us what slows your business down. In one meeting we find the constraint behind it and show you what removes it.
