TL;DR

A Note From Ysi

I have loved purpose for as long as I can remember.

Not just success. Purpose.

The kind of work that has a reason underneath it. The question of why we are here and what we are meant to do with the time we get. That pull showed up early in me and never left.

It is built into the company, too. One of the words behind the name Vantelira is Telos. It is Greek. It means the end goal, the purpose, the reason a thing exists at all. So it is no accident that one of our core practices is serving mission-driven organizations.

This week's letter is a special edition for exactly that reason.

I want to show you the work a non-profit shelter in Montréal is doing to fight homelessness. Not by managing it after the fact. By stopping it at the source.

And if you know me, you know there is nothing I love more than a problem solved at the root. Do not get me started on root cause analysis. 😃

So let me introduce them.

The Model the Province Just Decided to Fund

Maison du Père is a Montréal organization that has spent decades on homelessness. Most people know the shelter work.

The part I want to talk about is less evident, and to me, more powerful. Prevention. Keeping someone in the home they already have, before they ever lose it.

Think about what that actually means.

A family stays at the table they already sit at. A person keeps the address on their ID, the bus route they know, the neighbour who waves. The crisis never happens. That is the whole point.

That work has a name in policy circles now.

On May 7, 2026, Premier Christine Fréchette announced 28 million dollars to fight homelessness across the Montréal, Québec City, and Outaouais regions. The largest share, 21 million, funds a 1,000-home pilot of rent-supplement prevention: when a household is at imminent risk of losing its home, that home is converted to subsidized housing so the tenant can stay and pay only a quarter of their income in rent. The approach is built directly on the model Maison du Père and the OMHM developed on the ground.

Why is a newsletter about process before tools and operations improvement telling you this?

When a model gets scaled with public money, the question changes. It stops being "did you help people this quarter." It becomes "can you show, the same way every time, that the help worked."

That is not a compassion problem. It is an operations problem.

Someone has to produce those numbers, period after period. And if they are doing it by hand, that time comes straight out of the work itself. Out of the hours meant for the person facing eviction.

It is the exact same problem a growing food brand has when a retailer asks for its numbers. Which is the part that still amazes me, and where this story is going.

An initiative this important needs infrastructure underneath it. Something to carry the intake, the decisions, the aid, and the proof that it worked, without stealing the team's time to do it.

That is what we built with Maison du Père. Internally it's called SIPI. It is live, in production, handling real cases and real money. This is not a pitch for something we might build. It is a look under the hood of something that already runs.

The Real Workflow, Not the Documented One

And it did not start with software. It started on paper.

Before we wrote a single line of code, the entire system lived on butcher paper, taped up, the whole flow drawn in marker. Two ways a person enters. A triage step. The documents they need. The aid they qualify for. Who signs off. Sticky notes stuck on the open questions nobody had answered yet, like whether a small emergency loan could be auto-approved or had to go to a human every time.

The dashboard, the part everyone pictures first when they think "software," was the very last box on the wall.

I have spent my career mapping how operations actually run, from Fortune 500 supply chain rooms to growing food brands trying to keep up with their own demand. At Vantelira, we embed inside an organization, watch how the work really happens, and build the infrastructure that runs without us.

The wall is where every build starts. Because the wall is the only place you find out that the documented process and the real one are two different things.

Every organization has two versions of how it works.

There is the documented one. The org chart and the policy binder, the version that gets described in meetings. And there is the real one, the version the people doing the job actually follow, with all the workarounds and judgment calls that never made it into the binder.

Build software for the documented workflow and you build a tool people have to fight. Build for the real one and you build infrastructure they own.

So we did not start with screens. We embedded alongside the case workers and watched how they actually managed a caseload. How a referral really comes in. What they check first when someone is at risk. Where a file stalls. The wall came out of those weeks. By the time anything became software, the hard decisions had already been argued out in marker, in the room, with the people who live the work.

Before SIPI, every case already had notes. They just lived in separate Word documents, scattered across a shared drive. There was a record. They needed a single source of truth they could pull from.

Today it runs on one system. One place that carries the whole flow, from a person's first contact to the proof, months later, that they stayed housed.

The Work That Was Getting Crowded Out

Here is the part I want every operator to sit with.

The most expensive thing these teams were spending was not money. It was time. And it was the wrong people's time.

Before SIPI, a case worker's week carried a quiet tax. The numbers funders need do not assemble themselves. Someone had to pull them together by hand, period after period: copying from one sheet into another, reconciling figures that never quite lined up, rebuilding the same report every cycle.

Hours that should have gone to a person facing eviction went to wrangling spreadsheets instead.

That is the real cost of running an operation on manual processes. It is not that the data is missing. It is that gathering it eats the hours meant for the actual work.

A social worker did not train for years to spend their afternoon re-keying a report. A founder did not start a company to rebuild the same inventory sheet every Monday.

So the goal was never a prettier dashboard. The goal was to hand people their time back.

We have a name for how we get there: process before tools. Map the real work first. Build the system so the numbers become a byproduct of that work, captured once as the case worker does their job, and let the reports build themselves from there. The same entry that records an intervention for a participant is the entry that shows up, already counted, in the funder's report. Nobody assembles anything twice.

There is a bonus waiting on the other side of that. When a number comes straight from the work instead of being copied by hand three times, it also happens to be right. But correctness was the side effect. Time was the point.

The Same Shape Underneath Two Very Different Businesses

Now the part that surprised even me.

Around the same time, we built an operating system for a growing Canadian food brand. Different universe. Retail buyers, co-packers, trade shows, not prevention casework.

And yet, underneath, it was the same business shape and the same broken pattern.

