Skip to main content
AI consulting and software development

Decide what to build with AI. Then we build it.

We tell you which parts of your operation are worth automating with machine learning and language models, then design, build and deliver the application into production. Fixed scope, fixed price, agreed before work starts. You own the code.

  • 1-week assessment · 2–6-week builds
  • Fixed scope, fixed price
  • You own the code

Free, 30 minutes, no preparation. You leave knowing whether your case is clear enough for a proposal, needs a one-week assessment first, or is not a fit.

Prefer email? hello@xval.ai

What we do

Two kinds of work. Advice on what to build, buy or leave alone; and the build itself, delivered running in your systems.

Advise

AI assessment

1 week, €2,500, credited against a build that starts within 90 days. We go through your operation and your data and come back with a ranked list of what is worth automating, what to buy instead of build, what to leave alone, and a fixed-price proposal for the first build.

Review of an existing AI project

A pilot that stalled, a tool that was bought and not adopted, or a system another supplier built. We tell you whether it can reach production, what it would take, and whether it is worth it.

Training for your team

Half-day to two-day sessions for the people who will use AI at work: what it can and cannot do, how to use it safely with company data, and how to spot the next task worth automating.

Build

Document and workflow applications

Invoices, contracts, claims, supplier files, emails, tickets. Language models read them, extract what matters, classify, route and answer, with a person in the loop where the decision matters.

Forecasting and prioritisation

How many units will sell, how many people are needed on Saturday, which of 500 applications to look at first, which customers are about to leave. Models trained on your history, answering every week automatically.

Search and assistants over company data

Thousands of projects, records, manuals or tickets in your systems. Staff ask in plain language and get the right record, version or answer back, with the source attached.

AI features inside your product

Classification, extraction, recommendations or an assistant inside the software you sell. We work in your repository, follow your conventions and ship behind your feature flags, with evaluation data your team can rerun.

One clear, scoped workflow goes straight to a fixed-price proposal. Several candidates, an open question, or a stalled pilot go through the assessment first. When the agreed build needs a pipeline or dashboard to run, it is included in the fixed scope.

Example first builds

Not every project needs a model trained on years of history. Many first builds use language models to read, write or search what the company already has. One clear operational need, one working system.

  • Manufacturing

    Purchase orders typed into the ERP

    Orders arrive as PDFs, scans and emails. AI reads each one and creates the order in the ERP. A person checks only the ambiguous ones.

  • Food & ingredients

    Supplier onboarding files

    Each new supplier sends a stack of documents. AI checks them against the required list and the regulation, and fills in the file for the quality team.

  • Waste & recycling

    Field photos checked automatically

    Photos come back from every collection round. AI spots the anomalies and writes a standard report with the evidence attached.

  • Retail & e-commerce

    Product descriptions from product data

    Descriptions written and translated from the data already in the ERP, in the brand’s tone. The merchandising lead approves before anything goes live.

  • Print & packaging

    Ask your project system a question

    Thousands of projects, versions and proofs in a bespoke tool. Staff ask in plain language and get the right record, version or history back.

  • Software & fintech

    Transaction categorisation inside the product

    A categorisation service in the company’s own codebase, with an evaluation set the team reruns on every release. Customers see categories; engineers see the metric.

How it works

One call, then either a proposal or a 1 week assessment, then a fixed-price build with a fixed end date. Assessments are €2,500, credited once against a build that starts within 90 days. Most builds are €5,000–€25,000 depending on data and integration scope. Maintenance is optional.

  1. 01

    Assess

    Free call · 1 week assessment when needed

    On the call you describe the task and the data; we say whether it is feasible. If the case is clear, you get a written proposal within a business day. If it is not, we run a 1 week assessment: data audit, ranked candidates, build-or-buy per candidate, a go/no-go and the proposal. Nothing is built before you sign off.

  2. 02

    Build

    2–6 weeks · fixed price

    We connect to your data, design the architecture, build the application and deliver it where your team works: your ERP or line-of-business system, your product, a service your systems call, or a dashboard. The build ends with results against the acceptance test and a handover of everything we made.

  3. 03

    Operate

    Monthly · optional · cancel anytime

    We host, monitor and keep the system accurate: drift checks, retraining with new data, fixes and new features as your business changes. Or your team runs it; the choice is yours.

What you can count on

  • Fixed scope and fixed price, agreed in writing before we start.
  • Acceptance test in plain numbers, agreed before the build, measured on delivery.
  • You own everything we create: code, models we train, prompts, tests and documentation. Third-party models stay under their own licences; your data stays yours.
  • Assessment deliverables are yours and written so any supplier could act on them.
  • Runs on your servers or on our cloud. Maintenance and hosting available if you want them.
  • If the delivered system does not meet the acceptance test on the agreed evaluation data, we keep working at our cost — or you do not pay the final milestone.

