ASSA ABLOY Global Solutions · KEYper EMEIA · Proposal by LEGNA

Proposal for KEYper EMEIA · ASSA ABLOY Global Solutions

Every vehicle in the DMS, automatically in KEYper Go.

One platform, built once, that connects any dealer management system to KEYper Go — starting with Keyloop in the UK.

Approve now

EUR 35,200 net

Then

EUR 650 / month managed service

Each further DMS

from EUR 7,600 net

Scroll to read ↓

Chapter 01 · Why

The DMS is the record dealers trust. KEYper Go should follow it.

The DMS stays the master record; KEYper Go receives vehicles and stays in sync.

~70%

of UK dealers on Keyloop

10,000+

dealerships on Nextlane

1

platform, built once

Today

Vehicles are typed into KEYper Go by hand or bulk-loaded from a DMS export before a key can be attached to a FOB. It is slow and error-prone, and KEYper Go drifts away from the DMS — the system dealers trust.

Tomorrow, with AXLE

KEYper Go receives vehicles automatically from the DMS and stays in sync as they change.

Keyloop serves ~70% of UK dealerships
Dealer groups choose key systems that follow their DMS
Competitors already claim DMS integration

Chapter 02 · What AXLE is

One integration core, agnostic on both ends.

Dealer systems on the left, key management on the right, and a single platform in between that every DMS and every phase reuses.

Dealer systems (DMS)

AXLE · integration core

Key management

How to read it

Solid = Phase 1 (this proposal) Dashed = designed for, not includedClick any block for detail.

Built once

Reused by every DMS and phase.

Agnostic on both ends

Any DMS in, any key system out, through one common vehicle model.

Operated, not just delivered

No infrastructure for KEYper to run, full freedom: containers, installers and source code delivered under the Framework Agreement.

Chapter 03 · Phase 1 · scope

Platform + Keyloop connector, live with a UK dealer.

Create, update and archive vehicles automatically, starting with a live UK dealer.

Create

New or used vehicle enters stock, or a service booking is created → Asset created in KEYper Go with VIN as key, searchable name per dealer convention, make/model/colour/references in attributes.

Update

Registration plate assigned, data changes → Asset updated automatically.

Archive & reactivate

Vehicle sold or leaves · vehicle returns → Archived and kept, ready to reactivate when it returns.

  • Initial stock load of the pilot dealer
  • Users and permissions stay in KEYper Go
  • FOB attachment stays in KEYper Go

How it is delivered · 10–14 weeks from availability of environments

  1. 01 · 2 weeks

    Stage 0

  2. 02 · 6–9 weeks

    Build

  3. 03 · 2–3 weeks

    Pilot & acceptance

  4. 04 · 3 months

    Hypercare

  5. 05 · Ongoing

    Managed service

Details
  • Stage 0: Technical validation against the real Keyloop and KEYper Go APIs, signed Baseline, price fixed
  • Build: Platform, Keyloop and KEYper Go connectors
  • Pilot & acceptance: With a live UK dealer
  • Hypercare: Close monitoring and tuning
  • Managed service: Operated by LEGNA

From Keyloop and KEYper: Keyloop Partner Programme access; KEYper Go test environment, credentials and a contact for decisions within 5 working days; a UK pilot dealer. No KEYper R&D effort.

Chapter 04 · Roadmap

Phases 2 and 3, and further DMS — each its own decision.

Every connector and later phase reuses the core and remains a separate order.
  1. 1Phase 1

    Platform + Keyloop

    The integration core and the first DMS connector, live in the UK.

    Priced: Fixed price

    What it needs

    Keyloop partner access, KEYper Go environment, pilot dealer.

  2. 2Further DMS

    One connector each

    Standard or complex connectors added to the same core.

    Priced: Assessment/discovery first, then fixed price

    What it needs

    Vendor access; assessment (standard) or discovery (complex).

  3. 3Phase 2

    Key status back to the DMS

    Current key status in the DMS: in/out, holder, time, vehicle location.

    Priced: Discovery first, then fixed price

    What it needs

    DMS write-back capability per vendor.

  4. 4Phase 3

    Key operations without opening KEYper Go

    An operations API — list free FOBs, attach/detach, reserve/release — with VOLONIA as LEGNA's voice/WhatsApp channel. The DMS-side button belongs to the DMS vendor.

    Priced: Design first, then fixed price

    What it needs

    KEYper Go operations endpoints; DMS vendor for the button.

