Intellarys Ingénierie
FR
Menu
Let’s talk
← Back to home

Client proof · EasyOpto

Regain control of your business software.

At training provider EasyOpto, changes to the CRM and mobile app depended on an external provider. The aim: restore the tools to service and give the founder the means to develop them further.

Lionel Bricard leads a training session in front of a room, with a projected screen behind him.

Unblock the tools. Hand over control.

The CRM, mobile app and infrastructure were taken over with a wider purpose: enabling Lionel to develop his own system.

Intellarys builds.
The founder takes over.

  1. Unblock

    Intellarys builds the foundation

    Scope the need together, recover the tools and access, then document the system.

  2. Guide

    Work side by side

    Practise on the real tool, write down the rules and adjust with the founder.

  3. Hand over

    The founder remains in control

    Develop the tool with an AI assistant, within the framework handed over.

Written rules, tests and backups stay with the system.

A simplified view of the engagement, with no time or workload scale.

What this engagement made possible.

1 → 20 tests
Within the documented mobile app scope: one failing test replaced by twenty passing tests, with an automated testing pipeline.
Code handed over
Code ownership set out in the contract, publishing accounts recovered and applications released from EasyOpto’s repository.
Test, then deploy
A test environment, guides and support enabling the founder to validate and release changes.

These outcomes relate to the EasyOpto engagement. The test count reflects the documented state at delivery, not a coverage measure or a guarantee of bug-free software.

Their collaboration, on film.

EasyOpto · The client story

Lionel Bricard and Sylvain Andlauer discuss their collaboration. French audio, with English on-screen text and subtitles, in the format suited to your screen.

Safeguard changes. Plan ongoing support.

Each change follows a framework: a traceable proposal, checks and a decision to release.

Approval
unlocks the next step.

The founder keeps the decision.
  1. Propose

    A traceable change.

  2. Check

    Automated tests and checks.

  3. Approve

    The founder decides.

  4. Deploy

    Back up, then release.

  5. Verify

    Check the site; roll back if needed.

Checks inform the decision. The release waits for the founder’s approval.

An illustrated safeguards workflow: checks are defined for the system.

The framework stays in place.

Tests, backups and checks support changes. They help detect problems and prepare a rollback; they do not replace review.

Support when needed.

The proposed follow-up includes routine audits and explained, prioritised fixes. The founder approves and chooses who makes the changes.

Proposed optional follow-up, separate from the completed engagement. Scope and frequency to be agreed.

« I was stunned by the new ecosystem my company was projected into: there is radically a before and an after. »

Lionel BricardFounder and CEO, EasyOpto

Your tools should grow with your business.

Let’s start with a specific bottleneck in your working day.