BRD Manager is offered as part of an engagement: set up and run with you, not handed over as a login and a manual.
The best way to find out whether it fits is to run one engagement through it. Tell me the edition, the region and roughly where the project is, and I'll tell you what the first workshop would look like.
NetSuite partners and implementation teams who want every BRD to start from the same standard, whoever writes it.
Companies about to implement or re-implement NetSuite who want to see, before signing a statement of work, what's standard, what needs a license and what will have to be built.
Anyone replacing a template-and-memory process with something they can actually go through with a client in a workshop.
Where does the catalogue come from? It's a leading-practice catalogue of about 9,700 lines. It stays current with each NetSuite release through the AI release-note review described on the BRD Manager page, with a person approving every addition.
Does it touch our NetSuite account? No. It produces the requirements document and the fit-gap. It doesn't configure anything.
Can our team comment and attach files? Yes. Every requirement has a discussion thread, and so does every catalogue line linked to it. Flow diagrams and supporting documents are stored with the engagement.
Is the fit-gap decided by AI? No. It's a published rule applied to the engagement's scope, and you can change any result by hand. The AI helps you discuss and refine requirements. It doesn't score them.
What does it cost? That depends on the engagement. Tell me about yours and I'll give you a straight answer.
The edition, the region, the go-live date and where you are today. I'll reply with how I'd run discovery through BRD Manager.