CASE STUDY / OPERATIONS & SCHEDULING

One schedule.
Everyone in sync.

Helping an Abu Dhabi business coordinate people and locations through a shared scheduling platform, with fewer handoffs and a clearer view of the day ahead.

Discover the project

MSD WEB STUDIO / CLIENT STORY

Onimo

From spreadsheet-led coordination to a connected scheduling experience for multi-location teams.

ABU DHABI, UAE

Client: Onimo
Location: Abu Dhabi, UAE
Focus: Multi-location scheduling
Our contribution: Product engineering & QA

40%

Faster scheduling

Reduction in scheduling cycle time.

One

Shared operational view

Schedules, updates, and notifications together.

Built in

Access & accountability

Role-based permissions and an audit trail.

01 / THE CHALLENGE

When the schedule changes, everything else moves with it.

For a team working across locations, a schedule is more than a calendar. It connects people, availability, and daily operations. Managing that through spreadsheets left room for double-bookings, missed alerts, and changes that were difficult to trace.

THE BRIEF

Create a responsive scheduling platform that supports concurrent changes, keeps the right people informed, and makes responsibility clear.

THE STARTING POINT

Working around the tools.

Separate spreadsheets to coordinate daily activity
Missed updates and conflicting bookings
No consistent record of who changed what

THE CONNECTED EXPERIENCE

Tools working together.

A shared schedule for multi-location coordination
Notifications connected to scheduling changes
Permission-based access with traceable activity

02 / THE SOLUTION

Designed around
the people using it.

A schedule that keeps up

A Next.js interface with optimistic updates makes slot changes feel immediate, helping teams stay focused on the work rather than the waiting.

The right information, to the right people

Queue-based notifications connect scheduling activity to timely updates, while role-based access defines what each person can manage.

Changes with a clear history

Audit logging records scheduling activity, giving operations a more dependable way to trace decisions and support reporting.

A CONNECTED PRODUCT JOURNEY

Less chasing. More coordination.

The experience connects the change itself with the people and records that depend on it. One clear sequence replaces a chain of manual follow-ups.

Next.jsNode.jsTypeScript

Scheduling workflow

CONNECTED OPERATIONS

01
Update a slot
Make a scheduling change in a shared workspace.
02
Keep people informed
Route updates through background notifications.
03
Keep the history
Record the activity for visibility and review.

Workflow illustration · Not a product screenshot

Planning and documenting a project workshop

CLARITY IN THE PLAN. CARE IN THE DELIVERY.

03 / THE DELIVERY

Built together.
Thought through.

Focused delivery

Two-week sprints and regular releases kept implementation structured and feedback close to the work.

Quality in the workflow

Regression testing was tied to availability objectives, making reliability part of delivery rather than an afterthought.

Visibility after release

Monitoring and alerting supported the operating team, with communication aligned to shared UAE working hours.

Next.jsNode.jsTypeScriptRole-based accessBackground jobsAudit logging

04 / THE IMPACT

A clearer day for the whole team.

Scheduling cycle time was reduced by 40%. Alongside the faster workflow, the platform brought scheduling updates, notifications, and activity history into one connected system.

The value is in the everyday experience: less manual coordination, clearer ownership, and a schedule people can work from together.

40%Faster schedulingProject-reported improvement

WHAT COULD WORK BETTER FOR YOUR TEAM?

Let’s explore your next chapter.

Bring the challenge. We’ll help shape a practical way forward.

Talk to our team

ANOTHER STORY FROM ABU DHABI

Power of Music

Connecting enrollment, tuition, and teaching schedules.

Explore the case study

One schedule.Everyone in sync.