Skip to main content
Auto-memory
Retell + Twilio
MCP ecosystem
Founder Pres.
Obsidian + QMD
Review pass
Claude / Codex
Convex
75K+ sold
SwiftUI CloudKit
Next.js + Vercel
1,350+ locations
Shopify
Session notes
Founder
MCP forks
<60s response
Operator chapters
QMD retrieval
121+ skills
Six figures raised
Founder office
back to grid
Operating rolecurrent

Leading Outdoor

I built and run the deal system behind Leading Outdoor's site acquisition. It carries every location from first screen to signed lease to filed permit.

1,350+
locations tracked
25
connected databases
19
pipeline stages
Multi-market
acquisition footprint
15-year
leases signed to permit
§01The workLive system

One deal record per site, built from an empty workspace and running end to end today.

The work

A deal operating system.

Built from an empty workspace and run end to end — the CRM, outreach, lease, and permitting layer behind an LED billboard operator's site acquisition.

  • Record depthEvery site is a ~40-field due-diligence record
  • Pipeline modelA 19-stage lifecycle with a branch state for every way a deal dies
  • Screening logicPass/fail bylaw screening kills 500+ weak sites in minutes
  • AutomationFormulas, buttons, rollups, mail-merge, and AI search handle the busywork
Source of truthOne deal fileEvery site, one governed record
01Prospect
02Qualify
03Lease
04Permit
NotionScribelessDocuSignCOMMB
The workBuilt from an empty workspace and run end to end — the CRM, outreach, lease, and permitting layer behind an LED billboard operator's site acquisition.
§02The pipelineEnd-to-end flow
01

Prospect

Qualified sites enter one record with ownership, constraints, outreach context, and next action attached.

Source of truth
02

Qualify

Traffic, visibility, zoning, and ownership get checked before a site moves to proposal.

Screening layer
03

Lease

Proposal, negotiation, redlines, and signatures track against the same record.

Commercial close
04

Permit

Survey, engineering, design, and application work stays tied to the deal file until the permit package is ready.

Build readiness
§03What I builtPieces that compound

Twenty-five databases across five connected systems.

Five regimes, codified to pass/fail.

Separation distances, height caps, setbacks, and variance odds across five regimes, codified into reusable pass/fail criteria.

Sign-bylaw rules

250+ stakeholders, one record.

177 property owners plus municipal officials and legal, survey, engineering, design, and traffic partners route through one deal record.

Owners · officials · partners

Daily list, weekly email.

Over 3.5 years: a Rolling Task List, a working-session dashboard, and an auto-compiling weekly summary that keeps leadership current.

RTL · dashboard · metrics email
§04StackEvery tool earns its line
Notion / CRM · automations · dashboardsScribeless / Formula-driven mail mergeDocuSign / ContractsCOMMB / Traffic dataGeoWarehouse / Parcel & ownership dataGoogle Maps / Site qualificationMunicipal portals / Permits