A repeatable directory engine, populated at scale and monetised, that can be pointed at any listing market

Systems thinking and repeatability: one engine, built once, pointed at any listing market.

RoleData model, platform build, content generation, monetisation

TimelineOngoing development

StatusLive

StackDirectory platform engine

The situation

Directory content is valuable to readers and expensive to produce by hand, and the same underlying structure repeats across dozens of unrelated verticals: parks, trails, restaurants, coworking spaces. Nobody was treating that as one problem.

What I did

I designed the data model, the content generation approach and the page structure, built the base platform, populated it at global scale, and integrated advertising as the revenue model. Dog Park Explorer is the specific site; the actual product is the engine underneath it. If a reader comes away thinking this is a project about dog parks, the page has failed — the point is the machine that can produce a site like this in a fraction of the original build time.

Diagram

FIG. 01 — DOG PARK EXPLORER SYSTEM DIAGRAM, PENDING THE FINAL ASSET.

Key decisions and tradeoffs

Four decisions that shaped the engine, the alternative in each case, and what the choice cost.

Decision 01

Building a reusable engine rather than a single site

ALTERNATIVEbuild Dog Park Explorer as a one off site, which is faster to ship the first time.WHY NOTthe underlying structure, listings, locations, content generation, monetisation, repeats across dozens of unrelated verticals. Building it once as a platform means the next site is a redeployment, not a rebuild.COSTthe initial build took longer than a single purpose site would have, in exchange for every subsequent site taking a fraction of that time.

Decision 02

Content generation approach and quality control at volume

ALTERNATIVEwrite listing content by hand, which is the safest way to guarantee accuracy at small scale.WHY NOTit does not scale to a worldwide directory, and the whole premise of the engine depends on populating a market quickly.COSTcontent is generated rather than hand written, which means accuracy has to be handled through the generation process and page structure itself, not through manual review of every page.

Decision 03

Advertising as the revenue model, rather than listing fees or subscriptions

ALTERNATIVEcharge venues or listers a fee to appear, or run the directory as a paid subscription for visitors.WHY NOTlisting fees work against populating the directory at scale quickly and completely, which is the point of the engine, and a subscription does not fit a directory people expect to browse for free.COSTrevenue depends on traffic and ad rates rather than a predictable recurring fee, which is a slower, less certain way to monetise than charging up front.

Decision 04

Page structure and internal linking decisions made for search and AI visibility

ALTERNATIVEa flatter site structure with less deliberate cross linking between listings, locations and categories.WHY NOTa directory lives or dies on being findable for very specific queries, and both search engines and AI assistants rely on structure and internal links to work out what a page is actually about.COSTmore upfront design work on the information architecture, before there was any content to put into it.

Current status

Live, and built to be repeatable: the same engine can be pointed at a new listing market, such as hiking trails, vegan restaurants or coworking spaces, in a fraction of the time the original build took.

Stack and timeline

The build split into a base platform phase, a population phase to bring the directory to global scale, and an ongoing phase adding advertising and new verticals.

Directory platform engine

Next case — 04POSFlow SolutionsRead →

Have a system that half works and nobody wants to touch?

A systems review puts the situation, the cost and the options in writing.

Book a systems review Or send a direct message →