Service · Web development

Custom generative AI solutions.

A working AI feature in your own software: text, image, code or audio generated on demand. Not isolated experiments, but an integration that fits your workflow, your security requirements and the European AI Act.

Text generationImage generationRAG & your own dataGDPR & AI Act

Generative AI = AI that creates new content.

Generative AI is the umbrella term for models that produce new content from a prompt: a blog text, a product description, an image, a piece of SQL, a speech fragment or a summary of a long document. The difference from classic AI is that the output is not a score or label, but new content that is immediately usable. For your end user, this usually means a visible creation or generation interface in your product: a "write for me" button, a suggestion field, an image generator or a summariser that works in one click.

For organisations, the question is rarely "can this be done?" and almost always "how do we do this securely within our existing systems?", a question we hear from many clients in exactly those words. We build that layer: from initial use-case selection to production-ready integration with your application, your data and your compliance frameworks. We work custom, the code stays in your repo, and we also deliver an AI strategy and roadmap if you need direction first before we build.

Our typical clients are content agencies, marketing teams, e-commerce organisations with large product catalogues, creative agencies, media and publishing houses, training and learning companies, customer service organisations, and product teams who want to add an AI feature to their existing SaaS. The use cases vary widely, from automatic product descriptions to legal contract generation to question-answering bots over internal documentation, but the pattern is the same: a model that creates content, a UX that keeps the human in control, and an architecture that doesn't leak your data unnecessarily.

Three flavours of generative AI.

Most enquiries we receive fall into one of these three categories. Which one fits depends on where the generation becomes visible to your end user and how much the model needs to know about your data.

Compact project · fixed sprint budget

AI feature within existing software

You already have a product and want to add a generative layer: a "write for me" button, a summariser, a suggestion field, a translation flow or an alt-text generator. We build it into your stack, with a prompt layer you can adjust yourself, streaming output so users don't wait for a long response, and cost monitoring so a sudden spike doesn't blow your monthly budget.

Prompt engineeringAPI integrationStreaming UXCost monitoring
Mid-sized project · fixed sprint budget

Generation on your own knowledge base (RAG)

The model doesn't write from nothing; it answers based on your own documents, product data, policy rules or helpdesk history. Retrieval-Augmented Generation with a vector store, source citation and an evaluation set you can expand yourself. Related to our custom LLM integrations, but specifically aimed at generative content flows.

RAG architectureVector storeSource citationEvaluation set
Larger project · fixed sprint budget

Multi-modal generation platform

A custom platform or feature suite in which multiple models work together: text, image, audio and code. Often for marketing, e-commerce or media organisations producing branded content at scale. We build the orchestration between models (Stable Diffusion for images, Claude or GPT for text, ElevenLabs or similar for audio), a review workflow in which editors or brand managers can approve content, and cost controls per user, project or campaign. For public-facing output, we handle the transparency labels required by the AI Act.

Multi-modelImage & audioReview workflowBrand guardrails

What you get at the end.

A working generative AI solution, embedded in your application, plus everything around it so you can manage and fine-tune it yourself.

We work custom: no white-label SaaS, no wrapper around a chatbot product. The code lives in your repository, the choice of model is yours, and you can switch providers at any time without us having to rebuild anything.

  • The generation feature itselfProduction and staging, running in your own cloud (GCP/AWS/Azure) or hosted by us, with streaming UX and latency monitoring.
  • Codebase and prompt libraryFull source code in your repo, plus a structured library of prompts and system messages that you can maintain yourself.
  • Model abstraction layerA thin internal API so you can switch between Claude, GPT, Gemini, Llama or Mistral without touching the application.
  • Evaluation set and monitoringA test set with expected outputs, hallucination detection, a cost dashboard per user or feature, and alerts when model behaviour deviates.
  • Compliance packageDPIA template, AI Act classification of your use case, output labelling where required, and clear documentation for your DPO or compliance officer.
  • Management contract (optional)Monitoring, model updates, prompt tuning, further development and evaluation of new models. Fixed monthly fee, four response-time levels.

When generative AI is the right choice.

Four patterns we often step into. If you recognise one of them, we're happy to talk through how we would approach it in your situation.

Content at scale

Marketing or e-commerce content

You produce blog posts, social posts, product descriptions, alt text or multilingual variants in volumes where writing by hand no longer scales. AI delivers the first draft based on your product data, tone of voice and SEO guidelines; an editor reviews and publishes.

Service and support

Making customer contact smarter

Tickets are summarised automatically, replies are suggested based on your knowledge base, and sentiment and urgency are made visible. Your service team stays in control and makes the final decision, but handles more cases a day without quality slipping.

Document flows

Generating contracts and reports

Quotes, contracts, audit reports or policy documents are largely filled in by a template plus AI, based on structured input. Lawyers or consultants review and finalise, rather than writing every paragraph from scratch.

Product features

AI features in your own software

You have a SaaS product and your users now expect there to be "something with AI" in it — a writing assistant, a suggestion, a summary. We build it in neatly, without disrupting the existing UX.

HR & recruitment

Vacancies and CV screening

