Costs stated upfront
Scope, assumptions, rates and recurring costs are written down before an engagement starts.
What we write down before starting: scope, costs, code ownership, use of AI and how we communicate.
Updated: August 2026
Pôle Digital Inc., Québec, Canada. This page describes our current practices and is not a certification. A question or a gap to report? Write to us.
info@poledigital.caScope, assumptions, rates and recurring costs are written down before an engagement starts.
Deliverables built for you are transferred to you, with no forced dependency on Pôle Digital.
We state where artificial intelligence is involved and what remains under human decision.
Section 01
Digital work is often sold through opacity: vague estimates, hidden dependencies, unverifiable promises. We prefer to write down our rules.
This page is maintained by Pôle Digital Inc. to answer the most frequent questions about how we work, bill and communicate. It describes our current practices; it is neither a certification nor an independent audit.
Section 02
Every proposal presents the agreed scope, starting assumptions, exclusions and billing model. An estimate resting on unknowns is presented as a range, not as a firm price.
Section 03
Developments carried out under an engagement are transferred to you as set out in the contract. You retain access to your code repositories, your data and your environments.
We document architecture, dependencies and deployment procedures so another team can take over. Our reusable components and proprietary platforms - Ndjanguih, ConciergeX, PrestaGo - remain the property of Pôle Digital and are provided under a clearly identified usage licence.
Section 04
We use artificial intelligence as a production and assistance tool, never as a substitute for human responsibility. When a delivered feature relies on a model, we state it, along with its limits and the human control point.
A client's confidential data is not sent to AI services without explicit agreement, and impactful decisions - financial, contractual, regulatory - remain validated by a person.
Section 05
We work with technologies and vendors we recommend for technical fit, not for a commission. Where a partnership or vendor programme exists, we disclose it in the recommendation.
If an open or less expensive solution fits your need better than a product we know well, we say so. The vendor categories that process data are described in our privacy policy.
Section 06
The work and case study pages describe real projects as well as representative scenarios. Where content is illustrative, it is identified as such rather than presented as a delivered engagement.
Section 07
Every engagement has a named responsible person, a tracking channel and an agreed reporting rhythm. Progress is presented with what is done, what is blocked and what remains.
A delay, an estimation error or a technical difficulty is communicated as soon as it is identified, with the available options and their impact on budget and schedule.
Section 08
We favour the simplest solution that meets the need: reuse before rebuilding, automate what is repetitive, and avoid oversized infrastructure that costs without serving.
We document the trade-offs chosen so you can decide knowingly between cost, speed and scalability.
Section 09
If information published here appears inaccurate, if an invoice or estimate seems inconsistent, or if a commitment was not met, write to us at info@poledigital.ca. We acknowledge receipt and provide a reasoned answer.
Security and vulnerability matters are handled on the Security page; personal information matters on the Privacy page.
Section 10
The commitments described here express our practices. Contractual obligations applicable to a project - scope, service levels, warranties, liability - are those of the contract signed between the parties.
Pôle Digital Inc. is established in Québec, Canada. Our terms of use set out the framework applicable to the site itself.
An open question
Ask before committing. We answer in writing, with the assumptions and limits of our answer.