Investigations

Find what's holding growth back.

A promising market goes quiet. Repeat purchases slip. Refix follows the evidence to understand what's happening and brings your team a plan, including opportunities nobody thought to ask about.

Used by teams at

A finding worth acting on starts with a thorough investigation.

  • Test the explanation

    An apparent demand problem might start with supply. Refix checks competing explanations against the data before recommending a change.

  • Follow the evidence across tools

    The cause may sit somewhere different from the symptom. Refix follows the relevant records across your connected systems.

  • Know what to try next

    Get a proposed change or experiment with the reasoning behind it, ready for your team to review.

Across systems

Find where the opportunity is being lost.

In this example, customers are searching, but the first available slots require a phone call. Refix follows the journey across four tools to see why demand isn't becoming revenue.

  • Connects relevant records across sources
  • Uses read-only access to investigate
  • Checks likely causes against the evidence

From finding to next step

Give your team a reason to make the change.

See who is affected and why the proposed change is worth trying. When a business rule is missing from the data, Refix asks a teammate before drawing its conclusion.

  • A clear explanation of the finding
  • Charts that show where the pattern appears
  • A recommendation with supporting evidence

Booking conversion reached 19.6% after the ranking change.

Completed bookings per search, Jul 6 to Aug 24

Bookable options moved first13.4% before+6.2 ptsCancellationsstayed near 4%

Security and control, built in.

Choose what Refix can access and set the approvals it needs. Review the data and reasoning behind its recommendations.

Read-only by design

Writes are refused at the database, not left to the model.

Approvals you control

Require your team's approval before Refix takes action in connected tools.

Roles for every teammate

Decide who connects data, approves actions, and manages billing.

Usage you can see

Daily credit use, with an alert before you reach your limit.

Zero data retention

Model providers keep nothing and never train on your data.

  • AICPA SOC 2 SOC 2 Type II*
  • ISO/IEC 27001 2022 ISO/IEC 27001*

* SOC 2 Type II audit under observation. ISO/IEC 27001 certification in progress.

Self-hosting

Run growth investigations on your infrastructure.

Run the Refix agent on your own Kubernetes cluster. Your platform team controls access and model connections, with our engineers helping you deploy.

  • Helm chart for your Kubernetes cluster
  • Your model keys or LLM gateway
  • Slack sign-in or your identity provider
  • Network access controlled by your firewall
  • Application updates you approve
  • Controls for reporting back to Refix

Questions about investigations.

How Refix chooses a lead and works through the evidence.

Talk to a human

What starts an investigation?

Your question can start one. Refix also chooses opportunities to investigate on its own, using your business context and connected data. A goal gives that work an ongoing focus.

How does Refix decide what caused a change?

Refix tests likely explanations against the data and rules out those the evidence doesn't support. Its conclusion includes the evidence so your team can assess the reasoning.

What if the data cannot answer the question?

Refix asks for the missing context, such as a business rule only the operations team knows. With Slack connected, it can reach the teammate who can help.

Does Refix act on what it finds?

Refix brings a next step, such as a proposed test or a ticket in a connected tool. Actions follow your workspace's approval settings.

Your next growth hire isn't a person.