How we engineer AI applications

A chat tool gives you an answer. An application gives you the same answer tomorrow, inside your systems, with a number that says how often it is right. The difference is engineering.

  1. 01

    Architecture

    We decide which part of the problem is a classifier, a forecast model, a retrieval layer or a language model, and where a person stays in the loop. The cheapest component that passes the acceptance test wins; a trained model is used where it beats a prompt, not by default.

  2. 02

    Evaluation

    Before the build: a baseline (what your team achieves today), a held-out evaluation set, and the metric in plain numbers. Every release is scored against it. You keep the evaluation set and can rerun it on any future version, ours or anyone else’s.

  3. 03

    Delivery

    Delivered into the system where the work happens, with tests and documentation. In your repository and conventions where you have one. Implementation is AI-assisted; the engineer who owns the architecture and the acceptance test reviews and tests every change before release.

  4. 04

    Operation

    Monitoring, drift checks and retraining as a monthly service, or a documented handover (code, tests, runbooks, evaluation set) so your team or another supplier can run the system without us.

Who does the work

Pedro Marcelino, founder

  • PhD; research in machine learning, time-series forecasting and decision analysis, cited around 780 times.
  • Owns the specification, architecture and acceptance test on every xval.ai build.
  • The person you meet on the call is the person accountable for the result. No sales hand-off.

Verify: LinkedIn · Google Scholar

Questions we get before the call

Is my problem a fit?
Good fit: a task your team repeats often and can check objectively. Reading and filing documents, answering questions from company records, forecasting a number, deciding which cases to look at first, a feature inside your product. What data it needs depends on the task: document and search work starts from the files you already have; forecasting and prioritisation need past cases with the outcome. If you have one clear task, book the call. If you have several candidates or none yet, the 1 week assessment exists for exactly that. Not sure? Email a redacted sample and the task to hello@xval.ai.
What data do you need?
Exports from the systems you already use: your database, your platform, spreadsheets, CSV files, document folders. Nothing has to be clean. Every assessment and every build starts with a data audit where we tell you what is usable and what is missing. For models trained on history, a few thousand past cases with the outcome is a good rule of thumb.
Does it connect to our systems or codebase?
Yes; that is where the work is delivered. Operational builds connect to your ERP, WMS, CRM or line-of-business system through its API, database or file exchange, and push results back the same way. Product builds are written in your repository, in your language and conventions, and shipped as pull requests your engineers review. Integration effort is part of the fixed scope, not an extra.
We already tried an AI pilot. Can you look at it?
Yes. Bring the pilot, the tool that was bought and not adopted, or the system another supplier built. We assess whether it can reach production, what it would take, and whether it is worth it, and say so in writing, including when the answer is no.
What do I get at the end, and who owns it?
The working system delivered where your team works, with results against the acceptance test (for example: forecast error, share of documents filed correctly), plus everything we created to build it: code, models we trained, prompts, tests and documentation. You own all of that and can run it yourself or with another team. Third-party models and software (for example a language-model provider) stay under their own licences, and your data, including any evaluation data you supplied, remains yours throughout.
Where does it run, and who maintains it?
Either on your servers or on our cloud; we recommend once we know the data volume and where it lives. Maintenance, monitoring and retraining are available as a monthly service, cancel anytime. The handover includes code, tests, runbooks and the evaluation set, so you can take it in-house or to another supplier at any point.
How do you protect our data?
Before any data is transferred we agree in writing where it is stored, who can access it, which subprocessors (including AI model providers) are used, how long it is kept and how it is deleted. We sign a data processing agreement where required, and we can work entirely inside your environment so data never leaves it.
What happens if the agreed result is not achieved?
The acceptance test is written into the proposal before the build starts. If the delivered system does not meet it on the agreed evaluation data, we keep working at our cost or you do not pay the final milestone. Your obligations (data access, a named contact, evaluation data) are written into the same proposal.

Find out if your workflow is a fit.

In a free 30-minute call we look at the task and the data behind it. You leave with one of three answers: a fixed-price proposal for a clear build, a one-week assessment when the question is still open, or a straight “not a fit”.

  • No preparation
  • Straight answer in 30 minutes
  • Proposal or assessment plan within a business day

30 minutes with Pedro Marcelino, founder. No sales hand-off.

Prefer email? hello@xval.ai