Skip to main content
The Forgeby HustleForge

Launch templates

The checklists we use to get your business ready, move your information, and confirm everything works before you switch.

Readiness checklist

What a Blueprint conversation confirms before a launch is scoped, regardless of which launch path you choose.

  • Current-software inventory — every system in use today, with monthly cost, active users, and overlapping capability noted
  • Named owner for each system slated to connect, consolidate, or be retired
  • Access confirmed for each system that needs to connect (API credentials, admin access, or export capability)
  • Existing data cleaned or flagged for migration — duplicate contacts, stale records, inconsistent statuses
  • A decision on Guided Launch vs. Managed Launch for your team

Who keeps the official record

For every connected system, we confirm before go-live which side keeps the official record.

  • Which system keeps the official record for this type of information after launch?
  • Does The Forge read this information, update it, or both?
  • What happens on a conflict — which side wins?
  • Who is notified when information stops syncing?
  • Is this information regulated or otherwise required to stay in its current system?

What must be true before you go live

Confirmed before a Managed Launch is called complete, or before a Guided Launch milestone is approved.

  • Every in-scope system is connected at its agreed setup classification
  • Customers, jobs or accounts, staff, and history have been migrated and spot-checked
  • Role-based access matches the org chart confirmed during the Blueprint
  • Existing systems remain available and unaffected until the customer approves the switch
  • Reports and dashboards show complete information from every connected system
  • Training completed for the roles who will use The Forge daily

Launch paths

Both templates above apply under either launch path — the difference is who executes each item.

  • Guided Launch: Included on Forge Start, Core, and Pro. Work through a structured launch and earn Forge Credits as your team completes each onboarding milestone. Forge Operations requires a scoped Managed Launch instead.
  • Managed Launch: You provide access, context, and approvals. Our team configures, connects, migrates, tests, trains, and launches The Forge remotely.

Related

More resources

Have a question these guides don't answer?

Full $249 applies toward Managed Launch, an annual Core or Pro agreement, an approved integration, or migration assistance.