yucod

AI features in your SaaS or app that users actually use

We build LLM features into your product: an assistant, search over your documents, auto-fill, text extraction. We start with a pilot tied to one measurable KPI, then scale what works. Prices are public, and code and accounts are yours under the agreed terms.

Quote and schedule after your brief

Who it's for

  • SaaS owners who want an AI feature and don't know which one to start with
  • App teams whose support queue is full of repeat questions
  • Products with large document or data libraries that users can't search well
  • Startups that need a working AI prototype for investors or first customers

Problems we solve

We want AI in the product, but can't tell a useful feature from a gimmick.

We start with a free project brief and one scenario with a clear KPI, such as how many requests the assistant resolves without a human. Everything else waits until the pilot shows results.

The model makes things up and we can't risk that in front of customers.

We build RAG (retrieval: the model answers from your documents) and require source citations. If the data isn't there, the model says so and hands off to a human. Errors can't be removed entirely, but we measure them with tests.

We worry the API bill will climb out of control as usage grows.

We set per-user limits, cache repeated requests and match the model to the task: a cheap one for simple jobs, a stronger one for hard ones. Cost per request is visible on a dashboard.

Our data is confidential and must not train anyone else's model.

We use provider APIs with training on your data turned off and mask personal data before sending. If needed, we host an open-weight model on your own infrastructure.

What's included

  • Product review and choice of one AI scenario with a KPI
  • Model selection (OpenAI, Anthropic, Google or open-weight) for the task and budget
  • Data preparation and RAG: document chunking, a vector database such as pgvector
  • Prompt design and testing, with structured JSON outputs
  • In-product interface: chat, suggestions, streamed answers
  • Guardrails: input checks against prompt injection (attempts to trick the model), output filters
  • An evaluation set of test queries, re-run after every change
  • Request logging, rate limits and cost tracking
  • Fallback model in case a provider goes down
  • Documentation and handover of code, keys and accounts

Choose the scope

Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.

01

Pilot

You want to test one AI feature on real users without a large budget

  • Project brief and scenario with a KPI
  • One feature: assistant, text summary or data extraction
  • Connection to one data source
  • Test query set
  • Pilot results report
Discuss this scope
02

Production feature

The pilot worked and you need a stable feature for all users

  • RAG over your documents with source citations
  • In-product interface and streamed answers
  • Guardrails, limits and cost tracking
  • Automated quality tests
  • Fallback model and request log
Discuss this scope
03

AI product platform

Several AI features, AI agents that take actions in your system, complex access rules

  • Multiple AI features on a shared foundation
  • An AI agent that calls your API (creates, edits, looks up records)
  • Tenant separation and per-customer access rules
  • Quality and cost dashboard
  • Training for your team to maintain the system
Discuss this scope

How we work

01

Brief and requirements

You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.

02

Data and access

You provide a staging environment, sample documents and 20–50 examples of good answers. We create model provider accounts in your name.

03

Pilot

We build a minimal version and test it on the query set and a small group of users. Payment is in stages.

04

Production hardening

We add guardrails, limits, logging and the final interface. We check the KPI and decide together what to scale.

05

Handover and support

You receive code, documentation and keys. Optionally we stay on monthly support to watch quality and cost.

Scope and limits

  • We don't promise error-free answers: models can be wrong, and we reduce the risk with tests and sources.
  • We don't guarantee results without data: with no documents or examples of good answers, the feature won't work well.
  • We don't take on use cases where a model error could harm health or money with no human check.

FAQ

How much does LLM integration cost?

We prepare a quote after reviewing your brief and requirements. A first stage can cover: project brief and scenario with a KPI; One feature: assistant, text summary or data extraction. Scope, payment and schedule are agreed before work starts.

Which model do you use?

We pick per task: OpenAI, Anthropic, Google or open-weight models. We structure the code so the model can be swapped without rewriting the feature.

What do you need from us to start?

Access to a staging environment, sample data or documents, and a person who signs off on results. Ideally 20–50 example questions with correct answers.

Will the model provider see our data?

Requests go to the provider's API, but we turn off training on your data and mask personal data. If that isn't enough, we host an open-weight model on your own servers.

How do you measure quality?

We build a test set of queries with expected answers and run it after every change. We also track the pilot KPI and review real user queries in the logs.

Who owns the code and accounts?

We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.

Start with your task

Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.

Start a project brief