Launching a program successfully goes far beyond simply configuring settings. It’s about aligning your teams, preparing your processes, and ensuring that every part of the program ,from budget and workflow to communication and community engagement, is ready to run smoothly.
This checklist helps guide you step by step, making sure nothing is overlooked and that all stakeholders are informed, aligned, and empowered for a successful launch. Following these actions upfront reduces risks, improves researcher experience, and sets your program up for long-term success.
If you are onboarding with us, you will be supported by an onboarding manager and a dedicated Customer Success Manager, who will guide you through each step required to successfully launch your program.
🎖️ Intigriti Program Review
Before launching, schedule a final review with your customer success manager. This step is strongly recommended to catch missing details, clarify open questions, and ensure your program is fully aligned with Intigriti best practices.
Program
When setting up a program, it is important to look at it from a researcher’s perspective. Clear instructions, a well-defined scope, and easy access to test credentials help researchers understand what to test and how to do it. This leads to higher quality submissions and a smoother launch.
Discuss scope and priority areas. Clearly define which assets are in scope, how they should be tested, and how this aligns with your security objectives.
Complete the Program Details according to Intigriti best practices. Make sure descriptions, scope, and rules are clear and actionable.
Prepare test accounts where needed and upload test credentials so researchers can claim them once the program goes live.
Communication
Clear communication is often underestimated during a program launch. Even with a perfectly configured program, success depends on internal teams knowing what is coming, why it matters, and how they may be impacted. Early alignment avoids surprises and helps your organization respond quickly once submissions start coming in.
Inform the development team about the launch timeline and expectations. Confirm they have capacity to address exceptional, critical, or high-severity findings shortly after launch. Check whether integrations such as Jira are required for remediation.
Inform the operational or support team about the launch, especially if user-facing elements such as support forms or order flows are in scope.
Notify the communication or PR team if the program launch is public-facing or may attract external attention.
Community
A healthy program depends on a strong relationship with the researcher community. Setting expectations early and understanding how to handle collaboration and unwanted behavior helps create a respectful and productive environment for everyone involved.
Discuss your expectations and preferred way of working with the researcher community together with your Success Manager.
Decide which researcher restrictions you want to enforce. Verify that your program settings reflect these choices, including identity checks, area restrictions, enforced 2FA and collaboration settings.
Define the confidentiality level of your program to control its exposure to the researcher community.
Decide whether researchers must agree to custom terms and conditions before participating, and configure your program settings accordingly.
Make sure you understand how to respond to unwanted researcher behavior, including escalation paths and reporting procedures.
Workflow
A well-prepared workflow ensures that submissions are handled efficiently from day one. Correct assignments, notifications, and integrations help your teams stay informed and respond quickly without manual overhead.
Verify that the default assignee is correctly configured on the Program Members page. This user will receive submissions automatically after triage verification.
Ensure that email notifications are enabled for the appropriate users.
Make sure emergency text messages are enabled by adding the required emergency contacts.
Configure the necessary integrations such so submissions, updates, and notifications flow smoothly into your internal systems.
Review and configure message templates before launch to ensure consistent and efficient communication with researchers for common scenarios such as acknowledgments, information requests, or delays.
Prepare for incoming submissions by reviewing how submissions are handled and how Intigriti triage works.
Budget
A clearly defined budget is essential to avoid interruptions after launch. An insufficient budget can result in automatic program suspension or delayed rewards, which negatively impacts researcher trust and engagement.
Contact your Success Manager to learn more about the recommended program budget.
Ensure the recommended budget is added to your program, either by expanding the program budget directly or reallocating funds from the company budget.
Make sure you understand how the auto-suspension mechanism works, including when and why a program may be automatically paused due to budget depletion.
Prepare for scenarios where your program performs very well and the budget depletes faster than expected. Make sure you know how to replenish the budget quickly to avoid downtime.
Decide whether to enable dynamic budget pooling to allow your program to automatically draw from the company budget when the program budget is exhausted, and configure this setting if it fits your setup.
Best practices
Review this checklist with all involved teams before launching to confirm ownership and readiness.
Reach out to your Success Manager to schedule a program review before launching.
Monitor the first days after launch closely to address early feedback, submission patterns, and potential bottlenecks.
Related articles