Define the contribution.
Bring an idea, lead a project, help distribute it: roles can complement one another. Participation and any remuneration are agreed for each project.
Understand the contributionTrust is built at every step.
Who brings the idea, who decides and who builds? Whether teams work in one province or several, we agree on responsibilities, languages and data access for the actual project.
Set the project framework
Know how everyone contributes.
The framework depends on your path and the selected project. Responsibilities and terms are discussed before committing to delivery.
Define the delivery.
With you, we define the delivery scope, validation steps and product follow-up. Everyone involved knows what they bring and which decisions they take part in.
Understand the platformPeople are accountable for decisions.
The project lead or client team brings domain knowledge. Delivery experts assess technical choices. Together, we identify who can approve a step or authorize a launch.
- Define responsibilities from the start.
- Set boundaries for actions delegated to AI.
- Plan approvals and ways to recover.
The right access for the right use.
Data, sources and access are part of the project. With you, we review what needs to move, who can see it and where the application will run.
- Identify the information needed.
- Define user and partner permissions.
- Choose hosting to suit the project’s constraints.
Understand what was decided.
A product evolves through choices. Priorities, important changes and verification results give the project lead and team a basis for deciding what comes next.
- Identify the version and uses verified.
- Make known limitations and gaps visible.
- Keep the reasoning behind important decisions.
Prepare for the product’s life.
Launch starts a new phase. We clarify follow-up arrangements, who needs to be involved and how to prioritize improvements within the agreed project framework.
- Prepare onboarding and first use.
- Clarify follow-up and operational responsibilities.
- Choose improvements based on real-world feedback.
Questions that make the next step clearer.
What is the difference between the Studio, CDE and the Factory?
The Studio brings together ideas, project leads and partners. CDE is the platform for building applications. The Factory is the delivery method that organizes the steps and approvals.
Will every proposed idea be developed?
A proposal opens a conversation. The need, possible uses and delivery conditions must be examined before selecting a project. Participation and any remuneration are defined within that framework.
Does AI make all the decisions?
Experts guide its use. Permitted actions, checks and accountable people are defined for the system being built. Domain expertise remains essential when accepting a result.
How do you prepare a product for distribution?
The project lead and partners define the intended audiences, territories and each person’s contribution. Collaboration terms and any remuneration are agreed for the project.
Where will our application be hosted?
We make that choice with you, considering data, connected systems and project constraints. Operating conditions and the associated responsibilities are part of the discussion.
Where can I read the contractual documents?
Existing documents are available in our legal section. Commitments specific to your project are agreed with you in the applicable documents.
Let’s move forward with the right questions on the table.
You don’t need all the answers. Let’s start with what you would like to make possible.
Let’s talk about your idea