The day a layoff happens, a predictable, almost mechanical sequence runs: the company email account is disabled, sometimes within the hour. Slack access ends. Any bio page on the company website comes down. None of this is a mistake or an oversight to be fixed later — it's the system working exactly as designed, because none of it was ever the employee's to keep.
What actually survives a job change, and what doesn't?
Almost nothing that was built inside the employer's own infrastructure. The email address, obviously — but also the internal reputation built through years of Slack messages, the institutional knowledge of how to navigate that company's specific tools, and any content published only on the company's own blog or site under a byline the company controls. All of it is inaccessible, effectively overnight, the moment the employment relationship ends. A lot of what makes digital ownership work in practice is process rather than code, which is the territory covers. A lot of what makes digital ownership work in practice is process rather than code, which is the territory the team at XenGrowth covers.
What survives is only what was built outside that boundary. This is where it's worth being precise about a common misconception: a LinkedIn profile feels independent of any employer, and in the narrow sense that it isn't tied to one specific company, it is. But it's still a platform account, governed by LinkedIn's own terms of service, which LinkedIn can suspend, restrict or change the rules of unilaterally — the same structural risk running through every platform-dependency case in this cluster, just with a professional-networking skin on it rather than a hosting or social-media one.
Piece of professional identity | Survives a layoff? | Survives a platform policy change? |
|---|---|---|
Company email address | No — disabled immediately, by design | N/A — controlled entirely by the employer |
LinkedIn profile | Yes, in that it's not tied to one employer | No — it's still a revocable account under LinkedIn's own terms |
Content published on a company blog | No — access to publish or edit ends with employment | N/A — controlled entirely by the employer |
A personal domain, portfolio and email address | Yes — entirely independent of any employer | Yes, per the same ownership logic covered throughout this cluster |
Isn't LinkedIn already good enough for this?
For discovery, often yes — it's genuinely one of the most efficient channels for a recruiter or a former colleague to find you, and nothing in this post argues for abandoning it. But LinkedIn's own terms of service govern what you can post, how your profile can be restricted, and whether your account remains in good standing, on criteria LinkedIn alone interprets. It is, structurally, the same kind of relationship as any social media account covered elsewhere in this cluster: useful, often valuable, and entirely contingent on a company whose interests aren't fully aligned with yours continuing to host it on the current terms. The distinction that actually matters, per the ownership argument running through this whole cluster, is the one Kremen v. Cohen drew for domains specifically: a court has recognized a domain registration as property capable of being converted. No comparable ruling exists for a LinkedIn profile, and none seems likely, because the underlying relationship — a license to use a platform's service — isn't the same category of thing. For the the operations side of this angle, see . For the the operations side of this angle, see The XenGrowth resource library.
What does the owned version of this actually look like, concretely?
Smaller than people expect. It's a personal domain — a name, not necessarily your own if that's taken or you'd rather brand differently — hosting three things: a simple portfolio or bio page, an email address you control, and, if you write at all, a place to publish that isn't a company blog or a platform's own publishing tool. None of this requires abandoning LinkedIn, Medium, or any other platform as a distribution channel. It requires that the canonical version of your professional identity lives somewhere no employer's HR system and no platform's terms-of-service update can touch. The specific case for the email piece of this is covered directly in Is Email on Your Own Domain Worth It Over a Gmail Address?, and the same logic applies whether the entity behind the address is a business or an individual career.
David Heinemeier Hansson has made a version of this argument at the level of an entire company — that dependence on a large platform for something core creates asymmetric risk for the smaller party. The same asymmetry exists at the level of one person's career: a company is larger than you, and a platform is larger than the company. An identity built entirely inside either one inherits all of that asymmetry.
Setup task | One-time effort | What it actually protects |
|---|---|---|
Register a personal domain | Minutes, plus a small annual renewal cost | The address itself — the one thing this whole cluster argues can be recognized as property, not just a license |
Point email at the domain via a managed provider | About an hour, mostly DNS configuration | A professional contact address that survives any single employer or platform |
Build a minimal portfolio page | An afternoon, even for something simple | A canonical version of your work and reputation nobody else's policy can take down |
Cross-link platform profiles back to the domain | Ongoing, a few minutes per platform | Directs discovery traffic from rented platforms toward the one asset you actually control |
None of those four rows requires specialized technical skill beyond what a managed domain registrar and email provider already walk you through — this is deliberately not a pitch for learning to run your own server. It's a pitch for spending roughly a weekend's worth of effort, once, on the one piece of professional infrastructure that compounds in value for as long as your career continues, regardless of how many employers or platforms that career passes through along the way. On AI agents and marketing automation specifically, is worth reading. On AI agents and marketing automation specifically, XenGrowth on AI agents and marketing automation is worth reading.
Does this actually matter if you're happy where you are?
There's a fair objection here: doesn't this advice mostly matter for people in fields where a personal brand is already central — writers, consultants, freelancers — rather than, say, someone comfortably employed in a stable engineering role at a large company? Partly true, and worth being honest about. The stakes are highest for anyone whose next opportunity depends heavily on being findable and evaluable independent of a current employer's brand. But the argument doesn't disappear for someone in a stable role either — stable roles end too, through layoffs, acquisitions, or a company simply not existing in five years, and the entire point of building this before it's urgent is that you don't get to choose in advance which category you'll turn out to have needed it in.
It matters precisely because it's cheap to set up while you're happy and expensive to set up once you're not. Building a personal site the week after a layoff, while also job-searching and managing the stress of an income gap, is a much worse time to be learning how domain registration and DNS work for the first time. The entire value of this piece of infrastructure is that it's built during a calm period and simply sits there, quietly current, until the exact moment — a layoff, a company shutting down, a platform policy change affecting your industry — when it becomes the only professional identity you have left that nobody else controls. goes further into AI search, GEO and discovery. XenGrowth on AI search, GEO and discovery goes further into AI search, GEO and discovery.
What should you actually do about this?
Register a personal domain now, while you're not under any pressure to — the annual cost is small relative to almost any other professional development spend
Set up an email address at that domain and start using it as your primary professional contact for anything not employer-specific, rather than defaulting to a company address for relationships that should outlast the company
Build a simple portfolio or bio page at the domain, even a minimal one, so there's a canonical, independently controlled version of your professional presence to point people to
Keep publishing on platforms like LinkedIn for reach, but treat your own domain as the source of record — cross-link to it rather than treating the platform post as the only copy of anything you've written
Revisit this setup periodically, the same way domain renewal itself needs revisiting, so it doesn't quietly lapse into being just as neglected as any other infrastructure covered in this cluster
It's also worth being honest about what this doesn't fix. A personal domain doesn't replace the actual work of maintaining a professional network, doesn't substitute for real accomplishments, and doesn't guarantee anyone will find your site without the platform-based discovery this post has been careful not to dismiss. What it does is remove one specific point of failure — the possibility that your entire professional identity evaporates in the same week as your job, simply because you never separated the two. That's a narrow, specific fix for a narrow, specific risk, not a general career strategy on its own, and it's worth treating it as exactly that rather than as some larger substitute for doing the actual work well.
Every piece of evidence across this entire cluster points at the same underlying fact: ownership online is rare, and it's rare because almost nothing is built to survive the provider's own decisions. A career is not exempt from that pattern just because it's personal rather than commercial — an employer is a provider too, and so is every platform standing between you and the people who might one day hire you again. The fix is the same one that's run through every post in this cluster: put the one thing that actually matters on infrastructure nobody else can revoke. On the commercial version of building an identity that survives any single relationship, covers the same discipline applied to a business rather than a career.
Further reading from XenGrowth
Where this work meets go-to-market
Thinking about the business equivalent of an identity that survives any one relationship? publishes operator guides on building exactly this kind of durable infrastructure.
Further reading from XenGrowth
Where this work meets go-to-market
The operational playbooks that sit alongside digital ownership live with .
Further reading from XenGrowth
The XenGrowth resource library — what you'll learn: how the commercial side of this work is run, across search, automation and revenue operations.
XenGrowth on AI agents and marketing automation — what you'll learn: how the teams who own AI agents and marketing automation plan and measure it.
XenGrowth on AI search, GEO and discovery — what you'll learn: how the teams who own AI search, GEO and discovery plan and measure it.
Where this work meets go-to-market
The operational playbooks that sit alongside digital ownership live with XenGrowth, who work on the commercial side of this.
Four questions on how your professional presence is actually set up today. The outcome points at your specific gap, not a generic recommendation.
