The implementation standard
A finished build has to work after the handoff.
The technology is only one part of the system. Every project defines the work, keeps people in control, tests what can go wrong, and leaves you with something you own.
Choose the result you already know you need, or use the free assessment tool to help guide you.
You get the whole working system: scoped, built, tested, and handed over. Not a recommendation, a pile of tools, or a demo that sits beside your real work.
The technology is only one part of the system. Every project defines the work, keeps people in control, tests what can go wrong, and leaves you with something you own.
Four assurances
Before anything gets built, you agree on the result, the scope, who owns it, how it's measured, the backup plan, and when the work counts as done.
Your accounts, domains, data, settings, exports, and custom code stay yours. Any third-party license is disclosed up front.
It gets tested for the bad days too, like missing information, an outage, or a failure, with a way to roll back. The riskier the job, the deeper the testing.
You get documentation, a handoff, and a set period to settle in, plus training when the system needs it. The old way is retired, or kept only as a planned backup.
Defined before build.
• Before anything gets built, you agree on the result, the scope, who owns it, how it's measured, the backup plan, and when the work counts as done.
Client-controlled.
• Your accounts, domains, data, settings, exports, and custom code stay yours. Any third-party license is disclosed up front.
Tested beyond the happy path.
• It gets tested for the bad days too, like missing information, an outage, or a failure, with a way to roll back. The riskier the job, the deeper the testing.
Stabilized in real use.
• You get documentation, a handoff, and a set period to settle in, plus training when the system needs it. The old way is retired, or kept only as a planned backup.
Defined before build.
• The result, scope, accountable owner, measure, fallback, and stopping condition are agreed before implementation.
Client-controlled.
• Your accounts, domains, data, configuration, exports, and custom code remain under your control, subject to disclosed third-party licenses and services.
Tested beyond the happy path.
• The agreed normal, exception, missing-input, outage, failure, and rollback conditions are tested in proportion to the risk.
Stabilized in real use.
• Documentation, handoff, and a defined stabilization period are part of the implementation. Workflow-specific training is included when the approved system requires it. The old way is retired or kept only as an explicit fallback.
Before you pay, the proposal spells out what's included, what you need to provide, which systems it touches, how it's tested, the handoff, and what's not included.
Software, hosting, APIs, phone usage, data services, and other vendor charges are disclosed separately before approval.
Your accounts, access, data, settings, and custom work never turn into a subscription you have to keep paying me for.
Ongoing support is optional, unless your system needs someone watching it: monitoring, fixing incidents, maintenance, or vendor changes.
The questions most owners ask first. A short conversation settles the rest.
Tell me what should move, how the work happens today, and what can't break. If it fits one of these, the next step is a short call to scope it.
![[digital project] media outreach strategy featured on a laptop screen in a dimly lit study](https://cdn.prod.website-files.com/69fb71a05229680366066549/6aa803244b937c5edc213603_Litbox%20OS%202400%20Wide%20Chris%20Gallego%20Laptop.png)