The Brainmood pilot

A defined scope.
Six months to decide.

Deploy Brainmood on one team, department, division or one or several sites. Establish a collective readout, put actions in motion and evaluate the program’s contribution before deciding what comes next.

Explore a pilot for my organizationView pilot terms

A practical starting point

A sponsor. A decision to inform.

The pilot is for organizations that want to try organizational steering in their real working conditions. It requires leadership able to act on what is observed.

  • A leadership sponsor who approves the scope, owns decisions and takes part in reviews.
  • A situation to understand: unclear priorities, coordination across teams, operational tensions or an ongoing transformation.
  • A scope compatible with collection and aggregated reporting. Respondent numbers and thresholds are checked during scoping.
  • Contacts such as HR or managers available to inform teams and follow up on agreed actions.
The process

Establish, adjust, then evaluate.

Indicative cadence, to be confirmed during scoping. Collection dates, readouts and reviews are agreed with your organization.

  1. During scoping

    Define the question and scope

    Agree on the sponsor, objectives, participating groups, reporting rules and criteria for the final review.

  2. 4 to 6 weeks

    Establish the first readout

    Deploy and configure the program, organize pseudonymous collection and produce the first decision synthesis according to the agreed schedule.

  3. Following cycles

    Prioritize and track actions

    Start one to three adjustments per cycle. Each has an owner, a deadline and a completion criterion. Review changes and follow-through.

  4. At six months

    Review and decide

    Examine the quality of readouts, decisions made, action follow-up and limitations encountered. Decide whether to continue, expand or stop.

The deliverables

What you use during the pilot.

Deliverables, reporting scopes and support are detailed in the agreed proposal.

01

Collective readout

Access to the Brainmood platform, secure collective collection, a dashboard and aggregated reporting within the defined scope.

02

Synthesis and decisions

Decision synthesis, identification of areas needing adjustment, action prioritization and a PDF export for leadership.

03

Follow-up over time

An action plan with owners, deadlines and criteria, follow-up of agreed actions, interpretation of changes and a final review.

Prepare the review from the outset

Evaluate use and decisions.

Criteria are agreed together before launch. They should help assess the program’s contribution, without promising a quantified reduction in turnover or automatic performance improvement.

  • Readouts: are they usable and understandable for the sponsor and relevant managers?
  • Decisions: did the observations inform explicit decisions with identified owners?
  • Follow-up: do agreed actions have a deadline, completion criterion and documented review?
  • Feasibility: do participation, cadence and time requirements fit how the organization works?
A collective framework

What the pilot helps you understand.

  • Reported collective working conditions, interpreted in light of participation and the context of each period.
  • Exclusively aggregated results. A scope that is too small or has insufficient participation may limit readouts.
  • An organizational view, without individual assessments, psychological profiles or medical diagnosis.
The trust framework

Pseudonymous collection

Contributions collected without nominative profiles.

Aggregated readouts

Anti-reidentification thresholds checked against the agreed scope.

Collective interpretation

No individual readouts or psychological scoring.

Understand the method and confidentiality
A published experience
“A high-quality pilot experience. Our employees are satisfied. We wish to continue the program with Brainmood.”
Stéphanie GuittonneauBeauté InsolenteTestimonial published on our homepage
Commercial terms

A six-month commitment, scoped together.

Pilot pricing

A proposal for your scope

The pilot is paid, with a firm six-month commitment. The amount is defined in the commercial proposal according to size, the selected scope and the level of governance required.

Recurring offer prices appear on the Offers page. No pilot-specific price is listed: scoping establishes the contractual amount before any commitment.

View Brainmood offers
Billing

30% at signature

A deposit of 30% of the contractual amount is required at signature. The balance is invoiced according to the schedule defined in the contract.

Scope, schedule and deliverables are specified before launch. At the end of six months, the organization decides what comes next for the program.

Frequently asked questions

Before launching the pilot.

Is the pilot free?

No. The Brainmood Pilot is a paid program with a firm six-month commitment. The amount and payment schedule are specified in the commercial proposal and contract.

How many employees can take part?

The scope can be a team, department, division or one or several sites. It must support aggregated reporting and meet anti-reidentification thresholds. Compatibility is checked during scoping; organization size alone does not determine it.

How much leadership time is needed?

Allow time for scoping, readouts, decisions and action follow-up. Time requirements and participants are agreed during scoping, according to the scope and review cadence.

Can an employee’s answers be identified?

Readouts are exclusively aggregated. Collection is pseudonymous, with no nominative profile; the platform offers no individual readouts. Threshold rules apply to the scopes being reported.

What happens at the end of six months?

The final review lets the company decide whether to continue, expand the scope or stop. It examines the criteria agreed at the outset, decisions and actions completed, and limitations encountered.

The first conversation

What scope would be useful for you?

Thirty minutes to understand your context, the sponsor’s role and the decision to inform. The contact request starts a discussion about the pilot; it does not sign a contract.