Skip to content
ScrutableEvidence-native product studioDiscuss a system

Scrutable · evidence-native product studio

Software that can explain itself.

Scrutable designs and builds consequential software for teams working with AI, automation, and complex decisions.

The problem

Powerful software is becoming harder to question.

AI, automation, and complex operational systems increasingly shape what people see, decide, and do. Too often, the explanation arrives later—if it arrives at all.

Scrutable treats understanding as part of the product. We design and build software whose results, evidence, and responsibility remain visible to the people who depend on it.

Selected work

Proof before promises.

Every project shown here comes from Scrutable’s publication-gated catalog. Its current standing and supporting proof travel with it.

01platform

A Scrutable Works project

Antechamber

Agents knock. You decide.

Browser leases, user-present approvals, repair handoffs, and redacted audit records give agents bounded access to authenticated surfaces — without hijacking your own sessions.

Lifecycle
active
Delivery
operational
Inspect the project
02application

A Scrutable Works project

BurstWPM

Bursts, not averages.

Measures typing the way you actually type — in bursts, not test averages — with live WPM in the menu bar and day-over-day trends.

Lifecycle
active
Delivery
operational
Inspect the project
03developer_tool

A Scrutable Works project

Callover

Your name is called. You appear.

A harness for the steps automation can't do alone — sign-ins, hardware, senses, judgment. The run holds, calls you in for one bounded step, binds what happened to machine evidence, and resumes — recorded, not recollected.

Lifecycle
active
Delivery
operational
Inspect the project
See all public work

What we do

From difficult decision to inspectable product.

Scrutable works where product behavior, organizational responsibility, and human judgment meet.

  1. Frame the consequential decision

    Clarify what the system is being trusted to do, who carries the consequences, and what a responsible result must make visible.

  2. Design for understanding

    Turn complex behavior into an interface people can inspect, question, and use without needing hidden institutional knowledge.

  3. Build the working system

    Connect product strategy, interaction design, and engineering so explanation is part of the product rather than a document added afterward.

  4. Keep the work answerable

    Preserve the evidence, ownership, and routes for challenge that let a system remain trustworthy as it changes.

Explore what we do

How it works

Explanation is a product behavior.

A scrutable system makes four things legible: what happened, what supports it, who is responsible, and what someone can do when it is wrong.

See the method
OutcomeEvidenceResponsibilityRecourse

Ideas

The questions behind the work.

Research, field notes, and experiments will appear here when they are ready for public inspection. Nothing is being presented as published before it clears that threshold.

Visit Ideas

Start with the system

Working on software that carries real consequences?