---
name: ecosystem-map-crm
description: Build an ecosystem map and relationship CRM in Lovable - people, organizations, events and how they connect, with table, tabletop board and map views. Use when the user asks for an ecosystem map, stakeholder map, partner CRM, community directory or relationship tracker.
---

# Ecosystem Map & CRM for Lovable

Made by Žarko Antanasković (zarkoantanaskovic.com), based on Ecosystem Navigator, an internal tool used to map 11 countries. Free to use.

The question every screen answers: who do I know, how do I know them, and what should I do next?

## 1. Data model
- **people**: name, role, organization, city, country, email, LinkedIn, tags, last_contacted
- **organizations**: name, type (startup, investor, corporate, public, university, hub, NGO), country, website, stage, tags
- **events**: name, date, city, organizer
- **relationships**: from, to, kind (works at, invested in, met at, partner of, mentor of), strength 1-3, note
- **interactions**: person, date, channel, summary, next step, due date
Every record has an owner and a created date. Put tags in their own table, not free text.

## 2. Three views of the same data
1. **Table**: fast filters (type, country, tag, strength), sortable columns, inline edit, CSV import and export.
2. **Tabletop board**: columns for stages (Identified, Contacted, In conversation, Partner, Dormant); drag cards between them. Each card shows name, organization, last contact, next step.
3. **Map / network**: organizations as nodes grouped by country or type, lines for relationships. Click a node to open its profile.

## 3. Profile page
- Header with name, type, location, tags.
- Timeline of interactions, newest first.
- "Connected to" list from relationships.
- A single "Next step" field with a due date, shown on the dashboard.

## 4. Dashboard
- Overdue next steps, people not contacted in 90 days, new organizations this month, count by country and type.

## 5. Research workflow
- Start with a CSV: one row per organization, the columns from section 1.
- Add a "source" field to every record (link where the fact came from).
- Only store public professional information. Respect GDPR: no private data, easy delete.

## 6. Access
- Sign-in required. Each teammate sees shared records; private notes stay private.
- Never expose the map publicly unless every record is meant to be public.