Every engagement has its own scope. The essentials are consistent: confirm the work, bring the context, review the experience, and agree on launch.
01
Confirm the starting point.
Your accepted offer defines the work, fees, and service term. For a product purchase, follow the confirmation and onboarding instructions sent to your email. For a bespoke project, use the agreed proposal and kickoff instructions.
What this gives usAn agreed scope and a clear way to continue.
You bring
Check the offer, contact email, and person authorized to make decisions.
We handle
Confirm available capabilities, the agreed scope, and the next setup steps.
02
Bring the business context.
Provide the materials and access required for your scope. Business details, approved content, and the tools you use help shape the setup. A kickoff call is optional in the product checkout flow; a project may have its own agreed meeting plan.
What this gives usThe information and permissions needed to begin the agreed work.
Review what’s needed and identify missing information or unsupported integrations.
03
Build, review, and decide.
Review the agreed experience: the content, inquiry path, supported integrations, and any AI or automation rules. Consolidate feedback through your decision-maker and use the review points in your agreement.
What this gives usA reviewed experience and a confirmed launch decision.
You bring
Check facts, permissions, contact details, and customer-facing messages; approve the final direction.
We handle
Build within scope, make agreed revisions, and review the enabled workflow.
04
Launch and continue.
Confirm the launch milestone and ongoing service arrangements. For the published Website, Pro, Nova, and Ultra checkout offers, the monthly plan starts at launch; setup or design charges are separate. Your accepted offer controls any different arrangement.
What this gives usA live agreed setup and a clear route for ongoing help.
You bring
Know who receives inquiries, handles exceptions, and requests further changes.
We handle
Activate the agreed service and provide the next support or maintenance steps.
02 / Prepare the essentials
A little preparation. A clearer beginning.
Use this checklist to gather what’s ready and identify what needs a conversation. Your actual onboarding requirements follow the offer you’ve accepted.
Share access thoughtfully.
Use delegated account permissions and the access method agreed with the team. Don’t email passwords, API keys, full card details, or private customer lists through an ordinary inquiry.
Not everything applies to every project. Tell us which assets or tools you don’t have so responsibilities can be defined before work starts.
The product or engagement changes the details. We confirm what is available, what is included, and what needs a separate scope.
Website & Pro
Your business, made understandable.
Prepare business details, approved branding, content, domain access, and the destination for inquiries. Pro may also need services and locations, calendar access, review rules, and phone escalation details.
Gather services, FAQs, hours, contact rules, qualification questions, and supported booking requirements. Define the handoff to a person and any phone routing before activation.
Define sales stages, record ownership, team permissions, existing tools, and any migration needs. Agree on available modules, approval steps, usage allowances, and growth-manager responsibilities.
Bring the brief, audience, assets, decision-maker, budget, and constraints. Agree on deliverables, revision rounds, milestones, and whether ongoing execution is part of the engagement.
The shared dashboard and expanded platform modules are in development. We confirm available features, integrations, setup scope, and service allowances with you before activation.
Before we call it ready
Timing, scope, and the handoff.
Onboarding comes before the clock.
Your Pro website, live in 3 business days or less after you complete onboarding. The applicable Pro offer and confirmed production slot define the start conditions. Other projects follow their agreed schedules. Missing materials, access, approvals, or new scope can affect timing.
Review the path a customer will take.
Confirm the offer, forms, inquiry destination, supported booking flow, and human escalation rules. Know which messages and actions need approval, especially when AI or automation is enabled.
Understand the ongoing arrangement.
Confirm billing, support allowances, AI usage, external fees, and what changes require a new scope. Rocket Launch retains its creative and platform IP; usage rights and any export or transition needs follow your accepted agreement.
I paid but haven’t received onboarding instructions. What should I do?
Check the inbox and spam folder for the email address used at checkout. If the instructions aren’t there, contact support with that email address, the offer, and an order reference if available. Don’t send full payment credentials.
Do I have to complete a kickoff call?
The product checkout describes a kickoff call as optional. Bespoke engagements may have agreed discovery or review meetings. Follow the requirements for your actual order rather than assuming every project has the same meeting plan.
Can I start without all my copy or images?
Tell us what is missing. Whether we can begin depends on the scope and launch requirements. Writing, artwork, asset sourcing, or a larger content program must be included or separately agreed; they aren’t automatically part of every setup.
When does monthly billing begin?
For the published Website, Pro, Nova, and Ultra checkout offers, setup or design is charged separately and the monthly service starts at launch. We confirm with you before the first monthly charge. Any different signed arrangement or offer-specific terms control.
Can I add features during the build?
Yes, you can ask. We’ll confirm availability, dependencies, fees, and timing before changing the scope. Expanded platform modules and custom integrations aren’t automatically included because they appear in a demonstration or roadmap.
Does completing this checklist complete my onboarding?
No. This checklist helps you prepare on this page and resets when you reload. Complete the actual requirements using the instructions for your order. The team confirms when the agreed prerequisites are met.
Where do I go after launch?
Use Support for existing-project questions, errors, or agreed service requests. Include the affected page or workflow, what you expected, and what happened. For a new project or substantial extension, start a conversation so it can be scoped.
Keep the next step clear
Ready to begin. Or need a little help?
If you’ve already started, we can help you find the next step. If you’re still deciding, bring us the goal and the context.