Back tostdlib
Blog Post

Building in Public - Part 2

A lean, automation-first workflow turns Google Maps results into qualified coliving and coworking leads, letting a two-person team build a 120-partner network with minimal manual effort.

The core insight is that a well-designed automation pipeline can handle repetitive partner outreach while preserving the human touch for relationship building. By flagging new dive-center locations and running a nightly n8n workflow, the team pulls nearby coliving and coworking spaces from Google Maps, enriches the data, and scores each prospect with an OpenAI-powered rating based on vibe, workspace quality, amenities and proximity to dive sites.

The workflow stores results in NocoDB, filters out low-quality leads, then scrapes each venue's website for a contact email. Validated leads are queued for automated email campaigns via Brevo, with webhook tracking of delivery, opens and bounces feeding back into the database. Follow-up emails trigger after seven days, and any reply halts automation so a human can step in.

Operating on a six-node Hetzner Kubernetes cluster with S3 storage and Traefik, the stack costs about €50 per month. In the last month the system delivered over 120 qualified partners, all managed by two people, freeing them to focus on relationship quality rather than data entry.

Technical leaders can apply this pattern to any repetitive, scalable process: automate data collection, enrichment and outreach, let non-technical teammates own the workflow, and intervene only where trust and nuance matter. The result is faster validation, lower overhead and a replicable engine for growth.

Source: tidbits.mende.io
#building in public#leadership#engineering management#product development#automation#partner outreach

Problems this helps solve:

Process inefficienciesScalingCommunication

Explore more resources

Check out the full stdlib collection for more frameworks, templates, and guides to accelerate your technical leadership journey.