Selected work

Projects that started as problems and became working software that changed how a business operates.

We do not list every project we have completed. We share the ones that best illustrate how we think, what we decided and why. Each story includes the context, the approach, the key decisions and the outcome.

Project case studies

VERGEIT team presenting the completed logistics management platform to the client team
Enterprise Platform Logistics 2024

End-to-End Logistics Management Platform — UK Distribution Group

A national distribution company operating across multiple UK regions came to us with a familiar but complex problem. Their operations depended on three separate legacy systems — a custom-built order management tool from 2011, a commercial warehouse management system, and a carrier portal — none of which could share data automatically. Staff were spending over forty hours per week on manual reconciliation between systems. Order errors were running at a rate that was affecting client relationships.

The brief was to build something that unified these three workflows into a single platform. After three weeks of discovery sessions with the operations team, warehouse supervisors and client account managers, we identified that the real requirement went beyond data unification. The platform needed to handle routing logic, carrier selection rules, client-specific labelling requirements and real-time tracking updates — all in a way the operations team could configure without developer support.

Key architectural decision

Rather than building a monolithic replacement, we designed a modular system with clear domain boundaries — orders, warehouse, carriers, and client notifications as separate services sharing a common data layer. This allowed the client to extend individual modules independently after handoff.

We built on Node.js with a PostgreSQL database, integrated with three carrier APIs and the client's existing ERP via a custom integration layer, and delivered a React front end. The project ran for four months to a fixed scope. Deployment was phased over two weeks to allow parallel running with the old systems before cutover.

Outcome

Manual reconciliation time reduced from 40+ hours per week to under 4 hours. Order processing capacity increased by 60% without additional headcount. The client has since extended the platform with two additional modules delivered by us in 2024.

System architect reviewing the new microservices design on the whiteboard
Legacy Modernisation Financial Services 2023

Monolith to Microservices Migration — UK Financial Services Firm

A UK financial services firm had built their core customer portal as a .NET monolith in the early 2010s. By the time they came to us, the system had accumulated over a decade of feature additions and quick fixes. Deployment cycles were taking days. Any change to the system required testing the entire application. The team had grown to a size where multiple engineers constantly needed to coordinate on a single codebase, with the merging complexity that brings.

The business case was clear: the system was costing them more in engineering time than it was worth in its current form. But replacing a production financial system is not something that can be done in a single go. The risk of disruption was significant, and the regulatory implications of data handling changes required careful documentation and phased implementation.

Key architectural decision

We recommended a strangler fig approach — gradually extracting services from the monolith starting with the highest-friction areas, running new and old code in parallel, and cutting over each domain once the new service was stable. Zero downtime was a hard requirement throughout.

The migration ran over eight months. We extracted five core domains: user authentication, account management, transaction processing, notifications and reporting. Each was deployed independently, documented fully and handed over with a complete test suite. The original monolith remained running throughout until the final cutover, which was completed in a planned two-hour maintenance window.

Outcome

Deployment cycle time reduced from 3–5 days to under 2 hours. Engineering team capacity for feature work increased by an estimated 35%. Zero incidents during migration. The client's internal team was fully capable of extending all services independently at handoff.

Developer building the custom scheduling system, code visible on screen
Product Development Healthcare Services 2023

Custom Scheduling and Communication Platform — Healthcare Service Provider

A private healthcare service provider was managing their appointment scheduling, staff rota, patient communications and service record-keeping across four separate tools — a commercial scheduling system, a spreadsheet-based rota, a generic email platform and a paper-based records process. The fragmentation was creating errors: double-bookings, missed follow-up communications and difficulty reporting on service delivery.

The client had explored commercial healthcare scheduling platforms, but none handled the specific combination of services they offered, their multi-location structure and their patient communication requirements in a way that would not require significant process compromise. A custom platform was the right answer.

Key architectural decision

We separated the staff-facing scheduling and rota tool from the patient-facing communication interface, connecting them through a shared data layer but allowing each to be designed independently for its actual users. The records system was built as a structured module with export capabilities to satisfy reporting requirements.

The platform was built in Python with a Django backend, PostgreSQL database and a React front end. Automated patient notifications were handled through a queue-based messaging service. The rota system was designed with the practice managers directly, using working sessions that brought their real scheduling logic into the data model rather than approximating it.

Outcome

Double-booking incidents eliminated in the first month. Patient communication response rate increased by 28%. Staff administrative time reduced by an estimated 6 hours per week per location. The client has since expanded the platform to two additional service locations.

VERGEIT engineers reviewing the SaaS platform architecture and code together
SaaS Platform Professional Services 2022–2023

Multi-Tenant SaaS Platform — Professional Services Company Entering a New Market

A professional services firm had identified a repeatable service delivery model they wanted to productise as a SaaS offering to smaller businesses in their sector. They had a detailed understanding of what the product needed to do. What they did not have was a technical co-founder or a clear architecture for turning their service model into a multi-tenant platform that could operate reliably for paying clients.

We began with a six-week discovery and architecture phase. This was an unusually large investment in planning for a project of this nature, but the client agreed it was the right call after we explained the cost of architectural mistakes in a multi-tenant system — particularly around data isolation, billing and onboarding. The architecture document produced in that phase became the primary reference for all subsequent development decisions.

Key architectural decision

We chose a schema-per-tenant isolation model rather than row-level security, accepting the higher complexity of schema management in exchange for stronger data isolation guarantees and simpler tenant-specific customisation. This proved to be the right call when a major enterprise client required audit-level data separation.

The platform was delivered in phases over nine months, with a limited beta launch at month five followed by a general launch at month nine. We remained as the technical partner through the first six months of live operation, supporting the client team's onboarding to ownership of the codebase. The client subsequently hired a technical lead who joined the final phase of development to ensure a complete knowledge transfer.

Outcome

Platform launched on schedule with 14 paying clients in the first month. Enterprise client acquired at month four requiring the data isolation design decision described above. Client team fully independent within six months of launch.

Have a project in mind?

Tell us about your situation. We will be honest about whether we are the right fit.

Every project we take on starts with a direct conversation. We want to understand your actual problem before we talk about how we would approach it. There is no sales process — just an honest conversation about your situation and ours.

Start a conversation See our services
VERGEIT founder reviewing a project with the team