efestra

Flywheel

Every experiment and study is checked before it reaches a decision.

Your teams plan, run and report experiments and research with whatever tools they use, including AI assistants. Flywheel checks each piece against the standards your organisation sets, and shows leaders which results passed and which did not.

What gets checked

  • Planned before it started
  • Research method on record
  • Not changed after the results came in
  • Findings checked before they are shared

Trusted by

  • Coop
  • Haufe Group
  • Bitdefender
  • UNRVLD
  • Travelopia
  • Enchanting Travels

Decision Intelligence Stack

Three layers, one standard

Flywheel covers each layer of the Decision Intelligence Stack, for experiments and research alike.

  • Evidence integrity

    Can the experiments and research be trusted?

  • Evidence synthesis

    Can what you know be found and connected?

  • Decision influence

    Does the evidence reach decisions?

Governance runs through all three

The standard your organisation sets, applied to every experiment and study at every layer.

Governance

Who Flywheel is for

Flywheel suits organisations where experiments and research already happen, but the results do not reliably reach the people making decisions. It is likely to fit if one or more of these is true.

  • You run 50 or more experiments a year but cannot show their effect on strategy. Winning tests are reported, but nobody tracks whether they delivered value once released.

  • Your research team's work sits in repositories nobody reads. Product decisions are made without reference to studies that already exist.

  • Experiments and research are managed across Jira, Airtable, Notion and spreadsheets. No single place shows the whole picture.

  • Leadership relies on the team to report on its own work. There is no independent view of quality.

Not sure yet? Start with an evidence audit. It shows where you stand before you commit to a platform.

Decision influence

What leaders see

  • Decision influence

    Trace any decision back to its evidence

    Each decision records who made it, which experiments and research informed it, when it was implemented and whether it delivered the expected outcome.

    A decision record, linked to the insights that informed it.
  • Evidence integrity

    Know which results you can rely on

    Every experiment receives a governance score based on how it was planned, run and documented, so you can see which results are sound enough to act on.

    An experiment's health score, with the changes that lowered it.
  • Decision influence

    Report what the programme delivered

    Dashboards show decisions informed by evidence, governance health and outcomes compared with predictions, instead of test counts and win rates.

    Executive portfolio: objectives, alignment and programme health in one view.

Experiments and research

What Flywheel does

Evidence integrity

Evidence integrity: can the evidence be trusted?

  • A hypothesis, primary metric and decision rule are required before an experiment launches.
  • Every change to a record is logged with the time and the person who made it.
  • Flags hypotheses edited after launch, metrics changed mid-test, tests stopped early and documentation added after the fact.
  • Detects experiments that overlap and could contaminate each other's results.
  • Scores each experiment and the programme as a whole.
Planning an experiment, with checks for collisions and similar past tests.

Evidence synthesis

Evidence synthesis: can what you know be found and connected?

  • Research files (PDF, slides, transcripts) are uploaded and an AI draft of the findings is produced. A researcher verifies it before anyone else sees it.
  • One search across experiments, research and insights.
  • Related studies and experiments are linked, and people are shown when something similar has been tested before.
  • The AI features are labelled Mosaic in the product.
Drafting observations from a research report, ready for a researcher to verify.

Decision influence

Decision influence: does the evidence reach decisions?

  • Every experiment and study is linked to a business objective and a named decision owner.
  • A decision log links each decision to the evidence behind it.
  • Predicted impact is compared with the actual outcome after release.
  • Dashboards for executives, who use Flywheel free of charge.
Quarterly objectives, with status, owners and the experiments behind them.

Works where your teams work

Use Flywheel from your AI assistant

Flywheel connects to AI assistants that support the Model Context Protocol (MCP), such as Claude. Before suggesting a test, the assistant checks what your organisation has already learned. What it records goes into the same Flywheel records that leaders see.

Works with
  • Claude
  • ChatGPT
  • Gemini

Illustration. The company and figures are fictional.

Conversation transcript

User
Mobile checkout abandonment is still high. Can you suggest a test for next sprint?
Assistant
I'll check what has already been tested in Flywheel first.
Flywheel tool
Search past experiments for "mobile checkout delivery". Results: EXP-031, Free-delivery progress bar, March, result Flat. EXP-044, Express pay buttons, June, result Inconclusive on mobile.
Assistant
A free-delivery progress bar looks like the obvious fix, but EXP-031 tested it in March and it made no difference. I'd show the delivery cost on the basket page instead. Shall I set it up?
User
Yes, set it up.
Flywheel tool
Create experiment from your template. Name: Delivery cost on mobile basket. Hypothesis: Showing delivery cost earlier will reduce abandonment at the shipping step. Primary metric: Checkout abandonment. Status: Draft.
Assistant
Created as a draft in Flywheel, in the same record your leaders see.

Governance

How Flywheel compares

  • Trackers such as Jira, Airtable and Notion

    They record what people choose to enter. Fields are optional, and a hypothesis can be edited after the results are known without anyone seeing the change.

  • Testing tools such as Optimizely, VWO and AB Tasty

    They run experiments well. They do not hold research, and they do not link results to the decisions they inform. Flywheel connects to them; you keep using them.

  • Building your own

    An internal build or an AI workflow gives full control, but it takes engineering time to build and maintain, and the team whose work is checked ends up setting the standard.

Governance

Getting started

Most organisations are live within four to eight weeks. The total time needed from your team is about one to two days.

  1. Governance design. A half-day workshop with your executive sponsor and the people who will use Flywheel. Together we agree the required fields, approval steps and quality checks.

  2. Set-up. We configure Flywheel, connect your testing tools, import past experiments and research, and assess their governance so your dashboard shows real data from the first day.

  3. Training. Separate sessions of about two hours for practitioners and researchers, and for executives.

  4. First 90 days. We review the first experiments and studies entered, run a health check at week eight, and deliver your first quarterly governance report at week twelve.

Onboarding is included in the subscription.

Governance

Pricing

Flywheel is priced by user licence. Programme managers, who set the standards, are priced higher than practitioners. Executives and other viewers are free. Single sign-on is included. Request a call for a quote.

  • Programme managers
  • Practitioners
  • Executives and viewers: free
Request a call

Governance

Questions

With an evidence audit. We trace three recent decisions back to the experiments and research behind them, and send you a written finding for each. If the findings show you need checks on an ongoing basis, Flywheel is the next step. If not, you keep the report.

Flywheel

Talk to us about Flywheel.

Leave your details and Manuel will reply by email to arrange a call.