Structure complex briefs
Test structured extraction of functional requirements, quality needs, exclusions, constraints, and open decisions from permitted sample briefs.
AH BriefFlow is a proposed AI-assisted workflow for small software agencies and independent development teams: structure client requirements, identify missing details, and prepare proposal drafts for human review.
Current stage: Interactive browser-based prototype. Next milestone: Claude API integration for contextual requirements analysis and proposal drafting.
An early-stage client-brief workflow concept for small software agencies and independent development teams. AH BriefFlow helps small software agencies organize client briefs into structured requirements, clarification questions, and editable proposal outlines. The current interactive prototype runs locally in the browser using rules. Claude API integration is planned for deeper contextual analysis, with human review before proposals are used.
The problem: Client requirements often arrive as long documents, fragmented messages, and incomplete descriptions. Teams must manually clarify scope before they can prepare reliable proposals.
For: Small software agencies and independent development teams handling early-stage client requests.
Proposed outcome: A structured first draft that people can check, edit, and approve.
Paste a client brief into the live text-only prototype. Document upload is planned, not available yet.
Classify candidate requirements, context, constraints, exclusions, and undecided items using transparent rules.
Generate clarification questions and an editable proposal outline from the detected items.
Keep final decisions, editing, and sharing with the human user.
The public prototype runs in the browser using deterministic rules. It provides an inspectable baseline, not AI-based semantic analysis. Try the interactive prototype ↗
The next technical milestone is to evaluate the Claude API against our rule-based baseline, focusing on more accurate requirements classification and fewer unsupported assumptions.
Test structured extraction of functional requirements, quality needs, exclusions, constraints, and open decisions from permitted sample briefs.
Explore tool-supported checks for missing information and grounded follow-up questions, with each proposed action available for human review.
Keep generated scopes and proposals editable. The user reviews all assumptions before any client-facing decision.
AH Solutions is the early-stage project developing AH BriefFlow. Our commercial approach is a proposal to test, not an existing paid service.
Project leads, developers, and proposal owners at small software agencies who translate client requests into scopes.
We plan to explore whether small teams find enough repeated value to pay for a shared brief-analysis workflow.
Team-based subscription pricing is a hypothesis for later validation. There is no live paid plan, published price, or claimed revenue.
The planned Claude integration addresses a specific limitation: rule-based sentence extraction often confuses background facts, requirements, exclusions, and undecided items.
Paste a text brief; classify candidate statements; suggest clarification questions; edit and download a proposal outline. Processing uses local browser rules.
Compare Claude's structured classification and context-sensitive questions against this baseline. Explore tool use only where it improves reviewable output.
Use permitted or fictional briefs, and review missed requirements, unsupported additions, and how much human correction each output needs.
These are proposed tests and roadmap items, not claimed completed evaluations. Inspect the current prototype ↗
AH Solutions is an early-stage, founder-led software project developing AH BriefFlow. We share the product roadmap and current technical progress openly.
Backend developer with experience in web application development and technologies including Node.js, Laravel, and SQL. Building AH BriefFlow as an early-stage project focused on practical client-brief workflows.
Interested in the AH BriefFlow prototype or in giving feedback on client-brief workflows? We welcome thoughtful conversations.