Where it leaks Channels Proof Why us Contact Describe the task →

← the board · case study · pillar

PROSPECTMAP PARKING LEAD ENGINE

Solar carport sales used to start with manual OSM research. PILLAR now runs on a weekly-refreshed map of large German parking lots — scored, filtered and export-ready.

  • industryRenewable energy / solar carports
  • faderAutomation
  • countryGermany
  • periodOngoing · weekly refresh
  • leakdemand

research as a system, not a spreadsheet sprint.

01 the starting point

BIG PARKING LOTS. MANUAL DISCOVERY.

PILLAR sells solar carports into large German parking assets. Finding candidates meant stitching OpenStreetMap exports, area filters and gut feel — slow, inconsistent and impossible to refresh weekly at scale.

02 what we built

A WEEKLY PARKING ENGINE WITH SCORING.

An automation pipeline ingests German parking lots, applies area and carport signals, scores priority and publishes refreshed maps the sales team can filter — on a weekly cadence.

  1. 01

    INGEST

    OpenStreetMap parking assets merged into a master dataset.

  2. 02

    FILTER & SCORE

    Keep lots from 5,000 m² up, score sales priority, flag carport potential.

  3. 03

    REFRESH

    Weekly refresh of the prospect map for the sales team.

03 results

THE MAP IN NUMBERS.

40,594Parking lots ≥5,000 m² (DE)

6,456High-priority targets (score ≥80, 13 Jul 2026 snapshot)

WeeklyRefresh cadence

prospects you can open on monday — not rebuild from scratch.

04 the footnote

SALES STARTS
WITH A MAP.

Instead of analysts rebuilding parking lists by hand, the team opens a refreshed prospect map: 40,594 large lots and 6,456 high-priority rows, ready for field planning without inventing pipeline numbers we have not measured.

measured period
Weekly refresh cadence; high-priority count from the 2026-07-13 snapshot
source
public case on grandma.agency, numbers as recorded in the account — no rounding beyond what the label says

05 who this is for

FOR B2B TEAMS SELLING ON GEO DATA.

High-ticket field sales where the first bottleneck is finding the right locations — not writing outreach yet.

  • You need a living map, not a one-off CSV dump
  • Priority scoring beats scrolling OpenStreetMap by hand

06 timeline

HOW THE MAP COMPOUNDS.

  1. Foundation

    OSM ingest, area rules and scoring model for large lots.

  2. Weekly refresh

    The master map grows to 40,594 rows with priority and carport layers.

  3. Sales use

    6,456 high-priority targets ready for field planning.

07 asked about this case

Where does the parking data come from?

OpenStreetMap parking polygons, cleaned and merged into one Germany-wide master map with weekly refreshes.

Did you measure outreach or revenue from this map?

No — this case covers the research system and map metrics only. We do not publish pipeline € we have not audited.

What makes a row high priority?

A composite priority score of 80+ on top of the 5,000 m² filter — 6,456 rows in the 13 Jul 2026 snapshot.

How often is the map refreshed?

Weekly. Sales always opens a dated snapshot, not a stale export.

08 write to us

WANT THE
SAME LEVERAGE?

If sales still searches for locations by hand, describe the criteria. We will check whether a maintained map could remove that bottleneck.

No calls, no newsletter. A reply from a person, usually within one working day. Prefer chat? Telegram · hello@grandma.agency

GrandMa in an armchair, answering on her phone
she reads everything herself.