CASE STUDY · MK OPS
Bringing field operations into one place
Work done in the field, visible in the office at the same time. MK OPS brings telecom and fiber field operations, from daily work entries and approvals to crews, materials and progress payments, into one system that each company uses in its own space.
- Sector
- FIELD OPERATIONS
- What we built
- Custom software · Business systems
- Status
- Live demo


Whose problem?
Companies that run many crews, projects and materials at once on telecom and fiber infrastructure work. From crew leaders in the field to operations and accounting in the office, different people see different parts of the job.
- Field crews and crew leaders working on different projects on the same day
- Project and company managers who plan, check and approve the work
- The warehouse side tracking materials, vehicles and equipment
- The office preparing progress payments and reports
What was the problem?
In the field, work moves fast; information ends up scattered across messages, photos and separate spreadsheets. Which crew is doing what and where, which job is waiting for approval, where a material went: often visible only at the end of the day, pieced together by hand.
- Daily work stays in messages and paper forms
- Which job is waiting for approval stays unclear until the end of the day
- Material issues don't match the stock
- Crew earnings and progress payments are collected by hand at period end
- Several companies' data gets mixed up in the same spreadsheets
How did we approach it?
We started from the flow of a day in the field rather than from screens: work entries during the day, review and approval in the evening, reports at period end. The aim: whoever sees a piece of information first can enter it directly, and everyone sees only what is useful to them.
- Thinking in roles: crew leaders, project managers and company managers see different things
- Quick entry on the phone in the field, bulk review on the desktop in the office
- A clear approval flow: draft, submitted, approved or rejected
- Collecting records around progress payment periods
Each company in its own space
We built MK OPS as a multi-tenant SaaS that several companies can use, each in its own isolated space. Every company manages its crews, projects, field work and approvals in its own workspace; role-based permissions make sure everyone sees only their own work.
- Per-company data isolation and role-based permissions
- Daily field work entry and approval flow
- Material delivery notes and stock tracking
- Crew earnings, company share and progress payment periods
- Audit log, Excel and PDF reports
- Interface in Turkish, English, German, French and Spanish
The resulting system



All records on these screens are sample data; they contain no real people, companies or projects.
Core modules
Daily work entry and approval
Work done in the field is recorded the same day; a manager approves it or asks for a correction from one list.
Crew and project management
Crews, projects and work items are defined per company; daily entries are made against them.
Material delivery notes and stock
Material issues are recorded with delivery notes; the stock updates from the same records.
Vehicles and equipment
Vehicles and equipment are kept in one place together with the crews.
Progress payment periods
Crew earnings and the company share are calculated per period from the same records.
Company space and roles
Each company works in its own isolated space; company managers, project managers and crew leaders see different screens.
Audit log
Who changed what and when is kept on record.
Reports and languages
Reports export to Excel and PDF; the interface can be used in five languages.
Where is it today?
- MK OPSLive demoProduct website
Related work
Related solutions
Facing a similar problem?
If you want to bring field work and office tracking together, tell us how your day runs today and we’ll shape the right approach together.