The founder's words, before we started, could have come from any operator running blind. "We can't get ahead, we keep running out of things." "Everything they do for us is perfect, it's just too slow." "We have a lot of opportunities we're not seizing right now."

Chronic stockouts across multiple products. A reactive loop of crisis to co-packer to new crisis. Every decision started with a scramble to find the real numbers first, because the picture of the business lived in a half-dozen places and someone had to assemble it before anyone could act.

Sit those two organizations side by side and the resemblance is almost uncomfortable.

A homelessness charity runs an intake-to-processing-to-fulfillment funnel: a person is referred or walks in, gets triaged, gets served, and you check months later whether they stayed housed. A food brand runs the identical shape: an order comes in, it draws down inventory, it gets produced, it ships.

Different nouns. Same funnel. Same gates where a decision has to be made and someone has to sign off.

And they get stuck identically. Both were pouring hours into keeping the lights on instead of moving forward. The charity's outcomes lived in spreadsheets someone had to stitch together by hand every reporting period. The brand's real inventory lived somewhere its books could not see, so every move started with a hunt for the truth.

In both, the team's best hours went to chasing and assembling information instead of using it. The work the organization actually exists to do kept getting pushed to the bottom of the list.

The one-liner I keep coming back to: a homelessness charity and a food brand get stuck the same way, because both spend their best hours assembling a picture of the business instead of acting on it.

And because they get stuck the same way, the fix is the same. Not a dashboard. Map the real funnel, build the single source of truth so the picture assembles itself, and give the team back the hours they were losing to the hunt.

That is the move that turns a reactive operation into one that can see what is coming. The brand's own way of describing the change said it best: they went from "we're always catching up" to "we know what's coming."

What Actually Changed

Start with the work, because that is what changed first.

For Maison du Père, the day-to-day stopped depending on who remembered what. The whole journey, from a first referral to whether someone stayed housed, now lives in one place the team works in together. A file does not stall because the one person who knew it is out that day. Anyone can pick it up, see where it stands, and keep it moving.

That changes what the team can take on. They can respond to a referral faster, carry more cases without the work turning to chaos, and keep a clear, current view of the donor and government funds they steward, where the money is going and what it is doing, instead of piecing that together after the fact.

The same steps happen the same way every time, which is exactly what you want when the stakes are someone's home.

Then the reporting. It used to be its own job, rebuilt by hand every cycle. The system is built so it never has to be again. The same entries a case worker already makes are the ones that will feed the funder's report, instead of being reassembled from scratch at reporting time. They have not run that first official cycle through it yet. But the by-hand rebuild is already designed out, so when reporting time comes, those hours go to the people the organization exists to help, not the spreadsheet.

And it is theirs. Client-owned from day one, built so their in-house team runs it after we step back.

For the food brand, the change showed up first in how they ran, not in what they could report. They went from a reactive loop, crisis to co-packer to new crisis, to a planning rhythm where they could see what was coming and act before it hit. Going into the next show, the team already knew which product would run short and walked in with firm ship dates. They had stopped reacting.

And the numbers followed. Sales more than doubled at the first trade show after we engaged, compared with the show before. Stockouts went from chronic, across the line, to a single product. North of 25% year-over-year growth, and roughly doubled annual capacity as production stabilized.

Two organizations that share no customers, no sector, and no mission. One playbook. That is the whole point.

The goal was never a better dashboard. It was getting your people's hours back from assembling data, so they can spend them on the work only they can do.

How to Use This Monday Morning

  1. Count the tax. Add up the hours your team spends each month assembling, re-keying, and reconciling numbers for one recurring report. That figure is what manual process is costing you, and it is almost always bigger than you think.

  2. Find the double entry. Look for any fact that gets typed in more than once: once to do the work, again to report on it. Every one of those is time you can hand back, and they are your highest-return fixes.

  3. Map before you build. Before you commission any tool, put the real workflow on a wall with the people who do the work. The tool is the last box. Build it first and your team keeps doing the manual gathering anyway.

P.S. If you run a mission-driven organization and your team spends more time assembling the numbers than acting on them, that is the exact problem we just solved with Maison du Père. Reply. I'd genuinely like to hear what you're up against. 🖤

Ops Intel

Five items operators (and the people funding them) should have on their radar right now.

Canada's Competition Bureau opens a review of the entire food supply chain. ↑ When the regulator starts pulling apart pricing from production to shelf, "we'll assemble the numbers later" stops being a strategy, and clean cost data becomes the price of doing business.

One in four people in Canada now face food insecurity, per Food Banks Canada's 2026 Poverty Report Card. 👀 Demand on mission-driven organizations keeps climbing while budgets tighten, and the ones who can show their outcomes cleanly are first in line for the next dollar.

CPG's "growth at all costs" era is over, and investors now want profitability. ↓ Capital is rewarding margin and operational discipline over ad-fueled growth, so the brands running tight operations are the ones still closing rounds.

Canada's nonprofit sector is "starved" as the social-service load outruns its funding. ↓ The sector absorbing more of the safety net has the least slack to spare, which makes every hour lost to manual reporting an hour taken straight from the mission.

96% of small and mid-sized businesses say tariffs have hurt their sourcing or supply chain. 👀 A small operator cannot out-scale a tariff shock, so visibility into suppliers and lead times is the one lever they actually control.

If this was useful, the best thing you can do is forward it to one person who is drowning in data they cannot use yet. We build the quiet infrastructure that makes an operation legible to itself, whether it ships product or prevents homelessness. If that sounds like you, or someone you know, reply. We read every one.

Ysi

Vantelira Inc.

Let us help you.