Chapter 05 · DMS candidates

KEYper's list, read for access and cost.

Standard, probable, complex or to be confirmed — every reading is confirmed in writing with the vendor before a fixed price.
Reading
Country

Standard

Keyloop

Phase 1

UK

20,000+ retailers, ~70% UK

Details

Access model found
Published Partner Programme, JSON APIs, test environment, certification

Vendor cost found
KEYper figures: ~GBP 5k first market, GBP 1k per extra market, min GBP 25/site/year; press: 20–30% revenue share

Nextlane

FR + 11 markets

10,000+ dealerships

Details

Access model found
Public developer portal, API key, sandbox; 39 interfaces, 1,336 connected dealers, 179k calls/day

Vendor cost found
Not published

Standard probable

incadea

DE, international

4,000+ businesses

Details

Access model found
API-first cloud platform, partner ecosystem; no public docs

Vendor cost found
Not published

Pentana / SIPAD

IT

400+ Italian dealerships

Details

Access model found
Integrated Partner Program, tailored one- or two-way interfaces

Vendor cost found
Not published

Helios Auto

Nordics

1,000+ workshops

Details

Access model found
Open API, 150+ integrations

Vendor cost found
Not published

Complex

Cross (Porsche Informatik)

DE/AT, VW Group

1,600+ dealerships

Details

Access model found
Retail API exists; German market via dx.one (VW subsidiary); third parties go through it

Vendor cost found
Quote via VW subsidiary: EUR 12,000 connection, 18,000/yr, 3,000/month API, 4/transaction

Pinewood

UK

Major groups

Details

Access model found
Integrations exist but closed suite, no partner programme

Vendor cost found
Not published

To be confirmed

Loco-Soft

DE

3,400+ businesses

Details

Access model found
Many OEM/third-party interfaces, per-partner specs, no public API

Vendor cost found
Not published

Quiter

ES

2,200+ dealerships

Details

Access model found
Integrations exist (payments, paint, reviews); no public API

Vendor cost found
Not published

movec

AT/CEE

~1,000 installations

Details

Access model found
Public docs; file-based interfaces found

Vendor cost found
Not published

Vendor logos are the property of their owners and are shown for identification only.

Standard = documented API, direct access, cloud. Complex = intermediary, certification or per-dealer installation. Readings are provisional until the vendor confirms in writing. Other names on the list (Fleetback/Sharebox, vAutoStock, TKP, JobRouter, Evosec, Salesforce, Avanti, Hillmark) are other systems, so they sit outside this table.

Chapter 06 · Pricing

Price list

One platform now, further connectors and phases only when ordered.

How the price works

LEGNA list price44,000Framework Agreement (ASSA ABLOY · LEGNA, 2025)−20 %Your price35,200

You save EUR 8,800 on Phase 1 alone

The same 20 % applies to every one-off item in this proposal, as it did to the previous LEGNA deliveries under the Framework. Managed service fees are fixed monthly amounts.

Now: Phase 1

EUR 35,200 net

list 44,000

Paid once · 60% kick-off, 40% acceptance · then EUR 650/month managed service

The only decision requested today

Later: each further DMS

from EUR 7,600 net

list 9,500

Standard connector EUR 7,600 net · Complex connector EUR 13,200 net · paid once per DMS, each a separate order after its assessment or discovery

Later: Phases 2 and 3

EUR 24,800 net

list 31,000

Phase 2 (key status back to the DMS) EUR 24,800 net with Keyloop · Phase 3 design EUR 4,000 net, build priced in the design

Net = what KEYper EMEIA pays. List = LEGNA's standard rate. The difference is the 20 % discount agreed in the Framework Agreement between LEGNA and ASSA ABLOY, applied to every one-off item. Managed service fees are fixed monthly amounts and are not discounted.

Chapter 07 · Build your programme

Your programme. Four clear decisions.

The platform today; further DMS, later phases and connected dealerships on your terms.

1 · Platform

The platform and Keyloop are the decision today; further options are separate orders.

AXLE platform + Keyloop connector

Included

EUR 35,200 net

The decision today

Stage 0, integration core, Keyloop connector, live UK pilot and 3 months hypercare.

2 · Which DMS next?

Each DMS adds a connector; groups of three Standard connectors receive the block price.

Other DMS

Standard · EUR 7,600
0
Complex · EUR 13,200
0

Vendor logos are the property of their owners and are shown for identification only.

