IN PROGRESS / 2026 / Open-source creator operations CRM

Pangdun CreatorCRM

A LAN-first, open-source CRM that turns creator spreadsheets into a shared system for outreach, samples, costs, content, and follow-up.

ReactFastAPISQLiteWorkflow Design

Orbital system poster showing media, products, deliverables, campaigns, and contacts connected around a creator CRM core. — ANNOTATION TRANSCRIPT
One daily queue for every next step.
Link creators, samples, costs, and content.
Review legacy sheets before importing.
Roles and backups bound internal editing.
LAN-first MVP. Production hardening in progress.

ROLE

Product concept, workflow and data design, interface design, full-stack implementation, and migration tooling.

STATUS

IN PROGRESS

OUTPUT

OPEN SOURCE / GITHUB

01 / WHY

TURN SPREADSHEETS INTO FOLLOW-THROUGH.

PROBLEM

Creator lists, contacts, campaign trackers, sample logistics, costs, deliverables, and follow-up notes lived across separate spreadsheets and conversations. The records existed, but ownership, the next action, overdue work, and pending payments were difficult to see together.

SOLUTION

Pangdun Creator CRM links creators, contacts, products, projects, collaborations, shipments, costs, content, and activity into one relational workflow. A daily workbench turns dates and execution states into actionable queues, while preview-first imports, role-based access, exports, and backups keep a small internal team in control.

02 / SYSTEM

IMPORTLINKEXECUTEREVIEW

01
Preview legacy creator and execution spreadsheets, flag ambiguous fields, and confirm before writing records.
02
Normalize creators, contacts, products, projects, and collaborations into linked records instead of repeated rows.
03
Turn follow-up dates and execution states into overdue, today, seven-day, shipping, content, and payment queues.
04
Review samples, spend, content performance, and activity from each project, then export a reusable summary.

F—1

Searchable creator, media, contact, and shipping-address records with filters and duplicate review.

F—2

Projects connect products, owners, creators, and collaboration records without duplicating source data.

F—3

A daily workbench surfaces overdue work, today's follow-ups, the next seven days, shipping, content, and payment states.

F—4

Samples, costs, deliverables, performance, and activity live inside the collaboration and project context.

F—5

Preview-first Excel imports preserve the source file and route uncertain rows into a review queue.

F—6

Admin, Editor, and Viewer roles combine with LAN deployment, project exports, and SQLite backup and restore.

03 / EVIDENCE

BEFORE → BUILT → AFTER

BEFORE

Operational truth was fragmented across creator lists, campaign sheets, cost trackers, messages, and manually reconciled follow-up notes.

BUILT

A working React, FastAPI, and SQLite LAN MVP with linked records, daily queues, guarded imports, role-based editing, exports, and backup tooling.

AFTER

The current internal trial can move from imported records to follow-up queues and project review in one system. It is working software, but it is not yet production-ready.

Pangdun Creator CRM daily execution workbench — Fictional demo data shows follow-up, shipping, content, and payment queues in one workbench.

Pangdun Creator CRM linked project review — A fictional project connects creators, samples, spend, content performance, and next actions.

Pangdun Creator CRM creator and media filters — The fictional creator archive can be narrowed by country, channel, tier, and cooperation state.

LEARNING

The value of a CRM is not the number of fields it stores. It comes from making ownership, the next action, and every handoff visible without forcing the team to reconstruct context.

Add automated tests, audit trails, stronger authentication and background backups; move from a colleague-hosted SQLite setup to a dedicated internal host and PostgreSQL; and resolve the current non-commercial UI dependency before any commercial use.

SEE THE BUILD

[ GITHUB ↗ ]