SquidERP - modular ERP platform for SMB operations. 

• I rebuilt the authentication system end-to-end to support multi-tenancy and multiple identity providers (Google, Microsoft, phone-only login), and built a centralised authentication service that handles auth uniformly across the company's suite of apps. 
• I also delivered centralised user management across instances - so administrators manage users, roles, and access in one place rather than per-app - and built the billing portal handling subscriptions, plans, and customer self-service. 
• .NET 8 backend with Angular frontend. 
• The work covered token issuance and refresh, identity provider integration, tenant-aware permission resolution, and the migration path from the legacy auth layer to the new service without disrupting existing users.

US-based industrial commissioning SaaS used by field engineers in plants and large facilities.

• I led the migration from legacy .NET MVC to Blazor WebAssembly and rewrote core modules in the new architecture. 
• The frontend uses Syncfusion controls throughout - data grids, schedulers, document viewers, and a dynamic form builder that generates complex commissioning checklists. 
• One of the harder problems on the build was offline-first support:
  • field engineers often work in environments with no connectivity, so the app had to function fully offline, queue changes locally, and sync cleanly when the connection returned. 
• I designed the local persistence and sync layer, including conflict resolution when multiple users had edited the same records offline. 
• More recently I integrated AI features into the platform - LLM-powered summarisation of commissioning reports and assisted form filling - wiring model APIs into the existing production Blazor app without disrupting the core workflow.

German healthcare transportation client (medical patient transport coordination).

• I worked across both their flagship products: , the WPF/MVVM desktop platform used by dispatchers, with complex real-time geolocation, route handling, and dense charting where large amounts of moving data have to be readable at a glance; and , the Blazor web counterpart built on the same .NET backend, covering UI components, state management, API design, and the data layer. 
• Working on both products gave me a clear view of where it makes sense to share logic and contracts between desktop and web and where the two should diverge - the desktop side needs dispatcher-style information density, while the web side benefits from a cleaner, more conventional Blazor UI pattern. 
• The engagement was also where I got comfortable with the precision and formality that German engineering work expects - detailed specs, clear written communication, and a strong preference for "correct first" over "fast first."  

UK financial services client (consumer lending and financial claims).

• I built an open banking and credit report parsing service that ingests bank statement data via open banking APIs and credit reports from the major UK bureaus, normalises both into a common structured model, and surfaces the data into the platform's underwriting and case workflows. 
• The hard parts were the parsing layer - credit reports vary significantly in format and content between bureaus, and open banking transaction data is messy in its own ways (inconsistent merchant naming, categorisation drift, edge cases around joint accounts, refunds, and pending transactions) - and the normalisation model that lets downstream logic treat both sources uniformly. 
• The service was built on .NET with idempotent ingestion, async processing for long-running pulls, audit trails on every record (non-negotiable in an FCA-regulated environment), and clear separation between source-specific adapters and the canonical model so adding a new bureau or open banking provider is a contained piece of work, not a rewrite.

UK-based tax compliance and reporting platform. 

• I built complex middleware APIs that consolidate data from many third-party sources - ecommerce platforms, marketplaces, and external systems - normalise messy and inconsistent inputs into a clean canonical schema, and extract structured tax data into compliant, auditable reports across multiple jurisdictions. 
• The work centred on the kind of integration layer where every new connector (a new ecommerce platform, a new country's tax rules) is essentially a new client onboarding onto the platform, so the abstractions and ingestion pipeline had to be solid - idempotent processing, schema versioning, async sync patterns for long-running data pulls, and clear separation between source-specific adapters and the canonical model. 
• .NET on Azure infrastructure, with a strong emphasis on reliability and correctness - non-negotiable given the regulatory context.

• Windows desktop application for real-time monitoring of on-site equipment and sensor data across construction sites. 
• Handles continuous sensor ingestion, live operator dashboards, threshold-based alerting, and historical data review. I led the migration from .NET Framework 4.5 to .NET 8, including the substantial work of moving from legacy WCF and WinForms patterns to modern hosted services and clean separation of concerns. Beyond the migration, ongoing feature work covered the ingestion layer, dashboard components, and the alerting engine.
• The engagement was a good example of working inside an established industrial codebase with real operational stakes - sensors driving on-site decisions, so reliability and clear logging of every ingested data point and triggered alert mattered more than feature velocity. 
• Direct experience with a German engineering culture: detailed specs, precise written communication, and a strong preference for correctness over speed.

• I built from the ground up for an Irish company (VisionBlue, later acquired by Aryza), now used in production by multiple UK insolvency firms as tenants. 
• Full microservices architecture on .NET and Azure, with event-driven patterns where eventual consistency was acceptable (notifications, reporting, audit trails) and synchronous APIs on the critical path (case creation, payment processing). 
• The platform handles the end-to-end lifecycle of insolvency cases - client intake, creditor management, payment scheduling, compliance reporting, and integrations with external regulatory systems and lender APIs over both REST and SOAP. 
• Multi-tenancy was baked in from day one, with strict tenant isolation at the data and permission layers and senior staff able to see across multiple practitioners within the same firm. 
• Telemetry and structured logging were non-negotiable from the start - in a regulated environment where insolvency workflows are deeply interconnected, you need to know exactly where and why something failed, not guess from user reports. 
• Seven years of continuous work across the platform, covering everything from initial architecture to ongoing feature delivery and stabilisation.