Client-controlled foundations
Domains, business data, production accounts and primary service access are held under client control wherever the platform permits.
Continuity & ownership / Built into delivery
Founder-led.
Not founder-dependent.
Work directly with the person
who understands your business.
Keep control of what it depends on.
Access, documentation, client-specific source and operating knowledge are maintained so another competent specialist can take over if required.
The protection is ownership and transferability, not the appearance of a large permanent team.
The practical commitment
The knowledge stays
with the work.
I help understand the problem, build the solution and keep improving it. The information needed to operate and maintain it should not exist only in my head.
You get senior personal delivery, while the information and access needed to operate, maintain and transfer your systems remain clear, available and properly documented.
What this means in practice
Clear boundaries.
Practical protection.
Source continuity
Client-specific source is maintained in a client-controlled or mirrored repository, with the access another competent specialist would need to review and continue the work.
Operating knowledge
Architecture, integrations, dependencies, deployment requirements and important operating decisions are recorded in plain language.
Recovery and handover
Backup, restore, deployment and transition instructions are kept practical so continuity is possible during a planned handover or unexpected absence.
Honest ownership boundaries
Client data, accounts and agreed bespoke deliverables remain protected. Shared Blast47 core and reusable components are licensed rather than transferred, while third-party and open-source components remain subject to their own licences.
The maintained handover pack
A usable record.
Not a pile of files.
- Client and service account ownership
- Source repository and access location
- System architecture and integration register
- Important dependencies and licence boundaries
- Deployment, backup and recovery instructions
- Current operational notes and known priorities
- Last review date and handover readiness
If Andy is unavailable
A clear route
for the next specialist.
- Confirm the client's authorised continuity contact and secure access route.
- Release or confirm access to the mirrored source and maintained handover record.
- Give the appointed specialist the architecture, dependencies and recovery context.
- Transfer operation without withholding client data, credentials or client-specific knowledge.
Before starting
No ambiguity.
No hidden lock-in.
Does the client control its data and accounts?
Yes. Client data, domains and primary business accounts remain under client control wherever the service provider allows it.
Is all Blast47 software open source?
No. Client-specific deliverables are handled as agreed in the engagement. Shared Blast47 core remains licensed, and third-party or open-source software remains subject to its existing licence.
Can another specialist take over?
Yes. The purpose of the mirrored source, documentation and handover record is to give another competent specialist a clear route into the system.
When is the continuity record updated?
It is reviewed at meaningful delivery milestones and whenever a material change affects access, architecture, deployment or recovery.
Build for the business
Direct with me.
Ready for the future.
Discuss the work you need and the access, ownership and continuity arrangements that should accompany it. Those boundaries belong in the scope from the start.
Discuss your projectWays to work together