Legacy application modernisationRebuilds the in-house
team can run.
Strangler-pattern migrations off the system nobody wants to touch, one bounded piece at a time, with the old and new running side by side until the numbers match.
One seam at a time
No big-bang cutover.
Parity measured
Old vs new, same inputs.
Knowledge captured
Docs where your team looks.
Engagement
Built · fixed scope per increment
What you get.
Strangler-pattern migration: one bounded piece at a time, never a big-bang cutover
Old and new running side by side until the numbers match
Parity measured: same inputs, same outputs, in your environment, before anything is switched off
Knowledge captured where your team looks, not in our heads
Engagement: Built · fixed scope per increment · Ask about your migration →
Good for
— A system nobody wants to touch
— A framework three major versions behind
— A migration that has been ‘next quarter’ for two years
We will say no when
— Rewrite it all is the plan, and the only plan
— Nobody can say what the system does today, and nobody wants to find out
Stack · only what we have shipped to production
From the record.
All case notes →01 · Digital signage · enterprise
Built · embedded
Signage platform across four continents
Problem — A UK signage business operating across Australia, the US, China and APAC needed a platform its display-manufacturer partners could plug into.
What we did — .NET 6 microservices and Angular on AWS (EKS, ECR, RDS, CloudWatch) with Docker-based CI/CD. Scheduled sync integrations with SharePoint, Power BI and partner sources. Production infrastructure stabilised under sustained memory pressure ahead of a database end-of-support migration.
Measured — Shipped and running across four regions; partner integrations for three major display manufacturers — [ADD UPTIME / DEVICES].
Client withheld · details on the callAsk about this →
02 · Retail · integrations
Built
Retailer replenishment SDK
Problem — Retailers integrating a replenishment service each failed in their own way.
What we did — .NET Core microservices on Azure Service Fabric with EF Code First, plus an admin module that resolved SDK-level failures across retailer integrations.
Measured — SDK in production across retailer integrations — [ADD RETAILERS].
Client withheld · details on the callAsk about this →
03 · Enterprise · .NET
Embedded
Process-documentation platform backend
Problem — A browser-extension product that writes process documentation from recorded sessions, with a milestone that could not slip.
What we did — Owned Lambda and hosted worker services (SQS, SNS) across environments and led the refactor that shipped the critical milestone on deadline.
Measured — Critical milestone shipped on the date.
Client withheld · details on the callAsk about this →
Legacy modernisation · the call
Name the system nobody touches. We will say where to cut first.
Bring the problem, not a brief. If it is outside what we do well, we will say which of our contacts to call instead.
Or email info@hopsig.com — reply within one working day.