Ghosting
The industry default. No Sustain phase, no handoff, no advisory window — the consultant just stops returning emails. Systems decay silently. We refuse this mode on principle.
III.Flame
06 · Phoenix · Ongoing retainer or formal handoff
Sustain
The phase that decides whether year two survives.
Sustain is the final phase of the Phoenix Methodology, and the one that honestly explains why most consulting engagements fail in year two: nobody owns the system once the consultant leaves. We resolve Sustain two ways — either a monthly retainer that keeps the system alive, upgraded, and expanding, or a formal handoff with documentation and a 90-day advisory window.
What it is
A deliberate choice between two ongoing modes. Mode one: Creative Alliance retainer, where we continue to own, maintain, and expand the system on a monthly basis. Mode two: formal handoff, where we transition the system to your internal team with complete documentation and a 90-day advisory window. Both are legitimate. The one outcome we refuse is ambiguity.
What it is not
Sustain is specifically not:
- Not a vague 'stay in touch' arrangement. Ambiguous ongoing consulting is where systems go to die.
- Not a feature-request ticket queue. Retainer scope is defined up front, not negotiated per request.
- Not a lock-in. The handoff option exists for exactly this reason — if your team is ready to own the system, we transition cleanly.
You leave with
Either a managed system or a clean handoff
Retainer mode: monthly scope document, defined response SLAs, system health monitoring, quarterly expansion planning. Handoff mode: a complete systems-documentation binder, a 90-day advisory window, and a named contact for emergency questions. Both modes include a written Sustain Plan specifying who is responsible for what.
Why this phase exists as a formal phase
Because the industry norm is for the consultant to ghost at end-of-Build and for the client to discover, eight months later, that the software permissions are wrong, the automation is firing stale data, and nobody knows how to fix it. Sustain is the refusal to participate in that pattern. Every engagement has to end in a way that answers, in writing, the question: who owns this system starting next Monday?
Mode one: Creative Alliance retainer
The Creative Alliance monthly retainer absorbs Sustain for clients who prefer to stay with us long-term. Monthly retainer scope covers system health monitoring, minor enhancements, quarterly expansion planning, and on-demand creative production. Retainer tiers are published on the <a href='/CreativeAlliance'>Creative Alliance page</a>.
The retainer is not open-ended hourly billing. It is a scoped, defined monthly commitment with clear boundaries on what is in and out of scope.
Mode two: formal handoff
For clients with internal technical capacity, the handoff option is legitimate and actively supported. We deliver: complete written systems documentation (admin-level plus operator-level), a recorded video walkthrough library, administrative credentials transfer, and a 90-day advisory window during which your team can contact us for clarifications at no additional cost.
After the 90-day window, you either renew the advisory as a light retainer, or the engagement closes. Both are clean endings. Neither is a surprise.
How to choose between the two modes
Choose the retainer if: you don't have internal technical leadership, your system is still expanding in scope, or your monthly operational ROI from the system easily exceeds the retainer fee. Choose the handoff if: you have a capable internal operator, the system is stable, and you want to own the system outright.
We will recommend a mode based on our Phase 1 Diagnose findings, but the final decision is yours.
Where it fails
Ambiguous retainer scope
A retainer that bills monthly but has no written scope is a disagreement waiting to happen. Every Sustain retainer has a scope document. If it doesn't, it isn't a retainer — it's a subscription to chaos.
No named internal owner after handoff
A handoff that hands to 'the team' hands to nobody. Every handoff names a specific person on your team as the system owner. If you don't have that person, the retainer mode is the right choice.
Phase 6 Sustain — FAQ
Do I have to move to a retainer at the end of Build?
No. The formal handoff option is a legitimate, supported ending. Roughly half of our engagements move to retainer; roughly half hand off to an internal team.
What's included in the Creative Alliance retainer?
Monthly system health monitoring, minor enhancements, quarterly expansion planning, and scoped creative production. Full tier breakdown is on the Creative Alliance page.
What if we hand off and something breaks six months later?
Within the 90-day advisory window, you can contact us at no additional cost. After that, you can re-engage us on an hourly basis for specific fixes, or move into a light retainer. We do not charge a reactivation fee.
Inherited a system nobody's maintaining?
If your transformation shipped but nobody owns it now, Sustain-as-a-rescue is a valid scope. We audit, document, and either take over the retainer or hand it back to a named internal owner.
Get your time back.
Nicholas runs this studio on it. Mobile speed went from 49 to 92. We run on it too.