AI Client Scope Workbench

How to use AI Client Scope Workbench

Before promising automation, make every requirement testable. Pair each request with its delivery and acceptance row, then review count mismatches and missing access or schedule details.

1. Enter the original requirements, one per line.
2. Pair each with a proposed deliverable and measurable acceptance criterion in the same order.
3. Resolve the questions and review the effort assumptions before producing a quote.

Good to know

• The tool detects mechanical omissions and a small list of ambiguous words. It is not a semantic requirements analyst or feasibility guarantee.
• The equal effort per requirement is your explicit assumption. Additional rows are flagged rather than silently treated as agreed scope.
• Estimates use floating-point arithmetic, rounded for display. Inputs must be finite nonnegative decimals at most 1 billion (whole counts at most 1 million); nonzero inputs below 0.000000001 and results outside the supported range are rejected.
• Runs locally without AI model calls, network requests or saved input. Text is limited to 8,000 characters per field and lists to 100 nonempty lines. Downloads contain your text; review them before sharing.