Dana Dunford Built for the 2 A.M. Phone Call

The first useful thing to know about Dana Dunford is that she did not spend childhood rehearsing to become a property-technology founder. At 18, while working full time and going to school, neither entrepreneurship nor property management was on her list. Technology was. She was fascinated by what it could connect. The rest of the career arrived as a sequence of questions, each one a little closer to home.

Her early professional years were built around numbers. Dunford worked in finance at Symantec, then joined Apple's worldwide financial planning and analysis organization. At Apple she worked with new product introductions, examining what might drive revenue, how a new device could affect an existing one, and whether an idea's impact justified the cost of building it. The work taught her a habit that still appears in how she talks about products: do the analysis before momentum turns an idea into an obligation.

Then came Nest, the connected-home company later acquired by Google, where Dunford moved into business development. The progression looks tidy from a distance - finance, hardware, homes, real estate - but Dunford describes it as following what interested her. The useful pieces accumulated before she knew what they were for.

The spreadsheet behind the front door

Real estate supplied the problem. Around the 2008 market crash, Dunford's older sister and brother-in-law were buying rental properties in Denver and invited her to participate. The promise sounded familiar: a tenant would pay the mortgage, an owner would build equity, and the machine would mostly run. The lived version included property managers who did not fit the family's needs, a difficult eviction, remote coordination, and work that kept returning to the owner.

The available choices felt too blunt. An owner could self-manage, assembling listings, screening, rent collection, repairs, and local help. Or the owner could hand over the keys to a traditional manager. Dunford saw room for a third option: keep the owner informed and in control while software and people take specific work off the owner's plate.

That distinction matters. Dunford later warned that building only for yourself can turn one person's irritation into a feature nobody else values. She had been intensely focused on improving background and credit checks. Existing integrations already handled most of what the broader market needed. Her edge case was real, but it was still an edge case.

A professor writes the first check

Dunford stepped away from the day-to-day rhythm of work to attend Harvard Business School. In a design and innovation class, she wrote a paper dissecting property management: why managers charged a percentage of monthly rent, why screening worked as it did, where the process broke, and how a better system might be assembled. The professor gave the work the top grade. More consequentially, he told her to build it.

He had watched her work on the idea in the innovation lab, including Fridays and Saturdays. As Dunford considered offers to return to Apple or Nest, the professor supplied the first angel check, which she has described as $30,000. A classroom argument had acquired both an instruction and a budget.

Co-founder Frank Liu supplied the complement Dunford needed. He was a full-stack engineer and rental owner with properties in Florida, Georgia, and San Francisco. A mutual friend, Thomas Hopkins, introduced them after the group had already explored rental screening projects together. Dunford brought the operator's pain points and a finance-trained eye for consequences. Liu brought engineering, product, and a willingness to tell her that technology could do things she believed would be impractical.

The failure before the platform

The path was not a straight line from paper to working product. One early idea, Portico, imagined a LinkedIn for tenants. Renters could publish qualifications and timing, then receive invitations to relevant apartments instead of searching across listing sites. Dunford and Liu were passionate about it. They also started building too early.

Portico failed. Dunford's diagnosis was specific: they had transferred a pattern from employment into housing, related it too closely to their own preferences, and skipped the customer questions that would have exposed weak demand. The episode gave her a durable separation between strategy and labor. A team can work extremely hard on an idea whose premise remains wrong.

Hemlane emerged with a broader scope: advertising, tenant placement, screening, leases, rent collection, communication, repairs, inspections, and local support. The company connected a cloud platform to a tech-enabled operations team and a network of licensed professionals. By January 2022, it said it operated 14,000 rentals in all 50 states and processed nearly $200 million in annualized payments. That month it announced a $9 million Series A co-led by Asymmetric Capital Partners and Prudence, with Aglaé Ventures and State Farm Ventures participating.

The cost of building the whole thing

There was a strategic catch. Hemlane built a platform when conventional startup advice favored a narrow entry point. A landlord needed the pieces to work together, Dunford reasoned, so the team tried to deliver the whole flow. Years later, she can see the cost. Starting with one complete but smaller service might have made early revenue and growth arrive sooner. The integrated system became an advantage only after the slower first miles.

Her advice to founders reflects the tension: begin with one pain point, build for it, then layer on the rest. It is advice earned partly by doing something more difficult. Dunford does not rewrite the decision as perfect. She examines the counterfactual, keeps the benefit, and names the cost.

The same candor appears in how she talks about management. Hemlane's internal vocabulary includes “glass walls, open doors” and “be your own CEO.” Dunford has described sharing the company's profit-and-loss statement and cash balance with the team. The argument is operational: people cannot help solve the largest problems if the problems remain hidden. Ideas can come from anywhere, but an idea needs an owner and an account of its likely impact.

Local judgment, automated routine

Dunford's current product view returns to the apparent contradiction at Hemlane's center. Real estate is local. The owner may live across the country, the software may be in the cloud, and the payment may move automatically, but the leaking pipe is still in one kitchen. Someone nearby must understand the place, the tenant, the contractor, and the rules.

That is why she frames localization and AI as partners rather than substitutes. AI can remove routine analytical work from the daily queue. People can spend more time on communication, context, and judgment. Her warning is characteristically grounded in product discipline: companies often begin with AI as a solution before identifying a problem. The technology earns its place by clearing the path to better service, not by appearing in the pitch.

There is a personal consistency to all of this. Dunford says she loves work. In third grade, when her teacher did not assign enough homework, she copied entries from encyclopedias and wrote her own quizzes. She remains alert to the downside of that drive. She has spoken openly about comparing Hemlane with other companies and learning to redirect that energy toward its own path. The useful counterweight to intensity is not less care. It is a clearer target.

Hemlane's target is the ordinary coordination most people notice only when it breaks: a lease signed, a payment recorded, a repair answered, a local professional arriving when promised. Dunford's story begins with large technology companies and a business-school classroom. Its most revealing scene is smaller: an owner in one city, a tenant in another, and a phone that does not have to ring beside the bed.