I Wrote HR a Two-Page Letter About My 401(k) and Crypto — Page Two Did the Work

At 12:31 on a Wednesday, I hit send on the longest email I have ever written to a human resources department, and then I closed my laptop and ate a sad sandwich, certain nothing would come of it. The email was two pages about my 401(k), my outside crypto holdings, and a gap between them that had been bothering me for over a year. The reply arrived in nine days. It was four sentences long. And it was almost entirely about page two.

The stakes, to be clear, were mine alone. No one at the company cared what I did with my money. But I was 54, with a retirement account at my employer and a separate crypto position that had grown past $70,000, and I had reached the age where every financial decision gets judged by how it will look on a form I have not filled out yet.

the question that started it

The question was simple and I had asked it badly for months, in hallways and on webinars: can I direct any part of my employer retirement plan into Bitcoin exposure, and how do my outside holdings interact with the plan's rules? The plan menu had twenty-nine options — target-date funds, an index fund shelf, a stable value fund — and nothing else. Every hallway answer was some variation of "the menu is the menu." Fine. But my actual questions were about the boundary, and boundaries are exactly what hallways cannot answer.

page one: the argument nobody read

Page one of my letter made the case. I clarified why I believed a modest allocation to crypto exposure belonged in a diversified retirement portfolio at my age — one to two percent, rebalanced, no leverage. I cited the ETF approvals, the growing institutional adoption, the whole speech. I wrote it well. Im a decent writer. It did not matter, cuz page one was asking HR to agree with an investment opinion, and no HR department on earth will do that. Investment opinions belong to the plan committee and its advisors, and the fastest way to get a polite non-answer is to hand someone an opinion and ask if it is allowed.

page two: three questions with answers

Page two asked three things that had factual answers. First: does the plan's document prohibit holding crypto assets outside the plan, or is my brokerage account entirely my own business? Second: does the payroll system or plan provider report my outside holdings to anyone at the company, ever? Third: if the plan ever added a crypto-linked option, what is the actual governance path — who decides, and what would trigger the review? Those are policy questions. Policy questions have policy answers, and the benefits manager whose job it is to answer em had apparently been waiting for someone to ask them in writing.

the reply, four sentences

The answer to one: outside holdings are mine, full stop, with the usual conflict-of-interest caveat if I ever traded anything material to company business, which I do not. The answer to two: no reporting, no visibility, none of their concern. The answer to three was the surprise — she copied the plan committee's charter, showed me the annual review window every October, and noted that employee requests do get logged and weighed when several arrive. Three colleagues had already asked about a crypto-linked option that year. Nobody had known that, cuz nobody had asked in a way that created a record.

what I did with the answers

The permission structure changed my behavior immediately. I stopped treating my outside crypto position as a guilty secret living next to my responsible retirement account and began treating them as one balance sheet, which is what the IRS already weighed them. I ran the numbers with an investment advisor my wife trusted — one flat-fee session, worth every dollar — and we set a rule that felt almost boring: the crypto position gets trimmed toward a fixed ceiling each year, with the proceeds feeding the 401(k) contributions I was already maxing. The portfolio stopped being two animals in separate cages and became one animal on a leash, which is the correct way for a 54-year-old to hold anything.

the October window

Last October, during the review window, I submitted a one-paragraph note through the plan's official channel repeating my request for a Bitcoin ETF option on the menu, referencing the earlier letter. I do not know if it will pass. The committee is slow and conservative and the stable value fund people have real influence. But I now understand something that took me two pages of writing to learn: the difference between complaining about a system and working it is typically a document with a specific question in it.

the advice I give now

A neighbor, Tom, hit the same wall with his own plan this spring and wanted to march into a meeting. I told him what I absorbed the expensive, sandwich-flavored way: skip page one entirely. Nobody in HR can agree with your investment thesis, and asking them to is how you get ignored. Write the shortest possible letter with the largest possible number of answerable questions. Where is the line, who sees what, what is the process, who decides, when. Every one of those creates a record, and records are the only currency HR actually trades in.

back to the sandwich

The reply email sat in my inbox with four sentences, and I printed it, cuz Im the kinda man who prints things now. Page one of my letter — the passionate part, the part with the conviction — went unread into a compliance file. Page two, the part with three questions, got a benefits manager to hand me the map of the machine. Two pages, nine days, one sad sandwich: that is the full cost of turning a hallway complaint into a standing permission structure. If your plan's menu frustrates you, do not pitch. Ask. The map was there the whole time, waiting for someone to request it in writing.