Académie Lavalloise

Transparency note. This first deployment took place within an organization owned by the founder of The Agensee, Académie Lavalloise. This decision was made deliberately, in order to design, test, and refine the solution under real-world conditions — with real data, real processes, and real compliance challenges — before offering it to external clients.

Executive summary

Académie Lavalloise is a non-subsidized private elementary school with approximately 250 students, located in the Laval region of Quebec. Like many organizations of comparable size, it faces a significant volume of recurring tasks — parent communications, payment processing, admissions tracking, invoice management, and regulatory compliance — that consume considerable time and are prone to errors.

The Agensee deployed Avelle there, its AI operations service. Avelle takes over twelve distinct operational processes that it executes autonomously on a defined schedule. Rather than starting everything from scratch, it produces work ready to be validated.

Académie Lavalloise served as the first deployment. It is the same service we deploy today for SMBs across North America.

Result: The equivalent of 35 to 50 hours of recurring manual work per week is now handled by Avelle. This time is transformed into just a few hours of supervision, with a significant reduction in routine errors and complete traceability — a major asset in the context of Loi 25.

The challenge

Small and medium-sized organizations face a structural dilemma: their operational volume increases, but their administrative capacity does not follow without costly hiring. In the private education sector, where margins are tight and qualified staff is difficult to find, this dilemma is particularly acute.

At Académie Lavalloise, leadership is particularly sensitive to this reality. Hiring additional staff would directly increase operating costs, which would put upward pressure on tuition fees — a path the school actively seeks to avoid in order to remain accessible to families.

Before Avelle was deployed, the Académie’s administrative processes presented the typical challenges of manual management:

• Repetitive communications: Every response to parents, every summons, and every confirmation had to be drafted individually.
• Risk of error and oversight: Misallocated payments, forgotten follow-ups, duplicate communications, and lost tracking were frequent.
• Variable response times: Tasks accumulated based on staff availability, creating bottlenecks.
• Compliance burden: The traceability required by Loi 25 added a layer of rigor that was difficult to maintain manually and consistently.

The solution: twelve automated processes

The Agensee deployed Avelle to take over twelve distinct operational processes. Each process is executed according to precise instructions, a defined schedule, and strict validation rules.

Here are the automated processes:

Guiding principle

Automation does not replace human judgment — it amplifies it. Every sensitive communication is prepared by the system, then validated by a manager before final sending. The human retains control of strategic decisions, while the machine absorbs the repetitive and time-consuming work.

Observed results

The indicators presented below answer the most frequent questions from organizations considering a similar transformation. In the interest of transparency, each piece of data is clearly identified as either measured, estimated, or qualitative.

1. Workload: before and now

Before the deployment, the twelve automated processes represented an estimated workload of between 35 and 50 hours per week. This volume corresponds to the equivalent of a full-time administrative position, or the distribution of these tasks across several people.

Today, this same work is condensed into a few hours of supervision and validation per week.

Methodology: This range was established by evaluating, process by process, the time that complete manual execution would require (reading, drafting, data entry, and verification), taking into account the organization’s actual volume.

2. Volume of prepared communications

The system continuously prepares a significant volume of communications for parents, including:

• Responses to common inquiries
• Admission exam summons
• Acceptance and refusal letters
• Enrollment confirmations
• Payment reminders
• Seasonal communications

Each communication is personalized from templates and presented ready to be validated by a manager before final sending.

3. Reduction of errors and tracking loops

One of the most tangible gains lies in the significant reduction of errors and manual follow-ups. The system integrates control mechanisms that prevent duplicates, improve payment reconciliation, and automatically detect anomalies.

Concretely:

• No communication is sent twice to the same recipient thanks to persistent state tracking.
• Payments are matched to the right records through variation-tolerant name matching.
• Duplicate email addresses within a single group are automatically flagged.
• Late payments are detected and reported systematically, without relying on human vigilance.

4. Response time to inquiries

The processes run every business day on a fixed schedule. An inquiry or payment received is processed at the next execution cycle — generally the same day or the next morning — rather than depending on someone’s availability. The daily morning review provides the manager with an up-to-date picture at the start of the day.

5. Time redirected to mission

The time freed from repetitive tasks is reinvested in higher-value activities: teaching quality, family relationships, and organizational development. Automation does not eliminate important work — it frees the capacity to fully dedicate oneself to it.

6. Financial savings

The main savings lie in the administrative capacity that would otherwise require hiring additional staff as operational volume grows. To this are added indirect gains: reduction of costly errors (mistracked payments, missed deadlines), tighter handling of receivables and payables, and better cash flow visibility. The model enables the organization to grow and manage greater volume without burdening its administrative structure.

7. Compliance and Loi 25

Loi 25 imposes rigorous obligations on Quebec organizations regarding the protection of personal information. Avelle’s infrastructure addresses this by design:

• Traceability: Every automated action is logged, creating a complete and verifiable audit trail.
• Communication confidentiality: Bulk mailings use blind carbon copy (BCC), thus avoiding exposing family addresses to each other.
• Controlled centralization: Sensitive data is processed in a defined and secured environment, rather than scattered across multiple tools or people.
• Treatment consistency: Rules are applied uniformly, without variations linked to ad hoc human decisions.

Five benefits that transcend sectors

While this deployment was carried out in a school, the observed benefits apply to any organization facing a high volume of recurring tasks — whether professional offices, clinics, retailers, service SMBs, or manufacturers.

Proof made on our own ground

The Agensee chose to design and test its solution within an organization that its founder owns and operates: Académie Lavalloise. This choice is not incidental. It means that the solution was developed and refined on real data, real financial processes, real exchanges with families, and real compliance challenges.

This approach guarantees that when supporting a new client, The Agensee does not propose a theoretical solution, but a proven infrastructure under real-world conditions, where each process has been tested, adjusted, and stabilized over the months.

And for your organization?

Every organization has its own recurring processes that consume time and expose to error. The Agensee designs custom automation infrastructures, tailored to your operational reality, your existing tools, and your regulatory obligations.

The question is not whether your repetitive tasks can be automated, but rather how much time and capacity you will recover once they are.

Appendix — Methodological note

In the interest of transparency, here is how to interpret the data presented in this document:

Estimate The ranges presented are derived from the time that manual execution of each process would require, evaluated according to the organization’s actual volume. They aim to provide an order of magnitude, not unit-level precision.

Qualitative Qualitative observations are based on the nature and design of the deployed processes. They do not claim a quantified measurement, but describe the mechanisms and effects observed.

Organizations wishing to obtain precise quantified data in their own context can, from the deployment, set up indicator tracking (processed volume, delays, error rates, etc.) in order to quantify gains on their actual data.