Explore a partnership Versão em português

Platform

The platform behind every automotive process.

Caetano Core manages processes, documents, payments, communication and partners in a single system, from the moment a request comes in to completion. This page describes what each module does, what problem it solves and who uses it.

Overview

A single system, built inside a real operation.

The platform was born at Legaliza na Hora, the group's vehicle registration brand, to follow each vehicle from the receipt of the documents to the Portuguese number plate.

More than 10,000 vehicles processed since 2015, with processes able to reach the Portuguese number plate in under 24 hours. Today, the same foundation serves Caetano Trust, Caetano CarGo, LH Finance and Caetano COC. A process that spans several brands does not require information to be repeated.

Scope
Processes, documents, payments, communication and partners.
Origin
The Legaliza na Hora operation, since 2015.
Who uses it
The teams of the group's brands, professional partners and clients following their own process.
Relationship with third parties
Partnerships and integrations assessed case by case. The platform is not sold to third parties at this stage.
Principle
Automation within rules. Decisions and official submissions made by people.
Illustrative representation
Illustrative representation of the process dashboard. It does not show a real screen or real data.

End-to-end flow

Six stages. Four roles in each.

The operational tracks show who acts at each stage. Partner, team and platform work on the same process and see the same status.

  1. Request

    Partner
    Submits the request in the partner portal.
    Team
    Receives and confirms the request.
    Platform
    Opens the process and assigns the first status.
    Human sign-off
    MandatoryRequest confirmation.
  2. Documents

    Partner
    Sends documents as a photo or PDF.
    Team
    Requests what is missing, within the process.
    Platform
    Reads the documents and links them to the right process.
    Human sign-off
    ReviewAutomatic reading, reviewed by the team.
  3. Validation

    Partner
    Follows the status.
    Team
    Validates each document.
    Platform
    Flags what is missing.
    Human sign-off
    MandatoryEach document validated by a person.
  4. Payment

    Partner
    Pays by Multibanco, MB WAY or card, where applicable.
    Team
    No action
    Platform
    Reconciles the payment with the process.
    Human sign-off
    Not requiredAutomatic reconciliation.
  5. Operation

    Partner
    Follows the status.
    Team
    Submits on public portals.
    Platform
    Records every action, with date and author.
    Human sign-off
    MandatorySubmissions always made by people.
  6. Completion

    Partner
    Sees the completed process.
    Team
    Closes the process.
    Platform
    Keeps the full history.
    Human sign-off
    MandatoryClosed by the team.

MandatoryReviewNot requiredHuman sign-off at each stage.

Modules

Each module solves a problem the team used to solve by hand.

For each module: what it does, which operational problem it solves and who uses it. The modules share the same process and pass information to one another.

Process management

What it does
Follows each vehicle from the receipt of the documents to completion. Statuses, deadlines, owners and documents sit in the same record.
Problem it solves
Without a single record, knowing where each vehicle stands depends on emails, spreadsheets and the memory of whoever handled the case.
Who uses it
The brands' teams, who work on the processes. Partners and clients see the status their role allows.
Illustrative representation
Illustrative representation of a process status. It does not show a real screen or real data.

Documents and OCR

What it does
Receives documents as a photo or PDF, reads them automatically and links them to the right process. The mobile app lets you photograph a document and send it on the spot.
Problem it solves
Documents from several countries arrive in different formats, through different channels, and get lost between inboxes.
Who uses it
Clients, partners and the team, to send. The team, to validate each document.
Illustrative representation
Illustrative representation of the documents area of a process. It does not show a real screen or real data.
Illustrative representation
Illustrative representation of the mobile app with document reading. It does not show a real screen or real data.

Partner portal

What it does
Gives each professional partner its own access to submit requests, send documents and follow the status of its processes.
Problem it solves
A partner with several vehicles in progress asks for updates by phone and email, one vehicle at a time.
Who uses it
Dealers, importers, transport companies and financial institutions, under the terms of each partnership.
Illustrative representation
Illustrative representation of the partner portal. It does not show a real screen or real data.

Payments

What it does
Integrates payments by Multibanco, MB WAY and card into the process itself. Each payment is automatically reconciled with the process it belongs to.
Problem it solves
Checking by hand that each payment matches the right process slows the work down and leaves room for errors.
Who uses it
Clients and partners, to pay. The team, to see the status of each payment within the process.
Illustrative representation
Illustrative representation of payment reconciliation. It does not show a real screen or real data.