Job posting copy in several variants, anonymisation of CVs for more objective screening, or suggested interview questions based on a role profile. Quite feasible, but exactly the kind of use case where AI Act classification needs careful attention: high-risk when decisions about candidates are made with it.

Learning & training

Personalised learning paths

Generating quiz questions from study material, progress coaching with personal feedback, or an AI tutor that explains content at the learner's level. Popular with training and learning companies that want to scale their course library.

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

How a generative AI project works.

1

Use case workshop

We spend half a day with your team identifying which generative application would deliver the most value. Not the most spectacular one, but the one that fits your data, your users and your risk appetite. Without a workshop we build nothing, because we too often see impressive demos that fall apart in production.

2

Scoping and model selection

Together we choose the model (cloud API, open-source self-hosted or a hybrid), define the evaluation criteria, and draft a DPIA question if personal data is involved. At the end you have a concrete scope, a plan and the first screen flow with a working prototype prompt.

3

Build in sprints with human-in-the-loop

A working build every two weeks. We test not only whether the feature runs, but whether the output is good enough, using an evaluation set you help create. Hallucinations, prompt injection and output leakage are actively tested in this phase, not discovered later during an audit.

4

Rollout, monitoring and ongoing development

A phased rollout, starting with a small group, with monitoring of costs, latency, error rates and user satisfaction. Afterwards, ongoing management: evaluating new models, refining prompts, and expanding the evaluation set as you learn more about what works well.

Frequently asked questions.

What clients typically want to know before we start with generative AI.

What exactly is generative AI, and how is it different from an AI agent?
Generative AI is an umbrella term for models that produce new content: text, images, audio, video or code, based on a prompt. An AI agent is more specific: a system that carries out multiple steps independently, calls tools and completes tasks. Many generative solutions contain no agent layer at all; they generate something once, a person reviews it, and that's that. Which you need depends on how autonomous the system has to be.
How do I integrate generative AI safely into existing systems?
We work with a few fixed principles: personal data is not sent to the model without pseudonymisation, prompts and outputs are logged in your own environment, prompt injection is actively filtered, and the choice of model falls on providers with EU data residency or a self-hosted model where needed. We also build an output layer that filters for sensitive information before content leaves your application. Compliance is not a separate step at the end; we make it part of the architecture.
Which model do you choose: cloud API or open-source self-hosted?
It depends on your requirements. Cloud APIs (Claude, GPT, Gemini) are often the strongest and quickest to deploy, but your data leaves your infrastructure and costs scale with usage. Open-source models (Llama, Mistral, Qwen) run in your own cloud, giving more control and less convenience, with higher infrastructure costs but fixed monthly outlays. For most organisations a hybrid works well: non-sensitive flows in the cloud, sensitive flows on a model you host. We advise based on your data, use case and data classification, and build an abstraction layer so you can later switch between providers without rebuilding the application.
How do you handle copyright on generated content?
This is not yet legally settled, so we advise a conservative approach. For text and code, we follow the current consensus: the output of a model is generally not protected by copyright in most jurisdictions, so exclusivity cannot be claimed. For images, we choose models whose training data status is clear, and we set up logging so that provenance can be demonstrated. For questions about output IP or commercial reuse, we consult your legal adviser — we are technologists, not lawyers.
What do you do about hallucinations?
Hallucinations cannot be eliminated, but they can be greatly reduced. We use Retrieval-Augmented Generation so the model draws on your own documents rather than on its training. We add source citations so users can check where an answer comes from. We build an evaluation set with expected outputs and run it automatically. And for high-risk flows, we keep a human in the loop — the AI suggests, the human publishes.
What about the EU AI Act and GDPR?
Generative AI falls under the AI Act, which has specific transparency requirements: AI-generated output must be recognisable as such, deepfakes must be labelled, and high-risk applications face stricter obligations. GDPR is relevant to which data the model sees and where it is stored. We carry out a DPIA on every major project, classify your use case under the AI Act, and arrange labelling where required. We are not a law firm, so more complex questions we will discuss with your DPO or solicitor — but the technical side we deliver audit-ready.
What determines the cost of a generative AI project?
Three factors determine the build cost. One: the scope of the feature — a single-shot text generation is quicker to build than a RAG architecture with a custom vector store, evaluation set and source citations. Two: integration complexity with your existing systems, especially where multiple sources or legacy APIs are involved. Three: the compliance package — an internal tool for twenty employees has a different regime from a feature for a hundred thousand end users. There are also ongoing costs: model API usage, infrastructure costs if you run self-hosted, and maintenance. After the introductory conversation, we will give a concrete estimate based on your situation and data volumes.
Will our employees need training to work with this?
A short introduction almost always; lengthy training rarely. We build the feature so that it feels intuitive for your users — a writing assistant should be as natural to use as spell-check. For your IT team and any admins, we provide a manual, and we run a knowledge transfer in the final sprint so that your team can adjust prompts themselves afterwards. For larger AI projects, we also refer clients to our enterprise AI implementation page for the organisational side.

Talk to us about your generative AI solution.

A thirty-minute introductory call, without obligation. We listen to the use case you are unsure about, give direction on model choice and compliance, and are honest when generative AI is not yet the right solution. No sales pitch — nobody is waiting for that.

Edit content