Internship & PFE Catalogue 2026 · Selection

15 PFE projects
with real impact

Cloud & DevOps, Development & Integration, AI & Data, Marketing — topics sized to deliver a demonstrable building block within a PFE (final-year project) of four to six months.

Cloud & DevOpsDevelopmentAI & DataMarketing
15Topics
4Axes
5Priority topics
4-6Months of PFE
Use the arrow to browse the catalogue →
Statement of intent

Clear axes,
a concrete result

This selection complements the existing catalogue with three priority axes for the agency: Cloud & DevOps / Infrastructure, a reworked Development & Integration axis and an AI & Data axis.

Each topic is sized so that, over a PFE (4 to 6 months), it delivers a functional, demonstrable building block that integrates directly into Navitrends' Odoo / ERPNext / n8n ecosystem.

Selection summary: 5 Cloud & DevOps topics, 4 Development & Integration topics, 3 AI & Data topics, 3 Marketing & Content topics kept from the existing catalogue.

Why this catalogue

What you gain from a PFE at Navitrends

01

A real project

Every topic answers a need of the agency and fits into Navitrends' Odoo / ERPNext / n8n ecosystem: not an academic exercise.

02

A demonstrable deliverable

At the end of the PFE: a working, tested and documented building block that you can present at your defence and in your portfolio.

03

An enterprise stack

ERP, containers, CI/CD, monitoring, automation: the tools technical teams actually use in industry.

Catalogue stack
OdooERPNextn8nDockerKubernetes (k3s)GitLab CI / GitHub ActionsPrometheus / GrafanaMinIO / S3PostgreSQLPythonWordPress
Way of working

How a PFE unfolds

  1. 01

    Scoping

    A precise problem, the users, the authorised data, the deliverables and the success criteria.

  2. 02

    Short prototype

    Quick feasibility check on a sample or a representative case.

  3. 03

    Iterations

    A testable version every week, with a demo and a decision log.

  4. 04

    Validation

    Testing of results, security, maintainability and usefulness for the team.

  5. 05

    Handover

    Code, documentation, tests, transferable access and an operations guide.

Our commitments
  • A limited scope and verifiable deliverables
  • Measurable success criteria, defined before the start
  • Regular technical supervision: you are never alone on a critical system
  • A usable, documented and reusable result for Navitrends
The 5 topics to handle first

Priority topics

Priority CLD1 Cloud & DevOps

Multi-tenant containerised platform for Odoo / ERPNext

Provision a new isolated client instance in minutes

ImpactA client instance ready in minutes, with no manual installation

View full sheet →
Priority CLD4 Cloud & DevOps

Proactive monitoring & multi-server alerting platform

Detect the incident before the client reports it

ImpactThe team alerted before the client: SSL, server down, stopped container

View full sheet →
Priority CLD5 Cloud & DevOps

Automated backup & disaster recovery plan (DRP) for multiple clients

Back up every server — and above all prove that restoration works

ImpactA proven, timed restore: the RTO becomes a number, not an assumption

View full sheet →
Priority DEV1 Development

Complete management of bills of exchange (Kembiala)

A reference application for the Tunisian market, connected to the ERP — beyond existing standalone solutions

ImpactParity with market solutions, plus automatic accounting in Odoo

View full sheet →
Priority IA1 AI & Data

Intelligent B2B prospecting platform

From collecting companies to creating qualified sales opportunities

ImpactFrom collected companies to qualified CRM opportunities, with a measured cost per qualified prospect

View full sheet →
Contents

The 15 topics of the selection

01Cloud & DevOps / Infrastructure5

02Development & Integration4

03AI & Data3

04Marketing & Content3

● priority topic

Axis 01

Cloud & DevOps / Infrastructure

The infrastructure that carries client projects

Create the environments, deliver to them cleanly, monitor, protect. The five topics form a coherent lifecycle: CLD1 provisions, CLD2 deploys, CLD3 inventories, CLD4 monitors, CLD5 protects.

5 topics in this axis
CLD1
CLD1 Odoo + ERPNext PRIORITY Cloud & DevOps / Infrastructure

