CASE STUDY

Modernizing a client back office

Legacy SQL, manual changes and a dashboard that needed a clearer workflow.

The task

Legacy SQL, manual changes and a dashboard that needed a clearer workflow.

My role

I independently improved SQL, server-side logic, automation and the interface.

The solution

The work connected stored procedures, application logic, background tasks and the interface. Explore each change below.

See it in action

COMMERCIAL / ONE CLIENT, TWO WORKSTREAMS

Commercial work at eWave Online. Client identity and proprietary screens are withheld.

01B

COMMERCIAL / FULL STACK

Website features

Search, personal accounts, training and bilingual interfaces.

Umbraco 13 · C# · SQL Server

Commercial work at eWave Online · Client name withheld.

Website features I worked on

Standards search and filtering.
Registration and personal accounts.
Training catalogue.
Hebrew and English interfaces, including RTL layouts.

Across the stack

I worked with Umbraco 13, ASP.NET Core, C#, SQL Server and JavaScript/jQuery across the website’s backend and interface.

This website and the dashboard below belong to the same client. My website work covered both server-side functionality and bilingual user interfaces.

01BACK OFFICE / INDEPENDENT DEVELOPMENT

Modernizing a
client back office.

I independently rebuilt a client dashboard across SQL, server-side logic, automation and UI. The goal: more responsive functionality and less manual work.

Commercial project · Independently developed across SQL, backend, automation and UI.

SQL modernization
Automation
Usable interfaces

THE CLIENT’S RESPONSE

The client wanted to buy
the entire dashboard.

A purchase had not been part of the original plan.

Explore dashboard improvements

Choose a problem. See what I changed and why.

ENGINEERING CHANGE MAP2013 / LEGACY SQL

InterfaceAPI & business rulesDatabase

STARTING POINT

Stored procedures from 2013

Legacy database procedures were part of the dashboard’s existing foundation.

MY CONTRIBUTION

Rewritten for responsiveness

Rewrote the old stored procedures to improve how responsively the dashboard worked.

WHY I CHOSE THIS APPROACH

Responsiveness starts below the UI. Database work is part of the user experience.

From manual work to clearer workflows

Manual changes
Existing jobs & migrations
An interface to improve

An explanatory map of the improvements, not a reconstruction of the original screens.

Explanatory reconstruction, not the original client interface. The source code is no longer available to me, so this case presents my contribution without proprietary code or measured performance claims.

Improved server-side logic and reorganized API calls into appropriate layers.

Replaced manual changes with automatic functionality.

Optimized jobs and migrations.

Created a cleaner, easier-to-use UI.

Engineering decisions

Keep responsibilities clear

I reorganized API interactions and improved server-side logic so each layer had a clearer responsibility.

Improve the whole workflow

I worked on stored procedures, jobs and migrations alongside the interface. A clearer screen still depends on the work behind it.

How I checked the changes

I used both manual checks and automated testing when validating the dashboard changes.

Make repeated work automatic

I replaced manual changes with automatic functionality. The aim was to make everyday client work more comfortable and reduce the need for repeated intervention.

Evidence & limitations

This case uses an explanatory diagram, not proprietary screens. The source code is no longer available to me, and I do not claim measured performance gains or a completed purchase.