AI integration for the systems you already use

AI delivers the most value where work already happens. We connect models to your CRM, ERP system, intranet and custom applications.

No vendor lock-in

We build integrations that let you switch models. When a better or cheaper model comes along, switching should be a setting, not a new project. This also lets you use different models for different tasks. We integrate with OpenAI, Anthropic and Google, or Azure OpenAI when everything needs to stay within Microsoft.

Classification

A fast, affordable model for classifying tickets, emails and leads. Even thousands of calls a day cost very little.

Long documents

A more accurate model for contracts, reports and investigations, where precision matters more than price.

Sensitive data

Azure OpenAI or processing within the EU when data must stay in a specific region, under the same agreements as the rest of your cloud environment.

Images and audio

Models that interpret images, scanned documents and speech, from delivery notes and field photos to recorded calls.

How we implement AI

From the first connection to production, without disrupting the rest of your system.

  1. 01

    Data and permissions

    We map out what data the AI needs, where it lives and who is allowed to see what. Permissions from your existing systems carry over, so no one receives answers based on data they would otherwise be unable to access. We also agree on which data must never be sent to a language model.

  2. 02

    The integration

    We build the integration using the OpenAI, Anthropic or Google API, or Azure OpenAI when everything needs to stay within Microsoft. Calls go through a dedicated layer in your backend, never directly from the browser. This layer handles keys, timeouts and retries, and lets you switch models without affecting the rest of the system.

  3. 03

    Testing with real examples

    We evaluate responses against real cases from your organisation before anything goes live, and keep the tests for future use. When a new model version arrives or we change a prompt, we run the same tests again. That tells us straight away whether quality has improved or declined, rather than finding out in production.

  4. 04

    Operations and monitoring

    Logging, cost controls and alerts help us spot changes before your users do. We track response times, errors and cost per call, and set spending caps so a bug cannot run up your bill. We maintain the integration like any other code we deliver, updating it when providers change their APIs.

Common AI integrations

CRM

Summarises client history before a meeting, suggests next steps and updates the client record after the call.

ERP systems

Interprets orders, invoices and discrepancies, and routes them to the right place, with a person approving anything unusual.

Websites and e-commerce

Search that understands what visitors mean, product copy at scale and recommendations based on their needs.

Intranets and documents

Makes thousands of documents searchable through everyday questions, while keeping track of versions and permissions.

Ticketing systems

Classifies and prioritises incoming tickets, and suggests replies based on how similar cases were resolved.

Custom systems

AI as a feature within your own application, built and tested just like the rest of the code.

Built like every other piece of code we deliver

The AI component is version-controlled, tested and maintained in the same way as the rest of your system. It is not a separate experiment, but part of the code you rely on. That means the same standards for security, testing and documentation apply.

01

Version control and testing

Prompts, integrations and test cases are version-controlled like any other code. Every change goes through the same tests before going live, so an improvement in one area does not break something elsewhere.

  • Version-controlled prompts
  • Tests using real examples
  • Review before release
02

Security and permissions

API keys are never stored in the browser, and the AI can only access what the user is authorised to see. Sensitive data is kept out of calls when it is not needed.

  • Keys stored only on the server
  • User permissions respected
  • Sensitive data excluded
03

Maintenance after launch

When a model is updated or phased out, we run the same tests again before switching. The people who built the integration also maintain it.

  • Planned model changes
  • Cost and quality monitoring
  • The same team that built it
A person in a white T-shirt points to a screen displaying a chart in an office. The chart shows red and orange lines and bars, with the text Revenue SEK 977.63 and CTR 3.63%. The date range on the screen is 1 February 2020 – 31 March 2020.

What is AI integration?

AI integration means connecting a language model to the systems you already use via an API. AI becomes a feature where work happens, in your CRM, ERP system or custom application, rather than a separate chat window that staff have to copy text into and out of.

This is also where most AI projects get stuck. The model works in a test, but struggles when it needs to respect your permissions, handle your data formats and keep working when something changes.

Frequently asked questions about AI integration

Can't find the answer? Book an AI review or call us on 070-953 53 99.

AI review

30 minutes, one of your workflows

We look at a task that takes up time today and give you an honest recommendation: AI, conventional automation or no change at all.

  • A brief written proposal for next steps afterwards
  • The same people who will build it
  • Free of charge
Smiling man with glasses and short brown hair, wearing a dark blazer and white shirt, standing with his arms crossed against a light grey background.
Alexander DypbuktDigital Strategist & CEO at Pigment

We will get back to you within one working day with suggested times. Privacy policy