Multi-tenant containerised platform for Odoo / ERPNext

Provision a new isolated client instance in minutes

Duration4 to 6 monthsProfileDevOps / Systems
Expected impact

A client instance ready in minutes, with no manual installation

Context

Every new client currently requires a manual ERP instance installation, which is slow and error-prone. The goal is a platform where an isolated client instance is created automatically.

Objectives

  1. Containerise an Odoo (or ERPNext) stack + database + reverse proxy.
  2. Automate the provisioning of an isolated instance (subdomain, SSL, volumes).
  3. Manage the lifecycle: creation, update, clean deletion.

Expected deliverables

  • Working provisioning platform on 2-3 pilot instances.
  • Operations documentation.

Technical environment

Docker / Docker Compose or Kubernetes (k3s)Traefik or NginxLet's EncryptPostgreSQL / MariaDB

Skills developed

DockerKubernetes (k3s)Reverse proxy & SSLProvisioning automation

Interested in this topic? Write to us quoting the code CLD1.

Apply for topic CLD1 → contact@navitrends.com
CLD2
CLD2 Odoo + ERPNext Cloud & DevOps / Infrastructure

CI/CD pipeline for Odoo / ERPNext modules

Make production releases more reliable and faster

Duration4 to 6 monthsProfileDevOps / Software engineering
Expected impact

Automatically tested releases, with a simple rollback

Context

Custom module developments are deployed manually, without automated tests. The aim is to make deliveries more reliable and faster.

Objectives

  1. Set up a structured Git repository with automated tests on the modules.
  2. Build a build → test → deploy pipeline (staging, then production).
  3. Allow a simple rollback on failure.

Expected deliverables

  • Working pipeline on a real module.
  • Test coverage report.

Technical environment

GitLab CI / GitHub ActionsDockerpytest / Odoo test framework

Skills developed

CI/CDAutomated testingGit workflowContinuous deployment

Interested in this topic? Write to us quoting the code CLD2.

Apply for topic CLD2 → contact@navitrends.com
CLD3
CLD3 Navitrends internal use Cloud & DevOps / Infrastructure

Hosted estate register (CMDB)

A central inventory of everything the agency hosts

Duration4 to 6 monthsProfileWeb & data development
Expected impact

A single source of truth replacing Excel files

Context

Estate information (which client, which server, which domain, which Odoo/WordPress version, SSL expiry, hosting provider) is scattered across Excel files. The goal is a central, up-to-date repository that also feeds monitoring (CLD4).

Objectives

  1. Model and centralise assets: clients, servers, domains, certificates, versions, hosting providers.
  2. Automatically track deadlines (SSL expiry, end of version support).
  3. Expose an API to feed monitoring and dashboards.

Expected deliverables

  • Operational central estate register.
  • Expiry alerts (SSL, versions).
  • Documented consumption API.

Technical environment

Web application + APIRelational databaseCollection scriptsIntegration with CLD4

Skills developed

Data modellingREST APIAutomated collectionExpiry tracking

Interested in this topic? Write to us quoting the code CLD3.

Apply for topic CLD3 → contact@navitrends.com
CLD4
CLD4 Navitrends internal use PRIORITY Cloud & DevOps / Infrastructure

Proactive monitoring & multi-server alerting platform

Detect the incident before the client reports it

Duration4 to 6 monthsProfileDevOps / Networks & systems
Expected impact

The team alerted before the client: SSL, server down, stopped container

Context

An incident (expired SSL certificate, unreachable server, stopped Docker container) is often discovered by the client. The goal is a platform that continuously monitors all servers, shows real-time status and alerts the team by email before the client does.

Objectives

  1. Collect each server's status: availability, SSL certificate expiry, Docker container status, resources (disk, memory, CPU).
  2. Detect and qualify incidents using rules (SSL expiring within 15 days, server down, stopped container, disk > 90 %).
  3. Display a central dashboard (green / orange / red) + incident history.
  4. Trigger an email alert (Slack / WhatsApp option), with anti-spam.
