Case Study 03. Redevelopment Lead Engine, Productized Academic Methodology
Industry: Data Products and Urban Redevelopment. Timeline: 2009.
The Problem.
An academic had spent years developing a rigorous methodology for neighborhood redevelopment. Rather than evaluating a single property in isolation, his approach analyzed a whole neighborhood, running an address against a matrix of weighted factors, things like surrounding amenities and school systems, to determine what a given property could and should become. It was genuinely valuable work. The problem was that all of it lived inside a PhD and an Access database. There was no way to put it in front of the people who needed it, and no way to turn the analysis into business.
The Solution.
This was one of the first projects I took on after leaving IBM, and I built it by turning his methodology into a working software product. I converted his analytical data out of Access and into MySQL so it could drive an application. Then I wired in open-source geocoding: a user entered an address, the system resolved it to a geographic location, matched that against his methodology and property data, and pulled the relevant characteristics and neighborhood factors.
From there, the system generated a finished report. It extracted the matched data, merged it into formatted report templates, and rendered the result as a polished PDF on the fly, one generated on demand for each address rather than pulled from a shelf of pre-built documents. In 2009 that was real work. Automated, on-demand PDF generation was well before the mature tools that make it routine today, and I built it largely by integrating open-source components rather than writing everything from scratch, which kept it fast and inexpensive to stand up.
The finished reports were the point. Each one was a lead-generation engine: a specific, valuable, neighborhood-level analysis that brought potential clients to the academic’s redevelopment services.
The Outcome.
The methodology that had been locked inside a dissertation became a functioning product that generated qualified leads for a real business. Trapped expertise became an operational system, which is the connective work I have done ever since: taking knowledge that lives in one person’s head, or one academic’s framework, and turning it into something a business can actually run on.
The strength of the underlying analysis was borne out over time. Its author went on to bring the same expertise into analytical work at a major national research firm. And for me, this project was a starting point in more ways than one. It was my first work with geocoding and my first automated document-generation system, two capabilities that would show up again and again in the years of work that followed.