Skip to content
AI

GenAI development

Platforms, interfaces and the software a model lives in, or a model wired into the systems you already run.

Starts with
A test on your own data
Builds
Platforms and integrations
Typically
8 to 14 weeks
Send a short brief
What it involves
  1. 01Test setReal questions from your team score each version.
  2. 02PrototypeRuns on your own documents, in your AWS account.
  3. 03LiveGuardrails on, and a trace behind every answer.
On AWS
  • GenAI on BedrockAI built into your product on Amazon Bedrock and SageMaker, with any kind of model: language, vision, speech or forecasting. We build our own agent loops on Strands Agents, LangGraph and LangChain, train or tune a model when a ready one won’t do, and test it all before launch. Data stays in your account.Read more
  • MarketplaceSovereign AI PerimeterA private AI assistant running inside your own cloud account, on managed foundation models. Reachable only over VPN or another controlled channel, never the open internet. No new vendor holds your data.See the listing
Work like this
  • Client work

    Library-backed extraction

    Returns only what a library of known controls holds, in any domain.

    Learn more about Library-backed extraction
How it runs

Same four steps,a week or two years.

In all: 8–14 weeks.

In all: 8–14 weeks.

In all 8–14 weeks. 12 weeks shown.

  1. FrameWeeks 1–2
  2. JoinWeek 3
  3. DeliverWeeks 4–11
  4. HandoverWeek 12
Week 6 · Deliver

The first version answers in staging, scored against the test set.

The work lands in small pieces you can see and use. When the evidence changes, so does the plan.

4 / 7
  1. Frame

    Weeks 1–2
    • Day 1

      We pick the use case together and agree what a good answer looks like.

    • Week 2

      A test set of real questions from your team, to score every version against.

  2. Join

    Week 3
    • Week 3

      Access to your AWS account and data. The first prototype runs on your own documents.

  3. Deliver

    Weeks 4–11
    • Week 6

      The first version answers in staging, scored against the test set.

    • Week 9

      Connected to your systems, with guardrails on and the running cost measured.

    • Week 11

      Live for the first users, with a trace behind every answer.

  4. Handover

    Week 12
    • Week 12

      Code, evaluations and runbooks handed to your team.

Hello from Malmö

Adamass

Come with the work that feels heavy. We will make it light.

  • IKEA
  • Nasdaq
  • Tele2
  • Thomson Reuters
  • The Guardian
  • Liverpool FC
  • Stabenfeldt
  • Eyeradar