Scope boundary CLD4 / APA3 — The priority topic APA3 (monitoring agent + Helpdesk ticket) is centred on “AI agent + Helpdesk” within a pilot scope. CLD4 is centred on “infrastructure platform + multi-server dashboard”. If both are taken in the same season, APA3 consumes CLD4's detections and focuses on qualification and ticketing; CLD4 does not rebuild the ticketing agent.

Expected deliverables

  • Operational monitoring platform on a pilot estate.
  • Real-time dashboard + history.
  • Email alerts tested on the 3 cases (SSL, server down, stopped Docker).
  • Measurement of the average detection time before a client reports the issue.

Technical environment

Recommended hybrid approach: Uptime Kuma or Prometheus + Grafana + AlertmanagerCustom certificate / Docker layerLightweight agent (Python / Node) on each servern8n for alerting

Skills developed

ObservabilityPrometheus / GrafanaAlertingDocker monitoring

Interested in this topic? Write to us quoting the code CLD4.

Apply for topic CLD4 → contact@navitrends.com
CLD5
CLD5 Navitrends internal use PRIORITY Cloud & DevOps / Infrastructure

Automated backup & disaster recovery plan (DRP) for multiple clients

Back up every server — and above all prove that restoration works

Duration4 to 6 monthsProfileSystems & security
Expected impact

A proven, timed restore: the RTO becomes a number, not an assumption

Context

Losing client data would be critical. A centralised, encrypted backup system, tested through restoration, is needed. The intern does not rewrite a backup engine: they build the orchestration, centralisation and validation around proven tools.

Objectives

  1. Automate regular backups (databases + files) of all instances.
  2. Store them encrypted on object storage (S3 / MinIO), with a retention policy.
  3. Script and validate restoration on a test server, and time the recovery (RTO).
  4. Optional: backup dashboard (success/failure, last backup, n8n alert if a backup is missing).

Expected deliverables

  • Operational backup system across several servers.
  • Tested and timed restoration.
  • Documented retention policy.

Technical environment

MinIO or S3restic / borgbackupcron / n8nEncryption

Skills developed

Encrypted backupS3 / MinIO object storageDRP / RTOScripting & automation

Interested in this topic? Write to us quoting the code CLD5.

Apply for topic CLD5 → contact@navitrends.com
Axis 02

Development & Integration

Custom applications and connectors

High business-value applications, connected to Odoo.

4 topics in this axis
DEV1
DEV1 Navitrends internal use PRIORITY Development & Integration

Complete management of bills of exchange (Kembiala)

A reference application for the Tunisian market, connected to the ERP — beyond existing standalone solutions

Duration4 to 6 monthsProfileFull-stack developmentPositioningTunisian market
Expected impact

Parity with market solutions, plus automatic accounting in Odoo

Context

Bills of exchange (“traites”) have regained a central place in commercial transactions in Tunisia, and standalone solutions already exist on the market. The goal of the PFE is an application that matches these solutions on their key functions (multi-account, multiple due dates, status tracking, universal printing) and goes beyond them through accounting integration with the ERP, which is impossible with offline software.

Objectives

  1. Functional parity: complete entry (drawer, drawee, amount, due date), multi-bank-account management, multiple due dates, status tracking (pending / paid / unpaid), amount-to-words conversion (FR/AR), calibrated printing compatible with all printers.
  2. Portfolio of receivable and payable bills, with schedule, automatic reminders and cash-flow forecast.
  3. ERP differentiator: bill ↔ invoice reconciliation and automatic posting of the bills in Odoo.
  4. Bank remittances: generation of remittance slips (discount / collection) per bank, handling of unpaid bills and renewals.

Expected deliverables

  • Application reaching parity with market solutions, tested on a real printer.
  • Operational portfolio, schedule and remittance slips.
  • Accounting integration (reconciliation + posting) validated in Odoo.
  • Comparative note positioning the solution against existing products (internal benchmark).

Technical environment

Web application + APIOdoo AccountingCalibrated PDF / print engineRelational database

Skills developed

Full-stack webOdoo AccountingPDF print engineFinancial management (trade bills)

Interested in this topic? Write to us quoting the code DEV1.

