Problem and current cost
What is difficult today, why, and what does it cost or delay?
Private browser tool · No submission
Is your product brief
ready for decisions?
Paste a product brief to find missing decisions before a scope, estimate, or build plan hardens around assumptions. The text is scored locally in this browser tab and is never sent to LWS Studio.
Your working brief
Paste without contact or confidential data.
This page does not submit, upload, save, or analyze your text on a server. Refresh or close the tab to discard it.
Published methodology
Eight decisions.
Three evidence levels.
This is a deterministic checklist, not an AI judgment. Each dimension receives 0 when absent, 2 when broadly present, or 4 when both topic and specificity signals appear.
Specific user
Who has the problem, in what context, and who is not the first user?
Current and desired workflow
What happens from trigger to completed outcome now and in the proposed product?
Valuable outcome
What should the user or business be able to accomplish?
Success evidence
Which observable target would justify more investment, and by when?
First-release boundary
What must version one include, and what is explicitly not now?
Constraints and dependencies
Which systems, policies, data, schedule, or platform limits shape the build?
Decision and operating ownership
Who decides, supplies inputs, accepts launch, and runs the result?
Use the score correctly
A stronger brief
is still a hypothesis.
The grader checks whether important decisions are explicit enough to discuss. It does not prove demand, feasibility, usability, compliance, accessibility, security, cost, or commercial viability.
Phrase matching can miss strong writing or reward vocabulary without substance. Review the eight dimension prompts directly, then validate the brief with users, stakeholders, technical evidence, and delivery constraints.
Turn the brief into a scope signal