On April 1, 2026, Blossom at Park became the first HOA community to transition directly from a developer into nexova ai management. That sentence is short, but the milestone behind it isn't: it's our first direct-from-developer transition, our first collaboration with a Bay Area residential developer, and the first live proof point for an offering we've been quietly building for months — a management partnership designed specifically for the handoff from builder to homeowner association.
Blossom at Park is a three-townhome boutique community at 1945 Park Avenue, San Jose, developed by AlphaX RE Capital through its vertically integrated builder arm, AL Homes. The homes are modern American craftsman — 1,532 to 1,555 square feet, high-end finishes — the kind of small infill project that's reshaping Silicon Valley's residential landscape as California pushes denser housing onto lots that legacy developers wouldn't touch. Three units is small. The playbook we're running is not.
This post is two things at once. First, it's an announcement: we're proud to be working with AlphaX RE Capital, and we want Kathy Wu and Ruby Huo — the two people on AlphaX's side who ran the diligence on this decision — to know that. Second, it's the first public version of a playbook we think matters more than any case study we've written before: what a clean builder-to-HOA turnover actually requires.
If you're a developer, this is the one you should read.
Why AlphaX RE Capital picked us
AlphaX found us online. That's how most of our best partnerships have started — a developer, an operations lead, or a board member running a search, comparing what's out there, reading our llms.txt if they know enough to look for it. The AlphaX team did the work before they ever contacted us: they evaluated several management companies, tested the technology, and talked to community managers to see who actually understood builder handoffs.
When Kathy and Ruby decided on nexova ai, two things tipped the decision:
-
The technology was real. Most management companies demo a licensed third-party portal — AppFolio, Caliber, Buildium — and call it a "platform." We showed them a platform we built ourselves: 300+ API endpoints, an AI assistant that answers questions against the community's own CC&Rs with inline citations, and a real-time financial dashboard that updates on bank activity, not on a monthly PDF cycle. A sophisticated developer notices the difference in the first ten minutes.
-
Our community manager knew the work. Technology alone doesn't win developer conversations. AlphaX's team probed the operational side hard: SB 800 warranty tracking, governing-document indexing, first board seating, reserve study timing, the correct sequence for opening bank accounts in the association's name. Our CACM-certified community manager walked through each of those without a script. Experience is hard to fake — especially in front of a buyer evaluating other managers the same week.
We didn't win on price. We won on whether a sophisticated developer team believed we could run their community without making them babysit us.
That's the right kind of win.
Why a new townhome HOA is different from an HOA switch
Most of the case studies we've published are about existing HOAs that switched from another management company to us. Those transitions have their own mechanics: terminating a contract under California Civil Code §4820, transferring records, renegotiating vendor relationships, explaining the switch to homeowners. We've written the complete playbook for that transition elsewhere on the blog, and the steps are well understood.
A developer handoff is different in ways that matter:
- There is no "previous management company" to transition from. The developer has been running the community informally through construction and sales. The HOA is being activated formally for the first time.
- The governing documents are fresh and often unread. CC&Rs were drafted months or years earlier during entitlement, recorded at the first unit's close of escrow, and nobody has actually lived under them yet. Assumptions are baked in that the first board will discover the hard way.
- There is no operating history. Budgets are projected from construction-era comparables. Reserve funding starts at the developer's seed contribution. Assessment collection has no track record. Every operational data point begins at zero on day one.
- SB 800 is live. California's Right to Repair Act (Civil Code §895 et seq.) gives homeowners a structured process for construction-defect claims, with overlapping 1-, 2-, 4-, and 10-year warranty windows measured from close of escrow. Miss a notice period and the association loses the claim. The clock starts the day the first homeowner gets the keys.
- The first board is seated fresh. Under the Declaration and California Civil Code §5100, declarant control transitions to homeowner-elected directors on a schedule defined in the governing documents. At Blossom at Park, the transition was clean and immediate: the first board was seated on April 1, the same day we took over operations.
None of those things exist in an HOA-to-HOA switch. All of them exist in a developer handoff. And every one of them is a place where an inexperienced management company can create problems that will haunt the community for years.
What a clean developer handoff actually requires
Here's the checklist we ran for Blossom at Park. It's the same checklist we'll run for every developer partnership after this one, because the sequence is more important than the scale.
Governing documents: recorded, indexed, understood
The developer's counsel drafted the Declaration of CC&Rs, Bylaws, and Articles of Incorporation before construction began. On day one, we verified that each document was recorded with the Santa Clara County Recorder, pulled the recorded copies, and indexed them into our AI assistant. That indexing isn't decorative: the first homeowner question about architectural modifications, pet rules, or parking is going to be answered by the AI assistant referencing the community's actual CC&Rs with page citations. If the documents aren't indexed, the manager is answering from memory, and the manager is going to be wrong eventually.
Initial reserve funding and the first reserve study
California Civil Code §5550 requires a reserve study every three years, with an on-site visual inspection at least every three years. For a newly formed HOA, the first study is typically funded out of the developer's initial reserve contribution — a capital seed that becomes the association's reserve account. We set up the segregated reserve account on day one, documented the initial contribution, and scheduled the Level I reserve study for the first ninety days of operation. A developer-era reserve projection is an estimate. A post-construction reserve study is a verified baseline. The sequencing matters.
SB 800 warranty tracking, from close of escrow
The warranty clock under SB 800 started on the day of the first unit's close of escrow. At Blossom at Park, we documented the close date, tagged each unit's SB 800 notice windows in the platform, and set calendar reminders at the 1-year, 2-year, 4-year, and 10-year thresholds. The AI assistant will surface any homeowner question that looks like a construction-defect issue — water intrusion, roof problems, stucco cracking, plumbing leaks — and route it into the SB 800 documentation workflow automatically. Boards don't miss warranty claims because they don't care. They miss them because nobody was tracking the calendar.
Bank accounts in the association's name, not the management company's
This is basic and it's the single most common place we see bad management companies set up a new HOA wrong. The operating account and the reserve account must both be opened in the legal name of the association — not the management company, not the developer, not a pooled account. We opened both accounts on day one, in Blossom at Park's name, using the association's EIN, and gave the board view access from the first login. If any management company ever asks to open an HOA bank account in their own name, the answer is no.
Vendor relationships: inherited, audited, and priced
A new community inherits whatever vendor relationships the developer signed during construction. Landscaping, trash service, utility accounts — some of those contracts transfer to the HOA, some don't, and some transfer under pricing that was a favor to the builder and isn't going to be a favor to the homeowners. We audited every inherited contract, confirmed pricing, and flagged anything that wasn't market-rate for a competitive rebid within the first ninety days. Vendors who were priced right stay. Vendors who weren't get put on a competitive process.
First board seating and the transition of control
At Blossom at Park, AlphaX transitioned board control to the homeowner-elected directors on April 1, the same day we took over operations. That's a clean handoff — the developer didn't retain declarant control past the transition date, which simplifies everything downstream. We supported the first board meeting the same day: charter established, officer positions elected, initial resolutions documented, AI assistant onboarded to every director's login.
The master insurance policy
The HOA's master policy — typically a package of general liability, property coverage on common elements, and D&O coverage for the board — needs to be in place the moment the association becomes responsible for the common area. Developer-era coverage through the builder's CGL policy doesn't carry over. We confirmed the master policy was bound and active as of April 1, with all three units named and the board listed as insureds on the D&O rider.
Financial platform, live on day one
By the end of April 1, Blossom at Park's homeowners had logins to the community portal, access to the real-time financial dashboard, the AI assistant ready for questions, and a welcome communication explaining every link on their new account. "Day one" wasn't "sign the contract and wait a month for onboarding." Day one was operational.
The first ninety days
From here, the work is mostly rhythm. We're running the first reserve study, auditing inherited vendor contracts, supporting the first board in establishing its standing resolutions, and handling the ordinary flow of homeowner questions through the AI assistant. The SB 800 calendar is tracking the first notice windows. The operating budget is being reconciled against actual spend in real time. The first monthly financial packet lands in board members' inboxes at the end of the first full month — assembled by the platform automatically, not by a human staring at a spreadsheet.
For a three-unit community, the operational surface area is small. That's fine. It's the same surface area, shaped the same way, as the thirty-unit community and the three-hundred-unit community after it. Blossom at Park is the size at which we prove the sequence. The sequence is what scales.
We onboarded Blossom at Park onto our Full Service tier, which is the same tier we recommend for most new builder communities — one consolidated relationship covering financial operations, compliance, vendor management, homeowner support, and the full AI platform.
Working with AlphaX RE Capital
A note on the partner side of this story.
AlphaX RE Capital was founded in 2019 and is one of the few women-founded residential developers operating at meaningful scale in the Bay Area. Between the investment platform and the AL Homes builder arm, they've put more than 820 projects into operation, with over $400 million in assets under management and a clear focus on using new California housing legislation — SB 9, SB 35, and related reforms — to build more housing on infill lots that legacy developers wouldn't touch. The Blossom at Park project, a three-townhome infill at 1945 Park Avenue, is exactly that kind of project: a small parcel turned into three new homes in a neighborhood that needed the density.
Kathy Wu and Ruby Huo ran the diligence on this partnership from AlphaX's side, and the standard they set for developer-side evaluation is the standard more builders should set. If you're a developer or a management company operating in the Bay Area, both of them are worth connecting with on LinkedIn: Kathy Wu and Ruby Huo. We're glad they chose us, and we're glad they made us earn it.
For nexova ai, Blossom at Park is a beachhead. It's the first direct-from-developer transition, the first AlphaX RE Capital project, and the first proof point that the developer-services playbook we've been building for months works under live conditions. It won't be the last. We're building this specifically so the next developer running the same evaluation has an easier time saying yes.
For builders reading this
If you're a Bay Area residential developer — new construction, infill, small project or large — and you're tired of handing your communities off to management companies whose technology stopped improving in 2012, we built this for you.
Our developer-services offering is designed around the moments that actually matter in a builder's handoff: clean CC&R indexing, SB 800 tracking from day one, reserve study sequencing, vendor contract audits, master insurance verification, first board seating support, and a technology platform your homeowners will actually want to use. The community manager knows the work. The engineering team behind her ships software at the speed a builder recognizes — weeks, not quarters.
If that sounds like the partner you want for your next project, read more about our developer services — or request a quote and mention Blossom at Park.
We're ready for the next one.