Findings

Capture · inbox · release gate

Know when it is ready.

One button on every page. One inbox for everything you ship. A clean-days counter that tells you when a release has earned its launch.

One script tagUnder 8 KBHosted in the EU

your-siteEXAMPLE · 14 DAYS
12 clean days Gate passed on day 7
0.00finds a day, 7d
0open defects
3ideas, beside the gate
The pill your visitors see

Why it exists

You find a bug on your phone, in a queue, between two meetings. You mean to write it down. You don't. The next day looks clean, and the day after that. A find that is never captured becomes a clean day that was not one.

Findings exists so that capture takes one tap and one sentence, from wherever you are.

Three things, and the counter is the one that matters.

01 · THE GATE

Two numbers from real use

Clean days since the last real defect, and find rate over 7 and 14 days. Ideas never count against you. Reports you discard never count against you. When nothing has been recorded, it says no data, never an encouraging zero.

02 · ONE INBOX

For everything you ship

Run four side projects, or ten? Each gets the same button and its own counter. You triage all of them in one place. No per-project pricing that punishes you for shipping more.

03 · THE AGENT

It proposes. You decide.

Connect your coding agent over MCP. It reads graded defects on its own product and records the pull request it opened. It cannot deploy, merge, close a find, touch an idea, or move a gate number, and it works on a serious defect only when you allow it.

How it works

One line of code. One tap to capture.

  1. 1
    Add a site Name, allowed origins. You get one line: <script src="https://findings.dev/f.js" data-site="your-site" defer></script>
  2. 2
    Paste it before </body> Any stack. No framework, no dependencies.
  3. 3
    Tap the pill Write one sentence. Save. That is the whole capture. No signal on a plane? The find waits on the device and sends itself later.

Who sees what

Your product says who is signed in. Findings decides the role.

Nobody configures a browser. A tester is a person in one of your test groups. The visitor button is off until you switch it on.

RoleVisitorTesterYou
SeesOne button: ReportThe fast pathEverything, on every site you own
WritesOne sentence, optional emailDefect or idea, optional severity S1 to S4Triage, grading, settings
Moves the gateOnly once you file it as a defectYesYes
VisitorSees one button, Report. Writes one sentence, optional email. Moves the gate only once you file it as a defect.
TesterSees the fast path. Writes a defect or an idea, optional severity S1 to S4. Moves the gate.
YouSee everything, on every site you own. Triage, grading, settings. Move the gate.

What it will not do

This list is part of the product.

No screenshotsThey capture your users' data.
No session replayWe do not record anyone.
No page contentA find carries the path, the viewport, the browser and the build. Nothing else.
No lost findsA find the service refuses is shown to you, never dropped.
No agent with the keysIt proposes. You decide.

Free while we find the price.

Pro is priced from what the Pro list tells us, not from a competitor's page.

Free

EUR 0
  • Unlimited sites
  • You plus 3 testers
  • The gate, the inbox and triage
  • The offline queue
  • The API
Start free

Early access

FREE UNTIL PRO
  • The visitor button on public sites
  • The MCP agent endpoint

You get 30 days notice before either moves to Pro.

Pro, coming

PRICED FROM THE LIST

Visitor reports and the agent will move to Pro. Tell us what that is worth to you and we set the price from your answers.

Join the Pro list

Questions

Is this another bug tracker?It is the capture and the counter. Keep your tracker. Findings tells you whether the thing you are about to launch is ready.
What counts as a clean day?A calendar day with no real defect found on that product. Ideas, untriaged visitor reports and discarded reports do not count. The day a find happened counts, not the day it was typed in.
Why no screenshots?Because a screenshot of your app is a screenshot of your user. One sentence and the page path is enough to find almost everything.
Where is my data?In the EU, in Helsinki. One database, backed up daily.
Does it work offline?Yes. A find you cannot send waits on the device and sends itself when you are back online.
Which agents work?Anything that speaks MCP over Streamable HTTP: Claude Code, Cursor and others. One agent token per product.
Who makes it?YINDOR, a small software company in Eindhoven. Findings runs on every YINDOR product today.

Start counting clean days.

Three fields. Email, a password, and how many things you run.

Start free