Loading page…
A deeply vertical ERP for public and affordable housing agencies that reached nearly $10M in revenue before a strategic acquisition.
about $2M revenue after the first 5 years · acquired by Yardi Systems
A small market can still be a real business when every attainable deal matters and the software runs the customer's operation every day.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Raj Bhaskar started VisualHOMES in 2000 when he was 23, building vertical ERP software for public and affordable housing agencies. The product was not a lightweight reporting tool. It became the operating system for a public housing authority, combining roughly 25 to 30 integrated modules including accounting, payroll, public housing, Section 8 and related workflows. The company was bootstrapped and grew inside a narrow market of about 5,000 public housing authorities around the country. The numbers show a slow, durable climb. Raj says VisualHOMES reached about $2 million in revenue after its first five years and nearly $10 million after 10 years and two months. The company then sold to Yardi, a larger real-estate software business. Raj's brother Anu joined as head of R&D on August 1, 2009, and the company exited on July 31, 2010. The strategic logic was strong: VisualHOMES had built deep software for one housing niche, while Yardi served the wider real-estate market. Raj carried the lessons into Hurdler — service culture, serious operational software and the power of starting with a specific industry — while deciding that his next company should have a much larger eventual market.
VisualHOMES entered a market where trust mattered more than reach. Public housing agencies needed an operating system for accounting, payroll, Section 8 and daily administration, so the first customers were won by showing that the team understood the work behind the software.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Founder interview on Practical Founders. Raj Bhaskar reports VisualHOMES's revenue history and acquisition story, so the grade is Founder-Reported and not independently audited. The transcript states about $2 million in revenue after the first five years, nearly $10 million after 10 years and two months, a bootstrapped business, roughly 25 to 30 integrated modules, Anu joining on August 1, 2009, and the sale to Yardi after the July 31, 2010 exit date. It does not state customer count, margins, pricing, headcount, contract terms or sale price. All revenue figures are in U.S. dollars as stated. The interview is a later founder retrospective, so the figures describe the historical business and not current VisualHOMES operations.
For a housing-authority ERP like this, the first invoice is typically a paid pilot with one authority, priced against the cost of the paper process it replaces.
VisualHOMES's flywheel was reputation in a concentrated market. Once the company had a working deployment in a public housing agency, the next agency could evaluate a product built for its exact language and obligations rather than a generic ERP.
The early stretch lasted years, not weeks. Raj says the first five years were spent building reputation before VisualHOMES reached about $2 million in revenue.
VisualHOMES was an enterprise resource planning system for public and affordable housing agencies. Raj describes roughly 25 to 30 integrated modules, including full accounting, payroll, a Section 8 suite and a public-housing suite. In practical terms, the software served as the operating system of an agency: staff used it every day to run the organisation, not merely to produce an occasional report. It began as Windows software and later moved toward web software; the company operated before cloud SaaS was the default. Deployments included on-site implementation and training. That history explains why service became part of the company's identity. Our read: the best modern version of this idea would begin with one public-housing workflow that has a clear compliance burden, then expand only when the first customers repeatedly ask for adjacent modules. A founder should preserve the domain-specific vocabulary and operational reliability while using cloud delivery to reduce installation friction. The product becomes valuable when replacing it would mean retraining the agency, re-importing years of data and redesigning daily work.
VisualHOMES's disclosed revenue is about $2 million after five years and nearly $10 million after 10 years and two months. The transcript does not specify licence structure, annual recurring revenue, implementation fees or margins. The company was bootstrapped and later acquired by Yardi, so the value of the business was not limited to a subscription total; it included the product, customer relationships, domain knowledge and team. Our read: a vertical ERP should combine an initial implementation charge with recurring support, maintenance and module expansion. Public agencies may buy slowly, but a system that runs accounting, payroll and program administration can become deeply embedded. The commercial risk is that a founder prices the first deployment like a normal SaaS account while absorbing years of training and customisation. Separate configuration from product, document every recurring rule and make data migration a reusable capability. The acquisition path also matters: a narrow business can be strategically attractive to a larger platform if its customers sit adjacent to the buyer's market and the software is difficult to reproduce quickly.
The technical stack is not disclosed. The operating model is clearer: VisualHOMES started as Windows software, later converted the second half of the business to web software, and handled on-site implementations and training. Its cost base therefore included deep engineering, domain expertise, deployment work and customer service. Raj says his first company taught him that excellent human assistance is a differentiator, especially when software is a core system and a 20-minute outage is a real operational problem. Our read: the margin profile is likely shaped less by servers than by implementation and support capacity, but the transcript gives no margin number and none should be invented. A modern entrant should use a modular cloud architecture, a configuration layer for agency rules and strong audit trails. Build import tools before polishing every feature; the ability to move an agency from its existing system is a major part of the sale. Keep a small expert team close to deployments, then turn repeated implementation work into templates. This is a domain business where reliability and response time are operating metrics, not post-sale niceties.
Copy the niche selection. Public and affordable housing is narrow enough for a team to learn the rules deeply, yet large enough to support a multi-million-dollar software business. Copy the commitment to a system of record and the service culture: customers should feel that the vendor understands the consequences of downtime and bad data. Copy the patience too; the five-year reputation-building period is part of the model. Change the delivery model. VisualHOMES started before cloud software was normal and relied on on-site implementations. A new founder can use managed infrastructure, browser delivery, automated imports and remote training to reduce deployment friction. Start with a single module where the buyer can measure time saved or reporting accuracy, then expand into adjacent workflows only after the implementation is repeatable. Our read: do not copy the company by building a giant ERP first. Copy the wedge, the vocabulary and the service promise; let the integrated suite emerge from repeated customer demand.
The first risk is market concentration. A niche of public housing agencies can support meaningful revenue, but the number of buyers is finite and procurement cycles can be long. A founder may spend years building features for a market that cannot support the desired scale. The second risk is implementation drag. Deep ERP software can become a services company if every agency receives a different configuration and the product team never turns lessons into reusable modules. Public-sector requirements also change slowly, while security, reporting and compliance expectations remain high. Our read: the best defence is a sharp product boundary, strong migration tooling and a deliberate adjacent-market strategy. The Yardi acquisition shows one route to scale, but an exit is not a substitute for customer health. Validate that agencies renew support, adopt multiple modules and refer peers before expanding the addressable market. Treat the $10 million figure as a founder-reported historical outcome, not a promise that a new vertical ERP will reach the same result on the same timetable.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,403 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click