Loco-Soft and Quiter count as Standard for this estimate; their reading and price remain subject to assessment.

3 Standard connectors ordered together: block price applies automatically.

3 · Later phases

Add key status or operations API design later, under separate orders.

Phase 2 · key status back to the DMS

EUR 24,800 net with Keyloop

Additional DMS with write-back
+ EUR 5,200 each · midpoint of range
0

Phase 3 · design of the key operations API

EUR 4,000 net

Build priced in the design.

4 · Managed service: how many dealerships will be connected?

The monthly fee follows the number of connected dealership sites, not cabinets.

3

Stage A ≤3

EUR 650 / month

Stage B ≤15

EUR 950 / month

Stage C ≤40

EUR 1,600 / month

Stage D ≤80

EUR 2,400 / month

Above 80 dealerships: EUR 2,400 + EUR 30 per additional dealership. Stage A · EUR 650 / month.

One connected dealership = one dealership site whose DMS is synchronised through AXLE, whatever the number of cabinets.

Included in the monthly fee

Cloud hosting of AXLE (isolated production and test environments), encrypted credentials, backups, monitoring and alerting, security and platform updates, adaptation to minor API changes of connected systems, second-line support to the KEYper team, service objective 99.5% (A/B) / 99.7% (C/D)

Not included

New connectors, new phases or new functionality (separate orders); DMS vendor fees (Keyloop, Cross… paid by KEYper); first-line support to dealers (KEYper's)

Billed quarterly in advance from the first full month after hypercare · 12-month minimum · stage change by written agreement

1 / 4

Chapter 08 · Vendor costs

Vendor costs

Paid directly to the DMS vendors — not part of LEGNA's price.

Paid directly to the DMS vendors — for the business case, not part of LEGNA's price

Keyloop

Certification GBP 5,000 first market + 1,000 per additional market · minimum GBP 25 per activated site per year · revenue share 20–30% of what KEYper invoices dealers.

One-off certificationGBP 5,000
Keyloop share per yearGBP 1,250
KEYper net integration revenue per yearGBP 3,750

Cross (quote received via a VW subsidiary; terms unconfirmed)

EUR 12,000 connection · 18,000/yr maintenance · 3,000/month API · 4 per transaction.

Year 1EUR 162,000
Each following yearEUR 150,000

Figures as reported by the KEYper team and public sources, November 2026. Nextlane, incadea, Pentana, Helios, Loco-Soft, Quiter, movec and Pinewood do not publish terms; to be requested in writing. The GBP 500 site fee is a placeholder.

Chapter 09 · Business case

What the integration earns, DMS by DMS

Test the programme with KEYper EMEIA's own assumptions.

Assumptions are placeholders for KEYper EMEIA to replace; LEGNA has no visibility of KEYper's prices or margins.

What decides the case is KEYper's penetration on each DMS and the vendor's own fees, more than the connector price.

What drives the case

Integration fee

KEYper charges each connected dealership a yearly fee for the integration (Keyloop already expects a share of it)

New sites won

Dealer groups choose key systems that follow their DMS; each site won because of the integration leaves a one-off margin

Less manual load

Fewer errors, fewer disconnected customers; not quantified here

Global assumptions

DMS by DMS

EUR net · excl. VAT · linear ramp

Managed service is shared equally across included DMS. Average connected sites over the horizon = end sites ÷ 2.

DMSInstalled basePenetrationCase · 3 yearsIn programme

Keyloop (Phase 1)

Standard · approximate UK sites

Net
EUR 195,425
ROI
298%
Payback
0.75 yrs
In programme

Nextlane

Standard

Net
EUR 124,125
ROI
594.6%
Payback
0.43 yrs
In programme

incadea

Standard (probable)

Net
EUR 95,125
ROI
455.7%
Payback
0.54 yrs
In programme

Pentana / SIPAD

Standard (probable)

Net
EUR 37,125
ROI
177.8%
Payback
1.08 yrs
In programme

Helios Auto

Standard (probable)

Net
EUR 37,125
ROI
177.8%
Payback
1.08 yrs
In programme

Cross

Complex

Net
EUR -236,915
ROI
-71.9%
Payback
> horizon
In programme

Loco-Soft

To be confirmed

Net
EUR 72,125
ROI
272.4%
Payback
0.81 yrs
In programme

Quiter

To be confirmed

Net
EUR 42,925
ROI
205.6%
Payback
0.98 yrs
In programme

Chapter 10 · Why LEGNA

Why LEGNA · how we make this safe for you

Proven delivery, an operated platform and a project built to protect your investment.

What you get with LEGNA

  • ASSA ABLOY key-management add-ons already in production
  • A small senior team you talk to directly
  • Radical transparency
Details
  • Continuity guaranteed: containers, installers and source code under the Framework
  • LEGNA operates the platform, so KEYper runs nothing

How the project protects your investment

  • Stage 0 before building
  • A signed Baseline, then a fixed price
  • Written change control
Details
  • Acceptance on a live dealer
  • Schedule follows Keyloop access day for day, at no cost
  • KEYper Go API changes handled as contained change
  • Fixed service stages

Chapter 11 · Decision & next steps

Decision & next steps

One approval starts Stage 0; everything else can follow in parallel.

What we ask you to approve now

Phase 1 — EUR 35,200 net (list 44,000), 60/40, 10–14 weeks from environments, 3 months hypercare, then managed service from EUR 650/month.

This commits KEYper EMEIA to Phase 1 and its managed service, and to nothing else.

We can start now

To start Stage 0 (week 1)

  • Signed Phase 1 order (or Stage 0 on its own, EUR 3,600 net (list 4,500), deductible)
  • A KEYper contact for decisions within 5 working days
  • KEYper Go test environment and credentials

To complete Phase 1 (can follow in parallel)

  • Keyloop Partner Programme access requested by KEYper
  • UK pilot dealer nominated
  • Security requirements and contracting entity confirmed
  1. OrderSigned
  2. Stage 02 wks
  3. Build6–9 wks
  4. Pilot & acceptance2–3 wks
  5. Hypercare3 months
  6. Managed serviceOngoing

Proposal valid for 30 days · Contact: Angel Gómez-Castrillón Marañón, LEGNA Southern Europe.

Not part of this proposal or its prices. Shown so the roadmap is understood end to end. Separate product, separate agreement.

Annex · VOLONIA, the Digital Brain (future, not included)

VOLONIA · a Digital Brain for the dealership

VOLONIA is LEGNA's conversational intelligence layer. It stores the business knowledge of the organisation and makes every interaction smarter than the last — in any language, adapting to how each person speaks, and resolving their requests quickly, efficiently and securely from WhatsApp, Teams, Telegram, voice or any conversational channel. For customers, dealership staff and managers alike.

Digital Brain

Knowledge lives in the system, not in people's heads: vehicles, keys, processes, who may do what, what happened before. Every answer and every action feeds it back, so the brain gets better with use.

Any language, any voice

Understands and replies in the user's language and register — a mechanic's shorthand, a manager's question, a customer's message — and learns each person's way of speaking.

Any channel

WhatsApp, Teams, Telegram, voice notes, phone, web chat: the same brain behind all of them, with the same permissions and the same audit trail.

Everyone, with the right rights

Customers (where is my car, when is it ready), staff (where is the key, reserve it, who has it), managers (what is out after closing, what happened with that vehicle). Per-dealership authorisation, user attribution, every action logged through AXLE.

One scenario, end to end

Illustrative. Names, plates and times are fictional.

09:41
VOLONIA · Avanti Motors GranadaStaff · English
Illustrative scenario
Message

0 / 8 messages

What just happened, step by step

  1. 1

    Voice in

    The note is transcribed and understood (intent: locate key + reserve; entities: colour, model, plate, time).

  2. 2

    Vehicle resolved in the DMS

    AXLE's common vehicle model maps plate → VIN → asset (Keyloop today; any connected DMS tomorrow).

  3. 3

    Key located in KEYper Go

    Cabinet, slot, in/out status and last movement, read through the KEYper connector.

  4. 4

    Action through the operations API (Phase 3)

    Reserve, release, attach/detach, with per-dealership authorisation, user attribution and audit.

  5. 5

    Answer back in the same channel

    WhatsApp, Teams or voice; every action is logged in AXLE's audit trail.

Employee · voice/WhatsAppVOLONIA · understands & decidesAXLE operations API
DMS connectorKEYper Go connector

How it builds on AXLE

AXLE supplies the vehicle data from the DMS, the key status from KEYper Go and, with Phase 3, the operations API. VOLONIA sits on top and always works through AXLE's authorisation and audit

What it needs

Phase 1 in production; Phase 2 for key status; Phase 3 for actions. Offered under its own agreement; nothing here is priced

What it is not

Not a DMS button; not a replacement for KEYper Go; not included in Phase 1