Apply for topic DEV1 → contact@navitrends.com
DEV2
DEV2 Odoo Development & Integration

Helpdesk & ticketing platform with SLA

Reception, assignment, tracking and SLA reporting — connected to Odoo

Duration4 to 6 monthsProfileFull-stack development
Expected impact

Every request tracked, every response time under control

Context

Any company with customer support needs to centralise requests that currently arrive by email, phone or messaging, with no traceability or guaranteed response time. The goal is a complete ticketing platform, with SLA, integrated with Odoo Helpdesk.

Objectives

  1. Receive tickets from several channels (web form, email, optional WhatsApp) and create them automatically.
  2. Assign tickets (manually or by rules: category, workload, skill) and manage statuses and priorities.
  3. Implement SLAs: first-response and resolution times, breach alerts, automatic escalation.
  4. Provide a dashboard and reports (volume, average times, SLA compliance rate, workload per agent).

Expected deliverables

  • Operational multi-channel ticketing platform.
  • SLA engine with alerts and escalation.
  • Dashboard and performance reports.
  • Customer portal for ticket tracking.

Technical environment

Odoo HelpdeskWeb application + APIn8n (routing / notifications)Email / WhatsApp Business APIRelational database

Skills developed

Helpdesk & SLAOdoo integrationn8n automationMulti-channel API

Interested in this topic? Write to us quoting the code DEV2.

Apply for topic DEV2 → contact@navitrends.com
DEV3
DEV3 Navitrends internal use Development & Integration

Project and skills management cockpit

Reliable visibility on progress, workload, risks and estimate-vs-actual gaps

Duration4 to 6 monthsProfileBI, data, web development, information systemsFocusOrganisation
Expected impact

Reliable visibility on progress, workload and risks

Context

Give managers reliable visibility on progress, workload, risks and gaps between estimates and actuals.

Objectives

  1. Centralise projects, tasks, time spent and estimates.
  2. Provide a workload / capacity view per person and per period.
  3. Trigger alerts on delays, overruns and blocked tasks.
  4. Track skills and cross-training needs.

Success indicators

  • Gap between estimated and actual man-days
  • Time to detect blockers
  • Data update rate
  • Visibility on forecast workload
Watch-outThe project must integrate with the tools Navitrends actually uses rather than create a new parallel manual entry.

Expected deliverables

  • Documented data model and calculation rules.
  • Management dashboard with useful filters.
  • Alerts tested on representative cases.
  • Documentation and update procedure.

Technical environment

Existing project management tools (Odoo)Management dashboard with filtersRelational database

Skills developed

BI & dashboardsData modellingManagement alertsWorkload & skills management

Interested in this topic? Write to us quoting the code DEV3.

Apply for topic DEV3 → contact@navitrends.com
DEV4
DEV4 Odoo + ERPNext Development & Integration

Library of reusable ERP solutions and workflows

Reduce ad hoc development and speed up delivery of Odoo, ERPNext and n8n projects

Duration4 to 6 monthsProfileSoftware engineering, ERP, DevOps, automationFocusIndustrialisation
Expected impact

Less ad hoc development, projects delivered faster

Context

Reduce ad hoc development and speed up delivery of Odoo, ERPNext and n8n projects.

Objectives

  1. Identify recurring integrations and workflows.
  2. Create versioned, configurable, documented templates.
  3. Add tests and configuration checks.
  4. Prepare a deployment and rollback procedure.

Success indicators

  • Number of validated and reused components
  • Hours saved per project
  • Test and deployment success rate
  • Reduction in recurring defects
Watch-outStart with two or three frequent, proven cases rather than building an over-broad library with no users.
Complementarity CLD2 / DEV4 — CLD2 provides the CI/CD pipeline; DEV4 provides the reusable components (templates, integrations, workflows) that will be tested and deployed by that pipeline.

Expected deliverables

  • Initial library of reusable components.
  • Versioned repository with contribution conventions.
  • Automated tests on priority cases.
  • Before/after comparison of implementation time.

Technical environment

OdooERPNextn8nVersioned Git repositoryAutomated tests

Skills developed

