Things worth knowing before you call.

No. The consultation and contact forms do not need one. An account is created when you become a client, because that is when there are documents and records to protect.

Because the honest answer depends on what you already run. A fixed price on a page would either be so padded it is useless, or so low it changes after the first call. Services that can be priced without a conversation say so.

You do — the code, the accounts, the domains, the documentation. We record them in your Technology Passport so the details are not locked in one person’s inbox, and if you ever leave you take the record with you.

A structured record of your technology environment: domains and their expiry dates, hosting, applications, vendors and renewal dates, and the history of every service we have performed. Its most immediately useful part is a single dated list of everything that falls due — which is what stops a domain lapsing because a notice went to an address nobody reads.

Your checklist is generated from the services you actually asked for. A client taking consulting alone sees a short list; one taking server management sees infrastructure questions and an authorization form as well. You are not asked for information the work does not need.

In the client portal, versioned. When a document changes you are asked to acknowledge the new version, and the earlier acknowledgment stays on record against the version it applied to — so it is always possible to establish which text applied on a given date.

No. Emails tell you that something needs attention and link to the portal; they never carry the material. A message saying a document needs your attention is safe to receive on a phone in a public place. The document itself is not in it.

Only where you have authorized it in writing, for the systems named in that authorization, and only to do the work agreed. Every change is recorded against the system in your Technology Passport with the date and the person who made it.

No — never, and we will never ask you to. This portal is built for documents, not secrets. Where access is genuinely needed we agree a secure method with you separately. If credentials are uploaded here by mistake, tell us so the file can be removed and the credentials rotated.

A client administrator manages their colleagues’ access. A client user sees the organization’s services, documents, technology record and roadmap. Nobody outside your organization sees any of it, and no other client can reach your records by any means.

No. Maintenance is a separate service you can take or leave, and the work we hand over is documented well enough for someone else to maintain it.

Yes, and often. A great many problems presented as needing new technology are reporting problems or process problems, and solving them that way is cheaper and more reliable.

No. We take no commission or referral fee from any vendor, which is why the assessment can honestly recommend keeping what you have.

Yes — we restore from them before handover and record the result. A backup that has never been restored is an assumption, not a control.

You do — the source, the hosting account, the domain and the certificate. We record them in your Technology Passport so the details are not locked in someone's inbox.

Yes, and often. A great many problems presented as AI problems are reporting problems or process problems, and solving them that way is cheaper and more reliable.

No. We will tell you what was tested, what passed, what failed and what was not covered. Anyone who tells you a system is secure is describing a feeling, not a finding.

Yes. We set up editing for the pages that change, and train whoever will be doing it.

Yes, before anything is tested, and it has to come from someone with authority to give it.

Then it says that. An assessment whose only possible conclusion is 'buy more work' is not an assessment.

No. Maintenance is a separate service you can take or leave.