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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Live decisions show whether the current context setup is actually helpful, whether the outputs feel too generic, and where the workflow still creates friction.
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.
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.
The pilot is for teams willing to use the product for real, give direct feedback, and help shape what becomes the first public version.