ResourcesWhite paper
Owning your systems after the build
A system you cannot understand, change or move without your partner is not fully yours, however much you paid for it. This paper sets out what any organization should insist on from any technology partner, us included, and gives you a checklist to use before you sign.
In short
- Every account, license and domain in the organization's name.
- At least two of your own people with full admin access.
- Documentation in plain English, owned by you, kept current.
- A record of every change: what, why, who, when.
- A handover you test by doing, not by reading.
- Standard tools where possible, and a clear way to part.
ForAnyone choosing a partner or signing a technology contractTime to readAbout 25 minutesUse itBefore you sign, and at each renewal
- What ownership actually means
- Your own accounts and licenses
- Admin access that does not depend on anyone
- Documentation in plain English
- A record of every release
- A handover you can test
- No lock-in, by design
- The partner checklist
Rather talk it through?
A 30-minute conversation about your systems and what's getting in the way. You leave knowing what would help.