How we work

How we run your Microsoft Power Platform and 365 project

From the first conversation to delivery, every decision is explained, every step produces a verifiable result and nothing moves forward without your approval.

Choose your starting point Back to the service

Where you stand

We don't restart every project from scratch.

We tailor the first days of the engagement to your reality: a brand-new idea, an existing solution or a problem that needs solving fast.

Under-used Microsoft 36501

You pay for 365 but still work by email and Excel

We identify the processes that will gain most from automation with what you already own.

How we get started

Workshop on your repetitive tasks
Review of licences and available connectors
First automated flow within days

Migration02

You are moving to Microsoft 365

From a file server, Google Workspace or old mail systems, we migrate without data loss and without stopping work.

How we get started

Inventory of mailboxes, files and permissions
Target Teams and SharePoint structure
Cutover plan and team communication

Reporting03

Your numbers are scattered

We build reliable Power BI dashboards, fed automatically by your tools.

How we get started

List of metrics and their definitions
Connection to data sources
First dashboard on your real data

The full process

A clear path forward, with no gray areas.

At every step, you know what was done, what was delivered and what decision is needed to move on.

013 to 7 days
Assessment
We analyse your processes, licences and 365 environment to target quick wins and risks.
What we do
- Interviews with teams
- Security and sharing audit
- Prioritisation of use cases
Why this step: Many businesses pay for Microsoft 365 licenses they barely use, or share data more widely than they realize. This assessment reveals what you can do with what you already pay for, identifies security risks and targets the first use cases that will save time.
How we proceed, line by line
1. 1 An initial video call frames your goals and identifies the teams to interview.
2. 2 We hold short video interviews to spot shared spreadsheets, paper forms and repetitive tasks.
3. 3 With read access to the admin center, we review your licenses, available connectors and Power Platform environment.
4. 4 We check authentication, external sharing links and permissions in Teams and SharePoint.
5. 5 We rank use cases by time saved, difficulty and licenses required.
6. 6 We write a report with the risks, priorities and a roadmap, then present it by video call.
Who does what
A Microsoft 365 and Power Platform consultant leads the interviews and audit, with a project manager who organizes the meetings. On your side, your IT manager grants access and a few members of each team describe their day-to-day work.
What you provide
Read access to the Microsoft 365 admin center and Power Platform.
The list of your current licenses and subscriptions.
An hour of availability from a few people per team for interviews.
What you receive
Report, priorities and roadmap
Your approval
You choose the first cases to deliver.
021 to 2 weeks
Governance and foundation
We set the rules before multiplying apps: environments, permissions, security and conventions.
What we do
- Test and production environments
- Data policies and multi-factor authentication
- Teams and SharePoint structure
Why this step: Without rules, apps and workflows multiply unchecked, expose data and become impossible to maintain. Laying the foundation before building protects your information and makes every future solution easier to evolve.
How we proceed, line by line
1. 1 We create separate Power Platform environments for test and production.
2. 2 We configure data policies that restrict the allowed connectors by environment.
3. 3 We enable or check multi-factor authentication with Microsoft Entra ID and tighten permissions to least privilege.
4. 4 We structure Teams and SharePoint: teams, channels, sites and internal and external sharing rules.
5. 5 We set naming conventions and start a solution inventory in a shared document.
6. 6 We present the documented foundation to your IT manager in a video review.
Who does what
The Microsoft 365 consultant configures security, environments and the Teams and SharePoint structure, and writes the documentation. Your IT manager approves each rule and provides the necessary admin rights.
What you provide
Temporary admin rights or an administrator available to apply the settings.
Your internal security and sharing rules, even informal ones.
Approval of the rules by your IT manager.
What you receive
Documented Microsoft 365 and Power Platform foundation
Your approval
Your IT lead approves the rules.
031- to 2-week cycles
Build
We build apps, flows and dashboards in short iterations, tested with users.
What we do
- Power Apps, Power Automate and Copilot Studio
- Dataverse or SharePoint data model
- Power BI reports and automatic refresh
Why this step: An app built without its users often ends up abandoned in favor of the old spreadsheet. Short iterations, each tested by the people concerned, ensure tools that fit real-world work and are delivered progressively.
How we proceed, line by line
1. 1 We start with the priority use case chosen during the assessment and sketch a mockup of the app or workflow with its users.
2. 2 We design the data model in Dataverse or SharePoint, with permissions suited to each role.
3. 3 In the test environment, we build the Power Apps, Power Automate workflows and, if useful, a Copilot Studio assistant.
4. 4 For Power BI, we define the indicators with management, connect the sources and schedule automatic refresh.
5. 5 Each workflow handles its errors, notifies the right person and keeps a run history.
6. 6 Users test each delivery, including on mobile, and we adjust based on their feedback.
7. 7 We move the approved solution to production and add its documentation to the inventory.
Who does what
Power Platform developers build the apps and workflows, a Power BI specialist creates the dashboards and the project manager tracks the iterations. Your users test each delivery and management approves the indicator definitions.
What you provide
The files, lists and data sources to migrate or connect.
Access to the third-party tools to connect, such as Odoo or SAP.
Users available to test each iteration.
Any additional licenses needed, identified during the assessment.
What you receive
Tested, documented solutions
Your approval
Each delivery is approved by its users.
042 to 4 weeks, then ongoing
Adoption and follow-up
We train, support and measure usage so the tools are really adopted.
What we do
- Short role-based training
- Internal champions and guides
- Usage tracking and improvements
Why this step: A well-built tool that is rarely used brings no return. Training, appointing champions and measuring usage let us check that the solutions are really adopted and improve them where they still get in the way.
How we proceed, line by line
1. 1 We run short role-based training sessions by video call, on the tasks each team actually performs.
2. 2 We provide simple guides and, if you wish, record the sessions for newcomers.
3. 3 We train internal champions who can answer common questions and make small changes.
4. 4 We track usage of apps, workflows and reports using the statistics available in Microsoft 365 and Power Platform.
5. 5 An adjustment review after a few weeks lists the blockers and requested improvements.
6. 6 We keep the evolution plan up to date and deliver new use cases according to your priorities.
Who does what
A trainer runs the sessions and writes the guides, the consultant tracks usage and the project manager maintains the evolution plan. On your side, internal champions relay questions and management encourages use of the new tools.
What you provide
Training slots in each team's calendar.
One or two volunteer internal champions.
Your usage feedback at the adjustment review.
What you receive
Self-reliant teams and evolution plan
Your approval
The tools are used every day.

Our commitments

A collaboration designed to stay under your control.

Transparency

You see progress, decisions, risks and next steps without waiting for a crisis meeting.

Continuous validation

Key choices are demonstrated and approved along the way rather than discovered at delivery.

Verifiable quality

Every outcome is tied to concrete criteria for functionality, security, performance or adoption.

Knowledge transfer

Documentation and onboarding are part of the engagement, so you never depend on us unnecessarily.

First step

Let's start by understanding your situation.

Tell us about your project, even if it's still vague or already in trouble. Together, we'll find the safest place to start.

Tell us about your project

How we run your Microsoft Power Platform and 365 project

We don't restart every project from scratch.

You pay for 365 but still work by email and Excel

You are moving to Microsoft 365

Your numbers are scattered

A clear path forward, with no gray areas.

Assessment

Governance and foundation

Build

Adoption and follow-up

A collaboration designed to stay under your control.

Transparency

Continuous validation

Verifiable quality

Knowledge transfer

Let's start by understanding your situation.