Four steps, and the last one never stops running.
In BRD Manager, an engagement is a client, a scope and a list of requirements. Here's how the list gets built, and what happens to it after that.
Choose the client's licensed edition, region, market and target NetSuite release. Every later decision is measured against them, including whether a capability exists in the release they're going live on.
One click brings in every leading practice that applies as a draft requirement, already linked to its catalogue line. The button shows how many before you press it. Run it again later and it adds only what's newly in scope, without duplicating or deleting anything.
Go through the list by process area. Edit, remove and prioritise (Must, Should, Could, Won't), take notes, attach files and discuss, either on the requirement or on the catalogue line behind it. Add the client's own requirements alongside.
Every requirement shows its fit-gap result and the reasons for it. A summary bar totals up the engagement: how much is standard, what needs a license, what the edition or release doesn't support, and how much customization work is on the table.
Each catalogue line linked to a requirement is checked against the engagement's scope:
A requirement gets the best result among its linked lines. A requirement with no catalogue line at all is a Customization. Those make up the list of work you estimate and price.
It works this way on purpose. The AI doesn't decide the fit-gap; a rule you can read does. You can set any requirement's result by hand, and your choice stays until you switch it back.
It will. A client reconsiders an edition, adds a region, moves a go-live date. Before anything changes, BRD Manager shows you the effect: which requirements stay, which fall out of scope, and how many new leading practices the new scope adds.
Only seeded drafts nobody has touched are removed. Anything a person has reviewed, edited or moved forward is kept, and shows up as a gap to decide on. For those, Find in-scope match suggests the closest equivalent in the new scope and links it in one click. Real gaps stay gaps.
BRD Manager is built on AI Application Manager, so it uses the platform's sign-in, roles and permissions, usage tracking and AI access instead of building its own.
In practice, that means team workspaces: you're always working inside one team's engagements, or your own. Roles decide who can change an engagement's header details, only editors can change reference data, and the AI assistant's usage and cost are tracked like every other app's.
Tell me about the engagement and I'll tell you how I'd set it up.
Getting started