All work
    SD TeamIndustrial servicesTakeovers and rebuilds

    Two legacy systems replaced by one platform, built to work with SD's existing back office

    SD Team is one of the UK's leading finishing groups, with more than 50 years in the trade, nine offices and over 22,000 projects a year across construction, marine and insurance. MOHARA replaced the two systems behind its working day with a portal for operatives and a diary for managers, connected to SD's existing back office, and moved everything across without losing a day's data.

    A repair technician photographing a finished repair on a yacht's hull in a sunny boatyard.
    Sector
    Finishing, repair and sealant services for construction, marine and insurance, UK
    What we built
    A mobile operative portal that works offline, a work diary for managers, a link to the existing back-office system and a move to the cloud
    Timeframe
    Kickoff August 2024. Operative portal live February 2025. Work diary live June 2025. Ongoing support since.
    Outcomes
    32 teams on one platform at launch, and 22 today. The portal and diary rebuilt and moved to the cloud in two rehearsed cutovers, with nothing lost and no downtime in working hours.

    The client

    SD Team began as a sealants business and has grown into a group of more than 200 people, covering sealants, cosmetic repairs, insurance repairs and marine outfitting. It is also growing beyond the UK, with a sister business in the Netherlands. Its operatives work across the country on company phones, in regional teams set by trade and area.

    What they were going after

    SD had outgrown the systems behind its working day. There were three of them, each with its own logins. Jobs in the diary were typed as free text with no link to the contract behind them. A manager could look after one team or every team, nothing in between. The portal was built for sealants and didn't fit the other trades.

    SD wanted a platform its operatives would actually use, that worked on a weak signal on site and could take on new trades and new countries. It also had to come off a single server with no data lost.

    What we built.

    01

    The operative portal

    Operatives see their upcoming work and log what they did: the job, plots, materials, photos and signatures. It works offline and lets them reorder stock. They can start a work log straight from a diary job, with the date and contract already filled in.

    02

    The work diary

    Managers get a team calendar with drag-and-drop scheduling, unassigned work, holiday and sickness, reports and a full change history. Every diary job now links to its contract instead of being free text, and the diary also works offline. A manager can now look after several teams. Insurance work has run through the diary since it went live.

    03

    Built for more than one country

    The portal was designed for translation from the start, so SD can roll it out to teams abroad without a rebuild.

    04

    A link to the existing back office

    Which stayed in place and still reads and writes the portal's data directly.

    05

    A move to the cloud

    With nightly backups and point-in-time restore from day one.

    06

    Repair logging

    Released in August 2026 for cosmetic and marine repairs.

    How we worked.

    We designed the platform hand in hand with SD's team, in regular working sessions throughout the build and in close partnership with domain experts at SD. Before anything was built, SD ranked what mattered most to them. Usability came first, because if operatives don't want to use it, nothing else counts. Then reliability, upkeep, room to grow and cost. Those priorities shaped every decision that followed.

    The big call was to split one large release into two. The first plan moved every system and database at once. Instead, the team built the new apps in the cloud against the existing data and shipped the portal first, then the diary, so two databases never had to move at the same time. The business kept running throughout.

    Each cutover was timed to avoid the working week and had a tested way back if anything went wrong. The team rehearsed every move against fresh backups until the data matched SD's own samples.

    What it returned.

    32teams on one platform at launch, with 22 running their day on it today
    17managers now look after two or more teams from one calendar
    Delivered on time and on budget, a full rebuild of the platform SD runs its day on.
    Two connected apps, one for operatives and one for managers, in place of two old systems.
    Every diary job linked to the right contract, instead of free text, and work logs started straight from the diary.
    Two live systems moved to the cloud with no data lost and no downtime in working hours, including more than 66,000 work logs going back to 2021.
    Since the portal went live: about 6,000 contracts worked on, 65,000 work logs, 347,000 photos, 49,000 client signatures and 3,900 stock orders.
    Since the diary went live: about 45,000 entries scheduled.
    Still building together: diary improvements, security updates and repair logging have all shipped in 2026. Repair logging captured 20,000 repairs with 57,000 photos in its first 10 weeks.
    An airport concourse at dawn, travellers and ground staff crossing in low sun.

    Have a problem like this one?

    The team that built this for SD Team is the team you would work with. Tell us what you are trying to solve.