Tesla Technologies & Software
EN ES RO

Consortium partner

The partner you bring in when the hard work package has no owner

We coordinate a Horizon Europe action, we run two more on our own and our security is certified rather than promised. If the technical risk in your proposal is the part nobody wants to sign for, that is the part we take.

Spanish SME · R&D centre in Santiago de Compostela · delivery hubs in Madrid, Manchester, Buenos Aires and Arad

Send us the call and the gap Check the record first

The seat

Four seats in a consortium, and we have sat in all four

Tell us which one is empty in your proposal. Every one of these carries the project that proves it, and the register where you can check it without asking us

  • Coordinator

    Somebody has to hold the consortium together, keep the deliverables on the calendar and answer the project officer. We do that job today, not in a past life

    Proof IMAGINE-SOIL SOILSCAPE

  • Work-package leader and technology partner

    The package with the integration risk inside it. In RACON we were the technology partner of the consortium, and the award names the company with its tax ID in the official journal — you can read our role without taking our word for it

    Proof RACON ConectaPEME · DOG

  • Experiment owner, executing alone

    Two cascade-funding calls won and executed with no consortium to lean on. We wrote the experiment, we ran it and we reported it — which is the same discipline your work package needs, minus the meetings

    Proof AuraSec ResilMesh HoloCast-6G 6G-PATH

  • Technical lead in an industry programme

    Q-Stream is ours: we proposed it, we coordinate it and we lead it technically, in the IBC Accelerator and with BFBS, the IET and Associated Press validating the chain with us. Second year running inside the programme

    Proof Q-Stream IBC Accelerator

Scope

What we can own inside your proposal

Five capabilities, one engineering practice, and a project in operation behind each one. If your topic sits across two of them, better — that is usually where the package nobody claims lives

  • Getting the signal through when the network won't

    Live contribution and immersive media in adverse conditions

    Proven by Q-Stream HoloCast-6G

  • Seeing the attack before it happens

    Early detection and operational resilience

    Proven by AuraSec

  • Deciding with AI that can be explained

    Applied AI with decision traceability

    Proven by AURA IMAGINE-SOIL

  • Proving your data to a regulator

    Indicator certification and verifiable reporting

    Proven by Indicages

  • Shipping R&D without stopping the operation

    Integration into critical and industrial systems

    Proven by AMFEAFIP RACON

This is what we are asked for most, not all we do. Much of what we build runs under NDA and is never named in public — banking cores, operator platforms, systems in hospitals and government agencies.

Due diligence

The annex data, without an email exchange

Copy it straight into the proposal. The three security documents are the real files, not a badge on a page

Ask for the PIC and the declarations
Legal name
Tesla Technologies & Software S.L.
Legal form
Private limited company · Spanish SME
Tax ID
CIF B70305578
Registered address
Rúa Fontiñas 92 · 15703 Santiago de Compostela · Spain
R&D centre
Santiago de Compostela, Galicia
Delivery hubs
Madrid · Manchester · Buenos Aires · Arad
Working languages
English · Spanish
Security and quality
ISO/IEC 27001:2022 · TÜV AUSTRIA
ENS · RD 311/2022
Security policy, published in full
On request
PIC, LEAR contact, declarations of honour and letter of intent

The rules

What we sign for, and what we won't

  • The engineers who wrote the work package are the ones who execute it. No handover to a delivery team after the kick-off
  • We publish the measurement, including the KPI we did not meet. Your reviewers will see the number before they ask for it
  • We answer the project officer ourselves on our part, and we hit the deliverable dates that are on our name
  • We do not join a consortium to be a logo in the annex while somebody else does the work
  • We do not sign a work package we cannot staff on the dates in the Gantt
  • We do not promise a TRL we cannot demonstrate, and we will tell you so while the proposal can still be changed

Getting started

Three steps, and the first one costs you half an hour

  1. The call and the gap

    Topic, deadline and which package has no owner. Half an hour on a call is enough for both of us to know whether this is a fit

  2. One page back

    Tasks, deliverables, person-months and the TRL we go in and out at, written to drop into the proposal. If we think the package is undersized we say it here, not at the review

  3. Signed and in the annex

    Entity data, declarations and letter of intent the same working day. Nothing in this step should ever be what makes you miss a deadline

Deadline in under three weeks? Put it in the first line and we answer the same day. Most consortia look for the missing partner late — that is normal, and it is not a reason not to write.

Send us the call and the gap

An engineer reads it, not a sales desk. Under NDA when it has to be

Send us the call and the gap info@teslatechnologies.com