Home Product Pilot Program Pricing Get in Touch Book Demo
Pilot Overview

Join the Decision Referee pilot.Help shape the product with real usage.

This pilot is for teams that already make meaningful decisions in Slack and want a more structured way to review them. Initial setup usually takes about 2–3 minutes, each decision takes about 30 seconds to 5 minutes depending on depth, and the current focus is Norwegian teams, though international teams are also welcome.

What the pilot actually is.

The pilot is not a waitlist and not a broad self-serve launch. It is a small working group of teams using Decision Referee on real decisions while the product is still early enough to improve quickly.

Real usage
In Slack

Used where decisions already happen

Pilot teams use the product in normal Slack workflows rather than in isolated demos. That matters because the product only gets better if it is tested against real team tradeoffs.

Founder-led
Direct access

No layers between you and the builder

The founder stays involved directly in onboarding, feedback, and product decisions. If something is unclear or not useful, the feedback goes to the person shaping the roadmap.

Still early
Honest stage

Early enough to influence the product

Decision Referee is already usable, but still early. That is exactly why pilot teams matter: the product can still improve quickly based on what proves useful in practice.

Who the pilot is for.

The best fit is a team that already makes cross-functional or operational decisions in Slack and is willing to test the product on real work. Norwegian teams are the main focus right now, but international teams are also welcome if the usage fit is strong.

01

Teams with real decision traffic

We are looking for teams that regularly discuss tradeoffs around scope, hiring, priorities, operations, ownership, or go-to-market decisions. If decisions already happen in Slack, the fit is better.

02

Usually around 6 to 40 people

That range tends to be a strong fit because the team is large enough to have recurring decision friction and small enough to move quickly. It is a preference, not a hard gate.

03

Teams willing to give sharp feedback

The pilot works best when teams are willing to say what is weak, what is unclear, and what was genuinely useful. Strong feedback is part of the value exchange.

How onboarding works.

Onboarding is hands-on and practical. The goal is to get a team to real usage quickly, with enough private workspace context in place that the analyses are more grounded than a generic prompt.

01

Intro and fit check

We start with a short call to understand the team, current workflow, and whether the pilot is a real fit.

02

Slack install and initial setup

The app is installed in Slack, and the first firm profile is created with /firm_profile "Org. number" "domain/website". Setup usually takes about 2–3 minutes. Strategic info fields are optional but useful, and company website content plus Brønnøysund Register Centre data can enrich the workspace profile automatically where relevant.

03

First real decisions

The team starts using /decide_simple, /decide, /decide_deep, and later /outcome on actual decisions rather than synthetic examples. Each decision takes about 30 seconds to 5 minutes to submit inside Slack, depending on depth.

04

Ongoing review

We review usage, weak spots, outcome tracking, and weekly reports together. The founder stays directly involved throughout the pilot.

What pilot teams get.

The pilot is meant to be useful, not symbolic. Teams get real product access, direct support, and a chance to shape how Decision Referee becomes more valuable in day-to-day use.

Access to the full core workflow
Pilot teams can use /decide_simple, /decide, /decide_deep, /outcome, and weekly reports in normal Slack usage.
Founder-led onboarding and support
Setup is handled directly with the team, including the initial workspace firm profile in Slack and follow-up on what is or is not working.
A chance to influence the product
Feedback from pilot teams directly affects how context, outputs, and reporting are improved in the next iterations.
No pilot fee
There is no charge during the pilot period. The real ask is engagement, honest usage, and useful feedback.
What we ask in return
Use the product on real decisions, not only test prompts.
Give direct feedback on what felt useful, generic, unclear, or weak.
Keep the workspace firm profile current enough that the analysis reflects the business as it is now.
Join short check-ins so the feedback loop stays active.
If the pilot goes well, be open to a testimonial, case study, or reference conversation.
Why this matters
Decision Referee only gets sharper through real usage. Pilot teams help test where the context helps, where the outputs stay too generic, and what actually improves decisions in practice.
Why pilot teams matter so much.

This product is meant to support real business judgement, not generate polished but empty output. That only happens if pilot teams use it in real decision flows and tell us where it earns its place and where it does not.

A

Real usage exposes weak spots fast

Live decisions show whether the current context setup is actually helpful, whether the outputs feel too generic, and where the workflow still creates friction.

B

Feedback shapes the product directly

Pilot teams help refine the Slack flow, the context model, and the reporting layer. This is the stage where sharp feedback still changes the product meaningfully.

C

Strong pilots create proof

If the product helps in real team usage, the best outcome is evidence: testimonials, case studies, or referenceable stories that show where it actually adds value.

If your team already decides in Slack, this is the right time to try it.

The pilot is for teams willing to use the product for real, give direct feedback, and help shape what becomes the first public version.