The word delivery suggests a moment. The package arrives, the project closes, both parties move on. That is not what handover means in the Prymetheus process — and understanding the difference matters for anyone considering what a Custom Build actually produces.
Handover is not the end of the engagement. It is the point at which the system moves from Savannah's hands into the founder's. And that transition is a phase in itself.
What the founder receives at handover
At handover, the founder receives the system itself — installed on her machine and running. She also receives the full repository: every file, every folder, every configuration, organized and documented so that she can understand what she has and how it works. Not a black box. A readable, navigable system she can learn and eventually modify.
She receives the documentation: how the system works, what decisions were made in the build and why, what the system does in each workflow step, and what to do when something unexpected happens. The documentation is not a technical manual for an engineer. It is a practical guide for the founder who owns the system and needs to be able to operate it confidently.
And she receives the Stabilization Window.
What the Stabilization Window is
The Stabilization Window is the period after handover during which Savannah remains available for questions and edge-case handling as the new system becomes the working default. Not a support ticket queue. A responsive window for the specific, real-world situations that emerge when a founder starts actually using a system — not in a testing context, but in the daily operations of her business.
Every new system encounters edge cases that were not anticipated in scope. Clients whose data does not conform to the expected format. Workflow situations that the design handled correctly in principle but required adjustment in practice. The Stabilization Window is where those situations are handled — while Savannah is still engaged and the system is still in its integration period.
“The system works on the day of handover. The Stabilization Window is what makes it work on the day she doesn't think about it anymore.”
What handover is designed to produce
The goal of handover is not a successfully delivered project. It is a founder who owns a system — who understands it, trusts it, and is capable of using it independently. A system the founder is afraid to touch or does not understand is not owned infrastructure. It is just another dependency.
This is why the documentation, the repository structure, and the Stabilization Window all exist in the same phase. They are the components of a transfer that ends with the founder in genuine control. Not just in possession of a new tool. In ownership of a system she built her workflow around.