Forge / FAQ
Forge FAQ
Is it right for us
Can Forge draft our specs, stories and tests, from idea to release?
Yes. Forge automates your product chain. It drafts your BRD and PRD, user stories, test cases and release material. AI agents handle the reasoning, and fixed logic keeps traceability intact.
Can our product team trace each story back to the need behind it?
Yes. Each story traces back to the need that justified it. Forge is built for product management and delivery teams who turn ideas into releases.
Can Forge turn scattered customer feedback into clear, themed ideas?
Yes. Your ideas arrive organized. Forge captures ideas from customer signals, sales notes, support tickets and your product-planning records, removes duplicates and groups them into themes.
How it works
Can we keep sign-offs and an audit trail across delivery?
Yes. You get one linked chain from requirement to design, story, test and deployment. Sign-off gates and role-based approvals are built in, and each override gets an audit entry. Forge writes in your house style and builds on your existing product docs.
Will our developers get tickets with the context they need to start?
Yes. Developer tickets come pre-filled with context, pointers into your codebase and acceptance gates. Each user story links to its PRD section and carries Given/When/Then acceptance criteria traced to test cases.
Can Forge write our test cases, including accessibility tests?
Yes. Forge writes functional, regression, edge-case and accessibility test cases. Each one traces back to the acceptance criteria it checks.
Can Forge draft our release notes, customer updates and training material?
Yes. Forge drafts release notes, customer communications and training material in your voice, as part of the same linked chain from requirement to release.
Your systems and data
Will Forge work with the tools and code we already have?
Yes. Your tools and code stay in sync. Forge connects to your product-planning, work-tracking and documentation tools and your code, and keeps them updated both ways, with an audit trail. It reads your source code to scope a solution and flag the services it affects.
Can Forge shape the solution around our real architecture?
Yes. Your solution definitions are grounded in your actual codebase. Forge reads your source to scope the solution and flags the services each spec affects. It produces system and data designs with component contracts, sequence diagrams and dependencies.
Getting started
Can we try Forge with one team first?
Yes. Bring one squad's delivery chain, and we'll scope a pilot from there. Use the form on our contact page, and our team will be in touch.
Can we start Forge from our existing discovery notes?
Yes. Your team starts from material it already has. Forge drafts your BRD, PRD and solution definition from your discovery notes and codebase. Use the form on our contact page, and our team will be in touch.
Pricing and support
Can you give us a Forge price based on our scope?
Yes. Pricing depends on scope. Use the contact form and our team will be in touch.
After go-live, will Forge keep learning how our team works?
Yes. Forge learns your style, vocabulary and decision logic with each release, so its drafts follow your house style.