Language proof
Ask to see a sample resolution note or change summary in the language you would actually use — not a translated marketing page.
Due diligence Diligence raisonnable
Before you commit a client relationship, evaluate the partner — not just the pitch.
A bilingual claim is easy to print and hard to verify from a website alone. Use these questions on us, and on anyone else you are considering.
Four categories to verify Quatre catégories à vérifier
What deserves a real answer, not a marketing line
Scope clarity
Ask what happens the first time a request falls outside the agreed scope — who decides, and how fast.
Escalation path
Ask for the name of the role (not necessarily the person) who receives an exception, and what information they need to decide.
Commercial terms
Ask what is priced per user, what is scoped separately, and what currency and billing cadence apply.
Questions to ask directly Questions à poser directement
Four questions that quickly reveal an unprepared partner
What happens first when your team can’t answer a client in the client’s language?
A good answer names a specific path, not a general coverage promise.
Who signs off before a security baseline changes, and in which language does that approval happen?
Approval should follow a named owner, not an anonymous queue.
What does exit look like — who removes access, and in what order?
A poorly defined exit leaves orphaned access months later.
Can I see a fictional example of a deliverable before I commit a real client?
An evasive answer here is a useful signal on its own.
Signs to slow down
- A partner that can’t describe its own escalation path without checking with someone else.
- A partner that treats “bilingual” as a checkbox rather than an account-level declared language.
- A partner unwilling to name what stays a practice decision versus a delivery decision.
- Pricing that can’t be explained without a live sales call.