At Kleiner Perkins, Ray Bradford helped build a piece of software called Dragnet. The name sounded as though it belonged to a detective with a sensible coat and little patience. Its assignment was less cinematic: gather signals from app stores, AngelList and Twitter, and help investors notice companies before those companies arrived through the usual introductions. Venture capital has a taste for the unexpected, provided someone can put it on the calendar.
Dragnet began as a side project of Bradford’s colleague Chi-Hua Chien and Chien’s brother. Bradford helped turn it into a product. That small episode offers a useful entrance to his career. He had already worked on database products at Amazon Web Services. He would go on to found Spruce Health in 2013. In between, even with an investor’s job title, he was still making software.
The sequence is easy to reduce to a polished résumé: Westminster, Stanford, Amazon, Kleiner, founder. But the interesting part sits between the names. Bradford kept moving between the people who use technology, the people who build it and the people who finance it. Each position gave him a different view of the same practical question: how does an idea become something another person can actually use?
A student president with an argument to make
Before the cloud products and investment meetings came Westminster College in Salt Lake City, now Westminster University. Bradford graduated in 2007, studied economics and finance, joined the Honors program and served as student body president. Economics supplies a vocabulary for incentives. Finance asks how resources should be allocated. Student government adds the charming complication of having to persuade actual people.
His own account of that education puts the emphasis on discussion. He credited the Honors College with improving his ability to develop ideas and stand behind them. It is a revealing choice of emphasis for someone whose later work crossed business and software. An idea can sound splendid until a person with a different set of assumptions asks the second question.
“The Honors College prepared me for both graduate school and my career by sharpening my ability to propose and defend ideas.”
Ray Bradford
Westminster’s connection to Bradford continued after graduation. He received an alumni award in 2015 and appeared in the university’s 2018 presidential inauguration program. The program described him as living in San Francisco while retaining an affection for Salt Lake City. His professional geography had changed; the place he associated with home still had a claim on him.
From Westminster he went to Stanford’s Graduate School of Business, earning his MBA in 2009. He was an Arjay Miller Scholar, and his studies also included computer science coursework. Business school and computer science make an instructive pairing. One asks whether a proposition is worth pursuing. The other makes you confront the rather less flattering question of whether it works.
The machinery behind the screen
Bradford’s early experience included internships at Linden Lab and Twitter. The companies offered different kinds of software environments: a virtual world on one hand, a public conversation network on the other. They belong to the period before his longer roles at Amazon and Kleiner. His career would soon take him toward the infrastructure underneath the applications people see.
At Amazon Web Services, Bradford led product management for database services. His work included the development of new data products, with Amazon Redshift and DynamoDB among the products associated with his early product leadership. These are the sorts of names that make a software team pay attention and leave a dinner party searching for a more promising subject.
Yet infrastructure is where a great deal of everyday convenience begins. A service can look simple because another team has absorbed the complexity beneath it. Databases concern storage, organization and access. Product management concerns what someone needs to accomplish with those capabilities. Bradford’s position put those two conversations in the same room.
He also appears as a named inventor on database patent applications. The subjects include scalable data storage and the partitioning and indexing of table data. These details give substance to the Amazon chapter: his connection to technical products extended beyond a company name on a biography. He worked in a field where the practical arrangements behind a system matter.
That background helps explain why the later Dragnet episode is interesting. Someone who had managed database products was helping an investment firm organize information into a useful tool. The setting changed, but there was still a task to perform, data to make sense of and a person waiting for a useful answer.
A venture capitalist who kept building
Bradford joined Kleiner Perkins in 2011. His investment work covered cloud computing, big data and mobile technology, with ClearStory Data and PernixData among the investments associated with him. Forbes recognized him in its 30 Under 30 coverage. The recognition came during the investment chapter of his career, before Spruce became his principal public association.
There is a familiar distinction between an investor evaluating a company and an operator trying to build one. Bradford’s time at Kleiner complicates it a little. In Chien’s account, Dragnet gathered publicly available activity into an internal system that helped identify prospective investments. App rankings and online mentions became material for a working product.
Chien credited Bradford with taking the project further: “Ray Bradford really built it into a product.” The sentence is unusually helpful because it describes a contribution rather than a title. A partner could spend the day assessing someone else’s roadmap. Here was a partner helping make the firm’s own tool usable.
The project also exposed a tension familiar to anyone who has tried to make a decision from too much information. Signals are plentiful. Attention is finite. A feed can keep refreshing long after the person watching it has ceased to learn anything. The value of a tool depends on what it helps a user notice and do next.
An editorial map of Bradford’s career, rather than a measure of company performance.
What happens between introductions
In 2012, Bradford joined a discussion in Seattle about the differences between that city and Silicon Valley. He spoke alongside investors Neil Sequeira and Bob Abbott. Having worked at Amazon and then moved into venture capital, he had experience on both sides of the comparison. His answer gave engineering talent its due.
He pointed to the depth of Seattle’s software talent, including the people working at Amazon and Microsoft. But he also described the Bay Area as an industry town, shaped by the concentration of people working in technology. His explanation concerned the conversations that happen when those people encounter one another.
“It is just in the water,” he said. His point was that repeated encounters could lead to recruiting, business relationships and new companies. In that account, proximity has a practical consequence. A city’s advantage can accumulate in the space between appointments. The coffee shop gets an unofficial job description.
This is an appealing companion to the Dragnet story. One episode involves collecting digital signals. The other concerns people exchanging ideas in person. Both address how opportunities become visible. A useful system can widen the field of view, whether it consists of software or a community in which people keep meeting.
From the investment meeting to the founder’s desk
Bradford founded Spruce in 2013 and launched its first public app in September 2014. At launch, the San Francisco company had eleven people. Kleiner backed the seed round, with Baseline Ventures and Cowboy Ventures also participating. The former partner had become a founder supported by his former firm.
The move brought together his previous positions. He had experience with product development inside a large company, then with assessing young companies from an investor’s seat. Now he was responsible for a young company’s own choices. The team had to turn its plans into a service that people could understand and use.
One early design comment shows how he approached that work. Bradford wanted the app to avoid feeling “cold or too sci-fi.” The wording is pleasantly plain. A futuristic appearance can be a poor bargain if it makes an ordinary task feel unfamiliar. The screen still has to earn the confidence of the person looking at it.
In March 2015, Spruce announced a $15 million financing round involving Kleiner, Google Ventures, Baseline and Cowboy. Its funding reached $17 million at that point. These are historical milestones, tied to the company’s early years. They mark the resources available to Bradford’s team as it expanded its work.
The product can change. The work continues.
In April 2016, Bradford introduced Care Messenger, a new Spruce communication product available on the web, iOS and Android. His launch essay described lessons learned from operating the original service and a move toward bringing conversations together. The account shows a founder revising the form of the product as the team learned what its users valued.
By 2018, Spruce was concentrating its effort on Care Messenger and ending its original direct service. Bradford and colleague David Craig each wrote about the decision. For a small team, focus meant choosing which work would continue. Product history rarely fits the tidy arrow drawn in a pitch presentation.
Bradford’s support for other founders continued through early investments in companies including Segment, Looker and Farmers Business Network. His career contains several ways of participating in a company’s beginning: developing its products, supplying capital, or taking responsibility for founding it. Those positions bring different obligations, even when they share an interest in what comes next.
Today, Spruce’s public leadership listings identify Bradford as founder and David Craig as CEO. The distinction belongs in the story because a founder’s contribution persists through changes in management. Bradford’s path remains visible in the earlier decisions: studying both business and computing, building data products, making an investment tool, and starting a company of his own.
Dragnet makes a fitting place to return. It was a modest piece of internal software with a rather theatrical name. Bradford helped make it useful. Across the more public turns of his career, that is the recurring activity worth watching: an idea acquires a form, someone tries it, and the next version has to answer to what happens.