Before launch, the team should make sure the agreed Booking Ninjas setup works, the right users have access, important data is ready, and people know what to do on day one.
The exact checklist depends on the project. A simple setup may need fewer checks than a project with several locations, integrations, user groups, and custom work. The goal is not to make everything perfect. The goal is to remove problems that could stop the first live process from working.
What Should Be Ready Before Launch?
- The main workflow. Users should be able to complete the process the project was built for.
- User access. The right people should be able to see and change the right information.
- Data. Important customer, booking, space, payment, or other records should be loaded and checked.
- Integrations. Required systems should exchange the information the workflow depends on.
- Reports. Managers should be able to trust the key reports they need from day one.
- Training. Users should know how to complete their own tasks and what to do when something goes wrong.
Why Is Final Testing Important?
Testing should cover the real process, not only individual screens. Salesforce recommends testing again after changes are moved into the live environment because production can behave differently from a test environment.
Important problems should be fixed before launch. Smaller issues can sometimes wait if they do not stop the main process. For more detail, see How Changes Are Tested.
Tested does not mean perfect
A small visual issue is different from a problem that stops a booking, payment, integration, or user from completing required work.
Who Should Approve the Launch?
The people who own the business process should confirm that the setup supports the agreed need. The implementation team should also confirm that the technical work is ready.
A system can be technically complete but still fail the business process. Someone who understands the real work should be able to say that the first live workflow is ready enough to use.
What Should Users Know Before Day One?
- What tasks they are expected to complete in Booking Ninjas.
- Which records or information they are responsible for.
- What each important status means.
- What to do when the normal process does not work.
- Where to find help or training material.
Training should match the user role. See How Training Works.
Should Every Open Item Delay Launch?
No. The team should look at the effect of each open item. A small display change may be safe to finish later. A missing payment method, broken integration, wrong access rule, or major workflow gap may be a reason to wait.
Salesforce launch-readiness guidance uses the same idea: gaps should be written down, given a priority, and handled based on their effect on the launch.
What Happens Right After Launch?
The team should watch real usage, check important data and integrations again, collect user feedback, and fix launch problems quickly. See What Happens After Launch?.
Sources and Further Reading
- Salesforce Trailhead: Roll Out the Salesforce App to Your Users — recommends testing again in production, controlling access, collecting feedback, and measuring results.
- Salesforce Trailhead: Review Business Requirements Before Launch — explains how launch gaps should be identified, documented, and prioritized by impact.
- Salesforce Trailhead: Develop a Training Plan — shows why training should be based on user roles and the work each person needs to perform.
Sources support the general launch-readiness ideas. The exact Booking Ninjas launch checklist depends on the agreed project.