KP Reddy and the question that followed him to every job

The computer arrived before the career plan. KP Reddy was thirteen when his father, a civil engineer, handed him an IBM PC and asked him to work out what it could do for the firm. He began running engineering software under his father’s direction. An office full of adults had acquired a machine; the teenager received the instruction manual by implication. Figure it out.

It was a useful introduction to two trades. Engineering supplied problems with physical consequences. Computing supplied a way to approach them differently. Reddy later chose civil engineering at Georgia Tech because he already knew how to write code. Learning to design bridges required a different sort of education. His eventual career would keep both sets of skills in the same room.

Now based in San Francisco, he is the founder and CEO of Zero RFI and a general partner at Shadow Ventures. The roles put him on both sides of the startup conversation: evaluating other founders’ ideas while building an operating company of his own. The problem he has chosen is construction’s uneven distribution of knowledge, especially the position of the owner paying for the project.

A portable computer, an impatient engineer

Reddy grew up in Stone Mountain, Georgia. His mother was a computer programmer. In his recollection, her on-call work brought a Compaq portable home at weekends, carried on a small dolly. He experimented with programs, including blackjack. In 1985, he moved to India with his father, whose design-build office became another classroom. After school, Reddy made software work, wrote mail-merge programs, and learned surveying and rebar inspection.

At Georgia Tech, he worked in computer and geotechnical labs. One involved putting academic material online; the other involved sensors, data files, and analysis. Later, as a field engineer, he tried instrumenting job sites. Better information could make reporting more efficient. The awkward discovery was that an employer selling billable hours had reasons to hesitate about reducing them. He began developing fixed-fee contracts instead.

He graduated in 1994 with a degree in civil and environmental engineering. Asked what pushed him toward entrepreneurship, he gave a compact answer: “Being young and impatient.” At his first consulting job, partnership appeared fifteen years away. A business built on evenings and weekends offered a nearer horizon. The calendar, apparently, was an early competitor.

The internet needed a customer

His early web-based construction-management product struggled to find a receptive industry. The company pivoted into telecommunications and reached the public markets. That experience helps explain his later suspicion of a persuasive product story without a persuasive account of who will buy it. A working piece of software can still have a very long wait outside the customer’s door.

His subsequent ventures included Cereus Technology Partners, RCMS, and Ampirix. Cereus became a Nasdaq-listed business; RCMS was acquired by ARC; Ampirix went to The Combine. He also led enterprise transformation at Gehry Technologies, the company associated with architect Frank Gehry. Across those jobs, software had to contend with established organizations, contracts, and professional habits. The interesting technical question rarely arrived alone.

Then came Georgia Tech’s Advanced Technology Development Center, where he served as general manager. Running an incubator put him among founders facing unfamiliar decisions. He had already encountered enough of those decisions to be useful. His career was acquiring a second function: the accumulated experience could become someone else’s starting equipment.

His advice to younger engineers has a deliberate staircase. Learn how a large company works. Join a startup as roughly employee fifty, then another as employee five. Start your own after that. For someone whose first leap grew out of impatience, he makes a surprisingly patient case for preparation. Experience is an asset you can carry out of a job without asking the finance department to value it.

The owner gets a book

In 2012, Reddy published BIM for Building Owners and Developers: Making a Business Case for Using BIM on Projects. Building information modeling offered a way to use project data across the life of a building. His chosen reader mattered: the owner or developer, who should engage early enough for that information to influence decisions.

The title is an early marker of his current preoccupation. Much construction technology is discussed through the professional operating it. Reddy addressed the person commissioning the work. A building’s model has value beyond the screen on which someone produces it; its usefulness depends on how decisions travel through a project.

He later wrote What You Know About Startups Is Wrong, challenging eleven entrepreneurial myths, and Creating the Intangible Enterprise, focused on human skills in an AI-driven business world. Those subjects extend the same practical concern. Tools change what people can do. Organizations still have to decide what to reward, how to work together, and where the benefit lands.

“To innovate, you need a passion for solving a problem.”KP Reddy, speaking about corporate innovation, 2018

He has little patience for the decorative version of innovation. In a 2018 conversation, he pointed to companies installing fashionable offices and encouraging T-shirts while leaving their incentives intact. Risk remained punishable, success insufficiently rewarded. A change of dress code, in that account, was a rather economical substitute for a change of management.

A check should come with working knowledge

