Phases, owners, and acceptance gates
| Phase | Owner | Work | Acceptance evidence |
|---|---|---|---|
| Verify the transferable model | Owner and first-site manager | Document the workflows, roles, economics, and local conditions behind the first site. | The team can distinguish repeatable practice from location-specific advantages. |
| Prepare people and coverage | Receiving manager | Assign local authority, train backups, and test central support arrangements. | The site can resolve normal decisions without waiting for the founder. |
| Rehearse the operation | Local team and support leads | Test intake, scheduling, purchasing, delivery, escalation, and reporting. | Critical scenarios work with the people and systems that will operate the site. |
| Open with a stabilization plan | Opening sponsor | Track constraints, support requests, staffing, and customer commitments. | The site has a clear escalation path and a review cadence. |
Before the first working session
Name a sponsor who can resolve competing priorities and a manager who will maintain the result. Gather a recent normal case, an exception, and the current instructions. Reserve time for the people doing the work; a plan cannot be validated entirely through leadership discussion.
Worked example
Illustrative example: the original site relies on its manager to approve every unusual order. Before opening the second site, the team documents normal acceptance limits and creates a central escalation path for exceptions. The new manager tests both routes during rehearsal.
When to pause or revise the plan
Do not treat this checklist as approval of the location’s financial, property, licensing, employment, or safety readiness. Resolve required specialist approvals and critical operating gaps before opening.
A practical review rhythm
At each phase boundary, review completed evidence, unresolved decisions, and the next owner. If a prerequisite is missing, record who will resolve it and when the team will review it again. Keep acceptance separate from effort spent: a completed meeting is not proof that the new workflow can operate.
Handover and continuing ownership
Compare sites using shared definitions with context for demand and staffing. Keep early support work visible so a successful opening does not quietly overload the original location.
Related implementation resources
Discuss the operating problem
Elixir consulting starts at $5,000 per month, with final pricing based on scope. Bring a recent example, the current workflow, and the person who owns the result to define the appropriate implementation scope.