Case studies
Relevant work with legacy applications, integrations and operational software.
Client details are generalised, but the situations, existing environments, technical challenges and approaches are drawn from work already represented on this site. No unsupported metrics or outcomes have been added.
Case study 01 / Legacy .NET support
A business-critical .NET application gained ongoing technical ownership.
Situation
The application handled day-to-day work across stock, sales, invoicing, contracts and reporting. Operations still depended on it.
Technical challenge
The system needed fixes and workflow improvements from someone who could understand the business context before changing live code and data.
Approach
Stabilise the existing application first, address production issues and add useful changes in a controlled sequence rather than treating age as a reason to rebuild.
Outcome
The application has ongoing support, defects can be addressed and improvements can be planned around the operational work users already rely on.
Case study 02 / System integration
Ecommerce and warehouse orders started flowing without repeated manual entry.
Situation and problem
Orders, customer details and product information were moving between external platforms and internal systems with too much manual handling. Mismatches created additional support work.
Technical challenge
Different formats and system expectations required data to be validated and transformed, with failures made visible rather than silently dropped.
Approach and outcome
Integration workflows pull, validate, transform and send data into the appropriate operational systems. Repeated administration is reduced and exceptions are easier to identify and support.
Generalised architecture
Order to dispatch and status return
- 01
Ecommerce platform
- 02
Integration service
- 03
Validation and transformation
- 04
SQL Server and internal systems
- 05
Warehouse and dispatch
- 06
Status and tracking return
Case study 03 / Custom operational software
A quoting workflow moved out of spreadsheets and into a purpose-built .NET application.
Situation
Staff needed to quote detailed custom work while prices, customer details and job requirements varied from case to case.
Technical challenge
Spreadsheet logic was difficult to control and easy to misread, while the workflow also needed quote generation and production paperwork.
Approach
A custom .NET application brought pricing logic, customer details, quote generation and production documentation into one workflow backed by SQL Server.
Outcome
The business can manage quoting in a more controlled process, reduce duplicate entry and pass clearer job information into production.
Case study 04 / Legacy modernisation
Older ASP.NET systems moved toward cleaner hosting and more reliable deployment.
Situation and risk
Existing web applications and databases carried production risk through older hosting, unclear deployment steps and performance limits.
Approach
Application and database environments were reviewed, moved and validated with careful deployment checks and production troubleshooting.
Outcome
The business gained a more reliable base for support, performance and future change without assuming the entire existing system had to be replaced.
Secondary service / Managed websites
A small business website became an actively maintained service.
The managed plan keeps design, hosting, maintenance, forms, content updates and practical support together after launch. This service remains available without defining the wider software practice.
Your system
Recognise part of your own situation?
Describe the existing application, data flow or operational process. The first conversation will focus on what needs attention and whether the experience here is relevant.