You only need one.

The intelligence layer above AI models.

Yonoo selects a suitable AI for each task and compares several when needed. Engineering is our first market.

Investor brief · Antler · September 2026 · Confidential
02 · Problem

Engineers spend too much time finding and verifying evidence.

Scattered sources

Requirements, test results and decisions live in different systems.

Too many AI choices

Teams must select models and assess conflicting answers.

Manual verification

Engineers still have to find the current source and check the conclusion.

The cost is time spent checking before a decision can be made.

02
03 · Solution

Ask once. Yonoo coordinates the intelligence.

01

Engineering task

02

Understand and route

03

One model or Fusion panel

04

One synthesised response

Fusion runs several models independently on the same question, then compares their answers and surfaces where they disagree.

Live routing and panels Next source-level evidence links and deeper engineering workflows
03
04 · How it works

One specialist, or several perspectives.

Simplified view · full decision flow in appendix
04
05 · Customer

Engineering first. Expand from a proven workflow.

Where we start

Automotive, aerospace, energy and industrial engineering.

Buyer: an engineering or digital leader.

Today

Manual search, and manual comparison of AI models.

With Yonoo

Coordinated model access, with evidence-connected enterprise workflows being developed.

Target pilot: requirements review — which requirements lack acceptance criteria?

05
06 · Differentiation

Independent of the model. Built around the task.

Model independence

Models are selected for the task and can be replaced as the market moves.

Routing and comparison

Our own logic decides when one model is enough and when several should be compared.

Founder engineering expertise

Built by people who have worked inside the engineering organisations we sell to.

Yonoo Intelligence layer — routing, comparison and synthesis
Below Interchangeable models and deployment infrastructure
06
07 · Traction

From product launch to enterprise opportunities.

Jan 2026

Problem identified

Engineering teams juggling models and sources.

Feb – Apr

Product built

Routing and multi-model panels in production.

May – Jul

User growth

Adoption without paid acquisition.

Aug 2026

Partner integration

Yonoo embedded in a partner platform.

Sep 2026

Live partner pilot

Pilot running, enterprise conversations open.

Enterprise conversations

Bugatti Rimac · FEV · KONČAR

Conversations in progress. Not signed customers and not committed revenue.

07
08 · Metrics

Early adoption. A live partner pilot. Three enterprise conversations.

1,698
Registered accounts
~3,700
Total audience including anonymous trials
1
Partner API pilot live
3
Enterprise conversations
Commercial stage

Enterprise opportunities in discussion; paid enterprise conversion is the next milestone.

Company-reported snapshot, September 2026. The total audience already includes registered accounts — the two figures are not additive.

08
09 · Revenue model

One core. Two routes to revenue.

Direct enterprise

Sold to the engineering organisation

LicenceProposed annual licence plus usage.
DeploymentDeployment fees where required.
StatusProposed — pricing not yet contracted.
Platform partners

Embedded inside another product

ModelEmbedded routing and orchestration.
PricingUsage or active-user pricing.
StatusReported agreed — structure agreed, one pilot live.

License the intelligence. Reuse the core.

09
10 · Unit economics

Each active seat contributes about €8 a month.

€8.50
Revenue per active seat per month, both lines at list price
90%
Contribution margin after AI cost and payment fees
€20.4k
Annual value of a 200-seat deployment
1,300
Seats to cover €10,000 of monthly fixed cost
Not yet measurable

No customer is contracted at these prices, so acquisition cost, churn and payback have no cohort to be measured against. Break-even is a seat count, not a cost problem.

AI cost measured from provider-reported tokens on the EU-sovereign configuration, at list prices. Contribution after AI cost only — infrastructure, support and salaries are excluded, so this is not an all-in gross margin. Deployment value is arithmetic at list price, not a signed contract. Detail in appendix A4.

10
11 · Scale

Build once. Configure. License. Expand.

01

Build once

One routing and orchestration core serves every channel.

02

Configure

Customer configuration rather than bespoke rebuilds. Direction, not yet delivered.

03

License

The same core sold direct and embedded in partner platforms.

04

Expand

Adjacent engineering workflows and an ecosystem around the layer. Roadmap.

One core  Routing · comparison · synthesis Reused across every stage

Stages 2 and 4 describe direction and roadmap, not capabilities already delivered. The four-phase commercial path is in the appendix.

11
12 · Team

Engineering insight. Commercial execution.

Korina Mlinarević

CEO & Co-Founder

Rimac, Lilium and Airbus Defence & Space. Product and enterprise development.

Casper van het Hof

Co-Founder

C-level commercial experience. Previously built and exited an AI product. Commercial strategy and partnerships.

Next: technical leadership, platform engineering and enterprise integration.

12
13 · The ask
€500,000
Pre-seed

Turn early demand into paid enterprise delivery.

01

Source-level evidence

Answers connected to the document and clause they came from.

02

Enterprise controls and deployment

The security, audit and deployment options enterprises require.

03

Paid pilot conversion

Convert open conversations into paid enterprise pilots.

Indicative 18-month execution plan. Target first paid enterprise pilots: Q4 2026 / Q1 2027.

13
14 · Use of funds

Where the €500k goes.

Product intelligence & AI 35%€175,000
Engineering & infrastructure 30%€150,000
Security & compliance 15%€75,000
Customer deployment & success 10%€50,000
Operations & legal 10%€50,000
Total 100%€500,000

Illustrative allocation from the original deck, applied to the €500k raise.

14

You only need one.

Help us bring the Yonoo intelligence layer into engineering enterprises.

casper@yonoo.aikorina@yonoo.ai
15
Appendix A1 · Full decision flow
Complete architecture · branch detail on A2 and A3

Agreement between models is not proof of correctness.

A1
Appendix A2 · Fusion branch
Detail view of A1 · same architecture, not a variant
A2
Appendix A3 · Smart Routing branch
Detail view of A1 · same architecture, not a variant
A3
Appendix A4 · Unit economics detail

The same economics, per unit sold.

Smart Router — per 1,000 requests
Revenue€4.00
AI costUnder €0.10 — the routing decision. Model inference is carried by the customer against their own provider contract.
Contribution€3.90
97% contribution margin
Orchestration — per 1,000 runs
Revenue€35.00
AI cost€5.00 to €10.00, measured on the EU-sovereign panel from provider-reported token usage.
Contribution€25.00 to €30.00
71% to 86% contribution margin
Per active seat, per month  €8.50 revenue · €0.35–€0.65 AI cost · €7.60–€7.90 contribution ≈90% after payment fees

Two conditions hold these figures. The same panel on frontier models costs €90 to €130 per 1,000 runs — roughly three times the metered price — so frontier orchestration is not offered on the metered plan. And the inference pass-through requires per-customer cost attribution, which is being built before the pilot.

Measured from provider-reported token usage at list prices, no volume discount. AI cost only, not an all-in gross margin.

A4
Appendix A5 · Commercial path

Four phases. Not a revenue forecast.

Phase 01

Validate

Prove the workflow inside a real engineering team. Requirements review is the target pilot.

Phase 02

Monetise

Convert the pilot into a paid enterprise agreement and settle the pricing structure.

Phase 03

Replicate

Repeat the same workflow across comparable engineering organisations.

Phase 04

Scale

Add adjacent workflows and grow the partner channel on the same core.

Sequence  Validate → Monetise → Replicate → Scale Order of work, not a timeline

From the original deck's commercial path. No revenue, break-even or runway figure has been modelled; those are recorded as not supplied in the presenter notes.

A5