As a therapist, I understand how dependency forms in human relationships. What I didn’t expect was to experience a version of that dependency in the technical architecture of my own business.

Modern web services often promise autonomy. The language is confident and reassuring: “You have full control over your website.” But autonomy is frequently a slogan rather than a structure. What looks like empowerment on the surface can conceal a deeper system designed to keep the user dependent on the person who built it.

Many professionals never see the layers beneath the visible interface. DNS, indexing, analytics, verification tokens, and ownership records operate in the background. When a vendor controls those layers, the client’s “control” becomes symbolic rather than actual. The client sees the front-end; the vendor holds the infrastructure. Dependency is created not through force, but through opacity.

The illusion of autonomy is easy to maintain. The interface looks simple. The vendor’s language sounds reassuring. The client believes they are in charge because they can edit text or change colors. Meanwhile, the deeper layers, the ones that determine ownership, visibility, indexing, and access, are controlled elsewhere. The client is given the appearance of control while the architecture contradicts it.

At first, I thought autonomy meant being able to operate the thing I had paid someone else to build. I could see the website. I could make changes to it. I assumed that meant it was mine.

The moment of realization often arrives only when something breaks or when a client attempts to leave. Rebuilding a website reveals what was never theirs to begin with. Verification tokens appear that the client never placed. Analytics point to accounts they don’t own. Indexing systems are inaccessible. The promise of “full control” dissolves when the underlying structure is finally visible.

For me, the realization came gradually. Getting the website out of a server I had never wanted it on in the first place was only the beginning. Once I started looking more closely, I discovered other pieces that needed to be extracted, changed, verified, or reclaimed.

I discovered that my professional account had been placed within someone else’s Google Workspace. I encountered email settings and records I had never needed to understand. Even after moving the website and taking control of its visible infrastructure, I learned there was still another layer of verification required to establish that the website was truly mine in Google’s system.

I kept thinking I was finishing the process. In reality, I was learning what the process was.

The cost of disentanglement is granular and tedious. Reclaiming ownership requires technical literacy the client was never expected to have. Undoing the architecture is slow, meticulous, and largely invisible to outsiders. The emotional experience is not anger so much as fatigue; the kind that comes from discovering how much you didn’t know you didn’t know. It is the destabilizing disorientation of realizing that true autonomy was never part of the original design.

There is another kind of autonomy that emerges during this process, though. It is the autonomy that comes from learning enough to understand what you are looking at.

I still do not know what every technical term means, and I certainly don’t remember every acronym I’ve encountered. But I know considerably more about what lies beneath my website than I did before. I know enough to investigate. I know enough to ask better questions. I know enough to recognize when something needs attention. And I am significantly less afraid to get under the hood and tinker.

This dynamic extends beyond one vendor or industry. Many systems create dependency through complexity. Therapists, in particular, are vulnerable because their expertise lies elsewhere. When a system is difficult to see into, trust becomes risky when it is paired with an absence of understanding or access. The problem is not a single person; it is a model that thrives on asymmetry between what the client sees and knows and what the vendor controls.

That asymmetry is easy to miss when you are an expert in something else. My expertise is in people, relationships, and the complicated ways human beings make sense of their lives. I had no reason to know what existed underneath a website until I needed to know.

I suspect many professionals remain in arrangements they would prefer to leave simply because they cannot see how to disentangle themselves. Others leave frustrated, disappointed, and poorer, having paid for years of dependence they never understood they were purchasing.

Rebuilding from scratch becomes more than a technical project. It becomes a reclamation of autonomy. Control is not a slogan; it is access to the underlying structure. The real empowerment comes not from the interface, but from understanding the architecture beneath it. The process was tedious, and sometimes painful, but it restored something more valuable than a website: a sense of ownership that is informed rather than assumed.

My website is still evolving. There are things I would like to finesse. There are things that could be more beautifully finished. The spacing is not perfect. I realize all of this.

But websites, like so many things we care about, are never really finished. They need tending. Something needs attention. Something gets neglected for a while and needs to be returned to. There are always small things to notice, adjust, repair, or reconsider.

I now know how to do a good deal of that.

I know where things live. I know enough to investigate when something seems wrong. I know enough to ask better questions. I know enough to get under the hood and begin figuring things out.

And I am proud of it.

I poured my blood, sweat, and a few tears into this project. I learned things I never expected to learn. I became considerably less afraid of the machinery beneath the surface.

More than that, I came to understand something about myself. I had assumed that because I was not technically knowledgeable, I needed someone else to understand these things for me. Perhaps I did, at first. But needing help with something and surrendering your understanding of it are two different things.

I thought I was rebuilding a website. I didn’t realize I was also learning to trust myself with something I had assumed belonged in someone else’s hands.