I did not start with HomeVest.
I started with a simpler, more obvious idea: build affordable housing. Buy land, develop it, price it below market, and put first-time buyers into homes they could actually afford. I put together a proposal. I found investors. I made the case.
They turned me down.
I don't say that to frame this as a comeback story. I say it because that rejection is where HomeVest actually starts. Sitting with a turned-down proposal, I had to ask myself a different question. If I cannot address what houses cost, can I address what buyers can save?
That is how you end up building an employer benefit when you set out to build a neighborhood.
The median age of a first-time homebuyer in the United States is 38. That is the highest it has ever been, according to the National Association of Realtors. Thirty-eight. By the time the average American buys their first home, they may have been renting for fifteen or twenty years. They have watched prices move further away from them every single year. They have read the think pieces and the policy proposals and the op-eds about what Washington should do about it.
None of that moves the number.
What moved me was a simpler observation. The reason most first-time buyers cannot buy is not that they earn too little to afford a mortgage payment. It is that they cannot accumulate the lump sum required to get through the front door. The down payment. The closing costs. The cash that has to exist before any of the other math matters.
And the reason they cannot accumulate it is not entirely about income. It is about how saving works, or more accurately, how it fails.
"The 401k does not work because Americans are disciplined. It works because the decision is made once and then removed from their hands."
Most people are not disciplined enough to move money into a separate account every month and leave it there for years. Not because they are irresponsible. Because that is not how human psychology works with money that is sitting in an account they can see and access. The 401k does not work because Americans are disciplined. It works because the decision is made once and then removed from their hands. The money leaves the paycheck before it ever arrives. You cannot spend what you never see.
I did not understand why nobody had applied that same design logic to a down payment.
HomeVest is an employer-matched down payment savings benefit. It functions almost exactly like a 401k. An employee sets a monthly contribution. The amount comes out of their paycheck automatically. The employer matches a portion of it. And the match vests over four years, 25% per year, which means employees who leave early forfeit the unvested employer contribution.
The retention mechanic was not an afterthought. It was half the product. The reason employers pay for benefits is not pure generosity. It is because benefits reduce turnover, and turnover is expensive. A down payment benefit with a vesting schedule gives the employer something a gym stipend or a free lunch never does: a financial reason for their best people to stay until they can buy a house.
Fewer than 1% of employers currently offer anything like this. That is not a sign the idea is wrong. It is a sign the category does not exist yet.
I believed I could build it.
I built a landing page. I wrote the pitch. I started reaching out to employers in industries with the highest turnover: healthcare, hospitality, small businesses. These are the companies that feel the cost of losing people most acutely, and feel it most often.
In September 2025, Employee Benefit News ran a piece on HomeVest. Employee Benefit News is not a general publication. It is read by the HR directors, benefits managers, and people operations leaders at exactly the organizations I was trying to reach. The article explained the product clearly. The response was real. People were interested.
At the same time, I started pursuing capital. We were trying to raise $2 million in venture funding to build the infrastructure the product actually required: the banking integrations, the compliance framework, the application, the team to run it. I met with several VC firms. I made the case for the market, the product, the timing.
The VCs passed.
What I expected to follow the press coverage and the fundraising conversations was momentum. Pilots. Traction. The early proof that the idea could become a business.
What actually followed was three walls, one after another.
The first wall: banks.
HomeVest requires a banking partner. The product moves employee money through payroll into a managed savings account. To do that at scale, you need API access to banking infrastructure, the technical connection that lets a platform like HomeVest communicate with the financial system in real time.
I started meeting with banks. Not casually. I went through three rounds of meetings with multiple institutions. I presented to boards of directors. I made the case to compliance teams and technology officers and executive leadership. I did this across eight banks, from community banks with $500 million in assets to regional institutions with $50 billion on their balance sheets.
Eight banks. Multiple rounds each. Boards of directors.
Every one of them said no.
The reasons varied in language but were consistent in substance. Banking infrastructure in the United States is heavily regulated. The rules around how money is held, moved, and managed on behalf of third parties are not flexible. A 24-year-old with a working landing page and a press mention is not the profile that makes a bank's compliance team comfortable approving API access for a product that touches employee payroll. It does not matter how clean the pitch is. The regulatory risk is real, and the banks know it even when you don't fully yet.
I learned more about banking regulation in those meetings than I had in my entire time working inside a bank.
The second wall: employers.
The employer conversation had a different texture. The interest was genuine. People understood the problem immediately. Nobody needed to be convinced that their employees wanted to own homes or that turnover was expensive. The idea landed.
But then came the question I was not fully prepared for.
"You're 24. You're asking us to route our employees' paychecks through your platform. Who holds the money?"
That is a fair question. It is, in fact, the right question. And at that stage of the company, I did not have a clean answer. I was telling employers the product would be more developed soon. That the app was coming. That the banking partnership was in progress. I was selling a future state while standing in a present state that did not yet exist.
Trust, in financial products, is not given to ideas. It is given to infrastructure. And I did not have the infrastructure yet.
The third wall: the App Store.
The employer conversations made clear that a professional, fully functional application was not optional. A landing page and a dashboard prototype were enough to get meetings. They were not enough to close pilots. People needed to see something real.
So I started building toward an app.
What I discovered is that Apple does not approve financial applications the way it approves a to-do list or a weather app. A product that moves money, manages savings accounts, and integrates with payroll systems sits in a category with specific, strict review requirements. You need banking partnerships in place. You need compliance documentation. You need the regulatory infrastructure to already exist before the app can exist.
Which meant the App Store was waiting on the bank. And the bank was waiting on the compliance framework. And the employers were waiting on the app.
Everything was waiting on everything else.
There is a version of this essay that frames what happened as failure. I do not think that is the right frame.
What I ran into is a structural reality about building in fintech that is genuinely not obvious until you are inside it. The idea being good is necessary but not sufficient. Financial products require regulatory relationships, banking partnerships, and compliance infrastructure that have to be built before the product can exist, not after it gets traction. The sequence that works for a software product does not work for a product that touches people's money.
Most startup content does not say this clearly. It talks about iteration and pivoting and finding product-market fit, which is useful advice for products that can exist without a banking license. HomeVest cannot. The path to building it runs through institutions that move slowly, by design, because the alternative is chaos in the financial system. That is not a bug. It is how it is supposed to work.
I also learned something about trust and age that I could not have learned any other way. I am not the first person to notice that being young makes institutional trust harder to earn. But there is a difference between knowing that abstractly and sitting across from a bank's board of directors at 24, watching them do the math on whether you are the right person to handle something that touches their customers' regulatory exposure. Age is not everything in those rooms. But it is something. And the answer is not to pretend otherwise. The answer is to build the track record that changes the conversation.
HomeVest is not dead. The site is still up. The idea is still right. The problem it addresses, the median age of a first-time homebuyer creeping higher every year while wages crawl in the other direction, has not gotten smaller.
And something has changed since those eight rejections.
One bank, which I will not name here, is working with us. Under significant supervision and with strict constraints, they are extending API access to begin building the integration HomeVest actually needs. It is not a green light. It is more like a very carefully monitored first step. But it is real. After three rounds of meetings across eight institutions and more than a year of closed doors, one door is open.
That matters more than I expected it to. Not because it makes success certain, but because it proves the earlier rejections were about timing and trust, not about the idea being wrong. The infrastructure problem is solvable. It just takes longer and requires more credibility than I had when I started.
What has also changed is my understanding of what it actually takes to build this. It requires a banking partner who has the regulatory appetite and the infrastructure flexibility to work with a startup. It requires enough capital to build the compliance framework before the revenue exists to pay for it. It requires, in some ways, being a different version of yourself than the one who started the meetings.
I started HomeVest trying to solve a problem I could not solve another way. The investors said no to affordable housing, so I worked backwards to the next lever I could pull. The VCs passed on the $2 million raise. The banks said no eight times before one said something closer to maybe.
Maybe that is still what this is. A problem I have not figured out how to solve yet, not a problem I have given up on.
The number is still 38. It is still going up.