Most small businesses cannot produce a list of their own domains, logins and hosting. That is normal. It is also the reason ordinary jobs turn into week-long problems.
Technical cleanup is establishing what your business owns online, who controls it, and getting that control back where it belongs. Domains and DNS, hosting, email tenants, analytics, the website itself, and the accounts each one lives inside.
It is groundwork rather than a project with a visible result, which is why it rarely gets sold. It is also the thing that decides whether a redesign, a mail migration or a DNS change takes an afternoon or a fortnight.
Nobody sets out to lose track. It accumulates, and every step was reasonable at the time.
A friend registered the domain. A web agency built the site and pointed the DNS. An office manager set up the email. Each person did their bit properly and none of them wrote anything down, because they each only held one piece.
The domain sits in a personal account with a personal card on file. The analytics belong to someone's Gmail. When that person moves on, the business does not lose the service immediately, which is precisely the problem: it fails silently, months later, at renewal.
Or just ended. Handover was verbal, or never happened. The business is still live but nobody has the keys, and the previous provider has no obligation and no incentive to answer the phone.
Which is genuinely the most common version. Everything works, so nobody looks. The problem is only discovered on the day something needs to change, and by then it is urgent.
The output is an inventory and a set of recovered logins, not a redesign. It is deliberately unglamorous.
A good deal can be established from public records before anyone hunts for a password: what the domain points at, who serves the DNS, what the mail records say, what the site runs on. This costs you nothing in effort and usually reveals the shape of the problem.
We tell you what we found and you tell us what you expected. The gap between those two lists is the real scope of the job, and it is often the moment an owner realises a supplier relationship is a bigger dependency than they thought.
Anything needing a provider recovery process goes first, because those run on the provider timetable. Everything else can happen while they are in progress.
Accounts in the business name, billing on a business card, recovery details that do not depend on one person staying. Access for whoever needs it, ownership with you.
The record of what exists and where. Yours to keep, and specifically written so a future provider can pick it up without repeating this exercise.
This usually starts because something else is blocked. The rebuild cannot start, the mail cannot move, the renewal failed. Cleaning up first is what makes the next job ordinary.
Working out what your business actually owns and controls online, then getting it back into order. Domains, hosting, email, DNS, analytics, the website, and the accounts each of those sits inside.
It is the job nobody sells because it is unglamorous, and the one that quietly blocks everything else. You cannot move a website if you cannot log in to the domain, and you cannot fix email delivery if nobody knows who controls the DNS.
Sometimes not, and we will say so. If you can log in to everything today, the records are written down, and nobody is worried, then leave it alone.
It becomes worth doing when there is a single point of failure with a person's name on it. If one former contractor could lock you out of your own domain, that is a business risk regardless of whether anything is currently broken. The cost of fixing it in advance is a fraction of fixing it during an outage.
That happens more often than you would think, and it is usually recoverable. Domain registrars, Google and Microsoft all have recovery processes for exactly this, and they generally favour the business that can prove it owns the domain and the billing.
What they need is evidence: billing records, the original registration, control of the domain, company documentation. It takes patience rather than cleverness. Start it early, because these processes are measured in days and not minutes.
Only the access needed to do the work, and ownership stays with you. We would rather you held the master accounts and granted us access than the other way round. A provider who insists on owning your domain or your tenant has given themselves leverage over you, and that is not a relationship we want either side of.
When work finishes you get the record of what exists and where it lives, whether or not you continue with us.
The discovery part is usually quick. The unknowns are the recovery cases: if an account has to be recovered through a provider's process, the clock belongs to them, not us. We front-load those for that reason.
What we can say is that you will know what the situation is early. Finding out that three things are missing is itself the useful output, even before anything is fixed.
DNS, SSL, caching and protection, configured properly.
Licences, accounts, security settings and the day to day of running a tenant.
Straight advice on the systems your business runs on.
Plain definitions for the records and terms you get asked about.
Edits, updates, backups and monitoring so the site keeps working.
Warnings, hacks and certificate errors, and what each one means.
If your web person disappeared tomorrow, could you still get into your domain, your email and your website? If the honest answer is no, that is what this fixes.