Findry
Get started
Guides/Getting started
Platform

Getting started

Create your workspace, set up your first project, and capture your first signal in under ten minutes.

5 min

Create your workspace

After signing up, you land on the workspace creation screen. A workspace is the container for your team's product decisions — think of it as your company's instance of Findry. Give it your company name. The slug becomes the URL prefix for your projects. You can rename both later.

If you're evaluating solo, name it after yourself or your project. Once you're set up, invite teammates from Settings → Members. There's no limit on invites during your trial.

Create a project

A project maps to a product area, a feature track, or a business goal — whatever unit of work your team ships. Every signal, hypothesis, test, bet, and outcome lives inside a project. The boundaries you set here determine how focused your decision trail stays over time.

Click + New project from the workspace home, give it a name and an optional description. Most teams start with one project and split later when the scope diverges. Don't overthink the structure at this stage — the project is just a label. You can move signals and hypotheses between projects at any time.

The five-phase loop

Findry organizes every product decision into five phases that form a closed loop. Each phase feeds the next — and the last one feeds back into the first. Here's what each phase is for:

  • Signals — raw observations: customer quotes, data anomalies, teammate ideas, research notes. The unfiltered feed of what's happening in your product and market.
  • Hypotheses — falsifiable beliefs derived from signals. "We believe that X will result in Y because Z." Not roadmap items — claims about the world that can be proven wrong.
  • Tests — validation experiments designed to confirm or refute a hypothesis before committing resources. Structured enough to produce real evidence; lightweight enough to run fast.
  • Bets — promoted hypotheses. The ones you've decided to act on, with RICE scores and a predicted impact commitment. A bet is a hypothesis with a signature on it.
  • Outcomes — post-ship measurement. Did the bet deliver what you predicted? The outcome closes the loop and surfaces variance between prediction and reality.

Every bet has a hypothesis behind it. Every hypothesis has signals beneath it. The chain is always there — because you built it.

Your first signal

Click + Signal in the sidebar, or press N anywhere in the app. The capture wizard walks you through three fields: the raw content (a quote, a note, a data point), the source (where you heard or saw it), and an optional tag.

Don't over-structure it at this stage — signals are meant to be fast to capture. The point is to get the observation into the system before it fades. Refine the metadata later. After saving, your signal appears in the Signals list. It's ready to be linked to a hypothesis whenever you're ready to make sense of it.

What to do next

The best next move is to keep capturing. Aim for 5–10 signals before you write your first hypothesis — let the pattern emerge from the evidence rather than forcing a belief before you have enough to support it. Signals from different sources pointing in the same direction are the most valuable raw material you have.

When you're ready to go deeper, the Signals guide covers every capture method, metadata field, and filtering option in detail.

Signals