Case study 05

Extending an Existing Enterprise Platform with a New HR Domain

New HR capability inside OfficeAnyWhere — not a disconnected HR product

Client
Delmon Group
Product
OfficeAnyWhere — HR module
Location
Saudi Arabia
Industry
Enterprise / HR
Project type
Platform extension
Role
Database, backend & deployment

Overview

Business context

OfficeAnyWhere was an existing enterprise business platform.

The requirement wasn’t to build a completely separate HR application. The challenge was to introduce a new HR domain inside the existing product while maintaining compatibility with its existing architecture and deployment environment.

I created the HR module from the ground up within the existing platform. The frontend was implemented with Angular.

Business challenge

The problem

Adding HR as a bolt-on product would have created another disconnected system. The client needed HR capability that lived inside OfficeAnyWhere.

  • Fit the existing database
  • Respect existing authentication/authorization
  • Align with backend architecture
  • Integrate with application workflows
  • Deploy into the existing environment

The objective was to extend the existing platform rather than create another disconnected system.

Impact

Why the problem mattered

  1. 01

    Enterprise teams already operated inside OfficeAnyWhere — a separate HR app would fragment workflows.

  2. 02

    Greenfield habits fail when the real constraint is compatibility with production architecture.

  3. 03

    A substantial business domain had to land without destabilizing existing modules.

Engineering

Key engineering challenges

Technical constraints that shaped the architecture and delivery approach.

01

Extend, don’t fork

Adding a substantial business domain to an existing product requires a different mindset from greenfield development. The module needed to fit the existing database, authentication/authorization, backend architecture, application workflows, and deployment environment.

Ownership

My role

My responsibilities included:

  • Database design
  • Backend development
  • HR business logic
  • API development
  • Integration with the existing application
  • Deployment

Solution

How it was solved

The HR module was built from the ground up as a domain inside OfficeAnyWhere — sharing the platform’s .NET backend and MS SQL foundation rather than standing up a parallel product.

  • HR domain modeled for the existing platform boundaries
  • APIs integrated with existing application surfaces
  • Angular frontend within the established product
  • Deployment into the existing Plesk Windows Server environment

Architecture

Platform extension

HR as a peer domain beside existing OfficeAnyWhere modules — same .NET 6 / MS SQL stack.

OFFICEANYWHERE OfficeAnyWhere Platform Existing Modules Established domains Existing Modules Shared auth & workflows HR Module New domain .NET 6 MS SQL

Results

HR capability integrated into OfficeAnyWhere

The client received a new HR capability integrated directly into OfficeAnyWhere instead of requiring a separate HR product.

Technology

Implementation stack

Listed last on purpose — technology supported the business outcome; it was not the story.

.NET 6 Angular 20 MS SQL Server Plesk Windows Server

Next step

Need engineering ownership on a production problem?

Talk to Solastia Systems about the business outcome you need — architecture, delivery, and measurable results follow from that.