Software engineeringOdoo / ERPNext / n8nAutomated testingDeployment & rollback

Interested in this topic? Write to us quoting the code DEV4.

Apply for topic DEV4 → contact@navitrends.com
Axis 03

AI & Data

AI applied to the agency's data and knowledge

Three projects that turn data and documents into measurable value: sales prospecting, internal knowledge and an industrial AI demonstrator.

3 topics in this axis
IA1
IA1 Navitrends internal use PRIORITY AI & Data

Intelligent B2B prospecting platform

From collecting companies to creating qualified sales opportunities

Duration4 to 6 monthsProfileData engineering, computer science, applied AI, automationFocusShort term
Expected impact

From collected companies to qualified CRM opportunities, with a measured cost per qualified prospect

Context

Industrialise the path from collecting companies to creating qualified sales opportunities.

Objectives

  1. Collect company data from authorised, documented sources.
  2. Clean, deduplicate, normalise and enrich the records.
  3. Score and segment according to defined business criteria.
  4. Push to the CRM and track campaigns.
  5. Provide a dashboard: volumes, quality, cost per qualified prospect and sales results.

Success indicators

  • Number of companies collected and enriched
  • Share of complete data and duplicate rate
  • Cost per qualified prospect
  • Response rate and meetings generated (once campaigns are launched)
Watch-outCollection must comply with the sources' terms of use, applicable regulation and prospecting rules. Technical scoring does not replace sales validation.

Expected deliverables

  • Documented, reproducible pipeline.
  • Test set with measured quality control and error rates.
  • Connector or standard export to the CRM.
  • KPI dashboard and operations guide.

Technical environment

Authorised data sourcesCRM (Odoo CRM)Reproducible data pipelineKPI dashboard

Skills developed

Data engineeringCleaning & enrichmentScoring & segmentationKPIs & dashboard

Interested in this topic? Write to us quoting the code IA1.

Apply for topic IA1 → contact@navitrends.com
IA2
IA2 Navitrends internal use AI & Data

Navitrends internal technical copilot

Find and reuse knowledge from projects, procedures and lessons learned

Duration4 to 6 monthsProfileGenerative AI, RAG, software engineering, knowledge managementFocusKnowledge capture
Expected impact

Team knowledge that can be found and reused, with answers always backed by their sources

Context

Make it easier to search and reuse knowledge from projects, procedures and lessons learned.

Objectives

  1. Structure a document base with access rights.
  2. Index technical documents and procedures.
  3. Implement retrieval-augmented generation (RAG) with references to sources.
  4. Evaluate answers and provide error-reporting mechanisms.

Success indicators

  • Average time to find information
  • Share of answers backed by a relevant source
  • Error rate observed on a test set
  • Number of reusable procedures and lessons learned
Watch-outConfidential client documents must be excluded by default or included only with authorisation and appropriate access controls.

Expected deliverables

  • Copilot prototype linked to the selected documentation.
  • Cleaned and classified initial corpus.
  • Test protocol on real questions.
  • Update guide and access security rules.

Technical environment

RAG (retrieval-augmented generation)Document base with access rightsDocument indexing

Skills developed

RAGDocument indexingAnswer evaluationAccess security

Interested in this topic? Write to us quoting the code IA2.

Apply for topic IA2 → contact@navitrends.com
IA3
IA3 Odoo + ERPNext AI & Data

Industrial AI demonstrator connected to an ERP

A credible industrial AI demo on production, quality or maintenance data

Duration4 to 6 monthsProfileAI, data science, Industry 4.0, industrial systemsFocusCommercial differentiationPositioningCommercial demonstrator
Expected impact

A credible industrial AI demo, connected to the ERP, that the agency can show to prospects

Context

Build a credible industrial AI demonstration based on production, quality or maintenance data.

Objectives

  1. Choose a narrow use case: non-conformities, anomalies, production indicators or decision support.
  2. Define an authorised dataset and document its quality.
  3. Build a prototype and compare the results with a simple baseline.
  4. Present the results in a dashboard or an ERP flow.

Success indicators

  • Performance measured on a test set
  • False-positive or error rate depending on the use case
  • Time saved or estimated operational improvement, explicitly qualified
  • Feedback from prospects or a pilot client