Shadow Ventures gave Reddy a place to invest in technology for the built environment. His portfolio has included companies such as ICON, which works on construction printing, and Aren, which applies technology to infrastructure assessment. He has described looking for difficult technical problems whose solution would meet an existing market, rather than relying entirely on a sales story to establish demand.

He arrived at investing with reservations about the industry he knew. He had once become thoroughly discouraged by construction technology’s reception. Later, he saw a generational change: executives who had begun working with computers were taking responsibility. The audience was changing, even where the buildings and business structures looked familiar.

His investor’s job description is unusually concrete. Help find customers. Help recruit. Help raise the next round. Understand the technology well enough to assess the solution, and the market well enough to assess the problem. He argues that operational experience belongs in that work, because founders need practical expertise alongside capital.

In 2020, he wrote that he spent two hours a day studying economic, industry, and political trends. He also described giving summer interns a voice in investment discussions. The picture is of an investor who expects to keep learning and to hear an argument from someone without the senior title. Writing a check is one action in a longer job.

Buying a place at the owner’s table

Zero RFI’s public launch in March 2026 brought a $13.8 million seed round led by General Catalyst. Its first acquisitions were Brookwood Group, BuildingWorks, and KP Reddy Co. The plan put operating businesses inside the company from the outset, joining professional services with shared technology rather than waiting for an independent software product to spread through customers’ organizations.

The name refers to requests for information, the formal questions used to resolve uncertainty during construction. Zero describes the direction of travel: coordinated project information that leaves fewer questions waiting to be answered. It is a goal for the business, rather than a reported result across its projects.

Reddy’s explanation begins with the owner’s difficulty in adopting technology. A person who commissions buildings infrequently may have little reason to master each specialist’s software. Meanwhile, the specialists produce drawings, reports, submittals, and notifications. More information can arrive without a corresponding increase in the owner’s ability to understand it.

His answer is to provide people who represent the owner, equipped with AI. Acquiring established firms supplies those people and their relationships. Technology is meant to support their work across a project’s lifecycle. The distinction carries an obligation: the service has to help the client make decisions, rather than simply generate another document for the client to review.

Less pizza, more production

There is a small, revealing correction in Reddy’s recent writing. He used to dismiss hackathons as events whose lasting output consisted of pizza boxes and empty beer cans. In April 2026, he described a mandatory internal session across Zero’s team in Atlanta, the Bay Area, and remote locations. His old joke was becoming less reliable.

The team called it a Vibe-a-thon. An earlier session had taken three days; the new one produced its work in roughly six hours. Reddy described the output as operational infrastructure intended for deployment. The comparison is his account of an internal exercise, but it gives a glimpse of how he wants his own organization to learn: put the tools into everyone’s hands and require a practical result.

That willingness to revise an opinion appears elsewhere. Asked in 2016 about an entrepreneur’s essential trait, he identified listening and adapting. At SoftWear Automation, where he was then CEO, he talked about local manufacturing and customized apparel. His interests have moved across building and making, while retaining the attraction of technology that changes a physical process.

The information has to reach someone who can act

By July 2026, Reddy was describing plans to expand through owner’s-representative firms and selectively consider specialized architecture and engineering businesses. He favored focused firms over sprawling multidisciplinary organizations. The criterion he emphasized was a better customer outcome. Combining businesses would have to offer something beyond an improved margin on the same service.

September brought a partnership with PRIVV, a capital-project management platform. The arrangement made Zero RFI’s project managers and Foundation Zero intelligence layer available within PRIVV engagements. Customers could retain their existing platform while adding people to act on the information inside it. The project record, the software, and the professional were being brought closer together.

Later that month, Reddy returned to the uneven flow of information in an essay about owner’s representatives. Better tools let contractors produce more observations, analysis, and draft questions. The recipient still has to process the output. His concern is recognizable from the teenager’s first assignment: someone must make the machine useful inside the work people actually do.

On October 19, he is scheduled to join the AEC Summit in Brooklyn, the annual gathering presented by KP Reddy Co. with Zero RFI. Owners, builders, engineers, founders, and investors will share the program. They are the constituencies he has spent a career moving among, each with a different view of the same project.

The question has become more specific over time. Can better information reach the person who needs it, early enough to change a decision? Reddy has tried answering through code, contracts, books, investments, and now acquisitions. A computer can do considerably more than it could in his father’s office. Getting the benefit to the customer remains a job for the people in the room.