Communication within the process

What it does
Keeps messages and information requests within the process itself, alongside the documents and the status.
Problem it solves
When communication lives outside the process, whoever picks up the case next does not know what has already been asked or answered.
Who uses it
The team, clients and partners, each within their own process.

Integrations

Connections between organisations, assessed case by case.

The platform already exchanges information between the group's brands and with partners. Each new integration is assessed before it is built.

What we assess in each integration

  1. What data is exchanged and for what purpose.

  2. In which direction: from the partner to the platform, from the platform to the partner, or both.

  3. With which access role: the partner sees only what concerns it.

  4. Where human validation sits: what the integration prepares and what is still confirmed by a person.

Illustrative representation
Illustrative representation of an integration between organisations. It does not show a real screen or real data.

Automation and AI

Automation prepares. People decide.

AI agents handle repetitive work within rules. The limits are fixed and apply to every process and every brand.

What it does

  • Handles repetitive work within defined rules. Tasks that repeat in every process are no longer done by hand.

  • Reads documents and links them to the right process. The team receives the document already where it needs to be validated.

  • Flags what is missing. An incomplete process becomes visible before it causes delays.

  • Prepares and organises the team's work. Whoever validates finds everything gathered in the same process.

What it never does

  • No automatic submission to government portals. The person who validates and submits is always a member of the team.

  • No agent uses personal credentials. Including the founder's. Agents work only with the access assigned to them.

  • No destructive operation without approval. Deleting or changing data in bulk requires approval and a prior backup.

  • No final decision without a person. Decisions and official submissions stay with the team.

Roles and permissions

Each role sees what it needs. Nothing more.

Access is defined by role. A person or a partner only sees and only does what their role allows.

Platform roles: what each one sees and does
RoleSeesDoes
Brand teamsThe processes and documents their role allows.Validate documents, request what is missing, submit on public portals and close processes.
PartnerIts own organisation's processes, under the terms of the partnership.Submits requests, sends documents and follows the status.
ClientThe status of their process.Sends documents and pays, where applicable.
Group brandsThe same process, when it spans several brands.Work on the same foundation, without repeating the client's information.

Security and backups

Fixed development rules.

They apply to all development and the entire operation of the platform. They do not depend on who is working.

  1. Separate environments

    Development and production are kept separate. Development does not work on real data.

  2. Backup before changes

    Any bulk change is preceded by a backup.

  3. Approval for destructive operations

    Deleting or changing data in bulk requires explicit approval.

  4. Role-based access

    Each person and each partner accesses only what their role allows.

  5. Audit trail of every action

    Every action is recorded in the process, with date and author.

  6. GDPR

    Personal data is processed for the purpose of each process, with limited access.

See security and GDPR in detail

Human sign-off

At the critical moments, a person decides.

Technology speeds up the work. Responsibility for every official submission and every sensitive operation stays with a member of the team.

  • Document validation

    Automatic reading prepares. A person confirms each document.

  • Submissions on public portals

    Always made by a member of the team, never by automation.

  • Destructive or bulk operations

    Only with approval and with a backup made beforehand.

  • Closing the process

    The team confirms that the process is complete.

Technical FAQ

Technical questions.

Short answers to the questions most often asked by technology teams and partners.

All frequently asked questions

Can the platform be bought or subscribed to?

No. At this stage, Caetano Core does not sell software to third parties. External relationships are partnerships or integrations, assessed case by case.

Which integrations are available?

Each integration is assessed case by case: what data is exchanged, in which direction and with which access role. The technical form of the connection is defined with each partner.

Do automation or AI submit requests on government portals?

No. No submission to government portals is automatic. The person who validates and submits is always a member of the team.

How does automatic document reading work?

Documents arrive as a photo or PDF, including through the mobile app. The platform reads them and links them to the right process. Each document is then validated by a member of the team.

How are payments reconciled?

Payments by Multibanco, MB WAY and card are linked to the process they belong to and reconciled automatically.

Can a partner see other partners' processes?

No. Access is role-based. Each partner sees only its own organisation's processes, under the terms agreed in the partnership.

See the platform in a technical conversation.

We show you the platform in detail and assess with you which data, access and stages it would make sense to connect to your operation.