Watch-outAnnounced gains must be measured or presented as hypotheses, never as achieved results.

Expected deliverables

  • Working demonstrator on a defined use case.
  • Data quality report and evaluation protocol.
  • Demo dashboard or ERP integration.
  • Commercial sheet setting out benefits and limits.

Technical environment

ERP (Odoo / ERPNext)Production, quality or maintenance dataDashboard or ERP flow

Skills developed

Data scienceData qualityModel evaluationERP integration

Interested in this topic? Write to us quoting the code IA3.

Apply for topic IA3 → contact@navitrends.com
Axis 04

Marketing & Content

Automations usable in-house

Topics from the existing catalogue are kept — they balance the offer for profiles less focused on infrastructure.

3 topics in this axis
MKT1
MKT1 Navitrends internal use Marketing & Content

Automated blog generation pipeline

Topic → writing → publishing, without an advanced SEO layer

Duration4 to 6 monthsProfileAutomation & AI
Expected impact

A blog fed continuously, without tying up the team

Context

Regularly feeding a professional blog takes time that teams do not always have. The PFE delivers a pipeline that starts from a topic, writes an article consistent with the editorial line, and publishes it.

Objectives

  1. Orchestrate documentary research and the structuring of the article outline.
  2. Generate writing consistent with the company's editorial line.
  3. Automate formatting and publication on WordPress.

Expected deliverables

  • Operational editorial pipeline.
  • Quality-control charter for generated content.

Technical environment

n8nLLMWordPress REST API

Skills developed

n8n automationLLM & promptsWordPress APIContent ops

Interested in this topic? Write to us quoting the code MKT1.

Apply for topic MKT1 → contact@navitrends.com
MKT2
MKT2 Navitrends internal use Marketing & Content

Automatic SEO optimiser

Analyses the competition, fixes, republishes

Duration4 to 6 monthsProfileAutomation & AI
Expected impact

Articles brought back up to date against the competition, automatically

Context

An article's search ranking degrades over time against competitors who publish continuously. The PFE delivers a tool that compares an existing article with the competition on its keywords and proposes a corrected version.

Objectives

  1. Compare a published article with the best-ranked content on the same keywords.
  2. Identify structural and semantic gaps compared with the competition.
  3. Generate a corrected version and automate its republication after validation.

Expected deliverables

  • Operational SEO optimisation workflow.
  • Before/after comparison report per article.

Technical environment

n8nAhrefs / SEMrush APILLMWordPress REST API

Skills developed

SEOLLMAhrefs / SEMrush APIn8n automation

Interested in this topic? Write to us quoting the code MKT2.

Apply for topic MKT2 → contact@navitrends.com
MKT3
MKT3 Navitrends internal use Marketing & Content

“Quote” form qualification agent

Slack/WhatsApp notification, without heavy enrichment

Duration4 to 6 monthsProfileAutomation & CRM
Expected impact

A salesperson notified as soon as a quote request is submitted

Context

A quote request form filled in on the website deserves immediate handling. The PFE delivers an agent that notifies the relevant salesperson as soon as it is submitted, with the essential information from the form.

Objectives

  1. Automatically detect every new quote form submission.
  2. Immediately notify the relevant salesperson on Slack or WhatsApp.
  3. Automatically create the matching opportunity in the CRM.

Expected deliverables

  • Operational qualification agent.
  • Measurement of the average time to first contact.

Technical environment

n8nSlack / WhatsApp Business APIOdoo CRM or ERPNext CRM

Skills developed

Sales automationReal-time notificationsOdoo CRMn8n automation

Interested in this topic? Write to us quoting the code MKT3.

Apply for topic MKT3 → contact@navitrends.com

One PFE,
real deliverables

Choose a topic, build a concrete building block, used by Navitrends.

1Pick a topic and note its code (e.g. CLD1, DEV2, MKT3)
2Send your application stating the topic code
contact@navitrends.com

Full catalogue: stage.navitrends.com

Navitrends — Digital Engineering & Business Automation
FR
01 / 26