Helsa Sanschagrin Joins Sengo as Chief Operating Officer

An Announcement That Means a Lot to Us

Today we are announcing Helsa Sanschagrin as Sengo Chief Operating Officer. This one means a lot to us. Sengo adds people deliberately, and everyone who joins has to change what the firm can actually do. Helsa does.

She spent 15 years in insurance. Over that time, she built a reputation as a reference in her field. On every project she has been part of, she became the person people called when it mattered. That kind of reputation is not accidental.

What she brings to Sengo is operational rigor, along with the ability to move things forward quietly but without compromise.

Fifteen Years of Insurance Operations Rigor

Insurance operations is an unforgiving discipline. Policies, claims, and compliance obligations move on fixed calendars, and regulators do not accept “almost”. As a result, the people who last in that environment develop a specific instinct. They find the step that will break before it breaks.

Helsa spent 15 years sharpening that instinct. Consequently, she reads a process the way our architects read a system diagram. She sees where the load concentrates, where handoffs get dropped, and where a small gap turns into an expensive one.

Two habits transfer directly. First, insurance teams run on documented process, because an undocumented process becomes a liability the moment someone leaves. Second, they plan for the exception rather than the happy path. Enterprise platform work rewards both. Migrations fail in the edge cases, and the client who inherits the system needs that documentation long after we are gone.

That background also fits the organizations we serve. Sengo delivers for regulated, high-accountability clients — among them iA Financial Group, the Fonds de solidarité FTQ, and the Commission de la construction du Québec. Therefore, an operations leader who already speaks the language of compliance and financial services is not a nice-to-have. She is a fit.

Why Sengo Appointed a Chief Operating Officer Now

Sengo now holds official implementation partnerships across eight platforms: Sitecore, Optimizely, Contentful, Storyblok, Kentico, Coveo, Netlify, and ai12z. Meanwhile, our team carries two Sitecore Technology MVP awards and hands-on Coveo engineering experience.

Breadth like that creates a real problem, however. Every additional platform multiplies the ways a project can be scoped, staffed, and sequenced. In other words, vendor-neutral advice only holds its value if the delivery behind it stays consistent. That consistency is an operations problem, not an engineering one.

Until now, operations lived where operations tend to live in firms our size — spread across whoever had capacity, and ultimately on the founder’s desk. That arrangement works until it does not. Growth turns a hundred small judgment calls into a bottleneck, and the bottleneck lands on the person least able to step away from client work.

For that reason, we created the role. It exists so delivery quality never depends on which platform a client picked, or on who happened to be free that week.

What the Sengo Chief Operating Officer Role Covers

As Sengo Chief Operating Officer, Helsa owns how the firm runs day to day. Specifically, the mandate spans delivery operations, staffing and capacity planning, quality standards across engagements, and the client experience from first call to final handover.

Our mission commits us to transferring knowledge so clients become autonomous on their own platforms. That promise only holds, however, if engagements end cleanly — documentation finished, skills genuinely handed over, nobody left dependent on us by accident. Helsa’s mandate includes making sure they do.

She also inherits our bilingual delivery model. Sengo works in English and French across Quebec, the rest of Canada, and francophone Europe. Running that consistently in two languages takes deliberate operational design rather than goodwill.

What Changes for Sengo Clients

For clients, the short answer is less friction and more predictability.

Concretely, you should notice tighter scoping conversations up front. In addition, you should see clearer commitments on timelines and fewer surprises mid-engagement. When something does slip, you should hear it from us first — not discover it yourself three weeks later.

None of that promises perfection. Projects still hit surprises, and enterprise platform work in particular resists tidy estimates. What changes is who owns the response. Previously, a delivery hiccup escalated to whoever noticed it first. Now it escalates to someone whose actual job is resolving it.

Our vision has always described a deeply human approach built on transparency and active listening. Transparency needs machinery behind it, though. Someone has to guarantee that the status you receive reflects reality on the ground. That is now a named responsibility, held by the Sengo Chief Operating Officer.

What Comes Next

Helsa starts by listening. First, she is meeting the team and walking through every active engagement. Second, she will map how we currently scope, staff, and close projects. Only after that will she change anything.

That order matters. Operational rigor imposed without context tends to break the things that already work, and we would rather move carefully than look decisive.

Beyond that, expect her fingerprints on the unglamorous parts — onboarding, templates, retrospectives, and the checklist that catches the thing everyone assumed someone else had handled. Those details are precisely what a Sengo Chief Operating Officer should own, and precisely what firms our size tend to postpone.

Welcome, Helsa. We are glad you are here.

Work With the Sengo Team

If you are weighing a platform decision, a migration, or an AI initiative, we are happy to give you a straight answer — including when the answer is that you do not need us. Read our success stories to see how we work, or reach out directly.