Our Work
The work behind the numbers.
These engagements were led by Ouaes Jamali before JamSoft existed. The company is new. The experience behind it is thirty years old.
Manufacturing Operations Platform
$300M revenue operation
The problem
A discrete manufacturing company running a $300M operation had built its entire business on a single VB6 application. Inventory, orders, clients, production scheduling, reporting, supply chain — all of it lived in a system written in the 1990s that only two people in the company fully understood.
Any change to the system took months. New requirements sat in a backlog that never cleared. The business had grown well past what the software could support, but the thought of replacing it felt impossible — too much risk, too much business riding on it, and no one willing to be responsible for taking it offline.
What we did
We replaced the platform. Not the business logic — the infrastructure underneath it. Starting with a full assessment of the existing system, we mapped what the software actually did versus what the business thought it did, documented the decisions embedded in twenty-year-old code, and designed a phased migration plan that kept operations running throughout.
The delivery was staged so that no single phase created a business-stopping risk. Teams continued using the legacy system for each module until the replacement was validated and live. The final cutover was a non-event.
The outcome
A modern, cloud-ready platform that the business can maintain and extend without specialist knowledge. Changes that took months now take days. The two-person dependency is gone. The company has a system that can grow with the business rather than constrain it.
$300M
Revenue operation running on a VB6 application that only two people understood.
Legacy stack replaced
VB6 application covering inventory, orders, clients, production, reporting, and supply chain — rebuilt on a modern Microsoft stack with cloud-ready architecture.
Retail Pricing Pipeline
Multi-billion dollar retailer
The problem
A multi-billion dollar retailer was running a pricing pipeline that took eight hours to complete each day. Pricing updates processed overnight. Stores opened in the morning with yesterday's prices.
The pipeline had grown over years without a redesign. It had become slow, fragile, and expensive to change — and the business had accepted the eight-hour runtime as a fact of life.
What we did
We rebuilt the backend pipeline. The assessment identified where time was being lost — redundant processing, sequential steps that could run in parallel, and bottlenecks that had never been instrumented. The rebuild addressed each of them, producing a pipeline that was faster, more maintainable, and observable by the team running it.
The outcome
Eight hours down to ninety minutes — an 81% reduction in processing time. Stores get current pricing. The pipeline is observable and maintainable by the team that operates it.
81%
reduction in processing time. Eight hours down to ninety minutes.
What this meant operationally
Stores opened with current prices. A bottleneck the business had accepted as permanent was removed in a single focused engagement.
Market Expansion Modernization
Professional services firm
The problem
A professional services firm had a platform built for internal users on .NET 2.0 and ASP.NET. It worked — their internal teams used it daily and the business depended on it. But the company wanted to grow into an external audience, and the platform wasn't built for it.
Authentication was built for internal directory accounts. The interface was designed for trained internal users, not external customers. And the underlying platform was aging to the point where adding capability was becoming difficult. A full replacement felt too risky. Doing nothing meant the growth plan stalled.
What we did
We rebuilt the presentation layer in React, moved authentication to Azure Active Directory B2C to support external users, and migrated the data layer to Azure SQL — all while internal users kept working on the existing system throughout the transition.
The migration was phased so no module went dark during the build. Internal users moved to the new platform module by module, after each was validated. The external audience capability launched once the platform was ready to support it.
The outcome
Existing internal users got a better product. External audiences could access the platform for the first time. The business could grow without being constrained by its own software.
Stack replaced
.NET 2.0 / ASP.NET → React, Azure SQL, Azure Active Directory B2C
Two outcomes in one engagement
Internal users got a modern platform. External audiences got access they never had before. Business ran throughout.
30–50%
Operational efficiency gains clients typically report in the first year after a modernization engagement.
Your situation is different. Let's talk about it.
No two engagements look exactly alike. If something on this page sounds familiar, start a conversation and tell us what you're dealing with.
Start a conversation