Skip to content

Cases

AI engagements, as they are

Anonymised AI work: the starting point, what was built and where it stands. We report effects only once they are measured.

Cases

  • New freight booking where AI reads client emails and drafts the replies

    Industry

    Logistics

    Starting point

    A logistics company in Gothenburg receives requests from its clients by email and works across some eight different systems. The company has no IT department of its own.

    What is being built
    • A new freight booking platform that connects the transport management system, a booking portal, the shared inbox and EDI flows.
    • Language models read client emails, turn them into structured freight requests and suggest a carrier based on previous shipments.
    • AI drafts every outgoing email in the recipient's language.

    A person approves every message before it is sent.

    How the work was done

    We lead the architecture and the build. The whole build uses AI coding agents as the way of working, in Go and React on AWS.

  • Mobile glass-damage claims, tested for a new market

    Industry

    Insurance

    Starting point

    A Nordic insurance company wanted to try a faster way to reach a new market.

    What was built
    • A proof of concept for the Norwegian market: the policyholder reports glass damage on their phone and photographs it in the app.
    • The app runs on iOS and Android and was built with AI tools end to end.
    How the work was done

    Delivered under our framework agreement with the insurer, by a partner.

  • AI measures data points and raises alarms

    Industry

    Manufacturing

    Starting point

    A manufacturing company collects data points from its equipment and needs alarms from those readings.

    What was built
    • AI measures the data points.
    • Alarms are raised from those measurements.
    How the work was done

    We built the measurement and the path from a data point to an alarm.

  • A small fine-tuned model against a large general-purpose model

    Industry

    Private models

    Starting point

    Can a small model, fine-tuned on one task, beat a large general-purpose model that only gets instructions? The use case: answering customer support tickets.

    What was built
    • A small model, fine-tuned on growing amounts of support-ticket data.
    • A synthetic test set, held out from training, that scores both models the same way.
    Measured
    • 3.5×

      better reply quality

    • ~16×

      better key fields

    • ~50×

      faster replies

    • ~125x

      estimated lower running cost per ticket (internal estimate)

    Results on a support-ticket task. Your results depend on your data.

    The method and the learning curve
    How the work was done

    The large model got instructions and no fine-tuning. Both were scored on the same held-out test set.

  • A software factory for autonomous workflows

    Industry

    Software

    Starting point

    The work of building software should run as autonomous workflows.

    What was built
    • A software factory that runs those workflows.
    • The factory carries out the build, tests it, reviews it, deploys it and verifies it.

    A person only guides the product.

    How the work was done

    We built the factory so product direction stays with a person.

Next step

Bring one process.

30 minutes. An honest answer on whether AI fits.