Skip to main content
The ForgeThe Forgeby HustleForge

Sample Managed Launch

A week-by-week walkthrough of a Managed Launch for the same fictional Example Co. — illustrative only, not a real customer record.

This is a fictional example, not a real customer

This walkthrough follows the same invented "Example Co." (a fictional 12-person home-services company) used on the Sample Forge Plan page, through a Managed Launch. It is not a testimonial, case study, or record of an actual launch. For the general Guided vs. Managed comparison, readiness checklist, and data-ownership rules that apply to every launch, see the Launch page — this page only walks the Managed Launch path week by week.

Week 1 — Kickoff & Blueprint confirmation

Who does what: Example Co.'s owner and office manager confirm the software inventory and workflow review from their Blueprint; the Forge launch team finalizes the configuration scope from that conversation.

Week 2 — Configure

Who does what: the Forge launch team configures the plan to what was confirmed in Week 1 — intake form, quoting, scheduling, dashboards. Example Co. provides access and answers configuration questions as they come up; they do not perform the configuration themselves.

Week 3 — Connect & migrate

Who does what: the Forge launch team connects the approved integrations (Example Co.'s accounting package, in this example) and migrates customer, job, and staff records. Example Co.'s existing spreadsheet and accounting package keep running in parallel — nothing is disconnected yet.

Week 4 — Train

Who does what: the Forge launch team runs training sessions for each role (owner, office manager, technicians) on their specific view. Example Co.'s team attends training and begins validating moved records against their original systems.

Week 5 — Go-live

Who does what: Example Co.'s owner gives written go-live approval once the go-live checklist is met; the Forge launch team executes the coordinated switch and is available through the transition.

Weeks 6+ — Stabilize

Who does what: the Forge launch team monitors adoption, connection health, and support themes in the early weeks after go-live; Example Co.'s team uses the platform day-to-day and flags friction as it's found. This mirrors the post-launch monitoring described on the Launch page.

Cost, illustrative only

Managed Launch pricing for this example would be quoted against Forge Core ($1,250), confirmed during discovery — see the Launch page for how Managed Launch can be paid upfront, distributed over six months, or included in an Operations annual agreement.

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.