A useful quote starts with an assessment boundary. The number of systems matters, but access requirements, application roles, operational constraints, and reporting needs also affect the work.
Prepare the scope
Bring an inventory of the systems you want assessed, the reason for testing, any deadlines, and the people who can authorize the engagement. Identify systems that must be excluded or handled with particular care.
Compare deliverables
Check whether the proposal covers an executive summary, technical findings, remediation guidance, a results walkthrough, and follow-up testing. Ask about assumptions and what happens if the scope changes.
Agree before starting
Fortress provides proposals based on the agreed work. The proposal defines scope, fees, timeline, and responsibilities so you can review the engagement before committing.